How to find payer underpayments nobody is looking for

Every exception report a practice runs is built to find claims that did not pay. Underpayments pay. They arrive as ordinary remittances, post normally, close the account, and appear on nothing.

That is what makes them the quietest loss in the revenue cycle. A denial is annoying and visible. An underpayment is invisible and permanent, and it repeats on every claim for the same code until somebody notices.

You need an expected amount

The entire function depends on one thing: knowing what should have been paid. Without a contracted expectation there is nothing to compare against, and "this looks low" is not a position anybody can take to a payer.

That means the contracted rates have to be loaded and maintained — whether they are a fee schedule, a percentage of a published rate, a case rate or a tiered arrangement — and updated when contracts renew. It is the unglamorous prerequisite, and without it the question “are we being paid what we agreed” cannot be answered at all.

Compare, then group

With an expected amount in place, the comparison is mechanical: for every paid line, expected against actual, with the difference and the reason for any legitimate adjustment.

The output should never be worked as a list of individual claims. It should be grouped, because that is where the diagnosis is:

• By code — a single procedure paying below contract across many claims.
• By modifier — a modifier combination the payer is processing differently from the contract.
• By place of service — a site paying at the wrong schedule.
• By date range — a rate change applied late, early, or not at all.
• By provider — one provider’s claims paying differently, which usually indicates an enrollment or contract-linkage problem rather than a rate problem.

A pattern is one conversation. Four hundred individual reconsiderations is a year of somebody’s life.

Evidence, not argument

A recovery request that says the payment looks wrong gets nowhere. One that attaches the contract clause, the claim as submitted, the remittance as received, and the arithmetic showing the expected amount, is difficult to refuse.

Assembling that package is most of the work in this queue, and it is the part that separates a seat that recovers money from one that files complaints.

The legitimate reasons a payment is lower

Before raising anything, rule out the explanations that are not underpayments:

• Multiple procedure reductions and other contractually agreed reductions.
• Bundling the contract permits.
• Patient responsibility applied to deductible or coinsurance — a lower payer payment, not a lower allowed amount.
• A takeback or offset applied on the same remittance for an earlier claim.
• Coordination of benefits, where another payer is primary.
• A different rate that genuinely applies to that site, provider or plan product.

A seat that raises these as underpayments damages the practice’s credibility with the payer, which makes the genuine cases harder. Filtering them out is part of the job, not a nicety.

Mind the clock

Contracts commonly limit how far back a reconsideration can reach, and that period is sometimes shorter than the appeal window for a denial. A variance identified outside the window is a lesson rather than a recovery.

This is why the comparison should run on a regular cycle rather than as an annual project. Monthly variance beats an annual audit that finds a great deal of money nobody can now claim.

What to define before starting

The contract source

Where the current rates live, who maintains them, and how a renewal reaches the person maintaining them.

The materiality threshold

Below some amount, pursuing a single variance costs more than it recovers. Set the number, and set it separately for patterns, because a small per-claim variance across hundreds of claims is material even when each instance is not.

The evidence pack

What every recovery request must contain before it is sent.

The escalation route

When a pattern stops being a claims issue and becomes a contract or provider relations conversation — and who at the practice owns that.

The cycle

How often the comparison runs. Monthly is a reasonable default; quarterly risks the contractual window.

How to assess it

• What variance was identified this period, by payer and by pattern?
• How much was requested, and how much was recovered?
• How many requests were rejected, and on what grounds?
• Which patterns recur, and has any of them been raised as a contract conversation?
• Are the loaded rates current for every payer, and when were they last checked?
• Was anything found outside its contractual window, and why was it late?

How Soft Home Global staffs this

Soft Home Global provides trained full-time back-office seats from Rawalpindi, Pakistan. Underpayment recovery and contract variance is published at $1,900 per seat per month, billed per seat with a one month minimum. It is a seat rate, not a percentage of recoveries — the incentive is to run the comparison properly every month rather than to chase whatever is largest.

The seat works US hours inside your system: running the comparison against the rates you maintain, filtering out the legitimate reductions, grouping what remains into patterns, assembling the evidence pack for each request, following up until a decision exists, and flagging any pattern that belongs in a contract conversation rather than a claims one.

The first thing to check

Pick your largest payer and your five highest-volume codes. Compare last quarter’s payments against the contracted rate for each. It is a morning’s work and it answers a question most practices cannot currently answer at all: are we being paid what we agreed?

If the answer is no on even one code, the arithmetic across a year is usually enough to justify running the comparison every month from now on.