A claim goes out, and sixty days later a payment comes back. The claim shows paid. It clears the aging report, drops off the AR dashboard, and nobody looks at it again — because “paid” reads as done, even when the amount was wrong.
That’s the exact blind spot behind PayerLenz’s benchmark data: underpaid is not the same problem as denied, and most billing operations are built to catch only one of the two.
- A denied claim triggers a workflow — a code, a deadline, someone assigned to fight it. An underpaid claim triggers nothing. It just closes, quietly, for less than it should have.
- The same payer group can allow $675 a day or more than $2,900 a day for the same level of care in the same state, so a payment on its own carries no signal about whether it was correct.
- Without an expected amount built from what that payer has actually allowed, there is nothing to compare a payment against. That absence is why underpayments stay invisible.
- Closing the gap requires reconciling every claim against an expected rate, not just watching for denial codes.
Why Underpayments Don’t Look Like a Problem
Every billing workflow is built around exceptions: a denial code, a rejected claim, a missing authorization. Those trigger a task, a deadline, a person assigned to fix it. An underpaid claim triggers none of that — it was accepted and paid, just for less than the contract or the market actually supports.
The claim closes. The aging report shows a zero balance. The only way to catch the gap is to already know what the payer should have paid, and compare it against what actually arrived — a check that most operations have no data to run.
- Rejected outright, with a reason code attached
- Triggers a follow-up task and a deadline
- Gets tracked until resolved or written off
- Accepted and paid, just for less than expected
- Triggers nothing — it reads as closed
- Stays invisible without a rate to compare it against
This is a different failure than the one covered in denial root-cause resolution. Denials are a fight you know you’re in. Underpayments are a fight you don’t know is happening.
Where the Feedback Loop Actually Breaks
An active benefit isn’t a rate covers the first half of this problem — a VOB confirms coverage, not what a payer will actually allow. The second half is what happens after the claim is paid: almost nobody goes back and checks the VOB’s implied expectation against the EOB’s actual number.
The VOB said one thing at admission. The EOB said something else two months later. Without a reconciliation step, that gap repeats on every claim, every payer, every month, indefinitely — not from bad intent, just from nobody building the step that would catch it. That reconciliation step is the missing control, and reconciling paid against expected on every remit is what surfaces the pattern before it repeats for a year.
The money lost to a bad rate assumption almost never shows up as a denial. It shows up as a number that’s simply lower than it should have been, and nobody flagged it.Kyle McHenry, Founder, Revenue Logic
Federal oversight backs up how common processing gaps are industry-wide. The Departments of Labor, HHS, and Treasury’s 2024 parity enforcement report found claims-processing and disclosure violations affecting mental health and substance use benefits specifically, separate from the parity-comparison violations it’s best known for.
HFMA’s revenue cycle research tracks denied and underpaid dollar amounts climbing industry-wide year over year, on top of whatever gap already existed at any single facility.
What Closing the Loop Actually Looks Like
Closing the gap means comparing every paid claim against an expected rate built from real adjudicated data, not spot-checking the ones that look suspicious. Suspicious isn’t the tell here — underpaid claims are specifically the ones that don’t look suspicious at all.
A denial gets noticed because someone has to fight it. An underpayment doesn’t, because nothing about it looks wrong on the surface. That’s exactly why it’s the more expensive problem over time — it compounds silently instead of getting escalated.
This is also why underpayment recovery has to run as an ongoing reconciliation, not a one-time audit. New claims are paid every week, and each one needs the same expected-versus-actual check the last batch got.
How is an underpaid claim different from a denied claim?
A denied claim is rejected outright and triggers a follow-up workflow. An underpaid claim is accepted and paid, just for less than it should have been — and because it’s technically “paid,” it doesn’t trigger any of the usual follow-up steps.
How much revenue do underpayments typically represent?
It varies by payer mix, out-of-network share and claim volume, and no general figure would describe any particular facility. The only way to size it is to compare a facility’s own paid amounts against expected rates built from what those payers have actually allowed.
Can underpayments be recovered after a claim has already closed?
Often, yes — many payer contracts allow reconsideration or appeal within a window after payment, but only if the underpayment is caught. Without a reconciliation step, most never are.
If you want to see what a real reconciliation finds in your own claims, reach out to Revenue Logic and we’ll walk through it.
- Reconciles paid claims against expected rates, not just denials
- From the billing professionals at Revenue Logic
