Providers often ask us: what’s your Independent Dispute Resolution (IDR) batching strategy?
The not-so-exciting answer is “we just follow the rules.” The No Surprises Act and subsequent regulatory guidance clearly define which claims can be batched, how many can go into a dispute, and when they can be filed.
But two providers following the same rules can get very different results, and how each operates within the constraints is where things get interesting.
That’s what this post is about. We’ll quickly review the federal rules that govern IDR batching, but more importantly, we’ll discuss the pitfalls we’ve seen firsthand and the decisions that determine whether a batch is worth filing. By the end, you’ll be better equipped to batch compliantly, spot opportunities you might otherwise miss, and get more value from your IDR program.
What is IDR batching?
IDR batching is the process of grouping multiple eligible out-of-network items or services into a single dispute rather than filing each one separately. Batching matters because the No Surprises Act payment dispute process is operationally complex and comes at a cost. Each party pays an administrative fee per dispute, and the non-prevailing party generally pays the certified IDR entity (IDRE) fee.
If every eligible claim had to be submitted individually, the additional work and fees would make IDR economically unviable for many providers. Small, independent physician groups with limited resources and specialties with lower-dollar claims could effectively be shut out of the process.
Done compliantly, IDR batching gives providers a meaningful opportunity to pursue fair reimbursement while improving overall program ROI. Small errors, however, can trigger administrative closures and create urgent rework. And once the IDR Operations Final Rule’s resubmission flexibility ends, an improperly batched claim could lose access to the IDR process altogether.
Which claims can be batched together?
Under the Final Rule, qualified IDR items and services may be batched when they meet all of the following criteria:
- Same provider or provider group. Based on Taxpayer Identification Number (TIN).
- Same health plan or health insurance issuer. Based on the applicable identifier and funding type.
- Services or items meet one of these conditions:
- Furnished to one patient in a single encounter, billed on the same claim form.
- Billed under the same service code, or a comparable code in another coding system.
- Billed within the same Category I CPT code range, for anesthesiology, radiology, pathology, or laboratory services.
- Dates of service within the same 30-business-day period.
The health plan and insurance issuer factor deserves special attention because funding type affects which claims can go into the same batch.
For self-funded plans, the relevant entity is the employer’s health plan, not the carrier or third-party administrator that processes the claim. Claims from employees covered under the same self-funded plan with the same group number may be batched when they meet the remaining criteria. Claims from different self-funded plans may not, even if the same third-party administrator pays them.
This is also where batching gets messy. Group numbers on 835 remittance advice and 837 claim files are notoriously inconsistent across payors. At scale, figuring out which claims belong to the same self-funded plan can be harder than applying the batching rules themselves, which makes it less a regulatory question, and much more a data-quality challenge.
Fully insured plans come with their own complexities. In bifurcated states, certain fully insured claims may be subject to a state dispute resolution process rather than federal IDR. Self-funded plans generally remain subject to federal IDR, though there are exceptions, including when a self-funded plan has opted into an applicable state process. If state law governs a dispute, the state’s own rules, including any batching rules, apply.
If a fully insured claim is subject to federal IDR, otherwise eligible claims payable by the same health insurance issuer may be batched together, even when they come from different group or individual policies offered by that issuer.
How batching affects specialties differently
Batching does not create the same value for every specialty. Its impact largely comes down to two factors: how broadly a specialty can batch different service codes and how many eligible claims it generates. The first depends on the available batching pathways; the second is a question of volume.
Under the Final Rule, items or services can satisfy the “similar condition” requirement through the same or comparable service code, a single patient encounter, or, for certain specialties, a designated Category I CPT code range. That third pathway applies only to anesthesiology, radiology, pathology, and laboratory services.
Here’s how those rules affect different specialties:
Emergency medicine
Because emergency medicine does not receive the Category I CPT code range pathway, providers generally must batch by individual service code. A level 5 ED visit (99285), for example, can batch with other level 5 claims, but not with a level 4 visit (99284). ED claims volume can still be high enough for code-specific batches to create meaningful economies of scale.
Anesthesiology
Anesthesiology receives the Category I CPT code range pathway but tends to bill a relatively concentrated set of codes. Like emergency medicine, much of its batching value comes from volume, with incremental value where the new pathway allows different CPT codes to be consolidated.
Radiology
Radiology bills across a much wider range of service codes. That creates more opportunities to consolidate services that would otherwise need to be separated into code-specific batches. For a high-volume radiology group, this can materially improve the economics and reduce the operational burden of pursuing IDR. The same principle applies to pathology and laboratory services.
How batching fits into the IDR timeline
The No Surprises Act requires open negotiation for every item or service, including those that will eventually be batched. Batching only becomes possible after the negotiation period ends without the parties agreeing on a rate. That is when the timeline gets really tight.
Once open negotiation ends, a provider has four business days to initiate IDR. If claim A finishes open negotiation today but claim B, which would otherwise batch with it, still has five business days left, the two miss each other. By the time claim B is ready, claim A’s initiation window has closed, so they must be filed separately.
In our experience, payor payment behavior creates some natural alignment. Open negotiation timing is tied to the initial payment or notice of denial, and payors tend to process claims on consistent cycles, such as weekly or several times per week. Claims paid around the same time often become ready for batching around the same time.
Which IDR batches are worth pursuing?
Knowing which claims can be batched and when does not tell you whether a batch is worth filing. Two claims can be eligible to batch and still lose money after fees. The final piece of an IDR batching strategy is deciding which batches to pursue and how large to make them.
Calculate your breakeven by payor
Every batch carries an expected cost before you recover a dollar. Each party pays the $15 administrative fee per dispute, and the non-prevailing party pays the IDRE fee, which can exceed $1,000 for a batched determination. Since you will not win every dispute, the expected cost of a batch is roughly your loss rate multiplied by the average applicable IDRE fee, plus the administrative fee. That gives you the minimum expected recovery needed to justify filing (i.e., your breakeven).
If a batch’s expected recovery does not clear that threshold, filing can erode value rather than create it. And because determination history can vary widely by payor, the breakeven should be payor-specific. Note that this math covers fees only. The internal time it takes to assemble, file, and manage a dispute is a real cost too, especially for smaller groups.
Breakeven calculations also rely on recent determination data and assume recent win rates will hold. When win rates shift suddenly, those assumptions can break down. Thresholds should be revisited regularly rather than set once and left in place.
Watch the IDRE fee tiers when sizing a batch
The second consideration is how many line items go into a batch. IDRE batching fees are generally tiered, so beyond a certain point, adding more line items can shift a batch into a higher fee tier. For example, a batch of 25 line items might carry one fee, while adding a 26th shifts the whole batch into a higher tier several hundred dollars more expensive.
That changes the marginal math. A lower-dollar claim that pushes a batch past a threshold can reduce the ROI of the group. In some cases, the better move is to place it in another batch or file it individually. Fee amounts also vary by IDRE, and providers do not fully control which entity is ultimately selected, adding another layer of uncertainty.
How to put your IDR batching strategy into practice
Doing batching well day to day is harder than knowing the rules . Claims move through the process on different timelines, batches aren’t always economically viable, health plan data is often incomplete, and even a well-assembled batch can be challenged.
A strong IDR batching operation is built to handle all of it. Here’s what that looks like in practice:
1. Monitor your entire IDR-eligible book, not individual claims
IDR batches form while claims are still moving through open negotiation, spread across different service codes, providers, and health plans. If you evaluate batching only when an individual claim comes due, you will miss opportunities.
At high volumes, this requires a workflow management system, like Pivotal’s platform, that can evaluate batching eligibility across the entire book. More sophisticated workflows can also align claims that would otherwise miss one another’s filing windows, for example, by strategically timing open negotiation initiation so eligible claims become ready to batch together.
2. Set value thresholds to the shape of your book
Your batches will span a range of potential values, and the right threshold depends on how that value is distributed. Raising the floor increases the average return per dispute but eliminates the batches below it, so the question is where the value given up begins to outweigh the gain.
If a cluster of lower-value batches sits just above breakeven, nudging the threshold higher may improve returns with little lost volume. Push it too far, and you begin forfeiting batches that would have delivered a positive return.
Doing this well requires looking at the actual distribution of batches coming due, not setting one blanket number, and revisiting the threshold as claim mix, fees, and win rates change.
3. Confirm the health plan and enrich missing data
Batching lives or dies on correctly identifying the health plan. As covered earlier, group numbers are notoriously inconsistent across 835 and 837 files. Getting this right has become even more important as payors scrutinize and challenge batches during the IDR process.
When payor-provided data does not include the information you need, build in an enrichment step to identify the plan through eligibility verification or other reliable data sources. If the plan still cannot be confirmed, filing individually is generally the safer move and may also be the better financial one.
4. Build a resubmission workflow for rejected batches
Even a disciplined operation will encounter batches that are challenged or found ineligible because plans provide incomplete or inconsistent information, or just don’t provide certain necessary information altogether. What separates a minor setback from revenue leakage is what happens next.
Today, a rejected batch may require someone to identify the problem, pull the affected claims, and refile them correctly before the applicable window closes. A stronger workflow detects the rejection and routes the claims for the appropriate next action automatically. This capability will become even more important when the Final Rule ends the current flexibility to resubmit improperly batched disputes.
The value of IDR batching goes beyond cost
Batching is often viewed as a way to improve the economics of IDR. But it can also strengthen the record your claims present
A single dispute shows one instance in which a provider believes a payor underpaid for care. A batch can show a pattern. Twenty critical-care claims, for example, may show the same provider delivering the same level of emergent care across 20 patients and receiving similarly low initial payments each time. Presented together, those claims give the provider a broader set of facts to draw on when positioning the dispute and make the pattern itself part of the case.
This is a real advantage, and another reason to get batching right. The hard part is consistently identifying the right claims, bringing them together at the right time, and deciding which batches are worth pursuing.
Frequently asked questions about IDR batching
What is batching in Independent Dispute Resolution (IDR)?
Batching is the practice of grouping multiple eligible out-of-network items or services into one federal IDR dispute. The provider submits them together for a joint determination, reducing administrative work and spreading dispute fees across multiple line items.
Which claims can be batched together?
Claims generally can be batched when they involve the same provider or provider group, the same health plan or issuer, qualifying related items or services, dates of service within the same 30-business-day period, and open negotiation periods that ended within four business days of IDR initiation. The precise rules vary by plan funding type and specialty.
How many claims can be included in an IDR batch?
According to the Final Rule, one batched dispute may include up to 50 qualified IDR items or services for open negotiations on or after November 1, 2026. Because one claim can contain multiple line items, the cap is not necessarily 50 claim forms. This limit becomes applicable with the Final Rule’s related batching provisions after the Departments announce supporting portal functionality.
When can claims be batched for IDR?
Eligible items or services can be batched after each has completed the required 30-business-day open negotiation period without an agreement. Their open negotiation periods must end within four business days of IDR initiation, and their dates of service generally must fall within the same 30-business-day period, subject to the cooling-off rules.
What happens if one or more claims in a batch are found ineligible?
A certified IDR entity (IDRE) may remove ineligible items or services while allowing the eligible remainder of a batch to proceed. Current guidance may also permit incorrectly batched disputes to be refiled. Under the Final Rule, that resubmission flexibility will end 120 days after plans and issuers are required to register in the federal IDR registry.
What is the cooling-off period for IDR batches?
The cooling-off period temporarily prevents the initiating party from bringing another IDR dispute against the same opposing party for the same items or services after a determination. For open negotiations on or after November 1, 2026, the Final Rule shortens this period for batched disputes from 90 calendar days to 30 business days. Claims that mature during it can be filed afterward within a special four-business-day window.
See how your current IDR approach measures up
Our free IDR assessment reviews eligibility, batching, performance, and ROI to identify what’s working and where there may be room to improve. Request your free IDR assessment →
