Federal IDR Operations Rule: An Accounting Firm Guide

A new federal rule governing the No Surprises Act dispute-resolution process is now final, and accounting firms whose clients include group health plans, health insurance issuers, and the providers who bill them have a fixed date to plan around. The Federal Independent Dispute Resolution Operations rule, published at 91 FR 33900, was issued June 4, 2026 and is effective August 3, 2026. For firms that handle billing reconciliation, remittance posting, fee accounting, and revenue-cycle advisory work, the changes touch the documents and codes that flow through ledgers every day.

This guide explains, in plain English, what the rule changes, who is affected, and what covered firms must do to operationalize the newly required workflow before the effective date. It leads with the obligation and the deadline, not with software. The point-in-time index behind this post is a snapshot of 128 U.S. federal rules published January 1, 2026 – June 20, 2026 by 9 agencies governing the industries we cover, so the facts below are bounded and verifiable.

Key Takeaways

• The Federal IDR Operations rule, cited as 91 FR 33900, is final and effective August 3, 2026.

• The rule finalizes disclosure requirements that plans and issuers must include with the initial payment or notice of denial for items and services protected by the surprise-billing rules.

• Plans and issuers must communicate certain information using claim adjustment reason codes (CARCs) and remittance advice remark codes (RARCs) when sending paper or electronic remittance advice to entities that lack a contractual relationship with the plan or issuer.

• The rule amends the open-negotiation period, the initiation and eligibility review of the Federal IDR process, the handling of administrative and certified IDR entity fees, and adds a requirement that plans and issuers register in the Federal IDR portal.

• This is informational only and not legal or tax advice; the regulation directs covered entities, and firms should confirm scope with counsel.

What the rule is and where it comes from

The No Surprises Act, enacted as part of the Consolidated Appropriations Act, 2021, created a Federal independent dispute resolution (IDR) process so that out-of-network payment disputes for certain protected items and services can be resolved without billing the patient. The new rule finalizes a set of operational requirements for that process. Because it was issued jointly across several agencies, it carries multiple Regulatory Identifier Numbers — 0938-AV15, 1210-AC17, 1545-BQ55, and 3206-AO48 — and amends rules in several titles of the Code of Federal Regulations at once.

According to the Federal Register notice at 91 FR 33900, the rule reaches into 5 CFR Part 890, 26 CFR Part 54, 29 CFR Part 2590, and 45 CFR Part 149. That breadth is the practical headline for accounting professionals: a single rule can change how remittance information is coded and disclosed across health-plan, tax, labor, and public-welfare frameworks simultaneously, which means a change that looks like a coding tweak in one client's system may have a regulatory basis spread across four parts of the CFR.

The rule abstract describes the core of the change. It finalizes new requirements for the disclosure of information that group health plans and health insurance issuers offering group or individual coverage must include along with the initial payment or the notice of denial of payment for certain items and services subject to the surprise-billing protections. It also requires plans and issuers to communicate information using claim adjustment reason codes and remittance advice remark codes, as specified in guidance, when providing any paper or electronic remittance advice to an entity that does not have a contractual relationship with the plan or issuer.

What the rule requires

The table below summarizes the principal obligations the regulation directs, paraphrased from the rule abstract. It is a reading aid, not a substitute for the regulation text or professional advice.

Two of these deserve emphasis for accounting teams. First, the coding requirement: CARCs and RARCs are the standardized reason codes that explain, line by line, why a claim was paid, adjusted, or denied. When those codes are required on remittance advice sent to a non-contracted entity, the data that lands in a client's accounts-receivable system becomes more structured and more consequential, because mis-posted or missing codes can distort what a firm reconciles. Second, the portal-registration provision: plans and issuers must register in the Federal IDR portal, which is an administrative step a firm's clients may ask about as they prepare for the date in the source notice at 91 FR 33900.

Who is affected

The rule speaks to plans and issuers, but the operational ripple reaches the accounting and advisory professionals who serve them. The table below maps the audiences most likely to feel the change.

The takeaway is that "covered entity" in the rule does not equal "the only party affected." A firm that never files an IDR dispute itself can still see its workpapers change because the remittance data it relies on is now governed by finalized federal requirements. Every paragraph in this guide that states an obligation is tied back to the primary notice for that reason; the controlling text lives at 91 FR 33900 on the federalregister.gov site.

What covered firms must do before the date

The rule requires that the affected disclosures, codes, fee handling, and portal registration be in place under the finalized framework as it takes effect August 3, 2026. For an accounting firm supporting plans, issuers, or providers, a sensible reading-and-readiness sequence looks like this:

• Read the source first. Start with the Federal Register notice itself at 91 FR 33900 and the current regulatory text through the eCFR for the relevant CFR parts. Do not rely on summaries alone for client-facing conclusions.

• Confirm scope per client. Determine which of your clients are plans or issuers directly subject to the rule and which are providers on the receiving end of newly coded remittance advice.

• Inventory affected data flows. Identify where CARCs and RARCs already enter the books and where disclosures accompanying initial payment or denial are captured, so you know what changes when the finalized requirements apply.

• Update reconciliation controls. Map new or changed reason codes to general-ledger treatment and to any exception queues your firm maintains for unmatched or disputed amounts.

• Track fee accounting. Because the rule amends administrative and certified IDR entity fees, confirm how those fees are recorded and substantiated for clients that participate in the process.

