Underpayment Recovery Sequencing Tied to Payer Behavior Profiles in Home Infusion

Home infusion denial management and underpayment recovery should follow payer-specific behavior. Billing teams need to find which payers short-pay which lines, tell payer errors apart from billing and authorization gaps, and put work in order by recovery deadlines and the total dollars at stake. Claim age alone cannot show which money is recoverable or what action will recover it.

Why generic AR aging fails home infusion underpayment recovery

A billing team looking at an aging report sees time. The report groups balances by how long they have been outstanding, without explaining why a payer paid less than expected. In home infusion, that distinction determines the recovery path. An older balance does not automatically deserve attention before a newer short payment with a closing appeal window. Working oldest first can send staff toward difficult, low-value claims while recoverable revenue loses its window for action.

Some underpayments never reach that report at all. Denials are visible and produce a CARC code, while partial payments can clear the remittance as paid and disappear from denial queues. Without line-level reconciliation, the claim may look resolved even though the payer paid below the expected amount. One home infusion encounter can have drug cost, nursing service, and DME components that fall under different code sets and payer rules. A small shortfall on one line can thus add up to a large loss over a treatment cycle while the claim still looks paid.

How payer-specific remittance behavior creates predictable underpayment patterns

Payers do not short-pay in a uniform way. Their adjudication logic, clinical edits, and payment rules lead to patterns that repeat and can be spotted before claims become old balances. Different rules applied to the same codes create different results, and quarterly rule changes can introduce new patterns without provider notification. Published policy is therefore not enough to explain actual payment behavior. The useful evidence is what the payer repeatedly does to submitted claims.

Drug reimbursement makes that pattern concrete. ASP-based biologics reimbursement is recalculated quarterly, so a payer using an outdated ASP table or the wrong quarter can repeatedly short-pay J-codes for the same drug. Nursing payments require a different comparison. Missing CPT 99602 units on visits longer than two hours may reflect provider underbilling, while payer adjudication that ignores documented visit duration can produce a similar shortfall. The payment result alone does not identify the cause.

A payer behavior profile records those recurring differences. It documents which line items a specific payer short-pays, under which CARC codes, how often, and with what aggregate dollar impact. It also needs to capture how that payer responds to recovery efforts, because a payment pattern and a recovery path are not the same thing. This makes the profile more useful than a broad category such as “underpayment.” It connects the affected code and payer rule to the action the claim actually needs.

The two categories of infusion underpayment that require separate recovery paths

Contractual underpayment occurs when the payer pays below the contracted rate on a correctly coded, correctly documented claim. The claim itself is not the problem. A wrong fee schedule tier, drug ASP quarter, or site-of-care differential can cause the same shortfall across many claims. Finding it takes a check of each line against contracted rates that goes beyond a review of payment totals alone. Recovery then runs through a formal dispute or payer reconciliation request.

Operational underpayment starts on the provider side. If documentation supports additional CPT 99602 units but those units were never billed, the payer may have paid correctly for the submitted claim. There is nothing to dispute on that basis. The remedy is prospective billing correction and, in some cases, rebilling recent claims where the documentation is intact. Treating that loss as a contractual short payment produces a valid payer denial and consumes time that belongs elsewhere.

Authorization-driven partial payment is a hybrid of these categories. The payer may pay only some billed units because the authorization covers fewer sessions or a narrower code set than the claim. Here, recovery depends on the authorization record. Mid-treatment expiration is the primary trigger when reauthorization was not submitted before the existing approval expired. Classification must precede sequencing, because a contract dispute, a billing correction, and an authorization review cannot be handled as interchangeable appeals.

Building a payer behavior profile from remittance history

To build the profile, start with the practice’s line-level 835 remittance data and organize it by payer, procedure code, CARC code, and frequency over a rolling period. Compare the payments with the relevant contract fee schedules so that a paid line does not automatically count as a correctly paid line. Record the code combinations involved and the aggregate dollar shortfall across the period. A small adjustment on most claims from one payer can reveal a systematic problem that isolated payment reviews miss.

For home infusion, maintain the analysis by drug-payer combination. CMS re-prices ASP-based biologics quarterly, and stale pricing can affect one drug’s J-code claims without explaining the payer’s other payments. Keep documentation issues distinct from pricing issues. Waste modifier disputes, for example, require attention to dosage accuracy and vial wastage documentation. The profile should keep the evidence needed to tell those causes apart.

This work starts with organized reconciliation. Tools can expand the analysis, but they cannot replace the comparison between what was billed, what was supported, what the contract required, and what the payer paid. Review new remittances regularly against the prior period’s baseline. New CARC codes or code combinations appearing more often may signal a change in adjudication behavior. A profile built once and left untouched will miss those shifts, even if its original findings were accurate.

