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.