Detecting Payment Shortfalls and Pursuing Reimbursement Corrections
A zero balance can conceal an underpayment. If a payer paid less than the applicable contract supports and the difference was adjusted away, the account may look resolved even though the payment still deserves review.
Underpayment identification compares what the payer should have paid under the applicable agreement or payment rules with what it actually paid. Recovery involves validating the difference, determining why it occurred, and pursuing the appropriate correction or additional payment. The objective isn't to challenge every low payment. It's to establish a supportable expectation, calculate the actual shortfall, and document a path to resolution.
Payment Received Doesn’t Mean Payment Correct
An underpayment is a payment lower than the correctly calculated reimbursement due for the particular claim or service under the applicable contract, program, or payment methodology. A payment variance is the difference between an expected and an observed amount. It is a signal for review, not automatic proof of underpayment.
Denied claims, partial denials, contractual reductions, patient responsibility, and posting errors can all produce low-looking cash results. They require different investigation and follow-up. HFMA's revenue cycle overview describes underpayment work as comparing actual reimbursement with calculated or contracted payment, identifying patterns, documenting findings, and pursuing recovery, including in bulk where appropriate. HFMA underpayment recovery overview.
Where Underpayment Review Fits
Underpayment work often begins after adjudication, when a remittance becomes available and an expected-payment system or analyst can compare results with the relevant contract. It can also begin during AR follow-up, contract audits, denial recovery, or a retrospective review of previously closed claims.
Managed care or contracting typically maintains the authoritative agreement, reimbursement exhibits, amendments, effective dates, and interpretation of disputed terms. Revenue integrity and contract management may configure expected reimbursement, run variance reports, or analyze patterns. Billing and AR investigate individual claims and work authorized disputes. Payment posting confirms what was actually adjudicated and recorded. Finance or treasury can trace deposits and funds when needed. Legal and compliance teams may become involved in formal disputes under organizational procedures.
The sequence from service documentation through coding, claim submission, payer adjudication, and payment posting affects which data is trustworthy. An unexpected payment can originate from a wrong contract model, a modifier on the claim, a payer calculation, a secondary payment rule, or an internal posting mistake. Looking only at the deposit does not distinguish those possibilities.
What Determines Expected Reimbursement?
Before calculating a variance, identify the correct payer, product, network, contracted entity, service date, billing setting, facility or provider, and contract period. The reimbursement method may differ even when the CPT code is identical.
Common methodologies include a negotiated fee schedule, a percentage of an applicable Medicare schedule, a case rate, a DRG-based amount, APC-based outpatient reimbursement, a per-diem rate, a percentage of charges, or a carve-out. Some agreements establish separate treatment for multiple procedures, modifiers, bundled services, outliers, implants, professional and technical components, and noncovered services.
A contract that pays a percentage of Medicare requires the appropriate Medicare schedule, geographic locality, year, code status, and applicable payment policy, not one undifferentiated national rate. The CMS Physician Fee Schedule look-up overview describes locality-sensitive pricing and payment policy information. Medicare pricing is a benchmark only when the contract or applicable program makes it relevant; it is not a substitute for a commercial payer agreement.
The Financial Math: Allowed Amount, Payer Share, and Variance
The most useful formula is straightforward, but only after the expected payment has been modeled correctly:
Validated payer variance = expected payer payment − actual payer payment.
A positive result can indicate a potential underpayment; a negative result may indicate an overpayment, modeling difference, or another valid factor. Use the same service lines, period, payer, and adjudication state on both sides. Do not compare an entire EFT with one claim's expected payment.
Worked example: fee schedule with coinsurance
An illustrative contracted professional service has a billed charge of $400, a valid allowed amount of $250, and patient coinsurance of 20% of the allowed amount, with no deductible or other applicable reductions.
The $150 contractual reduction is not missing cash. The $50 coinsurance is not the payer's liability, assuming it is validly assigned. The $25 difference is the amount worth investigating. Before disputing it, review the actual payer adjustments, benefit terms, rate selection, units, and any other provisions affecting reimbursement. The example is illustrative and not a payer-specific pricing rule.
Worked example: contract percentage and effective-date error
Assume an agreement requires 140% of an applicable $120 fee-schedule amount, subject to no other payment reduction, and the payer is responsible for the full allowed amount. The correct expectation is $168. The payer instead pays $150.
The preliminary variance is $18. Before assigning fault to the payer, verify that the $120 underlying schedule amount is correct for the date, locality, service setting, and modifier, and that 140% is the operative contract percentage. A model using last year's rate could produce the same apparent discrepancy even when the payer's calculation is correct.
Finding Underpayments in Reports and Closed Accounts
A usable review starts with a dependable population: adjudicated claims or service lines with payer, plan, service date, adjudication date, submitted charges, procedure or revenue codes, modifiers, units, expected allowed or payment, actual payment, adjustment groups, and account status. Where available, include contract version, claim ID, remittance date, denial status, recovery history, and prior adjustments.
Zero-balance accounts deserve deliberate attention. A patient accounting system may close a balance because the expected contractual amount was written off or because an automated rule set the remaining amount to zero. A zero balance proves neither contractual accuracy nor successful recovery. Conversely, an open balance alone doesn't establish that the payer owes it.
A practical screening method is to calculate positive variances, remove obvious exclusions, sort by payer and payment method, and sample original remittances and contracts before escalating a larger population.
For large datasets, report claim counts, distinct accounts, gross variance, validated variance, submitted disputes, upheld disputes, and actual incremental cash recovered separately. These numbers answer different questions. A gross variance total should not be described as recovered revenue.
A Practical Underpayment Investigation
Step 1: Confirm the scope
Identify the specific claim, date of service, payer product, provider, service lines, and most recent adjudication. Check whether the claim was adjusted, reversed, resubmitted, or processed as secondary. A variance from an obsolete remittance may already have been corrected.
Step 2: Establish an authoritative expectation
Use the correct executed contract and rate schedule, with effective dates and amendments. Where access is restricted, seek an approved rate calculation from contracting or the designated analyst rather than estimating from another payer's payment.
Step 3: Reconstruct the adjudication
Compare billed units, allowed amounts when reported, claim and service payments, adjustment group codes, CARCs, RARCs, deductibles, coinsurance, and prior-payer information. CMS explains that ERA/SPR adjustments can occur at the service, claim, or provider level. CMS remittance overview.
Step 4: Validate the payment trail
Confirm actual claim-level payer payment in the 835 or EOB and the posting history. Reconcile the corresponding EFT at its proper deposit level, including provider-level adjustments, rather than assuming every lower deposit means a claim was underpaid. A PLB recovery can reduce cash received without reducing the adjudicated payment on the current claim.
Step 5: Determine the root of the variance
Check the rate model, contract dates, code/modifier mapping, units, claim edits, bundling, timely filing, secondary adjudication, and whether the payer applied the correct negotiated terms. Distinguish a payer discrepancy from internal data or posting defects.
Step 6: Choose the authorized recovery route
Depending on agreement and payer process, submit a reconsideration, contractual payment dispute, corrected claim where appropriate, provider appeal, or bulk variance package. Do not substitute a corrected claim for a contractual dispute without verifying the payer's instructions. Confirm submission method, supporting evidence, and deadlines.
Step 7: Record and track the dispute
Maintain claim references, calculated expected amount, actual paid amount, supporting rate source, dates, payer contact, case number, requested correction, and next follow-up. Tracking is essential because agreement terms may establish different dispute windows and escalation requirements.
Step 8: Verify the recovery
A favorable payer response isn't the same as received cash. Trace the adjustment or supplemental payment through the new ERA, posting system, and EFT or check; verify the account treatment and avoid duplicate recovery. Record amounts approved, paid, and posted separately when they differ.
Worked Investigation: Three Lines, One Underpayment
A fictional claim has three services. Authorized contract analysis establishes the expected payer amounts after applicable cost sharing. The remittance reports different actual amounts:
The analyst confirms service B's code, modifier, units, contract exhibit, service date, and cost-sharing treatment. If those inputs are supported and the payer gives no valid contractual explanation for the $12 reduction, the finding can be documented as a validated potential underpayment and routed for a payment dispute.
Suppose the account was zeroed out after posting $258 and a $12 additional write-off. The account balance is still zero, but the adjustment requires review because its financial treatment may have hidden the shortfall. Neither automatically reversing the write-off nor moving $12 to patient responsibility is appropriate without authorization and a valid basis.
If the payer subsequently issues an additional $12 claim payment, the analyst verifies its new remittance and posting, then records $12 recovered. If the payer merely agrees a correction is pending, the amount remains outstanding until received and validated.
Common Causes and How to Differentiate Them
An apparent underpayment should never be corrected by changing the patient's share just to force the account to balance. The remittance group code and valid adjudication determine the appropriate treatment, with contractual and legal requirements governing any patient billing. CMS explains that CO and PR group codes identify different financial responsibilities in its Medicare remittance guidance.
From Individual Recovery to Recurring Contract Variances
One missed payment can be a claim-specific error. Twenty similar claims may point to an incorrect payer fee-schedule load, an outdated internal expected-payment table, a service-category exception, or another shared cause. A repeat pattern is a reason to investigate, not evidence by itself that the payer acted incorrectly.
A manageable investigation starts with a small, verifiable sample across dates, providers, and codes. Reperform each expected-payment calculation from approved terms. Compare affected and unaffected claims. Identify whether the problem began after a rate change, system migration, new modifier mapping, or payer processing update.
For example, suppose 40 claims show a combined $2,000 preliminary variance. Manual contract validation confirms 30 claims totaling $1,350; eight have legitimate contractual exceptions totaling $500, and two totaling $150 remain unresolved. The validated candidate amount is $1,350, not $2,000. Even then, actual recovery is zero until funds are received.
Where a repeat issue is supported, contracting and payer relations may pursue a coordinated recovery request or broader configuration correction. Analysts can document the pattern and affected records without claiming authority to reconfigure the billing platform or amend an agreement. Detailed systemwide financial-leakage investigations belong in the Revenue Integrity & Contract Management series.
Recovery Deadlines, Documentation, and Financial Controls
Contractual dispute or reconsideration periods vary. They may be triggered by payment, remittance, denial notice, discovery of a variance, or another defined event. A payer's timely filing deadline for initial claims is not automatically the same as its underpayment-dispute deadline. Some agreements include notice, escalation, or audit-rights provisions that should be read together.
Use the applicable agreement and current payer guidance to establish the clock. A corrected claim or multiple reprocessings do not automatically restart a deadline. Retain payer acknowledgments, case numbers, correspondence, and dated rate calculations.
When collecting additional money, ensure payment posting reconciles the new remittance and cash receipt without introducing duplicate payments or unsupported write-offs. Finance and revenue integrity reporting should distinguish potential exposure, validated receivable, disputed amount, payer-approved amount, and cash actually recovered.
Controls that reduce repeated leakage
- Periodically validate approved contract-rate tables against executed amendments and effective dates.
- Sample expected-versus-actual calculations after significant payer or system updates.
- Review positive variances on both open and zero-balance accounts.
- Keep claim-level dispute deadlines and supporting evidence visible to responsible teams.
- Require documented reasons and appropriate approvals for manual variance write-offs.
- Reconcile recoveries through remittance, cash, and posting, not only favorable payer messages.
Practical Review Checklist
Before classifying a claim as underpaid, confirm the following:
- ☐ The correct payer, product, network, entity, and date of service are identified.
- ☐ The applicable rate schedule and amendments are authoritative for the claim.
- ☐ Coding, units, modifiers, setting, and service grouping have been validated.
- ☐ Expected allowed amount is distinguished from expected payer payment.
- ☐ Valid cost sharing, denials, bundling, and coordination-of-benefits effects are considered.
- ☐ Actual claim payment is supported by the correct remittance version.
- ☐ Provider-level PLBs and EFT balancing are not confused with line-level payment.
- ☐ Prior recoveries, retractions, reversals, and adjustments are reviewed.
- ☐ The discrepancy has a supported cause or a clearly documented unresolved question.
- ☐ The correct dispute process and deadline are confirmed.
- ☐ Any later recovery is verified against both the new remittance and cash/posting records.
Underpayment recovery is a bridge between everyday AR work and revenue integrity. The central skill is not producing the biggest variance report. It is turning a calculated difference into a defensible claim-level finding, then confirming whether the organization actually received what was owed.
References and Further Learning
These resources support the guide and provide opportunities for additional learning. Check applicability, publication dates, and current requirements before using a resource operationally.
References
Additional Learning
Educational Disclaimer
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.
Continue Exploring Revenue Cycle Uncovered
Explore related guides or return to the complete revenue cycle educational library.