Contracts

Payer underpayment detection: a repeatable checklist

A practical checklist for deciding whether a payment line is a genuine rate mismatch, an expected contractual write-off, or a payment that only looks low.

By PayerBeacon · Published · Updated

Written and edited by PayerBeacon. Sources are listed below with the date each link was checked.

How do I tell whether a payer actually underpaid a claim?

Compare the approved contract rate with the payer allowed amount for the same code, modifier, units, and date of service, then read every adjustment before calling the difference an underpayment.

It depends. If the contract gives a dollar rate and the remittance has line-level allowed amounts, the comparison is mostly arithmetic. If the contract is a percentage of Medicare, a case rate, or a bundled arrangement, the expected amount needs a different calculation and may not be supported by a simple line comparison.

The checklist

Use the same sequence for every line so a review can be repeated and audited. Stop at the first step that explains the difference; do not force a finding.

  • Confirm the payer, provider, and contract version that apply to the date of service.
  • Confirm the procedure code, modifier, units, and date of service on the claim and the remittance match.
  • Find the approved contract rate for that exact combination.
  • Reconstruct the payer allowed amount from the remittance: payer paid plus patient responsibility where reported.
  • Read every CAS segment and remark code on the line, not only the largest adjustment.
  • Check for a multiple-procedure reduction, bundling edit, or other policy adjustment that explains part of the difference.
  • Subtract the allowed amount from the expected rate. If the result is zero or negative, there is no rate shortfall to pursue.
  • If a positive difference remains, label it a review candidate and record the evidence and assumptions.
  • Have a second reviewer check the calculation before it becomes a recovery claim.

Example 1: a genuine rate mismatch

The contract rate is $120 for one unit. The remittance shows $100 allowed, made up of $80 paid by the payer and $20 patient responsibility. The expected amount is $120, so the difference is $20 before any other adjustment.

If the code, modifier, unit, and date of service all match and no other adjustment explains the $20, this is a review candidate. It is still not a guarantee of recovery: the payer may have applied a policy edit that needs a separate check.

ItemAmount
Contracted rate$120.00
Payer paid$80.00
Patient responsibility$20.00
Reconstructed allowed amount$100.00
Difference to review$20.00

Example 2: a payment that only looks low

The contract rate is $120. The remittance shows $120 allowed, made up of $96 paid by the payer and $24 patient responsibility. The payer paid less than the contract rate, but the allowed amount matches it. The $24 is patient responsibility, not a payer shortfall.

This is the most common false positive in a simple paid-versus-contract comparison. Comparing only the payer payment with the contract rate would produce a misleading $24 finding.

ItemAmount
Contracted rate$120.00
Payer paid$96.00
Patient responsibility$24.00
Reconstructed allowed amount$120.00
Difference to review$0.00

What can still explain a difference

Even a positive difference needs a second look. Multiple-procedure reductions, bundling edits, site-of-service rules, modifiers, and contract terms can all change the expected amount. If the contract is a percentage of Medicare, the expected amount depends on the correct Medicare fee schedule and locality, not a dollar figure copied from a different year.

Record excluded lines and the reason. A review that says "not supported" is a valid outcome and is more credible than a finding that cannot be explained.

Sources