RxDC reporting can feel invisible until a carrier asks for plan data or a deadline is near. For Washington employers, the safest approach is to confirm responsibilities early, document the response, and close any gaps before submission.
RxDC reporting requirements for employers call for group health plans and health insurance issuers to report prescription drug and health care spending data to federal agencies. A carrier, third-party administrator, pharmacy benefit manager, or another reporting entity may submit some or all of the files. Employers should not assume that a vendor’s submission covers every required data element. Confirm the reporting scope in writing, supply any employer-held information on time, and retain proof of submission. Because instructions can change, verify the current reporting year requirements through the official CMS RxDC resource.
This guide explains the employer’s oversight role, the parties that may submit data, and a repeatable checklist for annual preparation.
RxDC reporting requirements for employers explained
RxDC stands for Prescription Drug Data Collection. Under federal law, insurance companies and employer-based health plans must report information about prescription drugs and health care spending. Federal agencies use the combined data to better understand what drives health care costs and how prescription drug rebates affect premiums and out-of-pocket costs.
The employer’s oversight role
Many employers do not prepare every RxDC file themselves. A carrier, third-party administrator, pharmacy benefit manager, or another vendor may handle much of the reporting. That help is valuable, but it does not make employer oversight optional.
The practical employer role is to identify each reporting party, confirm what that party will submit. Provide requested plan sponsor data, and retain evidence that the work was completed. Treat RxDC as an annual compliance project rather than a one-time vendor form.
Why the details matter
One reporting entity may have claims data but lack employer-held information. Another may submit pharmacy data but not premium information. When responsibilities are split, an unassigned file or unanswered data request can create a gap.
A short written responsibility map makes the process much easier. List each plan, carrier, administrator, pharmacy vendor, reporting scope, contact, requested data, internal due date, and proof of completion. This turns an unclear compliance duty into a manageable annual workflow.
Use current federal instructions
RxDC is a federal reporting process, and technical instructions may change. Employers should use the current CMS RxDC guidance for the applicable reference year. Use vendor notices as operating instructions, but compare them with current federal resources when a responsibility or deadline is unclear.
Which employers and plans are subject to RxDC?
RxDC generally applies to group health plans and health insurance issuers. The exact reporting workflow depends on how the plan is funded and administered. Employers should confirm the status of every medical plan offered during the applicable reference year.
| Plan arrangement | Likely reporting partners | Employer’s key action |
|---|---|---|
| Fully insured | Insurance carrier and pharmacy vendor | Confirm the carrier’s scope and provide requested employer data |
| Self-funded | Third-party administrator, pharmacy benefit manager, and other vendors | Map which party submits each part and address gaps |
| Plan or vendor changed during the year | Former and current vendors | Confirm reporting for each portion of the reference year |
Fully insured plans
A carrier often submits most RxDC data for a fully insured plan. The employer may still need to answer a carrier questionnaire or supply plan sponsor details that the carrier does not hold. Ask for a clear statement of what the carrier will submit and what it needs from the employer.
Self-funded plans
Self-funded plans may have more than one reporting partner. A third-party administrator may hold medical claims data while a pharmacy benefit manager holds drug data. The employer should confirm that these submissions fit together and that no required element is left without an owner.
Special situations to review
Pay close attention after a carrier, administrator, or pharmacy vendor change. Also review mergers, plan terminations, and newly added plans. Do not rely on a broad statement such as “we handle RxDC.” Ask whether the statement covers the specific plan, reference year, and required data.
Who can submit RxDC data?
RxDC submissions may be made by health insurance issuers, group health plans, or entities that report on their behalf. In practice, employers often depend on carriers, third-party administrators, pharmacy benefit managers, and other vendors to submit data they already maintain.
Carriers and administrators
A carrier may report for its fully insured employer groups. A third-party administrator may report medical data for a self-funded plan. Each organization sets its own intake process, so employers may receive surveys, spreadsheets, portal requests, or formal attestations.
Pharmacy benefit managers
A pharmacy benefit manager may submit prescription drug information. If the pharmacy benefit manager is separate from the medical administrator, the employer should verify how the reporting parties coordinate. A response from one vendor does not prove that the other vendor’s portion is complete.
Employers and other reporting entities
An employer or another authorized entity may need to submit data when a vendor will not report a required part. Before taking on a direct submission, determine which files remain, what system access is needed, and who can verify the data.
Split reporting can work well when roles are explicit. Create one responsibility map for the full plan. It should show the submitter for each portion, the source of employer-held data, and the date that proof of filing is expected.
What should employers confirm with carriers and vendors?
Start with clear written questions. Ask who is doing the work, what plans and reporting periods are covered. Which data will be submitted, what the vendor needs from the employer, and when completion will be confirmed.
Get the scope in writing
Do not guess whether a health plan is filing for you. Ask for a written statement that identifies the files or data the vendor will submit. A clear email or letter gives your team a reliable record if responsibilities become unclear later.
Ask whether the response covers all plans and the entire reference year. If the plan changed vendors, confirm the reporting period handled by each organization. Save the response with the annual compliance record.
Find the data gaps
Some information may not be available to a carrier or administrator. A vendor may request plan sponsor data through a survey or online form. Assign someone to monitor these requests, gather the information, and have another person review it before sending.
Ask each reporting party whether another party must handle a remaining portion. When medical and pharmacy reporting are split, make sure both vendors understand their roles. Do not assume that one vendor is coordinating with the other.
Track dates and proof
Record the current federal deadline from official guidance, then set earlier internal due dates. Vendor intake cutoffs may arrive before the federal due date. Early internal dates give your team time to correct errors and resolve unanswered questions.
Ask what proof of completion the vendor will provide. Retain confirmations, the data you supplied, and related emails. Use WHIA’s employee benefits compliance calendar for Washington employers to coordinate RxDC with other annual obligations.
RxDC is only one part of an employer’s reporting picture. Review WHIA’s ACA reporting requirements for employers to keep separate federal reporting projects organized without assuming one vendor handles both.
Talk with WHIA about building a clearer reporting responsibility map for your benefits team.
An annual RxDC preparation checklist
Start early enough to resolve unclear roles and missing data. Use this checklist each year, and adjust it to match current federal instructions and vendor requests.
- Build a plan inventory. List every group health plan offered during the reference year. Note whether each plan is fully insured or self-funded, plus every carrier, administrator, and pharmacy vendor involved.
- Check current guidance. Review the official CMS RxDC resource for the applicable reporting year. Record the federal deadline and key technical changes.
- Assign each reporting responsibility. Ask each carrier or vendor what it will submit. Put every response in one responsibility map so any gaps are easy to see.
- Collect employer-held data. Complete vendor surveys and provide requested plan sponsor information before the vendor’s intake cutoff. Have a second person review figures before submission.
- Resolve gaps and overlaps. Follow up when two vendors both claim the same portion or when no party accepts a required portion.
- Confirm completion. Request written confirmation or other proof that each reporting party completed its agreed work.
- Archive the record. Save vendor notices, completed surveys, responsibility maps, correspondence, and proof of completion together.
A simple internal calendar
Set an internal kickoff well before the federal due date. Add separate dates for vendor confirmation, employer data review, gap resolution, and proof of completion. Internal dates should be earlier than external deadlines so your team has time to correct problems.
Questions for the final review
- Did every plan and reporting period receive attention?
- Did each vendor confirm its scope in writing?
- Were all employer data requests completed?
- Are any parts unassigned or duplicated?
- Is proof of completion stored with the annual compliance record?
A useful final review also checks adjacent plan administration tasks. WHIA’s open enrollment checklist for Washington employers can help benefits teams align records, vendor contacts, and internal ownership across the year.
Make the checklist reusable
Do not rebuild the process from scratch every year. Store the plan inventory, vendor contacts, responsibility map, data request log, internal calendar, and proof-of-completion list as one reusable package. At the next kickoff, copy the prior-year package, mark vendor or plan changes, and confirm whether current instructions require new information.
Assign both a primary owner and a backup. The primary owner coordinates requests and follows up with reporting parties. The backup reviews the final responsibility map and can keep the process moving during leave, turnover, or a busy enrollment period. This simple control reduces the risk that an unanswered email becomes an unassigned reporting task.
After the annual review, note what caused delays and update the checklist. If a vendor’s intake cutoff arrived earlier than expected, move the internal reminder forward. If a request required data from payroll or finance, add those teams to the kickoff list. A short retrospective makes the next reporting cycle more predictable.
How to document RxDC compliance each year
Good documentation shows what the employer asked, what each reporting party agreed to do, what information the employer supplied, and whether completion was confirmed. Keep the record organized by reference year and plan.
What to retain
- The annual plan and vendor inventory
- Written descriptions of each carrier or vendor’s reporting scope
- Completed surveys, worksheets, and data requests
- Emails resolving gaps or unusual plan events
- Submission confirmations or other proof of completion
How to handle vendor changes
A vendor change can divide a reference year between two organizations. Contact both the former and current vendor. Confirm which dates and plan data each one will report, then document any portion that the employer or another party must address.
When to ask for help
Ask for guidance when vendor answers conflict, no party accepts a reporting responsibility, or the plan arrangement changed in a way that affects data ownership. Washington Health Insurance Agency (WHIA) can help employers organize questions for their benefits partners and build a clearer annual process.
Broader compliance records may overlap with other plan obligations without being interchangeable. Use WHIA’s ERISA compliance checklist and Section 125 cafeteria plan guide as separate references when reviewing the full benefits compliance calendar.
Schedule a benefits strategy conversation with WHIA before the next reporting cycle begins.
Frequently asked questions about RxDC reporting
Does a carrier file RxDC for the employer?
A carrier often submits much of the required data for a fully insured plan, but employers should confirm the scope in writing. The carrier may still need employer-held plan sponsor information.
Can more than one vendor submit RxDC data?
Yes. Different reporting entities may submit different parts of the required data. Employers should map the full reporting scope to make sure split submissions do not leave a gap.
What should an employer keep as proof?
Keep vendor confirmations, responsibility maps, completed data requests, related correspondence, and proof that each reporting party completed its agreed work.
Where can employers find current RxDC instructions?
Use the official CMS RxDC page and its linked instructions for the applicable reporting year.
Get a clearer annual RxDC process
RxDC reporting is easier when each plan, vendor, request, and confirmation has a clear owner. Washington Health Insurance Agency (WHIA) helps Washington employers ask better benefits questions and build a more dependable compliance workflow. Employers evaluating plan structure can also review WHIA’s group health insurance requirements guide.
Call 360-464-1622 to talk with a Washington employee benefits advisor.