An underpayment occurs when adjudicated reimbursement is below the amount supported by the contract, fee schedule, policy, or claim facts. Detection requires more than finding unpaid claims; paid claims must be compared with a reliable expectation.
What medical claim underpayment detection means in day-to-day RCM
For contracting, payment integrity, and RCM teams, the practical goal is to turn this concept into a repeatable, documented workflow. The most useful approach connects the source evidence, the person responsible for action, the deadline, and the financial or quality outcome. That keeps the team focused on resolution rather than isolated account touches.
Start by defining what success means in your organization and which system is the source of truth. Payer products, contracts, coding guidance, program rules, and workflows can differ, so the claim-specific context should always control the final decision.
A practical workflow
- 01
Build expected reimbursement logic from current, applicable contract terms.
- 02
Compare expected allowed and paid amounts with 835 claim and service-line detail.
- 03
Exclude valid patient responsibility, bundling, reductions, and noncovered services.
- 04
Group variances by payer, code, location, and reason for efficient review.
- 05
Submit disputes with evidence and track recovery through final posting.
Document the evidence used at each stage. A strong note should let another trained person understand what happened, reproduce the research, and take the next action without restarting the account.
Common mistakes to avoid
- !
Using outdated fee schedules or the wrong contract product.
- !
Treating every difference between charge and payment as an underpayment.
- !
Closing recovery work when the payer promises reprocessing rather than when payment posts.
When the same failure appears repeatedly, review the earliest point where it could have been prevented. The lasting fix may belong in patient access, documentation, coding, system configuration, payer enrollment, payment posting, or team training.
What to measure
- Potential, validated, appealed, and recovered underpayment dollars.
- Variance by payer and procedure.
- Average days from detection to recovery.
Review trends by payer, plan, location, provider, service, team, and root cause when the volume supports it. Segmentation reveals operational problems that a single organization-wide average can hide.
Frequently asked questions
Can an 835 show an underpayment?
It provides paid, allowed, adjustment, and reason detail needed for comparison, but a contract or other reimbursement expectation is required to determine whether the amount is wrong.
What is the best place to start?
Start with high-volume services, material variances, known payer contract changes, and patterns visible in ERA data.
Authoritative starting points
Use current official guidance and payer-specific rules before applying any operational recommendation.
This guide is general operational information, not medical, legal, coding, compliance, or payer-specific advice. Requirements can change; verify current authoritative guidance.