Payment Posting: The Step Where Underpayments Get Caught (or Missed)

Payment posting sounds like the most boring step in billing — record what came in, match it to the claim, done. But that view is exactly why practices lose money here. Payment posting is the one moment where you compare what you should have been paid with what you actually were paid. Do it carefully and you catch underpayments. Do it as rote data entry and you accept them silently, forever.

Here's why this quiet step matters more than it looks.

What payment posting actually does

When a payer processes your claim, they send back a statement — an EOB (explanation of benefits) or ERA (electronic remittance advice) — showing what they paid and why. Payment posting is the process of reading that statement, line by line, and recording each payment against the claim it applies to.

On the surface it's reconciliation: match the money to the claim. But embedded in that reconciliation is a far more important question — did they pay what they were supposed to?

The underpayment problem

An underpayment is when a payer pays less than the contracted rate for a service. It happens more often than most practices realize, through:

• Payer processing errors
• The wrong fee schedule applied
• Quiet downcoding by the payer
• Simple mistakes in adjudication

Here's the trap: the claim was paid. It's not denied. It doesn't show up in your denial reports or your aging A/R. Everything looks normal. The only way to know you were shorted is to compare the payment against what you were actually owed — and that comparison happens (or doesn't) at payment posting.

Why underpayments get accepted silently

A paid claim feels like a closed claim. The natural instinct is to post the payment, mark it done, and move on. If posting is treated as pure data entry — "record whatever came in" — then an underpayment looks identical to a correct payment. It gets filed away as revenue received, and the shortfall is simply gone.

Multiply a small underpayment across hundreds or thousands of claims, and the cumulative loss is significant — all of it invisible, because each individual underpayment looked like a normal, successful payment.

Careful posting vs. rote posting

The difference between the two approaches is a single habit: verification.

Rote posting records the amount received and closes the claim. Fast, simple, and blind to underpayments.

Careful posting records the payment and checks it against the expected contracted amount. When the payment is short, it's flagged — and now it can be appealed or corrected, turning a silent loss back into recovered revenue.

This is also why automation alone isn't the answer. Automated posting speeds up the recording, but catching underpayments requires the comparison step — checking each payment against what should have been paid. Without that, automation just accepts underpayments faster.

The downstream value

Careful payment posting does more than catch underpayments:

• Recovers shorted revenue that would otherwise disappear.
• Reveals payer patterns — if a specific payer consistently underpays, that's actionable.
• Keeps your records accurate — correct posting means your A/R and reporting reflect reality.
• Surfaces denials correctly — proper posting routes partial denials and adjustments to be worked instead of buried.

The bottom line

Payment posting is where the revenue cycle's final truth gets recorded — and where a quiet category of losses is either caught or accepted. Treated as data entry, it lets underpayments slip through as "normal" revenue. Treated as verification, it catches money you're owed and recovers it. The difference is whether someone is checking each payment against what it should have been.

Novusmedix posts payments as a verification step for healthcare practices — reading each remittance against the expected amount so underpayments get caught and recovered, not accepted. If you suspect you're being shorted and not catching it, let's take a look.