Federal IDR Batching Rules: 2026 Provider Decision Guide
A provider decision guide to the Federal IDR batching rules effective for open negotiation periods beginning November 1, 2026, including the three batching pathways, 50-line limit, payer test, and cooling-off windows.

Before you act on this guidance
- Check the controlling jurisdiction, coverage terms and current agency guidance; a published overview is not a determination for your claim.
- Prepare the relevant records: Plan funding, initial payment or denial, open-negotiation status and the applicable deadline.
Federal Independent Dispute Resolution batching can reduce the number of dispute files and administrative fees, but it also concentrates eligibility risk. If unrelated claims are grouped, the certified IDR entity must determine which items are properly batched, and the provider may lose time while correcting its workflow. CMS's October 29, 2026 guidance translates the final rule into three permissible batching pathways, a 50-line-item cap, payer-identification rules, timing tests, and a decision tree.
This guide turns those requirements into a provider-side intake method. It should be used after confirming that each line is otherwise a qualified IDR item or service and that open negotiation was timely completed. For the broader sequence, use the Federal IDR Process Guide, the open-negotiation deadline guide, and the 2026 final-rule implementation timeline.
The provider batching test in one table
| Gate | Question | Operational evidence |
|---|---|---|
| 1. Underlying eligibility | Is every line independently eligible for Federal IDR, with initial payment or denial and required open negotiation completed? | Remittance or denial, eligibility analysis, open-negotiation notice, delivery evidence, and date log. |
| 2. Same provider entity | Were all lines billed by the same provider, facility, or air ambulance provider, identified by the same NPI or TIN? | Claim-level billing entity, NPI, TIN, and organizational mapping. |
| 3. Same plan or issuer | Is the same issuer responsible for fully insured claims, or the same self-funded plan responsible for self-funded claims? | Funding type, issuer HIOS when applicable, plan sponsor/TIN or EIN, Form 5500 plan number, and plan name. |
| 4. Similar-condition pathway | Does the proposed batch satisfy the encounter, same/comparable-code, or specified specialty CPT-range pathway? | Patient, dates, claim form, primary service code, modifiers, coding system, and specialty range. |
| 5. Furnishment window | Were the items furnished within the same 30-business-day period beginning with the earliest item, unless the cooling-off exception applies? | Earliest service date and business-day calculation. |
| 6. Initiation timing | Did each line's 30-business-day open negotiation period end within four business days of initiation, unless a cooling-off rule changes the window? | Open-negotiation start/end dates, initiation date, extension approval, and cooling-off record. |
| 7. Line count | Does the batch contain 50 or fewer dispute line items? | Final line-level manifest; modifiers that function only as modifiers are not separate lines. |
Three ways claims may satisfy the similar-condition requirement
Pathway 1: one patient, one encounter, one claim form
The first pathway covers qualified items and services furnished to one patient during a single encounter. CMS defines the encounter as one or more consecutive days during which the items or services were furnished to the same patient and billed on the same claim form. The service codes do not have to match, but the patient, consecutive-day encounter, and single-claim-form conditions do.
Pathway 2: the same service code or a comparable code
The second pathway can include one or more patients when the services were billed under the same service code or a comparable code under a different procedural coding system. CMS gives CPT, HCPCS, and DRG as examples. A team should not label codes comparable based only on clinical similarity; it should document the coding-system relationship supporting the comparison. Service-code modifiers do not prevent otherwise identical primary codes from being treated as the same code, but the remaining batching gates still apply.
Pathway 3: specified anesthesia, radiology, pathology, or laboratory CPT ranges
The third pathway is limited to anesthesia, radiology, pathology, and laboratory items and services. Claims for one or more patients may be grouped when their primary codes fall within the same Category I CPT code range specified in the CMS guidance. This is not permission to batch every service within a specialty: the codes must fall inside the same CMS-listed range, and the provider, payer, timing, and line-count gates still apply.
| Specialty | Examples of separate CMS ranges | Intake control |
|---|---|---|
| Anesthesia | 00600–00670 (spine/spinal cord); 00800–00882 (lower abdomen); 01958–01969 (obstetric) | Compare the primary anesthesia code, not merely a qualifying-circumstances add-on code. |
| Radiology | 70010–71555 (head, neck, chest); 72020–72295 (spine and pelvis); 73000–73725 (extremities) | Keep claims in the same listed range; a shared radiology department is not enough. |
| Pathology/laboratory | 82009–84999 (chemistry); 85002–85999 (hematology/coagulation); 87003–87999 (microbiology) | Use the current CMS table; these examples do not reproduce every permitted range. |
How the 50-line limit works
A batched dispute may contain no more than 50 qualified IDR line items. CMS clarifies that service-code modifiers and anesthesia qualifying-circumstances add-on codes that function as modifiers do not count as additional line items. By contrast, traditional CPT add-on codes are separate procedures; when submitted as separate dispute items, they count toward the cap. The safest control is a final line manifest that distinguishes the primary code, modifier-only information, traditional add-on code, patient, claim, and open-negotiation record.
Cooling-off periods change the calendar
| Prior determination | Cooling-off period | Held-over initiation window |
|---|---|---|
| Batched dispute | 30 business days beginning on the payment-determination date | Generally four business days after the cooling-off period, if the CMS conditions for the affected item are met. |
| Single dispute | 90 calendar days beginning on the payment-determination date | Generally 30 business days after the cooling-off period, if the CMS conditions for the affected item are met. |
| Bundled dispute | CMS's October 2 notice states that bundled disputes continue to use the 90-calendar-day cooling-off period | Use the applicable 90-day held-over procedure and verify the current portal instructions. |
A cooling-off period applies to the same parties and the same item or service. CMS interprets the same item or service by service code, including traditional add-on codes, without treating modifiers or anesthesia qualifying-circumstances codes as a different service. For self-funded claims, the same-plan analysis remains decisive even when a common TPA administers multiple plans.
CMS also describes an exception to the ordinary 30-business-day furnishment window when the dispute could not be initiated because of a cooling-off period. Do not apply that exception automatically. Record the prior payment determination, the parties and service code, every overlapping cooling-off period, the open-negotiation end date, and the resulting initiation window.
Batching is different from a bundled payment arrangement
A batch contains multiple qualified IDR items or services presented for separate payment determinations under the batching rules. A bundled payment arrangement instead involves multiple items or services represented by a single service code—CMS uses a DRG as an example—because the provider billed that way or the plan made its initial payment or denial under that single code. Calling a set of claim lines a bundle does not avoid the batching criteria.
A defensible provider batch file
- Screen every line for Federal-versus-state jurisdiction and baseline IDR eligibility before grouping.
- Record the billing NPI and TIN and reject mixed provider entities.
- Identify funding type and the actual issuer or self-funded plan; do not rely on the TPA name alone.
- Assign exactly one similar-condition pathway and retain the facts that prove it.
- For specialty-range batches, record the primary CPT code and the exact CMS range used.
- Separate modifiers from traditional add-on codes and calculate the line count.
- Calculate the 30-business-day furnishment window from the earliest service date.
- Tie each line to its open-negotiation notice, delivery evidence, end date, and initiation deadline.
- Test prior determinations for 30-business-day or 90-calendar-day cooling-off effects.
- Archive the submitted line manifest, portal confirmation, supporting documents, and any certified IDR entity questions.
Millennova operational interpretation
The most reliable batching workflow is claim-line first, not batch first. Build a normalized line-level table, prove plan identity and timing, then allow the system or reviewer to propose a batch only when all rows share the required gates. This reduces the risk that a high-level payer label or specialty label hides different self-funded plans, incompatible CPT ranges, or different open-negotiation clocks. Millennova's No Surprises Act arbitration support can help provider teams organize eligibility, evidence, deadlines, and dispute operations; legal conclusions for a particular claim should be made with qualified counsel where appropriate.
Official primary sources
Frequently Addressed Procedural Questions
Review an NSA dispute workflow
Discuss jurisdiction triage, open-negotiation records, QPA evidence and filing-readiness controls. Each dispute requires its own eligibility and deadline check. Millennova Legal provides non-attorney operational and documentation support, not legal advice or representation.