The Underpayments Nobody Is Checking For

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.