The Economics of Underpayments: Why Providers Focus on Denials but Miss Larger Revenue Losses
July 8, 2026|Read 12 min|Blog
The Economics of Underpayments: Why Providers Focus on Denials but Miss Larger Revenue Losses
Here's the deal. Your billing team is running denial reports every week. The appeal queue is staffed. The denial rate is tracked to decimal points and reviewed in monthly leadership meetings. The operation looks rigorous, and by the metrics most practices use, it is. But there's a category of revenue loss that none of those dashboards are measuring because the money in question was already paid. Just not paid correctly.
Underpayments are the silent version of the same problem denials represent. A denied claim is revenue not received. An underpaid claim is revenue not fully received. The financial outcome is structurally identical collectible dollars that earned and don't reach the practice. But the operational response is completely different, because denials generate worklists and underpayments generate nothing. The claim processes, the payment posts, the account closes, and everyone moves on. The $40 shortfall gets absorbed into the remittance as a contractual adjustment nobody questions, the $25 variance disappears into the payment posting workflow, and the $15 discrepancy on a routine code never surfaces because the claim is technically resolved and the AR shows zero. Multiply those variances across tens of thousands of annual encounters, and the cumulative loss in many organizations exceeds what denials cost on claims that were never denied, never appealed, and never flagged by any report anyone ran.
The Blind Spot Hidden in Plain Sight
The reason underpayments persist isn't that practices don't care about the money. It's that the standard revenue cycle infrastructure isn't designed to find them. Denial management works because denied claims are visible they sit in a worklist, they age in AR, they generate reports, they create urgency. Underpaid claims don't do any of those things. They close. They're gone. The only way to find them is to run a comparison between what the contract says the claim should have paid and what the remittance actually shows and most practices have never built that comparison into their payment posting workflow.
This creates what amounts to a measurement problem masquerading as a billing problem. Organizations are measuring collection activity how many claims were submitted, how many paid, what's the denial rate, what's the first-pass rate without measuring collection accuracy. Activity and accuracy are different metrics with different implications. A payer can maintain a low denial rate and excellent adjudication speed while consistently reimbursing below contracted amounts on thousands of claims. From the denial dashboard, everything looks fine. From the revenue perspective, the practice is losing money on every one of those claims, and nothing in the standard reporting stack surfaces that fact.
Why the Problem Is Bigger Than It Looks
The scale of underpayment exposure in most practices is genuinely surprising once it gets measured. It doesn't feel like a large problem because individual variances are small. A $15 difference between expected and actual reimbursement on a routine office visit doesn't register as a financial crisis. A $40 shortfall on a procedure gets absorbed without comment. A modifier processing error that costs $60 per claim on a high-volume code gets posted as received without anyone checking whether the modifier triggered the right calculation. None of these feel significant in isolation. They're catastrophic in aggregate.
The compounding dynamic is what makes underpayments financially dangerous at the practice level. Payer processing errors, when they occur, typically affect entire claim populations every claim with a specific modifier, every claim on a specific fee schedule, every claim in a specific geographic payment area not individual claims. When a fee schedule update fails to load correctly at a payer, the error doesn't affect one claim. It affects every claim that hits that fee schedule until someone identifies and corrects it. That timeline can span months. The revenue impact of a systematic processing error running uncorrected for 90 days across a high-volume code category is a number that would generate significant attention if it showed up as a denial spike. When it shows up as small per-claim variances on paid claims, it generates no attention at all.
Three Root Causes That Explain Most Underpayments
Understanding where underpayments come from is the prerequisite for building a recovery strategy, because the cause determines the fix. Contract misinterpretation is the first major source. Payer contracts are genuinely complex documents multiple fee schedules, carve-outs, modifier rules, bundling exceptions, specialty-specific reimbursement provisions, annual rate escalators. Even experienced billing teams struggle to translate every reimbursement methodology into the expected payment calculations they'd need to identify a variance. Payers process claims according to their interpretation of the contract terms. Practices assume a different interpretation. The gap between those interpretations generates underpayments that persist indefinitely because neither party has surfaced the discrepancy and neither system is automatically flagging it.
Systematic payer processing errors are the second source, and they're distinct from misinterpretation because they're not about disagreement they're about operational failures on the payer's side. Incorrect fee schedule loading, outdated reimbursement tables, modifier processing logic that hasn't been updated to reflect current policy, geographic adjustment mistakes, multiple procedure discounting inaccuracies. When these errors occur, the payer's system is applying the wrong calculation to a correct claim, and the result is an underpayment that the payer may not even be aware of unless the provider brings it forward with documentation. These errors can run at scale across large claim populations before anyone notices, precisely because the claims are processing and paying just paying incorrectly.
The third root cause is the absence of reimbursement variance analysis itself. Most revenue cycle teams focus on whether claims were paid, not whether they were paid accurately. Without a systematic comparison of expected reimbursement against actual reimbursement at the claim level, underpayments become accepted as routine business operations. The variance doesn't register as a problem because there's no process looking for it. This is a structural gap in the billing operation, not a payer behavior problem and it's the one that practices have the most direct control over.
Why Denials Get the Attention and Underpayments Don't
The psychology here is worth naming explicitly, because it explains why this imbalance persists even in sophisticated billing operations. Denials create immediate, visible pain. They increase AR days. They generate appeal workloads. They delay cash flow. They produce escalating operational costs that leadership feels and responds to. Underpayments create none of those warning signs. Cash arrives. Claims close. Revenue appears to flow normally. The billing operation looks productive. The metrics look reasonable. Nothing in the standard reporting architecture raises an alert, so nobody investigates, and the losses accumulate silently in the gap between what was contractually owed and what was actually paid.
The system failed them; they didn't fail the system. The billing teams that never built underpayment variance analysis weren't negligent they were responding rationally to a reporting environment that surfaces denial problems loudly and underpayment problems not at all. The leadership that reviews denial rates weekly without reviewing reimbursement accuracy monthly isn't making a bad decision they're making the decision their available data supports. The payment posters who absorb small variances without flagging them aren't missing something obvious they're processing remittances in a workflow that was never designed to make variance detection part of the job. Fixing the problem requires changing the infrastructure, not the people.
What Reimbursement Variance Analysis Actually Looks Like
Building an underpayment recovery capability starts with contract modeling converting payer contract terms into clear expected payment calculations for each code, modifier combination, and fee schedule so that the billing operation knows what each claim should pay before the remittance arrives. That model becomes the comparison point for variance detection: when actual reimbursement falls outside an acceptable threshold from the expected amount, the claim generates a flag rather than closing automatically. The threshold matters you don't want to investigate every $2 rounding difference, but you do want to catch every $50 variance on a high-volume code and every $200 variance on a lower-volume procedure.
Root cause analysis is what converts individual variance flags into recovery leverage. The question isn't just "this claim was underpaid" it's "why was this claim underpaid, and is the same issue affecting other claims?" A single underpaid claim is a billing dispute. A pattern of underpaid claims on the same CPT code across the same payer is a systematic processing error or contract interpretation problem that can be escalated to provider relations with documented evidence covering dozens or hundreds of affected claims simultaneously. Data-driven conversations with payers are significantly more effective than claim-by-claim disputes, because the payer's incentive to correct a systematic error is proportional to the documentation that demonstrates the error is systematic.
Signals That Underpayments Are Already Costing Your Practice
These patterns in your payment data tell you that reimbursement accuracy is a problem, even if the denial rate looks healthy and the AR appears stable.
Net collection rate consistently below your expected percentage of allowable reimbursement without a denial volume explanation. If you're collecting less than contracts suggest you should be collecting, and denials don't account for the gap, underpayments are filling it. The math is straightforward once you're measuring the right numerator.
Payment variance on the same CPT code across multiple remittances from the same payer over a 60-to-90-day window. Inconsistent reimbursement on the same code from the same payer almost always indicates a fee schedule loading error or modifier processing inconsistency that is affecting a much larger claim population than the individual variances suggest.
No formal process for comparing actual remittances against contracted rates before claims close. If payment posting is a data entry function rather than an audit function in your current workflow, underpayments are passing through undetected by design. The absence of the process is itself the signal.
Defending Revenue on Both Sides of the Equation
The strategic shift that solves this problem is recognizing that revenue cycle management has two financial enemies: revenue not received and revenue not fully received. Denial management addresses the first one. Reimbursement variance analysis addresses the second. Both are required for a complete revenue protection strategy, because a billing operation that's excellent at denial recovery but blind to underpayments is still leaking money on every paid claim that settled below contract and that leak has no natural stopping point without a system designed to find it.
If your practice needs revenue cycle support, denial management, or billing optimization, Medisure can help your clinical teams verify, submit, and collect with confidence. Underpayment recovery is one of the highest-return investments in Medical Billing infrastructure, precisely because the revenue is already being earned and already being partially paid the gap between partially and fully is what systematic variance analysis closes, and it closes it on claims that have already passed every other quality check in the revenue cycle.
Conclusion
The future of revenue cycle performance isn't just reducing denials. It's maximizing reimbursement accuracy measuring not just whether claims were paid but whether they were paid correctly, and building the infrastructure to recover the difference when they weren't. The practices that get there first will find a revenue stream they didn't know they had, on claims that were already processed and already closed, in a part of the billing cycle nobody was watching. That's the Revenue Building opportunity that underpayment analysis unlocks and it's available to every practice willing to add collection accuracy to the metrics they already track for collection activity.
Start with one payer, one high-volume code, one 90-day remittance window. Pull the actual payments. Compare them to the contracted rate. Calculate the variance. If the variance is consistent and directional always below, never above you've found a systematic underpayment that a documented escalation to provider relations can recover. That single exercise, run quarterly across your top payers and top codes, is the starting point for the reimbursement accuracy infrastructure that protects the revenue your billing operation has already done the work to earn.
On we go.
FAQ
What is an underpayment in medical billing and how is it different from a denial?
A denial is a claim that was rejected and not paid, generating an immediate worklist and appeal obligation. An underpayment is a claim that was processed, adjudicated, and paid but paid at an amount below the contracted rate. Because underpaid claims close normally in the billing system, they generate no automatic alerts, no AR aging, and no appeal triggers. The financial outcome is similar to a partial denial, but the operational response is completely different because the standard revenue cycle infrastructure isn't designed to detect claims that were paid incorrectly versus claims that weren't paid at all.
What causes payers to underpay claims?
Underpayments typically stem from three sources: contract misinterpretation, where payers apply a different understanding of contract terms than the practice assumes; systematic processing errors, including incorrect fee schedule loading, outdated reimbursement tables, modifier processing mistakes, and geographic adjustment errors; and the absence of reimbursement variance analysis on the provider side, which allows discrepancies to accumulate undetected. Not all underpayments are intentional many result from operational failures in payer systems that persist until a provider documents and escalates the discrepancy with supporting data.
How does reimbursement variance analysis work?
Reimbursement variance analysis compares expected reimbursement calculated from contracted rates, fee schedules, and modifier rules against actual reimbursement received on each claim. Claims where actual payment falls outside an acceptable variance threshold get flagged for review rather than closing automatically. Root cause analysis then identifies whether the variance is isolated or part of a pattern affecting multiple claims on the same code, modifier combination, or fee schedule. Pattern-based findings become the basis for payer escalation with documented evidence, which is significantly more effective than disputing individual claims one at a time.
Why do most practices focus on denials instead of underpayments?
Denials create immediate, visible operational pressure increased AR days, appeal workloads, delayed cash flow, escalating costs. These signals drive urgency and investment. Underpayments create none of those warning signs because the claim pays, the account closes, and revenue appears to flow normally. The measurement infrastructure most practices use tracks collection activity rather than collection accuracy, which makes denial problems visible and underpayment problems invisible. The imbalance persists not because underpayments are less important but because the standard reporting architecture surfaces one problem loudly and the other not at all.
How does Medisure help practices identify and recover underpayments?
Medisure builds reimbursement variance analysis into the payment posting workflow converting payer contracts into expected payment models, flagging claims where actual reimbursement falls below contracted rates, and conducting root cause analysis to identify systematic patterns rather than chasing individual variances. When patterns are documented, Medisure supports payer escalation with data-driven evidence that recovers underpayments at scale and builds the Medical Billing accountability structure that prevents future underpayments from accumulating undetected in paid claim populations.