Denial Management
Denials get all the attention, but underpayments quietly drain 1-3% of net revenue at most practices. Here is how to detect contract variances and recover what payers actually owe you.
Every practice watches its denial rate. Far fewer watch their underpayment rate, and that blind spot is exactly why underpayments are so costly. A denied claim is loud: it shows up as unpaid, it ages, and someone eventually works it. An underpaid claim is silent. It posts as "paid," the account closes, and the missing $40 or $150 disappears into the noise of thousands of remittances.
Multiply that small variance across an entire payer mix and a full year of volume, and underpayments routinely cost practices 1% to 3% of net collections. For a group billing $10 million a year, that is $100,000 to $300,000 owed under contract and never collected. This guide explains why underpayments happen, how to find them, and how to build a recovery process that turns silent leakage into recovered revenue.
An underpayment is any claim reimbursed for less than the amount your contract requires. The claim is adjudicated and paid, but the allowed amount falls short of the negotiated rate or fee schedule. This is fundamentally different from a denial, which is why it needs its own workflow rather than being folded into your existing denial management process.
The reason underpayments persist is simple: detecting them requires knowing the exact contracted rate for every code, payer, and plan, and then comparing that expected amount to the actual payment on every line of every remittance. Without that comparison automated, a paid claim looks fine. The variance is invisible unless you are explicitly looking for it.
Underpayments are rarely deliberate. They are the predictable result of complexity in payer systems. The most common root causes:
None of these require bad intent. They simply require that no one on the provider side is checking, which is usually the case.
Are payers shorting you under contract?
Revenue Synergy loads your payer contracts and runs every remittance through automated variance detection, recovering underpayments most practices never see. Part of how we've recovered $500M+ for 500+ providers.
Get a Free Underpayment Audit →A recovery program has four stages. The first is the hardest and the most valuable; the rest are about disciplined follow-through.
You cannot detect a variance without knowing the expected amount. That means digitizing every active payer contract, the rate methodology (percent of Medicare, flat fee schedule, case rate, per diem), the effective dates, and any carve-outs. This is the foundation, and it is the step practices most often skip. Pair it with disciplined coding accuracy so the expected amount is calculated against the correct codes.
For each paid line, the system calculates the expected allowed amount and compares it to what was paid. Any payment below the expected amount, beyond a small tolerance, is flagged. Automating this is non-negotiable: no human can manually price-check thousands of lines a month, and that is precisely why manual processes miss underpayments entirely.
Not every flag is worth pursuing, and some "underpayments" are legitimate (a coordination-of-benefits adjustment, a contractual reduction you forgot about). Group flagged claims by payer, plan, and root cause. Patterns emerge fast: one payer underpaying a specific code family points to a loading error worth a single high-leverage conversation rather than hundreds of individual appeals.
Submit corrected-payment requests with the contract language and expected-amount calculation attached. Small, systemic underpayments are best handled in batches; large or recurring ones may warrant escalation to your provider representative or contract management. Track every recovery to closure, just like the appeals in a mature denial management process, and feed the patterns back into contract negotiations.
The leverage of patterns: One underpaid claim is a $40 appeal. Two hundred claims underpaid the same way by the same payer is evidence of a systemic configuration error, the kind of finding that gets a fee schedule corrected and stops the leak at the source, not just for past claims but for every future one.
It is worth being explicit about the difference, because conflating the two is why underpayments go unworked. Denials are unpaid claims that demand attention. Underpayments are paid claims that don't, until you measure them. A denial workflow is triggered by a remittance code that says "not paid." An underpayment workflow is triggered by math: expected allowed amount minus actual payment. They share appeal infrastructure, but the detection mechanism is entirely different, and a practice can have a stellar denial rate while quietly bleeding through underpayments.
This is also why underpayment recovery belongs in the same conversation as your broader billing KPIs. Net collection rate is the metric that exposes the gap: if your net collection rate is below 97% and your denial management is solid, underpayments are a prime suspect for the missing percentage points.
Practices that stand up a real underpayment program typically see recovery in two waves. The first wave is retrospective: working through the backlog of underpaid claims still within timely filing and appeal windows, often surfacing a meaningful one-time recovery. The second wave is structural: catching systemic errors that, once corrected, stop recurring losses going forward and improve net collection rate permanently.
Revenue Synergy operates contract-variance detection across the revenue cycles we manage, comparing every remittance against loaded payer terms so underpayments are caught and appealed as a routine part of the workflow rather than discovered by accident. It is one of the quieter contributors to the $500M+ we have recovered for clients.
Revenue Synergy benchmarks: Our managed clients run at a 99% clean claim rate and 24-day average AR across 22 specialties. Automated underpayment detection is built into that performance, every paid claim is checked against contract, not assumed correct.
A claim reimbursed for less than the contracted rate. It posts as "paid," which is why it is so easy to miss without automated variance checking.
Roughly 5% to 10% of paid claims are underpaid relative to contract, costing most practices 1% to 3% of net collections.
Load contracts and fee schedules, calculate the expected allowed amount for each line, and compare it to the actual payment on the remittance. Variances below contract are flagged.
Individually, no. In aggregate and automated, absolutely, batched recovery of small variances adds up to real revenue and exposes systemic payer errors worth fixing at the source.
Underpayments are the revenue you already earned, already billed correctly, and simply weren't paid in full. Because the claim shows as paid, the loss is invisible without a deliberate detection process. Build the contract library, automate the variance check, work the patterns, and you convert one of the quietest leaks in the revenue cycle into recovered cash and a stronger net collection rate.
Related: Billing & AR Management · Denial Management Process · Medical Billing KPIs
Think payers are underpaying you? Revenue Synergy manages end-to-end RCM for 500+ providers with $500M+ recovered. Schedule a free revenue audit and we'll check your remittances against contract.