Notes on payer behavior
The zero-balance problem: why underpaid claims look paid
The zero-balance problem is this: a claim that was paid short of your contracted rate closes in your billing system exactly the way a correctly paid claim does. Balance zero. Status paid. No work queue, no flag, no report. The shortfall isn't hidden by anyone. It's hidden by the design of posting itself. Independent practices lose 1 to 3 percent of net revenue this way on average, and no one on the team is doing anything wrong.
Why a short payment posts as paid
Walk through what happens when a remittance arrives. The payer's 835 says: billed $1,412, allowed $1,180, paid $1,180, adjustment $232 with reason code CO-45, "charge exceeds fee schedule or contracted fee arrangement." Your practice management system does what it's built to do. It posts the payment, posts the adjustment as a contractual write-off, and closes the line. The balance is zero.
Nothing in that workflow asks the one question that matters: was $1,180 the contracted rate? If your contract says $1,412 for that code, the payer just kept $232 and labeled it your write-off. The system accepted the label. That's the whole problem. Posting trusts the payer's arithmetic because checking it, line by line, against a fee schedule, is a different job from posting.
Why nobody catches it
Three reasons, and none of them is a bad biller.
- Billers are measured on claims moving. Their day is submitting, fixing rejections, working the denial queue. A paid claim is a finished claim. Reopening finished work is not in the job.
- The shortfalls are small per line. Two, four, eight percent under contract. A $44 difference on a $142 visit. Nobody stops for $44. It only matters across a year of volume, and nobody sees the year.
- Fee schedules live in a drawer. Most practices of 3 to 15 physicians don't have their contracted rates loaded anywhere a computer can compare them. The contract is a PDF. The remittance is a file. They never meet.
Hospital systems staff whole teams for this. They call it zero-balance review or payment variance analysis, and it's routine at that scale. Below that scale it mostly doesn't happen, which is why the shortfalls concentrate exactly where no one is watching.
What a zero-balance review actually is
A zero-balance review takes claims that closed at zero and recomputes each line: what did the contract say this code should pay, what did the payer allow, what's the gap. That's it. No clinical judgment, no coding change. Arithmetic against a document you already signed. The output is a list of lines where allowed came in under contract, grouped by payer and by reason.
The reasons cluster. Across specialties we see the same handful:
- A stale fee schedule. You renegotiated; the payer's system still pays last year's rates. Every line is short by the same percentage, indefinitely.
- Downcoding. The paid code is one level below the billed code. Clean arithmetic on the wrong code. Its own note.
- Misapplied multiple-procedure reductions. The second procedure cut to 50 percent is fine. The highest-valued procedure cut to 50 percent because the payer ranked by billed charge instead of fee-schedule value is not.
- Bundling edits your contract doesn't allow. A payable add-on absorbed into the primary code at $0.
- Out-of-network rates on in-network claims. A credentialing hiccup, a wrong tax ID, and a quarter of claims paid off the wrong schedule.
How to run one without new software
You don't need a platform. You need three things and an afternoon.
- Your 835 files for the last 12 months. Your clearinghouse or each payer's portal has them. Twelve months matters because that's Florida's non-waivable window for underpayment claims on state-regulated plans (the 12-month rule).
- Your fee schedules. The contracted rate per code for each payer. If a payer never gave you one, ask for it in writing. They are required to provide it on request under most contracts and, in Florida, under the prompt-pay statute.
- Your top 20 codes by volume. Start there. In an orthopedic or pain practice, twenty codes usually cover 80 percent of the revenue.
For each payer, pull allowed amount by code from the 835s and set it next to the contract rate. Where allowed is below contract, that's a finding. Sum it. Most practices that do this for the first time find a number that changes the conversation. When we audited a full year of claims at a four-physician orthopedic group in Miami-Dade, 30 percent of net insurance revenue had been paid short or denied for reasons that could have been fixed. That practice had good billers. The money was in the zero balances.
What to do with the findings
Group them by payer and by reason, then pursue each group as one case, not one claim. A stale fee schedule is a single letter with a claim list and the contract page attached. A misapplied multiple-procedure reduction is a single reconsideration with the ranking rule spelled out. The mechanics, deadlines, and what to put in the packet are in how to appeal an underpaid claim. Move fast on the oldest lines. Contractual dispute clauses run 90 to 180 days, and whatever ages past the window is gone.
The so-what
A zero balance is not evidence a claim was paid correctly. It's evidence the posting workflow finished. Until someone recomputes the line, you're taking the payer's word for your own contract. Once a year, for your top codes and top payers, is enough to know whether the word is good. If you'd rather not spend the afternoon, that recompute is exactly what Clearia's diagnostic does, on every line, at no cost.