Underpayment Recovery Process for Infusion Practices

A denied claim announces itself. It lands in a work queue, someone sees it, and the billing team knows there's a problem to fix. An underpaid claim does the opposite: it posts as collected revenue, the balance clears, and the claim looks closed.

The mechanism explains why underpayments survive so long without anyone noticing. A denial sits in a queue, waiting for someone to act. An underpayment, by contrast, gets absorbed into the contractual adjustment line on the remittance and disappears, unless someone sits down and compares the payment against a benchmark, line by line. No alert fires. No task gets assigned. The money is simply gone, counted as collected, while the shortfall sits buried in a column nobody audits by default.

Infusion centers lose revenue every day because manual processes leave that comparison undone. When practices don't check actual payments against ASP rates or contracted fee schedules, line by line, underpayments accumulate quietly inside remits that already look paid. The scale of the loss is what sets infusion apart from most other specialties. A single biologic encounter can carry drug costs running into five figures, so even a small gap in reimbursement becomes a dollar figure a practice can calculate and should be chasing.

The structural reason these gaps pile up sits in how payer adjudication systems work. Contractual adjustments get applied at the line level, line by line, inside the payer's system. A practice that only reviews the net payment on a remittance, without reconciling each line, never sees which specific lines were shorted or by how much. The claim shows as paid. The chart shows revenue. Nothing flags the gap between what was billed and what the contract or the ASP schedule actually says should have been paid.

What makes infusion claims structurally prone to underpayment

Infusion billing carries more moving parts than most specialty claims, and every added dimension gives a payer's adjudication system another place to short-pay without the error appearing clearly on the EOB.

Start with J-code unit accuracy, because it's the single highest-leverage technical detail in infusion billing. If documentation doesn't tie the administered dose exactly to the units billed, a payer's system can adjudicate against a different, lower unit count than what was actually given, and nothing on the remittance will call that out as an error.

Buy-and-bill ASP pricing adds a second layer of exposure. Medicare reimburses at ASP plus a statutory add-on, but sequestration adjustments compress that margin further once the payment actually lands. The additional risk occurs in the ASP rate payers apply: they can price the claim against the wrong quarter's rate or against the wrong product entirely, producing a payment that looks like routine, correct adjudication while quietly shorting the practice.

Add-on codes and infusion time tiers create a third exposure. Because of the add-on hour structure in infusion billing, a documentation gap around infusion duration doesn't just risk a coding error. It risks a missed or underpaid sequential infusion code, a real dollar loss tied directly to how carefully nursing and billing capture the clock time of the visit.

Commercial contracts stack a fourth layer on top of all this. Four sources of exposure, each invisible on its own, together make infusion claims some of the most structurally prone to underpayment in specialty billing. This is why reconciliation has to happen line by line and has to account for the specific mechanics of infusion billing, not a generic denial workflow borrowed from another specialty.

The structural opacity of these line-level adjustments is why infusion practices need reconciliation workflows built to surface what standard remittance processing conceals. Ruby RCM, built specifically for infusion billing, centers line-level reconciliation and exception flagging so underpayments don't vanish into contractual adjustments unexamined.

How to detect underpayments before the dispute window closes

The 835 remittance file, read at the line level, is the primary tool for catching underpayments before it's too late to fix them. Each service line carries CARC and RARC codes that explain the adjustment reason the payer applied. A contractual adjustment code on its own does not mean the payer got the math right. It only means the payer applied some adjustment and attached a label to it. Someone still has to check whether that label matches what the contract or the ASP schedule actually allows.

The benchmark for that comparison changes depending on the payer. For commercial payers, the comparison runs against the contracted fee schedule for that specific billing code, factoring in site of service and any carve-out or tier that applies. These aren't interchangeable checks. Using a Medicare benchmark against a commercial claim, or vice versa, produces a false read on whether the payment was correct.

Certain patterns on a remittance are strong signals of an underpayment, distinct from a legitimate contractual adjustment. Payment on fewer units than billed, with no corresponding denial of those units, usually means the payer silently repriced the unit count without saying so. Check every time for a fourth pattern: add-on codes paid at zero dollars with no explicit denial reason code attached.

None of this matters without speed, because every payer runs its own dispute window, and that window is the clock the rest of this process has to run against. Without a system built to surface those patterns across sites and payers rather than hunting for individual claim errors one at a time, the root causes stay hidden and the window to dispute them keeps closing while the review drags on.

Prioritizing which underpayments to work first

Not every underpayment a practice catches deserves the same amount of effort, and working them in the wrong order burns the dispute window on claims that matter less while bigger claims time out. Sorting the list correctly is what turns a detection process into an actual recovery process.

The first sort runs on dollar value weighted against the days left in the relevant dispute window. A large underpayment with only 30 days left on its clock should jump ahead of a smaller underpayment that still has months of runway, even though both are ultimately recoverable. Time pressure, not just dollar size, decides what you work today versus next week.

The second sort runs on how recoverable each type of underpayment actually is. Add-on code omissions recover well when the clinical documentation clearly supports the extra time or service that was billed.

Payer-level patterns matter just as much as claim-level patterns. Aging matters too: accounts receivable should never become a parking lot for underpayments nobody is actively working. Anything identified late in the aging cycle needs to move to the front of the line immediately rather than sit queued behind items caught more recently.

