If your team has been living inside monthly machine-readable file uploads and arguing with vendors about whether anyone can actually use the data, the tri-agency Transparency in Coverage final rule published October 6, 2026 (91 FR 63748) is your new roadmap. The Departments of the Treasury (IRS), Labor (EBSA), and Health and Human Services jointly amended the PHS Act, ERISA, and Code rules for non-grandfathered group health plans and issuers — with a few No Surprises Act crossovers that even grandfathered plans should notice.

The regulatory effective date is December 7, 2026. Most operational changes hit on staggered clocks tied to publication and to plan years beginning on or after January 1, 2027. That timing overlaps open enrollment prep for calendar-year groups, which is why we are flagging it now rather than in December.

Two buckets: participant tools vs. public files

Think of Transparency in Coverage as two related programs:

  1. Participant-facing cost-sharing information — the internet (and paper) tool requirements in 26 CFR 54.9815-2715A-2 and parallel DOL/HHS sections.
  2. Public machine-readable files (MRFs) — in-network negotiated rates, out-of-network allowed amounts, and related disclosures under 26 CFR 54.9815-2715A-3.

The final rule touches both. It is explicitly aimed at making public pricing data more standardized, accurate, and findable, while acknowledging that the original monthly MRF cadence created enormous files with limited practical value.

Participant tools: add phone, and a No Surprises Act shortcut

For plan years (policy years) beginning on or after January 1, 2027, the final rule requires that the cost-sharing information already made available through the online consumer tool and on paper upon request also be available by phone upon request.

That phone channel matters for section 114 of the No Surprises Act (the price-comparison tool mandate). The preamble states that satisfying the amended Transparency in Coverage tool requirements also satisfies those No Surprises Act obligations — including for grandfathered group health plans that are not otherwise covered by the rest of this final rule. If you still have a grandfathered medical plan, check whether your carrier’s phone line and web tool actually deliver the same content; “we have a nurse line” is not the same thing.

Until the January 1, 2027 plan year, plans and issuers keep following the April/July/October 2025 versions of the current A-2 rules cited in the Federal Register.

Machine-readable files: quarterly updates, network-level reporting, attestations

For MRFs, the Departments did not adopt the proposed 12-month delay. Instead they finalized a phased rollout measured from publication (October 6, 2026):

| Phase | When it applies | Examples of what lands | | --- | --- | --- | | Phase 1 | 5 months after Federal Register publication | Quarterly (not monthly) reporting cadence; network-level in-network rate reporting; product type and HIOS identifiers; allowed-amount file changes (market-type aggregation, longer reporting period, lower claims threshold); dropping “unlikely” provider/service combinations; single file format | | Phase 2 | 11 months after publication | Taxonomy and Utilization contextual files; Text File with contact/location metadata; homepage footer link (“Price Transparency” or “Transparency in Coverage”) routing to the MRF landing page |

Five months after an October 6 publication is early March 2027; eleven months lands in early September 2027. During the overlap, vendors may be building Phase 2 deliverables while you are already posting Phase 1 files — budget project management time, not just developer hours.

CEO attestation encoded in the files

Starting with the applicability dates in 54.9815-2715A-3(c), each required MRF must include an attestation that, to the plan’s or issuer’s knowledge and belief, the file meets the technical requirements and is true, accurate, and complete as of the file date. Plans and issuers must also encode the name of the chief executive officer, president, or other senior official designated to oversee accurate encoding — modeled on hospital price transparency attestations.

TPAs can attest on behalf of a plan under a written agreement, but someone with authority still owns the accuracy story. This is a governance shift, not a checkbox for IT.

Prescription drug file — still on the horizon

The final rule continues work on a dedicated Prescription Drug File schema (development targeted for late 2026 with publication expectations in the December 2027 timeframe in agency summaries). Do not conflate that long-lead item with the Phase 1/2 MRF dates above; Rx reporting has its own timeline.

Who is on the hook?

Self-insured ERISA plans and their administrators share compliance responsibility with any issuer for insured business. Fully insured employers should not assume “the carrier handles it” without contract review — footer links, attestation naming, and file accuracy ultimately affect the employer’s brand and fiduciary oversight.

These rules do not replace your FSA, HSA, HRA, COBRA, or cafeteria-plan duties, but they sit on the same compliance calendar as Medicare Part D creditable coverage notices (due before October 15 for many calendar-year sponsors) and January 1 ICHRA notices for employers still onboarding reimbursement arrangements.

What employers should do this week

  1. Pull your vendor roadmap. Ask TPA, carrier, and MRF vendor for written Phase 1 and Phase 2 dates mapped to your plan year — especially if you have a non-calendar plan year starting mid-2027.
  2. Assign an attestation owner. Decide which officer will be named in MRF metadata and whether your TPA attests under contract. Legal and finance should be in that conversation early.
  3. Test the phone pathway for 2027. For grandfathered and non-grandfathered plans alike, confirm how participants will request the same cost-sharing detail available online — and document the number in SPDs and open-enrollment guides if needed.
  4. Plan for quarterly MRF operations. Finance and procurement teams used to monthly refresh cycles should rebaseline staffing and validation checks for a quarterly cadence with heavier upfront validation (the preamble cites extra QA time as a benefit of the slower schedule).
  5. Keep proof. Maintain publication logs, attestation records, and footer-link screenshots the same way you keep COBRA notice logs — DOL’s enforcement bandwidth is a separate debate, but employer due diligence is not.

Transparency in Coverage was never a “set and forget” FTP upload. This final rule makes that explicit with attestations, findability requirements, and phased technical standards. Treat it like any other 2027 plan-design project: name an owner, lock vendor dates, and do not wait until March to discover your files still reflect 2025 schemas.