Contract Variance Analysis, Explained Without Jargon

Variance analysis sounds like consulting vocabulary. The operation is simple: for every line the payer paid, compare what they allowed against what your contract says they should have allowed, and list the differences.

What it needs

• Your fee schedules, per payer, in a form a system can read.
• Line-level remittance data, which is why ERA enrollment matters — a paper remittance cannot support this.
• The contract rules: multiple-procedure reductions, modifier pricing, bundling terms.

What it produces

A list of claims, each with an expected amount, an actual amount, and a difference. Not an impression that a payer underpays. A number, with the claims that make it up.

That distinction is what makes it useful in a payer conversation. "We believe you underpay us" invites a discussion. "These four hundred claims paid below contract, here is the file" invites a correction.

What it usually finds

Three patterns. A specific code paying at the wrong rate consistently, which is a fee schedule loading error. A rate increase that never applied. And reductions applied where the contract does not permit them.

All three are systematic rather than random, which is the good news — a systematic error has a single fix and often a retroactive correction attached.

Starting without tooling

You do not need a platform to begin. One payer, your ten highest-volume codes, one month of remittances, and a spreadsheet will tell you whether there is anything here. If there is, the case for doing it properly makes itself.

Start with volume, not with suspicion

The instinct is to check the payer you distrust. The better first pass is your highest-volume codes with your largest payers, because a small per-claim variance across thousands of claims outweighs a large one on a handful.

Twenty codes and three payers is an afternoon and usually answers whether there is a problem worth tooling for.

Check after every renewal

The most common cause of systematic underpayment is a fee schedule that was renegotiated and never updated in the payer’s system or in yours. It pays at the old rate silently, on every claim, until somebody compares.

Build the check into the renewal process rather than discovering it a year later.

Bring the claim list

A conversation that opens with "you are underpaying us" goes nowhere. One that opens with a spreadsheet of claim numbers, dates, expected and actual amounts is a reconciliation the payer can act on.

That is the whole reason the exercise is worth doing rather than complaining.

Getting the fee schedules is half the work

Many practices do not hold current fee schedules for their own contracts, or hold them as PDFs that cannot be compared against anything. Requesting them in a usable format from each payer is the first task and frequently the slowest.

Payers are generally obliged to provide the rates you contracted for. Persistence is usually what is required rather than permission.

Distinguish variance from reduction rules

Multiple procedure reductions, bilateral adjustments and assistant-at-surgery percentages all produce payments below the base allowable that are entirely correct.

An analysis that does not account for them generates false findings, and a first conversation with a payer built on false findings damages the credibility you need for the real ones.

Report it as a claim list

Payers respond to specifics. A file of claim numbers, dates of service, codes, expected and actual amounts, with a total, is a reconciliation request they can process.

Set a follow-up date when you send it. Underpayment recoveries stall quietly more often than they are refused.