Sequencing recovery work by payer behavior profile rather than claim age

The first priority is underpayments approaching a payer-specific appeal deadline. That deadline can override both claim age and the apparent size of an individual balance. BCBS appeal windows vary by state plan, so “BCBS” alone is not a sufficient timing rule. The profile must name the actual plan and its appeal window instead of assuming one window applies across the carrier.

UHC claims with modifier-related adjustments and fewer than 14 days remaining in the appeal window belong at the top of the queue regardless of their aging bucket. The UHC timing example refers to time remaining within the applicable appeal period. The distinction prevents a timing example from becoming the wrong operating rule. A queue must surface the claim while the team can still act on it.

The second priority is recurring contractual underpayment with the largest aggregate dollar impact by payer-code combination. A wrong ASP quarter applied to a high-cost biologic across dozens of claims concentrates recoverable revenue around one payer error. The unit of priority is the pattern. A modest short payment repeated across many claims can deserve attention before a larger one-off discrepancy. The payer profile supplies the documentation that establishes the dispute as a systematic payment issue.

The third priority is to fix how billing is done so that future revenue is protected. Missing time-based units call for a fix to the billing workflow rather than payer disputes, and recent claims may be rebilled where the supporting documentation is intact. These corrections do not have appeal deadlines, but indefinite delay creates recurring permanent loss. Keeping them in a separate recovery path prevents urgent appeals from obscuring the need to fix billing.

Where prior authorization gaps seed the underpayments that surface later in AR

Authorization gaps can start when treatment is scheduled, and AR may not see them until the remittance arrives. Infusion treatment extends across multiple sessions over weeks or months, while an authorization may cover only a set number of sessions or a defined time window. Later sessions are at risk of underpayment when that approval expires before reauthorization starts. By the time the payment shortfall appears, the clinical documentation is already set and the authorization window may be closed. Recovery sequencing cannot undo every upstream gap.

The prevention step belongs in the same framework. For treatment cycles that are still underway, high-performing infusion centers start reauthorization at least two weeks before the current authorization expires. That timing requires the PA calendar to connect with the treatment schedule. Payer profiles should therefore include authorization-to-claim mismatches, PA denial patterns among MA plans, and authorization windows for specific biologics. Those inputs show both where underpayments have already appeared and where later underpayments are likely to originate.

UHC’s tightened authorization matching logic illustrates why a number on file is insufficient. NPI mismatches, date-of-service range edges, and place-of-service mismatches can produce retroactive denials even when the claim has an authorization number. These are matching failures whose causes may be independent of clinical medical necessity. A broad “authorization denial” category hides that distinction and points staff toward the wrong evidence. The payer profile needs the mismatch itself so that recovery follows the authorization record.

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) adds an external input to this analysis. The rule requires payer public reporting of approval, denial, and appeal rates beginning January 1, 2026, with initial reports due by March 31, 2026, and Prior Authorization API implementation by January 1, 2027 for impacted payers. Public reporting gives practices a basis for comparing their own authorization denial experience with payer-reported results. It does not replace claim-level analysis. Its role is to strengthen the payer profile with evidence beyond the practice’s own remittances.

What the revenue cycle operation needs to execute payer-behavior-based sequencing

Execution requires line-level analytics, payer-specific work queues, and experienced infusion billing operators. The analytics foundation is 835 data mapped by payer, code, and CARC. High-performing centers segment AR by payer, drug, site of care, age bucket, denial reason, and claim value. Operators with more than one site also need to compare sites to see whether what looks like a payer-wide pattern comes from one site or drug category.

The queues must turn that analysis into work. Claims close to payer-specific deadlines need to come up for work before older balances that have more time left for recovery. Contractual disputes and operational billing corrections belong in separate queues because their evidence and required actions differ. The operation gains little if staff must reconstruct the root cause each time they open a claim or search an aging report for urgent exceptions.

Automation can flag the discrepancy without settling its cause. A stale payer ASP table and a provider’s wrong J-code can both produce payment below the expected amount, yet require opposite responses. Experienced operators must work out how the drug and code relate and review the authorization history and contract terms before deciding what to do. They also need to distinguish a recurring payer behavior from a one-off problem. Software is most useful when it puts the right evidence and claims in front of those operators at the right time.

Ruby is built for this operating model in infusion billing. It pairs software built for this work with experienced infusion operators who work across the revenue cycle from start to finish, including remittance reconciliation, denial management, and AR prioritization. Practice operators see status and outcomes, with queue logic managed for them. That is the operational requirement behind payer-behavior-based sequencing. The profile has to determine which claim surfaces, which evidence accompanies it, and who can make the recovery decision.