If your company missed a carrier RxDC survey or cannot confirm that your vendor filed the full report, start by finding out exactly what was submitted and what was left out. The biggest risk is not always that nothing was filed. It is that the carrier, TPA, or PBM filed the data it had, while employer contribution data or plan list information remained the employer's responsibility.
RxDC is not a benefits marketing task. It is a federal reporting requirement tied to prescription drug and health care spending transparency. Employers should treat a missed survey or missing confirmation as a compliance issue, then work with their broker, carrier, TPA, PBM, or counsel to correct the record as quickly as possible.
What RxDC reporting is
RxDC stands for Prescription Drug Data Collection. Under Section 204 of the Consolidated Appropriations Act, 2021, insurance companies and employer based health plans must submit information about prescription drugs and health care spending. CMS collects the report on behalf of HHS, the Department of Labor, the Department of the Treasury, and the Office of Personnel Management.
The report is broader than prescription drugs. CMS says RxDC collects information about spending on health care services, premiums paid by members and employers, drugs with the highest spending, drugs prescribed most often, drug manufacturer rebates, and cost sharing paid by patients.
That is why RxDC often reaches across several parties. A carrier may have claims data. A PBM may have pharmacy and rebate data. The employer may have contribution and enrollment information that vendors do not keep in the same form.
Why a missed carrier survey matters
Many employers think RxDC is handled entirely by the carrier. That is sometimes true for fully insured plans, but it should still be confirmed in writing.
The common failure point is the carrier or TPA survey. Vendors often request employer data before their own internal cutoff. If the employer misses that cutoff, the vendor may still file the information it has, but not the employer specific data it never received.
Two files are especially important:
D1 premium and life years
The D1 file includes premium and life year information. In practice, this is where average monthly premiums and employer versus employee contribution amounts can become a problem. A carrier or TPA may not know the employer's payroll deduction structure, contribution tiers, or monthly employer share unless the employer provides it.
P2 group health plan list
The P2 file identifies group health plans included in the filing. If an employer has multiple plan options, changed carriers, or moved between fully insured, level funded, and self funded arrangements during the reference year, the plan list needs careful review.
The practical issue is simple: a partial vendor filing can leave the employer with a missing piece. The employer needs to know whether the missing piece exists before deciding what to do next.
What to check first after the deadline
Start with confirmation, not panic. The question is not "Did somebody file something?" The question is "Which files were submitted for which plan, by which entity, for which reference year?"
Ask each vendor for:
- The reference year covered
- The filing entity name
- The files submitted, including whether D1 and P2 were included
- Any files or fields excluded because employer data was not received
- The submission date
- A confirmation number or other proof of submission, if available
If the vendor cannot answer those questions, escalate through the broker or account team. Employers should not rely on a general statement such as "RxDC was handled" if the missing data question remains open.
Fully insured, level funded, and self funded plans are not the same
The recovery path depends on the funding arrangement.
Fully insured plans
For many fully insured groups, the carrier takes the lead because it holds the claims and prescription drug data. The employer may still need to provide premium contribution information through a carrier survey. If the survey was missed, ask whether the carrier filed without that information and whether any employer filing is now required.
Level funded plans
Level funded plans can create more confusion because they often feel like a packaged carrier product but may rely on TPA, stop loss, PBM, and employer data. Confirm which party filed each component. Do not assume the monthly invoice equals the data needed for D1 reporting.
Self funded plans
Self funded employers usually need tighter coordination among the TPA, PBM, stop loss carrier, consultant, and internal finance team. The employer is still the plan sponsor, even when vendors prepare parts of the filing. This is another reason to keep written proof of each vendor's responsibility.
What data employers may need to pull
If D1 or P2 data is missing, the employer may need records from payroll, enrollment, carrier billing, and plan documents.
Useful records include:
- Monthly enrollment by plan option and tier
- Employer contribution amounts by tier
- Employee payroll deductions by tier
- COBRA or retiree coverage treatment, if applicable
- Carrier or TPA account numbers
- Legal plan name and plan sponsor information
- Plan year and policy year dates
For contribution data, do not use one month as a shortcut unless a qualified adviser confirms that is appropriate for the filing facts. Midyear renewal changes, employee class changes, and contribution changes can make a single month inaccurate.
What not to do
Do not submit a duplicate filing without checking what vendors already filed. Duplicate or inconsistent data can create its own cleanup problem.
Do not assume the carrier survey deadline was the federal deadline. Vendor cutoffs often come earlier so the vendor has time to prepare its own submission.
Do not rely on verbal confirmation. Ask for email confirmation or a formal vendor note that identifies the reference year and filing scope.
Do not treat RxDC as only a pharmacy issue. CMS states that the report includes health care spending and premiums as well as prescription drug data.
How to document the recovery file
Create a simple internal record with:
- The plan names and reference year
- Vendor contacts and responsibility assignments
- Dates each vendor was contacted
- Vendor responses and submission proof
- Data sent by the employer
- Any unresolved files or fields
- Counsel, broker, or consultant guidance received
This file matters because RxDC is annual. Even if the immediate issue is corrected, the same vendor handoff can fail again next year unless someone documents where it broke.
How to prevent the same problem next year
Add RxDC to the annual benefits compliance calendar before the vendor surveys arrive. The Department of Labor RxDC resource page is a useful official reference point for employer and service provider responsibilities.
A practical calendar should include:
- January: confirm all carriers, TPAs, PBMs, and plan changes for the prior calendar year
- February: assign one internal owner for vendor surveys
- March: gather employer and employee contribution data
- April: complete vendor questionnaires before internal cutoffs
- May: request written filing confirmation before the federal deadline
- June: store submission proof and unresolved notes
The point is not to build a large compliance process. It is to stop RxDC from becoming a surprise email that arrives while HR is already handling renewals, open enrollment planning, leave questions, and payroll issues.
Where Benefitra can help employers think through related risks
RxDC often exposes the same operational issue that shows up in other benefits projects: no single person owns the handoff between HR, finance, payroll, the broker, the carrier, and the TPA.
If your team is also reviewing funding strategy, read Benefitra's guide to self funded plan compliance responsibilities.
If vendor sprawl is part of the problem, Benefitra's article on benefits administration technology for growing employers can help frame the operational side.
For employers trying to control pharmacy costs, the GLP 1 cost article gives a separate look at why prescription drug data matters to plan strategy.
FAQ
What happens if an employer missed RxDC reporting?
The employer should first confirm what was already submitted by the carrier, TPA, PBM, or other reporting vendor. If required data was not filed, the employer should work with its broker, vendor, or legal adviser on correction steps. Do not assume no action is needed just because one vendor filed part of the report.
Is RxDC reporting only for prescription drugs?
No. CMS says RxDC includes prescription drug data, health care spending, premiums paid by members and employers, patient cost sharing, and prescription drug rebates.
Can an employer rely on its carrier for RxDC reporting?
Sometimes, but the employer should get written confirmation. Fully insured carriers often file much of the data, but they may still need employer contribution information. Self funded and level funded plans often involve more than one vendor.
What are D1 and P2 in RxDC reporting?
D1 is a data file that includes premium and life year information. P2 is the group health plan list. These files matter when the employer has to provide plan and contribution information that a carrier, TPA, or PBM may not have.
Does RxDC apply to ICHRAs, HRAs, health FSAs, or dental and vision plans?
Carrier and compliance summaries commonly state that RxDC does not apply to health FSAs, HRAs, ICHRAs, excepted benefits such as standalone dental or vision, fixed indemnity insurance, or retiree only plans. Employers should confirm their own arrangement before relying on that general rule.
When is RxDC reporting due?
RxDC reports are generally due annually by June 1 for the prior calendar year. For example, reporting for the 2025 reference year was due June 1, 2026.