• Document the basis. Keep a short memo tying each operational change to the source citation and CFR part, so the workpaper trail is defensible.

None of these steps require legal conclusions to begin; they are operational readiness moves. Where a client needs a definitive interpretation, that is a question for a qualified attorney or tax advisor, not for an accounting checklist.

Operationalizing the change at volume

Reading one rule is manageable. The harder problem for a multi-client firm is catching the next one — and the one after that — without a partner personally refreshing the Federal Register every morning. This is where a monitoring layer earns its keep. US Tech Automations can configure an agent that watches the federal-rulemaking feed continuously, so that when a document like the Federal IDR Operations rule is published, the pipeline can extract the citation, agency, RINs, and effective date, then route a structured alert to the reviewer responsible for the affected client portfolio. The workflow is meant to surface the obligation, not to interpret it; a human reviewer still owns every compliance conclusion.

In practice, the value is in the routing and the flagging. A monitoring workflow can be set to trigger on rules touching the CFR parts a firm cares about — for the rule discussed here, 5 CFR Part 890, 26 CFR Part 54, 29 CFR Part 2590, and 45 CFR Part 149 — and then escalate a flagged item into a tracked review queue with the primary-source link attached. US Tech Automations builds that intake-and-route layer so a reviewer sees a single, deduplicated entry with the citation and the deadline already parsed, rather than a raw feed. The goal is to integrate rule-watching into the firm's existing review rhythm so a covered change cannot quietly slip past the date it becomes effective. Again, the regulation governs; the workflow simply makes sure the right person reads it in time.

How accounting workpapers may change

Even without taking on IDR cases, a firm's day-to-day records can shift. The disclosure-with-payment requirement means more structured information arrives alongside remittances, and the CARC/RARC requirement means the reasons behind adjustments are expressed in standardized codes on advice sent to non-contracted entities. For reconciliation, that is generally a help: standardized codes are easier to map than free-text explanations. But the transition period is where errors hide, because an old code mapping applied to a newly required code set can silently misclassify an adjustment.

A short, disciplined crosswalk — current code, new or changed treatment, and the general-ledger account it touches — is the kind of artifact that keeps a transition clean. Pair it with the source memo described earlier, and a firm has both the operational map and the evidentiary basis in one place, anchored to the notice at 91 FR 33900.

Frequently asked questions

What is the Federal Independent Dispute Resolution Operations rule?

It is a final rule that sets operational requirements for the No Surprises Act's Federal independent dispute resolution process. Per the notice at 91 FR 33900, it finalizes disclosure requirements tied to initial payment or denial, requires the use of CARCs and RARCs on certain remittance advice, amends the open-negotiation period and IDR initiation and eligibility steps, addresses administrative and certified IDR entity fees, defines bundled payment arrangements, amends batching and timeframe-extension rules, and requires plans and issuers to register in the Federal IDR portal.

When does the rule take effect?

The rule is effective August 3, 2026. It was published June 4, 2026. Both dates come from the Federal Register notice at 91 FR 33900.

Which Code of Federal Regulations parts does it amend?

The rule reaches 5 CFR Part 890, 26 CFR Part 54, 29 CFR Part 2590, and 45 CFR Part 149, according to 91 FR 33900. Current regulatory text for those parts is available through the eCFR.

Does this rule apply to accounting firms directly?

The rule's obligations run to plans and issuers. Accounting firms are affected indirectly: they post and reconcile the remittance data the rule governs and may advise clients on fee accounting and documentation. Covered entities must meet the requirements; firms supporting them should confirm scope per client and adjust their reconciliation controls accordingly. For a definitive determination, consult a qualified attorney or tax advisor.

What are CARCs and RARCs, and why do they matter here?

CARCs (claim adjustment reason codes) and RARCs (remittance advice remark codes) are standardized codes that explain why a claim was paid, adjusted, or denied. The rule requires plans and issuers to communicate certain information using these codes, as specified in guidance, on paper or electronic remittance advice sent to entities without a contractual relationship with the plan or issuer. For accounting teams, that means the reasons behind adjustments arrive in a structured, mappable form — useful for reconciliation, but worth re-checking against existing code mappings during the transition.

How can a firm keep track of future rules like this one?

Monitoring the Federal Register and the eCFR for changes to the CFR parts a firm cares about is the reliable approach. Some firms automate the watch so a published rule is flagged and routed to the right reviewer with its citation and effective date attached, while a human still makes every compliance call. The constant is the primary source: conclusions should trace back to the notice, here at 91 FR 33900.

Related guidance

For adjacent compliance reading, see our notes on small-business lending under the Equal Credit framework, the Geographic Targeting Order imposing recordkeeping and reporting requirements, and the extension of compliance dates for the healthcare nondiscrimination rule.

Disclaimer

This article is provided for informational purposes only and is not legal or tax advice. Reading it does not create an attorney-client relationship. Federal regulations are complex and fact-specific, and their application depends on circumstances this article cannot assess. Before acting, consult a qualified attorney or tax advisor about your specific situation.

Every date, citation, RIN, CFR reference, and figure in this post is copied verbatim from the Federal Register and eCFR as of the snapshot date. Nothing is estimated, modeled, or extrapolated. This is not legal or tax advice.

Last reviewed: June 20, 2026.

Source: U.S. Federal Register (91 FR 33900); current text via eCFR, 26 CFR Part 54.