Some variances are small enough to log and leave alone. Anything below a defined dollar threshold, inside whatever tolerance range the contract permits, should get closed out and recorded. Time spent pursuing sub-threshold variances is time pulled away from the high-dollar recoveries that actually move the needle.

Working a payer-specific underpayment through the dispute and appeal process

Recovering an underpayment takes a different workflow than recovering a denial, because there's no denial notice prompting the response. The practice has to initiate contact itself, armed with documentation proving what the correct payment should have been.

The first step is assembling the dispute package before ever contacting the payer. For disputes tied to a contracted rate, the package also needs the specific contract language or fee schedule exhibit establishing what the rate should have been.

The second step is identifying the correct channel for that specific payer. Some payers require a formal corrected claim. Getting this wrong carries real cost: submitting through the wrong channel does not pause the deadline clock. The clock keeps running regardless, and a payer can later argue the dispute was untimely simply because it arrived through the wrong door.

The third step is stating the basis of the dispute narrowly and specifically. The submission should name the exact line in question, the amount adjudicated, the amount expected, the contractual or regulatory basis for that expected amount, and the documentation attached to support it. A broad appeal that simply says the claim was underpaid is easy for a payer to deny with a generic response. A dispute that points to a specific ASP quarter, a specific contracted tier, or a specific unit count is much harder for a payer to wave away without actually engaging the substance of the claim.

The fourth step is tracking the dispute separately from the original claim, on its own timeline. A dispute that gets filed and then never followed up on accomplishes nothing. If the payer doesn't respond within its stated resolution window, the next move is escalating to a supervisory contact or a managed care representative, well before the outer filing deadline arrives.

The fifth step is documenting the outcome at the payer level, not just closing out the one claim. A payer that keeps underpaying the same J-code, keeps applying the wrong ASP quarter, or keeps repricing units without issuing a denial is showing a pattern, not a one-time mistake. That pattern becomes the basis for a contract-level conversation, not just another single-claim recovery. Without a system that flags underpayments against payer-specific and root-cause-specific patterns, rather than lumping adjustments together generically, practices keep losing revenue while the dispute window keeps narrowing on them. An infusion-focused RCM platform can show you which lines fall outside expected-payment tolerances for each individual payer, catching the signal that generic reconciliation tools tend to miss.

Using underpayment patterns to build a payer performance scorecard

Every underpayment you work through to resolution produces one data point. On its own, that data point just closes a claim. Accumulate those data points across payers and across J-codes over time, and they reveal systematic payer behaviors that no single claim dispute could surface by itself.

The practical output of that accumulation is a payer performance scorecard, tracking expected reimbursement against actual reimbursement, broken out by payer, by J-code, and by site of service. The scorecard shows exactly which payers have a persistent, repeating gap between what the contract says and what actually gets paid.

A scorecard catches things claim-level review never will. It can show you a payer consistently applying last quarter's ASP instead of the current rate, a pattern invisible on any single claim but material once it's aggregated across a high-volume biologic. It can show a payer repricing units on a specific J-code at a rate inconsistent with the contract, which may simply reflect a configuration error in the payer's system rather than a deliberate policy, and is fixable through a direct managed care conversation. It can also show you a payer whose underpayment rate on add-on codes runs noticeably higher than its rate on primary infusion codes, which points to a specific adjudication rule being applied wrong across the board.

High-performing infusion centers use analytics to track claim performance this way, and they uncover both denial and payment trends from the same underlying data. The same infrastructure that supports denial pattern analysis should capture underpayment patterns across those same dimensions, payer, J-code, and site, so the two workstreams reinforce each other.

That scorecard becomes a contract negotiation tool in its own right. A payer whose effective reimbursement rate sits materially below its contracted rate, across a volume of claims large enough to rule out coincidence, is a payer whose contract needs renegotiating, or a payer that warrants a formal compliance demand. The individual dispute recovers a claim. The scorecard built from hundreds of them recovers leverage.

The operating model that makes line-level reconciliation sustainable

A structured underpayment recovery process only holds up over time when someone with infusion-specific billing knowledge actually owns it, built into the billing workflow at the remittance stage itself rather than bolted on as a separate audit nobody has time for.

The ownership gap is the real obstacle in a lot of health systems. Nobody treats the line-level remittance review as part of their job, so it doesn't happen consistently.

Making this sustainable requires a defined remittance review step at the point payments post, not weeks later during an aging review. It requires benchmarks for ASP rates and contracted fee schedules that stay current as quarterly updates land, since an outdated benchmark produces the same false comfort as no benchmark. It requires a prioritization method, the kind laid out earlier in this piece, so the team always knows which claims to work first when the dispute clock is running. It requires a documented, payer-specific dispute process so each submission goes through the right channel the first time. And it requires the discipline to feed every resolved dispute back into a payer-level scorecard, so the lessons from one claim actually inform the next hundred.

Infusion practices built to run this way treat the remittance as the start of a review process, not the end of one. That's the operational standard this piece has been building toward across every section, from the first underpayment flagged on an 835 to the contract renegotiation a scorecard eventually makes possible.