Est.

Write-Off Prevention Policies for Infusion Underpayments

Practices can recover infusion underpayments by catching them before accounts close.

Staff Writer, Operations & Technology · · 10 min read
Cover illustration for “Write-Off Prevention Policies for Infusion Underpayments”
Remittance Reconciliation · October 7, 2026 · 10 min read · 2,197 words

Infusion underpayments turn into permanent write-offs because most practices have no post-payment policy designed to catch them before the account closes, even though the money itself is recoverable. A denied claim at least announces itself: a rejection notice lands, someone has to make a decision, and the claim stays visible until that decision gets made. An underpayment does the opposite. It arrives disguised as success.

The remit shows a payment. The account looks resolved. Nobody flags it, because nothing about the transaction screams "problem," the billing system has already moved on to the next claim in the queue, and that absence of a policy that would have stopped the account from closing in the first place is what turns the shortfall into a quiet write-off.

Infusion billing makes this especially dangerous. Time-based CPT coding, J-code unit calculations, and drug administration hierarchy rules each create a separate surface where a payer can pay less than it owes without tripping any denial flag. A correctly delivered infusion, administered exactly as ordered, can still produce a claim that gets paid short on three or four different lines simultaneously. None of those shortfalls generates a rejection. Each one just sits there, inside a remit that reads as paid in full, waiting for someone to notice it never was.

The specific billing mechanics that produce infusion underpayments at the line level

Underpayments in infusion billing trace back to a narrow set of recurring, line-level mechanics, each specific enough to infusion that general-purpose revenue cycle review tends to miss it.

J-code unit miscounting produces the largest dollar losses of any single error type. Infliximab (Remicade) illustrates the stakes: it's billed under J1745 at one unit per 10mg, so a large dose requiring 100 units demands that the claim actually state 100 units. The payer doesn't reject any of this. It pays what the submitted units justify and closes the claim as if nothing went wrong.

Biosimilar coding adds a second layer to the same problem. Biosimilar J-codes are distinct from the reference product's code: infliximab biosimilars like Inflectra, Renflexis, and Avsola each carry their own HCPCS code, separate from J1745. Billing the wrong code here is both a compliance exposure and a direct trigger for underpayment, since the payer will adjudicate against whatever code was submitted, correct or not.

Time-based CPT coding generates a third pattern, this one rooted in sequencing. Reporting the wrong service as primary means losing the higher-rate code tied to the correct hierarchy position, even when every minute of infusion time was documented accurately.

Contract rate mismatches sit apart from all of these. They are payment posting failures: cases where the fee schedule the payer promised in contract doesn't match what the remit actually paid, visible only through reconciliation against the real contract terms rather than a general expectation of what the claim "should" have brought in.

Each of these error types leaves its own signature on the remit: a unit count that doesn't match the descriptor, a code that doesn't match the biosimilar dispensed, a hierarchy that doesn't match the order of services, a rate that doesn't match the contract. Catching any of them requires knowing what signature to look for, which is exactly where generic AR review runs out of the specificity infusion billing demands.

Payer-side changes in 2026 accelerating underpayments

The window for catching an infusion underpayment is shrinking, and the shift is coming from the payer side faster than most practices have adjusted their review cycles to match.

Appeal timelines have compressed across the industry, and the range matters. UnitedHealthcare enforces the shortest standard appeal window among the large commercial insurers, while Aetna, BCBS, and Cigna allow considerably longer. The money was there to claim. The clock ran out before anyone looked.

Mid-year policy changes compound the timing problem that practices already face. Payers are expanding prior authorization requirements further into specialty and biologic infusions without necessarily flagging the change to providers in advance, so a drug or code that needed no authorization last month can need one now. A practice still running last year's checklist will keep submitting claims the same way it always has, and the payer will respond by paying less, or denying outright, for a reason the practice doesn't yet know exists.

AI-assisted adjudication on the payer side has widened this gap further. Payers are processing first-pass adjudication faster than many billing teams can review and respond. Underpayments are being issued at a pace that outstrips the review cadence most practices still run on. The asymmetry is structural: the payer's system moves on its own schedule now, and a billing team working in weekly batches is playing a game whose speed has changed without an announcement.

Site-neutral payment reform adds one more wrinkle. Payers are increasingly applying lower-rate payment rules to infusion services delivered in settings that once qualified for higher reimbursement, so contract-level reconciliation built into the post-payment workflow is what lets a practice recognize when the rate applied to a given claim was wrong.

Taken together, these shifts don't change what an underpayment looks like. They change how long a practice has to find one before the chance to fix it disappears.

Remit reconciliation as the first post-payment policy gate

Line-level remit reconciliation, done at the moment of payment posting, is the first and most time-sensitive policy an infusion practice can put in place. It's the only point in the entire post-payment workflow where an underpayment can still be caught before the account gets closed out.

Line-level means something specific. Each paid line on the remittance gets compared against the contracted rate for that exact J-code, that exact CPT code, and that exact drug, at that exact payer. It does not mean comparing the total payment against some global expected amount for the encounter as a whole. Line-level review catches it, because a remit paid against the claim at the wrong unit count or the wrong rate is an underpayment on that line, whatever the total looks like.

Contract rate mismatches need this same discipline applied against the real fee schedule for that payer, not a generic industry benchmark for what reimbursement "should" be. High-performing centers that run this kind of reconciliation achieve underpayment detection rates of 90% or higher. Platforms built specifically for infusion billing, Ruby RCM among them, are designed to run line-level reconciliation against those exact surfaces before a practice ever treats a paid claim as closed.

