Underpayment analysis begins with caution: a payment below the charge amount is not automatically wrong. Contractual allowances, deductible, coinsurance, bundling, multiple-procedure rules and payer policies can legitimately reduce payment.
The useful comparison is expected allowed amount versus actual allowed/payment, with the claim's modifiers, units, place of service, provider and contract context included.
Build an expected-payment reference
Use current contracts, payer fee schedules or other reliable reimbursement terms. Keep effective dates because contract rates change.
Use ERA/EOB adjustment detail
CARC/RARC and payer explanations help distinguish contractual reductions, patient responsibility, noncovered services, bundling and other adjudication outcomes.
Look for patterns, not only one claim
Repeated variance by CPT, payer, location or provider may indicate a fee-schedule configuration issue or systematic adjudication problem.
Check claim details before disputing
Modifiers, units, bilateral/multiple procedure rules, place of service and provider status can change expected payment.
Track recoupments and reversals
A payment received this month may be reversed later. Reconciliation should preserve that history so collection reports remain accurate.
Create a variance workflow
Set thresholds for review, document expected versus actual, attach contract support, submit reconsideration/dispute where appropriate and track recovery.
A practical review checklist
- Maintain current payer rate references.
- Compare allowed amount, paid amount and patient responsibility.
- Review adjustment reason codes.
- Segment repeated variance by CPT/payer.
- Validate modifiers/units/POS.
- Track disputes, recoveries and recoupments.
Separate true underpayments from expected reductions
A robust variance process assigns a reason to the difference. Examples include contractual allowance, deductible/coinsurance, bundling, multiple-procedure logic, modifier impact, unit reduction, noncovered service, payer processing error or contract mismatch. Only then can the team decide whether a dispute is appropriate.
Where contracts are complex, prioritize high-dollar or repeated variances rather than manually reviewing every paid line. Pattern detection can reveal configuration issues that affect many claims.
Report recovered dollars and prevented recurrence
Recovery is important, but leadership should also know whether the payer issue was corrected for future claims. Track disputed amount, recovered amount, turnaround, payer response and whether the same variance continues after resolution.
How practice leaders can operationalize the findings
The first step is to establish a baseline before changing the workflow. Export the relevant claim, payment, denial, aging or front-end data and define the period being reviewed. Record how the current metric is calculated so the practice can compare the same measure after changes are introduced.
Second, assign ownership by root cause. Revenue-cycle problems often cross departments: the front desk may own demographics and eligibility; authorization staff own approval tracking; coders review documentation and code selection; billing owns claim construction and submission; posting owns remittance application; denial and AR teams own unresolved balances. A problem without a named owner becomes an aging problem.
Use exception-based management
Leadership does not need to inspect every routine claim. Build exception reports for high-dollar balances, repeated denial reasons, claims approaching deadlines, unusual adjustments, unresolved payer delays and accounts that have not moved after prior follow-up. This concentrates management attention where financial risk is highest.
Close the loop upstream
When a claim is recovered, ask whether the underlying defect was corrected. If an authorization denial was overturned but the scheduling workflow still fails to capture authorization requirements, the same loss will recur. Recovery and prevention should be reported separately so the practice can see both immediate financial impact and long-term process improvement.
Keep reporting transparent
Monthly reporting should explain material changes in collections and AR. If a prior-period payment is reversed, duplicated posting is corrected, or a balance is adjusted, the change should remain visible rather than being hidden by a new total. Transparent reconciliation gives practice owners a more reliable picture of performance.
Review again after 30 days
After the first improvement cycle, compare the new data with the baseline. Look for fewer repeat defects, faster claim movement, clearer ownership and reduced high-risk aging. If the numbers did not improve, investigate whether the intervention addressed the real root cause or only changed the way activity was recorded.
Primary sources and further reading
Continue with Provider Insights
