Payer Payment Variance Analysis: How to Find Underpayments

Underpayments rarely show up as denials. The claim is adjudicated, the payment is posted, the account balance goes to zero, and nobody looks at it again. Whether the payer used your contracted rate is a separate question, and most billing workflows never ask it.

This post covers how to compare what payers paid against what your contracts say they should pay, how to separate real errors from legitimate adjustments, and how to decide which ones to dispute.

What Is Payer Payment Variance Analysis?

Payer payment variance analysis compares the allowed amount a payer used on a claim line with the amount your contract specifies for that service. The gap is the variance. A negative variance is an underpayment. A positive one means the payer allowed more than expected, which can lead to a recoupment request later, so it is worth noting.

You do this at the CPT-code level, by payer and plan. It only works if you know your contracted rates, so if those are not organized yet, start with our post on payer contract management.

Why Underpayments Go Unnoticed

Payers price claims through automated systems, and those systems depend on how the contract was loaded. If a fee schedule update was missed, or a claim was matched to the wrong product line, the payer will pay the wrong amount on every claim affected, with no denial and no flag.

A quick example with made-up numbers: your contract allows $120 for CPT 99214, and a payer is allowing $104. The difference is $16 per visit. At 300 visits a month, that is $4,800 a month, or $57,600 a year, from one code with one payer. Most practices have several codes and several payers, so a small per-claim error can add up to a large total.

What You Need Before You Start

You need three sets of data:

• Your contracted fee schedule for each payer, with effective dates
• Remittances (ERA files or EOBs) showing allowed amount, paid amount, and adjustment codes; our post on ERA vs. EOB explains how the two differ
• Claim details such as date of service, CPT code, modifiers, units, and plan name

Payment posting quality matters here. If contractual adjustments and other adjustments are posted into one bucket, you cannot tell which differences are expected.

How to Run the Analysis

1. Build the expected-rate table

Create a table with payer, plan, CPT code, and the expected allowed amount. Use the fee schedule that was in effect on the date of service, since rates often change mid-year. If your contract pays a percentage of Medicare, work out the dollar figure for each code using the correct year and your locality.

2. Pull actual allowed amounts

Export paid claim lines for a period, such as the last 90 days. Use the allowed amount from the remittance, not the paid amount. The paid amount has copays, deductibles, and coinsurance taken out, which hides the rate the payer applied.

3. Calculate the variance

Subtract the actual allowed amount from the expected amount for each line, then group the results by payer, code, and month. A spreadsheet can handle this the first time. Billing systems with reporting tools can automate it once you know what you are looking for.

4. Remove the differences that are correct

Some variances are not errors. Check each one against the usual reasons:

• Multiple procedure reductions on the same date
• Modifier pricing, such as reduced rates under modifier 50 or 51
• Bundling edits applied according to the contract
• Payer-wide adjustments such as Medicare sequestration
• A different plan or product than you assumed

What remains is the list that needs review.

5. Rank by total dollars and dispute the patterns

Sort by total variance, not by the gap on a single claim. A $6 difference across 400 claims is worth more than a $90 difference on two. Look for repeats: same code, same payer, same direction.

For each pattern, collect a few sample claims, the page of the fee schedule or contract that sets the rate, and the remittances showing the lower allowed amount. Then send it through the payer’s process for contract underpayments. Many payers handle these separately from regular appeals, so check the provider manual or ask your payer representative.

Common Causes of Underpayments

When you look at what the analysis turns up, the causes tend to repeat:

• A new fee schedule was never loaded
• The claim was priced under the wrong contract or product line
• A modifier was interpreted incorrectly
• A scheduled rate increase did not take effect
• Units were reduced or misread
• A carve-out rate for specific services was ignored

Knowing the cause matters because it changes your request. Instead of asking for one claim to be reprocessed, you can ask the payer to correct the rate setup and reprocess everything affected.

How Often to Run It

For your largest payers, run it monthly. Do a broader review across all payers every quarter. Add an extra check whenever a payer sends notice of a fee schedule change or when a contract renews, since new rates are when loading errors tend to happen.

Keep a simple log with the payer, the code, the issue, the amount, and the outcome. After a few months, it shows which payers have repeat problems, and that record is useful at the next contract negotiation.

When to Get Outside Help

This work needs clean posting data, contract rates in a usable format, and someone with time to follow disputes through. When a team is already busy with daily billing, variance analysis is usually the task that gets pushed back. Rapid RCM Solutions provides payment posting, reporting, and AR and denial management, which lets practices check payments against contracts as part of regular billing instead of treating it as a separate project.

Conclusion

Compare expected and actual allowed amounts, remove the differences that have a valid reason, and dispute the patterns that remain. Running this monthly for your biggest payers usually catches most contract underpayments while the dispute window is still open.

Frequently Asked Questions

rapid_admin