This policy infrastructure needs three pieces to function: a reconciliation cadence, a separation of duties, and a documented threshold. The reconciliation cadence has to match or exceed the tightest payer appeal window the practice deals with: if a payer's window is five business days, a weekly review cycle is already too slow to act on anything that window flags. And the person posting the payment should not be the same person deciding whether that payment was correct, because volume pressure creates a systematic bias toward closing accounts rather than reopening questions about them.

That threshold rule, the one that decides what gets flagged, is also where the next policy question begins: once something is flagged, what happens to it next.

Defining the appeal threshold policy that separates pursuits from write-offs

Flagging an underpayment is only half the job. What happens to a flagged line needs to be governed by a documented threshold policy, not left to whoever happens to be working the account that week.

Ad-hoc decisions tend to drift toward write-offs, and the drift is predictable. The recovery rate swings based on workload rather than on the actual value of the claims involved, and the swing stays invisible to anyone above the AR desk unless the policy requires it to be tracked.

The bigger risk sits in how small underpayments get treated in isolation. A shortfall that looks trivial on a single claim can be a systematic error repeating across dozens of claims for the same drug at the same payer, and a policy that requires root-cause identification before a claim gets closed is what surfaces that pattern. This section's most important rule: even when a single claim falls below the dollar floor set for pursuit, if the same payer-code-rate combination appears across multiple claims in the same period, the aggregate value has to trigger mandatory pursuit, regardless of how small any one claim looks on its own. A small shortfall repeated across many claims for the same drug at the same payer adds up to a much larger systemic problem, and treating each one as a separate trivial write-off buries that fact completely.

The policy needs a minimum dollar floor below which the cost of pursuing a claim outweighs the recovery, set per line rather than per encounter, and reviewed quarterly as drug costs and contracted rates shift. It needs an escalation path that routes high-dollar infusion underpayments, particularly those tied to biologic J-codes, to a specialist rather than a general AR queue, because the appeal documentation these claims require is materially different from a standard medical claim appeal.

A flagged underpayment that gets written off without scrutiny there is a loss layered on top of acquisition cost the practice fronted weeks earlier, an exposure that makes the next stage of the policy, how long a flagged claim is allowed to sit before someone acts, just as urgent.

AR aging rules that prevent underpayments from aging into invisibility

Standard AR aging thresholds, built for general medical billing, are too permissive for infusion claims, because infusion carries a layer of drug acquisition cost exposure that compounds with every aging bucket a claim passes through unresolved. For a buy-and-bill biologic claim, where the practice is holding tens of thousands of dollars in drug cost against a single patient encounter, that same degree of aging means the practice has been out of pocket on that drug for months with no recovery in sight, and every additional week it sits unresolved is a week of capital tied up with no return.

Aging infusion accounts lose something general medical claims don't lose nearly as fast: appeal eligibility. A claim that passes a payer's appeal window while sitting untouched in a 60-day aging bucket cannot be recovered through appeal, no matter how strong the underlying argument is. The deadline doesn't care how aged the account looks internally. It only cares what calendar date it hit.

Infusion-specific AR aging policy has to account for both of these pressures directly. A tiered aging structure should separate high-dollar biologic and buy-and-bill claims from lower-dollar infusion accounts, applying a shorter action-required timeline to the high-dollar tier specifically. Any infusion claim carrying a J-code for a biologic should receive active follow-up before the 30-day mark, not at the 90-day mark that general AR policy would normally allow. And no underpayment-flagged account should be closed to write-off without supervisor sign-off and a documented reason, because that sign-off requirement does two things at once: it slows down the drift toward casual write-offs, and it creates an audit trail that, over time, becomes the raw material for spotting patterns no single claim would ever reveal on its own.

Preventing payer-specific denial and underpayment patterns through root-cause tracking

Every documented sign-off, every threshold flag, every reconciliation note generated by the policies above accumulates into something larger than a transaction log. Tracked by payer and by code, that data becomes a map of where a practice's billing process is systematically leaking revenue, pointing to fixes that prevent the next underpayment.

Generic denial grouping destroys this signal before anyone can read it. An underpayment on infliximab at one commercial payer and an underpayment on tocilizumab at a Medicare Advantage plan might both land in the same broad "drug billing" denial bucket, but they almost certainly have different root causes, different contractual remedies, and different points upstream where the error could have been caught. Grouping them together produces no finding anyone can act on. Tracking them separately, by payer, by J-code, and by error type, produces an actual map of where authorization checklists need rewriting, where charge master unit calculations need correcting, or where a contract rate table has gone stale.

A payer that systematically underpays one J-code across multiple claims in the same period is almost certainly running an outdated fee schedule or misidentifying a biosimilar against the reference product, and that's a finding worth a contract-level correction, not another round of one-off appeals. A pattern of time-based CPT underpayments appearing at one payer but not others usually traces back to a documentation workflow problem, infusion time not recorded to the minute, solved at the point of care.

Each underpayment type, whether it's a J-code unit miscount, a wrong biosimilar code, an infusion hierarchy error, or a contract rate mismatch, leaves its own distinct signal on the remit, and catching each one consistently requires policies tuned to that specific signal rather than a single generic exception rule applied across the board. That's the reasoning behind why infusion-focused RCM platforms separate underpayment detection by error type and by payer instead of folding everything into one undifferentiated AR bucket. The underpayment that gets caught once is a recovery. The pattern that gets tracked and corrected at its source is the write-off that never happens again.

Sources

  1. Challenges Facing Providers with Revenue Cycle Management

More in Remittance Reconciliation