Underpayment Detection and Contractual Analytics

Underpayment Detection and Contractual Analytics#

Not every revenue leak is a denial. A claim can be *paid* — just paid less than the contract requires. Detecting underpayments is a distinct, high-value RCM discipline.

The mechanism. Every in-network claim carries a contractual write-off, reported as CO-45 (charge exceeds the contracted/allowed amount). The expected allowed amount comes from the negotiated fee schedule in the payer contract. An underpayment occurs when the payer's allowed/paid amount is *below* the contracted rate — the CO-45 write-off is larger than it should be.

How to detect it. Load the contracted fee schedules, then for each paid service line on the 835, compare the payer's allowed amount to the contracted expected amount. Variances below the expected rate are underpayments to recover; variances above may indicate overpayments to reconcile.

Why it is missed. Underpaid claims look "paid" and sail through manual posting unnoticed. Only a systematic, contract-aware comparison catches them. At scale, small per-claim underpayments add up to substantial recoverable revenue.

Related analytics.

• Net collection rate measures how much of the contractually collectible amount was actually collected — underpayments depress it.
• Contractual allowance analysis tracks CO-45 write-offs against expected contract terms to flag fee-schedule load errors and systematic payer underpayment.
• Denial analytics classify denials by CARC/RARC to find systemic root causes.

In RCM and AI strategy: underpayment detection is a quantitative, rules-plus-data problem ideal for automation — compare expected vs. actual at the line level, flag variances, and route recoverable underpayments to follow-up. It is one of the clearest "find hidden money" use cases in revenue cycle analytics.