A claim paid below the contracted rate looks identical to a correctly paid claim in every standard report. It is not a denial, it does not age, and nothing flags it — only a variance comparison against the fee schedule finds it.
Denials are loud. They arrive with a code, land in a queue, and somebody works them. Underpayments are silent — the claim paid, the balance cleared, the report shows success. Nothing signals that the amount was wrong.
How they happen
- The payer loaded the wrong fee schedule. Common after a contract renewal, and it persists until somebody notices.
- A rate update never applied. Your contract escalates; their system does not.
- Multiple-procedure reductions applied incorrectly, or applied where the contract does not allow.
- Modifier pricing ignored, so a service that should pay at a different rate pays at the base.
- You billed below the allowable. Then the underpayment is yours — the payer paid exactly what you asked.
Why standard reporting misses them
Reporting is built around what was collected versus what was expected, and "expected" is usually derived from what the payer historically pays — which bakes the underpayment into the baseline. A claim paid at the wrong rate consistently becomes the expected rate.
Finding them
The method is unglamorous: take each remittance line, look up the contracted allowable for that code and payer, and compare. At scale this needs your fee schedules loaded and the comparison automated, which is the work most practices have never done.
Start smaller. Pick your top ten codes by volume and your top three payers — thirty combinations. Compare a month of remittances. Any recurring gap is worth a conversation with the payer, and the same gap has almost certainly been running for as long as the contract has.
They are systematic, which is good news
Underpayments rarely occur at random. When a rate is wrong it is wrong on every claim for that code and payer, which means finding one usually means finding hundreds.
That also makes them recoverable in bulk rather than claim by claim, and worth the effort of a proper comparison.
Start with a sample
Twenty high-volume codes, three largest payers, one month of remittances. If the rates match, the problem is elsewhere. If they do not, you have found a systematic error and can size it before investing in tooling.
Recheck after every change
Contract renewals, fee schedule updates and payer system migrations all introduce this. Building the check into those events catches it in the first month rather than the following year.
Common questions
- How do I find underpaid claims?
- Compare remittance line amounts against your contracted fee schedule. There is no other way, because underpaid claims appear as paid in every standard report.
- Why do underpayments happen?
- Most commonly a fee schedule not updated after renegotiation, on the payer’s side or yours. Also incorrect contract assignment and outdated code rates.
- How much money is usually involved?
- It depends, but because underpayments are systematic rather than occasional, a small per-claim variance across a year of volume adds up substantially.
- Can I recover past underpayments?
- Often yes, subject to the contract’s reconciliation provisions and any lookback limit. Bring a claim list rather than a complaint.
- How often should I check?
- At least after every contract change, and periodically otherwise. A sample of your top codes and top payers is enough to detect a systematic problem.
Denials Piling Up?
We handle the revenue cycle end to end — coding by certified coders, claim submission, denial management and appeals, and A/R follow-up, with six reported numbers every month.