The Federal Independent Dispute Resolution (IDR) Operations final rule reshapes how payers, providers, and certified IDR entities move disputes through the No Surprises Act process. Its changes phase in on a staggered timeline over the coming year, with the largest procedural updates tied to the forthcoming IDR Gateway portal. But three IDR provisions attach directly to the rule’s August 3, 2026 effective date — and parties should prepare to square them away now.
At FHAS, our role as a certified IDR entity is to help parties understand each wave of change so disputes submitted to the IDR process can proceed smoothly to a merit-based decision. Here’s what becomes applicable on August 3 and what it means for your submissions.
1. The bundled payment arrangement definition becomes applicable
The final rule codifies a formal definition of a bundled payment arrangement. A bundled payment is an instance in which a plan or issuer pays a provider, facility, or air ambulance provider a single payment for multiple items or services furnished during an episode of care to a single patient. Beginning August 3, that definition is part of the operative regulatory text.
The EOB must contain the following information to qualify as a bundled dispute:
- A DRG Code (Diagnosis Related Group Code) is assigned by the insurer and appears on the EOB.
- One service on the claim received the payment for all other services. In this instance the dispute should be initiated with the bundled code as the main service and the remaining services on the claim as component codes.
Why it matters: A clear, shared definition removes a longstanding cause of guesswork about how bundled services should be characterized when a dispute is initiated. It also sets the foundation for how bundled items will be handled as the broader process mechanics — including the coordinated treatment of batched and bundled items — come online with the IDR Gateway. Parties preparing bundled disputes should align their internal coding and documentation with the finalized definition now, so submissions are consistent from day one.
2. QPA disclosure changes apply to disclosures required on or after August 3
The qualifying payment amount (QPA) sits at the center of nearly every payment dispute, and the information exchanged when a payer sends an initial payment or a notice of denial drives whether — and how — a dispute proceeds. Under the final rule, the modified QPA disclosure requirements apply after August 3, 2026. However, some disclosure requirements are dependent on future guidance and the new portal technology.
Under the final rule, payers must include additional identifying information alongside the QPA at the initial payment or denial stage: the plan or issuer’s legal business name, the plan sponsor’s legal business name where applicable, and once released or made available with the new portal technology and guidance still pending, the payer’s IDR registration number, and a clear statement about how a provider initiates open negotiation. (The standardized CARC and RARC remittance codes that travel alongside these disclosures follow their own implementation track under separate guidance.)
Why it matters: Better information up front means fewer disputes derailed by missing data and fewer ineligible filings reaching IDR. As August 3 approaches, providers should know what to expect in these notices, and prepare to incorporate this information into their workflows. Payers should confirm that their remittance and disclosure workflows can accurately capture and routinely communicate every required element before the date arrives.
3. Certified IDR entity fee provisions apply to disputes initiated on or after August 3
The rule’s fee framework has two moving parts. The administrative fee — the non-refundable fee both parties pay to participate — dropped to a flat $15 per party, per dispute, and that change has been in effect since June 11, 2026. Separately, the rule finalizes procedures governing the certified IDR entity fee (the fee the IDRE charges to make a determination), and those provisions apply to disputes initiated on or after August 3.
A key point codified in the rule: if either party fails to pay the administrative fee or the certified IDR entity fee by the time its offer is due, that party’s offer will not be considered received — and the party remains responsible for the fees. In short, timely payment is now tied directly to whether your offer counts. FHAS already follows this rule, but parties can check if this marks a change for other IDREs.
Why it matters: The message here is operational. Make sure your accounts-payable process can pay both fees on time, every time. A missed or late payment can impact the outcome of the dispute.
What to do before August 3
- Prepare to update disclosure templates and workflows so QPA notices carry the newly required identifiers and the open-negotiation statement. Monitor for CARC and RARC guidance and the IDR registry instructions that are expected with the portal’s release.
- Align bundled-service coding and documentation with the finalized bundled payment arrangement definition.
- Confirm fee-payment readiness so administrative and certified IDR entity fees clear before offers are due.
These three changes are the first checkpoint in a rollout that continues through 2026 and into 2027 as the IDR Gateway, expanded batching, the payer registry, and other procedural updates come online. Getting the August 3 items right builds the discipline the rest of the rule will demand. For the Departments’ own summary of applicability dates, see the CMS fact sheet.
Need help? Let FHAS be your guide
Have questions about how the August 3 changes affect your submissions? FHAS is here to help parties understand the final rule, meet the new timeframes, and arrive at IDR ready for a merit-based decision. Contact us to schedule a consultation with our team.
Legal Disclaimer
The information contained in this content piece is for general informational purposes only. While we strive to ensure the accuracy and completeness of the information presented, we make no representations or warranties of any kind, express or implied, about the accuracy, reliability, suitability, or availability with respect to the content or the information, products, services, or related graphics contained in the content piece for any purpose. Any reliance you place on such information is therefore strictly at your own risk. The content of this page is subject to change without notice. The information provided in this document does not constitute legal or other professional advice, and is non-binding upon FHAS and any federal government agencies.

