TL;DR: Transparency compliance now asks employers for far more than a basic filing. Annual RxDC reporting, pricing disclosures, and member-facing cost tools all depend on clean data and clear ownership. The work gets easier when your HRIS connects with plan vendors, your TPA can document its role, and your employee messaging explains what changed and why it matters.
Key Takeaways
- RxDC reporting remains the biggest annual transparency task for many group health plans, and 2025 data is due to CMS by June 1, 2026.
- Employers can assign filing work to carriers, TPAs, or PBMs, but they still keep legal responsibility for compliance.
- Manual reporting creates risk because eligibility, claims, pharmacy, and Premium data often sit in different systems.
- HRIS-connected reporting platforms can cut repetitive admin work by about 30 percent for many teams.
- Clear employee communication supports trust when more cost data and comparison features become visible.
Compliance pressure has changed shape. HR, finance, and executive leaders now face a wider set of transparency duties, and much of that work depends on data that rarely starts in one clean file.
By now, most employers know the rule set reaches beyond basic notices. It includes detailed prescription drug cost reporting, public pricing data, and member cost comparison tools. Some tasks can be delegated. The accountability cannot. The practical answer is simple: build a cleaner process with connected systems, reliable partners, and plain-English communication.
What employers actually need to report under 2025 transparency rules #
For most employers, transparency work centers on several separate obligations that touch the same plan data. RxDC reporting is the one that usually takes the most coordination, so it deserves the most attention.
This quick view keeps the duties straight:
| Requirement | What it covers | Who often helps | What the employer should confirm |
| RxDC reporting | Prescription drug spend, rebates, fees, premiums, and health care spending data | Carrier, TPA, PBM | Who files, what data is missing, and the June 1 deadline |
| Machine-readable files | Public pricing files for In-Network and allowed amounts | Carrier or TPA | Whether hosting and updates are contractually assigned |
| No gag clause compliance | Confirmation that vendor contracts do not block access to cost and quality data | Legal, broker, TPA | Annual review and attestation support |
| Cost comparison tools | Member-facing tools for comparing out-of-pocket costs | Carrier or administrator | Tool availability, accuracy, and employee awareness |
CMS requires RxDC reporting each year for employer-sponsored group health plans, whether the plan is fully insured or Self-Funded. The report covers the prior calendar year. As of April 2026, the framework has not changed from the stabilized rules used after earlier simplifications. That means 2025 data is due June 1, 2026.
Employers often rely on outside partners for the filing itself. Self-Funded plans may need data from a TPA, a PBM, and internal payroll or enrollment systems. Fully insured plans may have more carrier support, but Premium data and carve-out details can still come back to the employer. Broader CAA broker transparency rules add another layer by pushing employers to document who is paid, who is responsible, and what services are actually being delivered.
RxDC reporting is more than a one-time file upload #
RxDC looks simple from a distance. In practice, it pulls together data from several places that do not always line up.
The report may need medical spend from one vendor, drug rebates from another, Premium data from finance, and enrollment counts from your HRIS. If your PBM is carved out, that adds another handoff. If your TPA uses different eligibility snapshots than payroll, the numbers can drift.
That is where the work piles up. Teams chase missing fields, compare file layouts, fix duplicate member records, and confirm whether monthly Premium figures match the method CMS expects. Timing also causes trouble. One vendor may send its file in February, while another sends a survey in April. By then, HR may already be busy with other annual deadlines.
A clean submission usually depends on strong data discipline long before June 1.
Delegating the work does not remove employer responsibility #
Plans can hand off tasks. They cannot hand off accountability.
That point matters most for Self-Funded employers. A TPA may submit the file. A PBM may provide drug data. A carrier may help with a piece of the process. Still, the plan sponsor remains responsible if the reporting is late, incomplete, or wrong.
A better approach is written responsibility mapping. Your contracts should say who gathers each data element, who validates it, who files, and who keeps proof of submission. In addition, keep one internal owner who tracks the calendar, the vendors, and the open questions.
You can delegate filing work, but you still need proof that it got done correctly.
That discipline also supports related duties, from no gag clause reviews to plan disclosures. Employers that want stronger control often build this into a broader proactive compliance guidance process, so deadlines stop feeling like surprises.
Why manual reporting breaks down for HR and finance teams #
Manual compliance often starts with a spreadsheet and ends with a scramble.
The problem is not effort. Most HR and finance teams work hard. The problem is fragmentation. Eligibility sits in one system. Spend data sits with claims vendors. Pharmacy details sit with the PBM. Premium contributions may live in payroll or accounting. When each file arrives in a different format, someone has to stitch the story together by hand.
That approach creates extra work and extra risk. One tab changes, another tab breaks, and no one notices until the numbers fail validation. A long-Term strategy works better when data creates clarity and supports decisions, rather than adding another stack of comparisons that nobody trusts.
The biggest time drains are collecting, cleaning, and validating data #
Most of the work happens before submission day.
Teams pull eligibility files, compare covered lives, review Premium totals, chase Rebate amounts, and confirm service categories. Then they reformat everything to fit a vendor portal or reporting template. After that, they correct errors and repeat the review.
For lean departments, this is where the burden lands hardest. HR may own enrollment data but not claims. Finance may know the spend totals but not the plan detail behind them. If nobody has dedicated reporting support, the same people who manage Open Enrollment and payroll deductions also become the cleanup crew for compliance.
That is why automation matters. When reporting data connects earlier, many employers can reduce manual workload by about 30 percent, and sometimes more. The gain usually comes from fewer hand-built files, fewer duplicate checks, and fewer last-minute corrections.
Compliance risk grows when no one owns the full process #
Gaps appear when everyone owns a piece of the work and no one owns the whole result.
One team may assume the PBM sends Rebate data. Another may think the TPA validates eligibility. Finance may expect HR to confirm Premium amounts. Meanwhile, the deadline moves closer.
A single compliance workflow helps prevent that drift. Keep one shared calendar. Set internal deadlines well ahead of vendor deadlines. Name one accountable lead, even if several departments contribute. Then document every handoff.
A practical calendar also helps teams line up RxDC with other recurring obligations. This kind of group health compliance calendar makes the annual cycle easier to manage because it gives HR, finance, and leadership the same view of what is due and when.
How HRIS-connected tools make transparency reporting easier #
Connected systems do more than save time. They reduce avoidable confusion.
When your HRIS feeds current eligibility and plan data into a reporting platform, you remove many of the manual touchpoints that create errors. Vendor feeds can pull in claims, pharmacy, and Premium inputs on a set schedule. Standard file formats cut down on rework. Validation rules catch missing fields before a deadline does.
This is where a human-centered compliance strategy helps. The goal is not more data. The goal is better knowledge, clearer decisions, and fewer surprises.
What automation helps with most in the RxDC process #
Automation helps most with the repetitive parts of reporting.
It can aggregate data from multiple vendors, accept API connections or scheduled file feeds, and flag gaps before a submission is due. Many platforms also track versions, store prior-year filings, and create an audit trail that shows who changed what and when. That matters when you need to prove how a number was built.
Deadline reminders also help. So does having one place to review the full reporting package before it goes out. When those tasks happen inside a shared workflow, teams spend less time hunting files and more time checking accuracy.
For many employers, that shift cuts manual admin work by roughly 30 percent. The savings come from fewer duplicate tasks, less formatting work, and better control over version history.
What to look for before choosing a reporting platform #
Start with compatibility. If the platform does not connect well with your HRIS, payroll, TPA, and PBM, your team will still do too much manual cleanup. Next, look at reporting support. Some systems collect data well but provide weak help when a vendor file comes in late or incomplete.
Audit readiness matters too. You want clear submission records, stored source files, and visible approval steps. Data security is part of the same discussion because these files contain sensitive plan and enrollment details. Ease of use also matters more than many leaders expect. If the platform is hard to manage, people create side spreadsheets and email chains, which puts the risk right back into the process.
The best choice supports compliance now and stronger decision-making later. That is where the real ROR, Return on Relationship, starts to show. Clean data can help with Plan Design, cost review, and vendor oversight long after the report is filed.
Strong vendor partnerships and clear employee communication complete the strategy #
Good systems help, but they are only part of the answer.
Transparency rules depend on people as much as data. Employers need vendors that can document their role and stand behind their work. At the same time, employees need plain language about what these changes mean for their care and costs. Compliance works better when both sides are covered.
How to evaluate whether a TPA is truly ready for transparency compliance #
A strong TPA brings predictability. A weak one creates more questions than answers.
Ask whether the TPA has direct experience with RxDC submissions and whether it can explain the timeline in plain terms. Request written confirmation of who gathers each data element, who submits the report, and what the employer still needs to provide. Review how the TPA handles Rebate and fee data, especially when a separate PBM is involved.
You should also ask how the TPA shares files, how it flags missing information, and what proof it keeps after filing. A partner that is ready for transparency compliance should welcome these questions. Clear answers show control. Vague answers usually mean more work for your team later.
Simple employee messaging builds trust when cost data becomes more visible #
Transparency rules do not stop with regulators. They shape the employee experience too.
When plans offer price comparison features or member cost tools, employees need to know they exist. More importantly, they need to understand how to use them. A short email, a benefits FAQ, and a few Open Enrollment examples can go a long way. Managers and HR staff should also know where to point people for help.
This matters because cost data without context can create confusion. Plain-English communication gives employees a better sense of what they may owe, where to look for options, and why the employer is sharing more cost information. That supports trust. It also reflects a better standard for benefits leadership, one that connects reporting duties to the people who use the plan.
Compliance is easier when the work is clear, the data is connected, and the message makes sense to employees.
The smartest employers treat transparency as an operating discipline, not a once-a-year fire drill. They understand the rules, reduce manual work with HRIS-connected systems, and choose partners that can document accountability.
That approach improves more than filing accuracy. It builds efficiency, stronger oversight, and greater employee confidence over time.
