Insurance Underpayment Recovery: Finding the Money You’re Already Owed

Medical Billing & Revenue Cycle Management

Insurance Underpayment Recovery: Finding the Money You're Already Owed

An underpayment isn’t a denial — the payer paid, just not what the contract requires. Underpayments are quiet revenue leakage: they post cleanly, they don’t trigger denial workflows, and they accumulate silently unless something flags them.

How underpayments happen

Fee schedule drift. Payers update fee schedules; practices don’t always load the new ones. When the system expects last year’s allowed amount, this year’s lower payment posts without a flag — even though the contract entitles you to more.

Wrong fee schedule applied. Multi-plan payers maintain different schedules by product. If the claim processes under the wrong schedule — or the system matches it to the wrong one — the payment is wrong from the start.

Bundling and edit differences. The payer’s claim edits may bundle services your contract prices separately, or apply edits your system didn’t anticipate. Some of these are legitimate under payer policy; some contradict the contract.

Units and modifiers. A payer that ignores a valid modifier or reduces units without explanation underpays the line. These are often systematic — the same error across hundreds of claims — which makes them high-value once identified.

Credentialing and enrollment gaps. Claims processing under the wrong provider record or before enrollment completed can pay at incorrect rates. These overlap with credentialing and payer enrollment work.

The recovery workflow

1. Maintain current contracted fee schedules.
Load every payer contract’s fee schedule into the practice management system and update them when payers publish changes. Without current schedules, variance detection is impossible — this is the foundation everything else rests on.

2. Flag variances at posting.
When a paid amount differs from the expected allowed amount beyond a tolerance threshold, the line flags for review instead of posting silently. Tolerances should be tight enough to catch real variances and loose enough to avoid noise — small-dollar rounding differences aren’t worth chasing individually.

3. Validate before pursuing.
Not every variance is recoverable. Check: was the correct fee schedule applied? Were the units and modifiers correct on the claim? Did a legitimate payer edit apply? Is the variance within the contract’s terms? Only validated variances move to recovery — pursuing invalid ones burns payer goodwill.

4. Pursue through the payer’s process.
Validated underpayments go back to the payer through its correction, reconsideration, or dispute process — with the contract language, fee schedule, and claim documentation attached. Document every outreach: dates, reference numbers, and commitments. Payer follow-up discipline matters as much here as in denial work.

5. Aggregate patterns and escalate.
Individual underpayments get corrected; patterns get escalated. When the same variance repeats across claims, it’s a systemic payer issue — raise it through the payer’s provider relations channel with aggregate data. Systematic issues recovered in bulk are where underpayment work pays for itself.

6. Feed findings back to contracting.
Recurring underpayment patterns are also contracting intelligence: they reveal which contract terms are ambiguous, which fee schedules lag, and where the next negotiation should focus. Recovery data should reach whoever negotiates your payer contracts.

What recovery is not

Recovery is not rebilling the patient for the difference — balance-billing protections and payer contracts typically prohibit billing patients for amounts the payer contractually owes. It’s not a substitute for denial management either: denials (no payment) and underpayments (wrong payment) need different workflows, though both start from remittance data. And it’s not a one-time cleanup — fee schedules change, edits change, and new patterns emerge, so variance detection runs continuously.

FAQs

How do we know if we have an underpayment problem?

If you’ve never systematically compared paid amounts to contracted allowed amounts, assume you don’t know — which usually means yes. A sample-based billing audit comparing recent payments against your contracts will quantify it quickly.

What's the difference between an underpayment and a denial?

A denial is the payer’s decision not to pay (adjudicated, with appeal rights). An underpayment is a payment below the contracted amount. Denials go through the appeal workflow; underpayments go through variance detection and the payer’s correction process. See claim rejection vs denial for the related distinction.

Can we bill the patient for an underpaid amount?

Generally no — if the contract sets the allowed amount, the patient can’t be billed for the payer’s shortfall. Balance-billing rules and your payer contracts govern this; when in doubt, treat the variance as a payer issue, not a patient balance.

How far back can we recover underpayments?

It depends on the payer’s correction timeframes and your contract terms — which is another reason to detect variances at posting rather than discovering them a year later. Older variances face steeper procedural barriers.

Do small variances matter?

Individually, rarely. In aggregate, often enormously — a $3 variance across 10,000 claims is $30,000. This is why pattern detection matters more than individual variance chasing.

Who owns underpayment recovery — us or our billing partner?

Whoever posts payments should flag variances; whoever manages payer relationships should pursue them. In outsourced arrangements, make sure variance reporting is visible to you — see outsourced medical billing. Fee schedule maintenance should have a named owner either way.

Let’s Talk About Your Billing

Find out where your revenue cycle stands — and what it would take to improve it.