EOB Posting Errors: How to Catch Underpayments
The expensive EOB error is rarely a dramatic denial. It is the payment that looks close enough to post — and then quietly becomes lost revenue, a wrong patient…
The expensive EOB error is rarely a dramatic denial. It is the payment that looks close enough to post — and then quietly becomes lost revenue, a wrong patient balance, or an avoidable appeal once someone notices the numbers don't tie out. Underpayments hide in plain sight precisely because the claim did pay something.
The fix is to treat payment posting as a three-way match. Compare the ERA or EOB to your fee schedule, compare the adjustment codes to the payer's explanation, and compare the final posted amount to the actual deposit. For office managers, billing leads, and DSO operations teams, building that check into daily posting keeps short-paid claims from slipping into insurance AR as if nothing is wrong. This guide covers the daily underpayment check, the posting errors that hide short pays, and where cleaner front-desk intake reduces the variance that looks like a payer problem.
Key takeaways
- Catch underpayments before final posting, not later in aging. The safe daily process compares the remittance to the expected allowed amount, verifies Group Codes, CARCs, and RARCs, and matches the posted total to the EFT or check before patient balances go out.
- CMS says ERAs include final adjudication and payment information and can be posted automatically — a clean ERA workflow is your best first control.
- CMS explains claim adjustments through Group Codes, CARCs, and RARCs, so never post a short payment without reading those fields.
- A separate underpayment queue works better than a generic exceptions queue because it forces the team to compare expected reimbursement, not just whether any payment arrived.
- Group Code CO assigns responsibility to the provider and PR to the patient — so an office should never push a payer shortfall onto the patient ledger just because the payment posted low.
What counts as an underpayment?
An underpayment is any paid claim that lands below the expected amount after contract terms, benefits, and remittance logic are checked. Not every short payment is a payer mistake — some differences are valid contractual adjustments or patient responsibility. The practical question is simple: did the payer pay what the remittance says it should have, and does that match your contract and the claim facts?
Keep four fields in view:
| Checkpoint | What to compare | Why it matters |
|---|---|---|
| Allowed amount | EOB or ERA vs fee schedule | Confirms the payer paid at the contracted rate |
| Adjustment logic | Group Code, CARC, RARC | Explains whether the difference belongs to provider, patient, or payer rules |
| Patient responsibility | Posted balance vs remittance detail | Prevents shifting payer shortfalls onto the patient |
| Deposit match | Posted total vs EFT or check | Confirms the cash actually arrived as posted |
Why underpayments get missed
Underpayments slip through when posting rewards volume, fee schedules aren't visible during posting, and reconciliation happens days after the claim is posted. Three conditions make it worse: no current fee schedule visible while posting, adjustment codes posted without being interpreted, and deposit reconciliation that lags the posting by days. Front-desk interruptions compound all three — when the same people who post payments are constantly pulled to the phone, careful review is the first thing to go.
A daily underpayment review workflow
Your best workflow checks expected reimbursement before the claim leaves the posting desk, not after a patient gets a balance statement.
- Pull expected reimbursement first. Give the poster the amount the practice expected before they approve the payment. If you post first and research later, the ledger already reflects the short pay as normal.
- Read the ERA or EOB as a decision document. CMS says the remittance includes adjudication decisions, payment information, and standard adjustment codes. Check the Group Code (provider vs patient responsibility), the CARC (core reason the amount changed), the RARC (added line-level detail), and any provider-level adjustments.
- Compare the paid amount to the fee schedule. This is where most underpayments are caught or lost. Compare the allowed amount to the expected reimbursement for that payer, plan, CDT code, and effective date.
- Reconcile to the actual deposit. No review is complete until the posted payment agrees with the EFT or check. CMS notes that one EFT usually represents all benefits due for the claims in the remittance.
- Route confirmed short pays to a separate queue. An underpayment queue asks a different question than a denial queue.
A quick decision table for step 3:
| Scenario | Best next step |
|---|---|
| Paid amount matches expected allowed amount | Post and move on |
| Lower, and remittance explains a valid contractual rule | Post with documented reason |
| Lower, and the code or explanation doesn't support it | Route to underpayment queue |
| Patient responsibility increased unexpectedly | Review before the statement goes out |
| Multiple lines changed in different ways | Hold for manual review |
CMS is explicit that Group Code CO assigns responsibility to the provider and PR to the patient. That means an office should never convert a payer shortfall into patient responsibility just because the payment posted lower than expected.
Which posting errors hide lost revenue?
| Error | What it looks like | Why it hides underpayments |
|---|---|---|
| Posting from the payment amount alone | Staff post what came in without checking allowed amount | Any short pay becomes normalized |
| Misreading CO vs PR | A provider shortfall lands on the patient ledger | Patients get billed for payer variance |
| Ignoring provider-level adjustments | A deposit mismatch is left unexplained | Real cash loss gets buried in reconciliation |
| Using an outdated fee schedule | The current contract rate is never checked | Short pays look contractually valid |
| Delayed reconciliation | Deposit review happens days later | Recovery windows shrink before anyone notices |
CMS notes ERAs usually carry more detail than paper remittances and can post automatically — valuable only if the team still validates the remittance logic before it becomes final ledger activity. The same payer-by-payer reading logic shows up in the Aetna EOB processing steps, the BCBS EOB workflow, and the Cigna EOB process — knowing each payer's field layout makes variances easier to spot.
Don't confuse short pays with adjustment errors
Contractual adjustments create false alarms when staff compare charges to payments instead of comparing the allowed amount to the payment. If the payer applied the contracted write-off correctly, the claim can look short at first glance even though the posted amount is right — which is exactly why allowed-amount review has to happen before you label anything an underpayment. Recurring write-off and adjustment mistakes deserve their own review; see how to catch adjustment errors in EOB posting so the two issues don't get mixed in the same batch.
Common mistakes to avoid
- Posting first and researching later when the amount looks short.
- Letting fee schedules live in email threads or PDFs nobody checks during posting.
- Mixing underpayments with denials, recoupments, and missing documents in one generic queue.
- Assigning unexplained shortfalls to patient responsibility without reading the remittance codes.
- Delaying EFT reconciliation until the end of the week.
- Ignoring upstream intake quality, since missing subscriber data and bad plan details create downstream variance that looks like a payer problem.
How Velano helps upstream
Velano does not post remittances, reconcile deposits, or do any billing or revenue-cycle work — it is an AI receptionist for dental practices. Its value sits before posting, in two specific places that quietly weaken underpayment detection.
First, intake quality. A surprising amount of "payer variance" actually starts with bad data captured at the front desk — a wrong subscriber ID, the wrong plan, missing coordination-of-benefits details. Velano answers every call and text 24/7, books straight into your PMS, and captures cleaner insurance details on the booking call, so fewer claim-data mismatches reach billing in the first place. Second, focus. Underpayment review fails when billers are constantly pulled to the phone; industry research has long found dental front desks spend hours a day on calls and still miss a large share of them. By covering the phones — including after hours and overflow — Velano protects the uninterrupted time same-day posting review actually requires. Velano won't reconcile your EFTs or read a CARC for you, but it keeps the intake clean and the desk staffed so your team can do this work without losing it to interruptions.
See how Velano keeps your front desk covered.
Stop losing patients to voicemail.
See how Velano answers every call, books into your PMS, and follows up — so patients show up.