The claim posted as paid. Was it paid what the contract says?

A denial announces itself. It arrives with a reason code, it lands in a queue, and someone is assigned to it. An underpayment does none of that. The remittance shows a payment, the poster applies it, the system calculates a contractual adjustment for the difference between charges and payment, and the claim closes. Nothing about the transaction looks wrong, because the software was never told what the right number was. Months later, someone renegotiating the contract notices that a payer has been allowing last year's rate since the amendment took effect, and the question becomes how many claims that touched and whether any of them are still recoverable.

Why underpayments go unnoticed

The mechanics of payment posting work against you here. Most posting workflows treat the remittance as the authority: whatever the payer says it allowed becomes the allowed amount, and whatever is left between charges and allowed becomes a contractual write-off. That is correct when the payer is right. When the payer is wrong, the same logic quietly writes off money you are owed.

• No expected amount exists. If the contracted rate lives in a PDF in someone's inbox, the posting system has nothing to compare the payment against.
• Charges are set above contract. Because billed charges are usually higher than any contracted rate, every payment looks like a discount, and a small extra discount does not stand out.
• People reconcile totals. The deposit matches the remittance total, so the batch balances. Nobody is asked whether each line was right.
• The gap per claim is small. A shortfall that is minor on one IOP day is easy to dismiss and only becomes visible when someone adds up a quarter of it.
• Nobody owns it. Posters post, denial specialists work denials, and the contract sits with an owner or executive. Underpayments fall between all three.

Where the gap usually comes from

Underpayments are rarely random. They tend to come from a handful of causes, and knowing which one you are looking at decides how you fix it.

• A rate change that never reached the payer's system. The amendment was signed, but the payer's claims system is still loaded with the previous fee schedule, or the new rate was loaded with the wrong effective date.
• Wrong provider or facility profile. The payer processes the claim under a provider type, specialty or network status that carries a lower rate than the one in your agreement.
• Unit or modifier handling. Units are reduced, a modifier triggers a lower rate, or a code-and-modifier combination your contract prices separately is paid at the base rate.
• Level of care mismatch. A residential day is priced at a lower level's rate, or a PHP day at an IOP rate, because of how the revenue code or authorization was matched on the payer's side.
• Methodology confusion. The contract pays a percentage of a published fee schedule, and the payer applied the wrong year's schedule or the wrong percentage.
• Lesser-of logic applied incorrectly. Many contracts pay the lesser of billed charges or the contracted rate. If your charge for a code dropped below the rate, the payer may be paying correctly, and the fix is your chargemaster, not the payer.

Build the expected-amount table first

You cannot audit remittances against a contract you have not translated into data. The single most useful thing a billing manager can do this month is turn each active payer agreement into a table that a person or a system can check a payment against.

1. Collect the current agreements and every amendment. Include rate exhibits, fee schedule references and any letters confirming rate changes. If you cannot find the signed amendment, you cannot enforce it.
2. List the billable services by payer. For each one record the code or revenue code, any modifier that changes the rate, the unit definition, the rate or methodology, and the effective start and end dates.
3. Capture the methodology, not just the number. A flat per diem, a case rate, a percentage of a named fee schedule and a lesser-of clause each produce the expected amount differently.
4. Note the level of care and billing entity. If you have more than one tax ID or facility, rates often differ between them.
5. Name an owner. One person updates the table when a contract changes and records who confirmed the payer has loaded the new rate.

Build the expected amount from the contract, never from history. If you derive the expected rate from what a payer has been paying, you will faithfully reproduce every error the payer has been making.

Compare the right number, line by line

The comparison that matters is the payer's allowed amount against your expected allowed amount, at the service line. Comparing the paid amount alone misleads you, because the paid amount is net of deductible, copay and coinsurance, which legitimately vary by patient. A low payment on a patient who has not met a deductible is not an underpayment. A low allowed amount usually is.

A hypothetical to make it concrete. Say an IOP contract pays a flat per-diem rate of $400, effective January 1. A remittance line for a February date of service shows an allowed amount of $360, a coinsurance amount assigned to the patient, and a payment for the rest. The poster sees a payment and a patient balance and moves on. Compared against the table, the line shows a $40 allowed-amount variance. The patient's coinsurance was also calculated on the wrong base, so the patient's share is off too, in the payer's favor on one side and the patient's on the other.

Set a tolerance, then look at everything above it

Rounding and fee schedule quirks can create differences of a few cents. Decide on a variance tolerance you are willing to ignore, write it down, and review every line above it. Report variances by payer, by code and by date of service so patterns appear: a cluster starting on one date points to a rate load problem, while scattered variances on one code point to a modifier or unit issue.

Do not forget the paper

Payers that still send paper remittances or pay certain lines by check are the ones most likely to escape review, because the posting is manual and the comparison is easy to skip. Hold them to the same table.

What to do with the gap

Finding a variance is the start of the work, not the end. How you recover it depends on the cause and on what your contract says about disputes.

1. Confirm it is real. Check the line against the contract language itself, not your summary of it. Confirm the effective date, the billing entity, the level of care billed and whether a lesser-of clause applies. Rule out legitimate explanations such as patient cost sharing, coordination of benefits or a secondary payer.
2. Classify the cause. A systemic error, such as a wrong fee schedule or outdated rate, affects every claim that used it. A one-off processing error affects one claim. Systemic errors get escalated as a group; one-offs get worked individually.
3. Assemble the evidence. For each variance or group: the contract page and rate exhibit, any amendment, the claim as submitted, the remittance line, and a simple calculation showing expected versus allowed.
4. Use the route the contract specifies. Many agreements distinguish between a reprocessing or reconsideration request, often handled through provider services or a provider representative, and a formal payment dispute or appeal. They may also set deadlines measured from the remittance date. Confirm these against your agreement, and against any state prompt-pay or dispute rules that apply, before you start.
5. Ask the payer to fix the source. For systemic errors, ask your provider representative to correct the rate load and to reprocess the affected claims as a project, rather than submitting each claim one at a time. Get the correction and its effective date in writing.
6. Track it like a denial. Every open variance needs an owner, a dollar amount, a submission date, a follow-up date and a resolution. A variance that nobody follows up on is a write-off with extra steps.

Make it routine instead of a project

Underpayment reviews tend to happen once, after someone notices a large gap, and then stop. The programs that actually recover this money build it into the normal posting week.

• At posting: every line is compared against the expected amount, and variances above tolerance route to a named person instead of closing silently.
• Weekly: the variance owner works new items, groups them by cause and escalates anything that looks systemic.
• Monthly: a variance summary by payer goes to whoever owns contracting, with dollars identified, dollars recovered and dollars still open.
• At every contract change: the table is updated before the effective date, and the first remittances after it are checked by hand to confirm the payer loaded the new rate.
• At renegotiation: the variance history comes to the table. A payer that has consistently paid below contract is a payer whose administrative performance belongs in the conversation.

If you track revenue cycle measures, add variance dollars and recovery rate by payer next to your denial measures. They describe the same thing from different sides: money your services earned that has not yet arrived. Our piece on revenue cycle KPIs covers how to count them consistently.

Where software helps

None of this requires special software; a well-kept spreadsheet and a disciplined weekly review will find real money. It does get easier when the contract and the remittance live in the same place. In Unisona Health, contracted rates are loaded per payer and per code in contracts and rates, and each remittance line is compared against them as it posts, so a short payment shows as a variance with a running monthly total. Variances and partial payments route to the denials queue with the dollars at risk, a deadline and an owner, the same way a denial does.

Frequently asked questions