Reimbursement Validation

Comparing Received Payments Against Expected Reimbursement

A payer sends an explanation of payment, the transaction posts to the account, and the remaining balance appears correct. That still does not establish whether the organization received the reimbursement it was entitled to under the applicable agreement.

Reimbursement validation compares an independently established payment expectation with what the payer actually adjudicated. It requires more than finding a difference between billed charges and a deposited amount. Reviewers need the right contract terms, service information, dates, insurance benefits, and remittance details before identifying a true variance.

Payment validation begins with an independent expected amount, built from the right contract and claim details. Only after that comparison can a reviewer decide whether the variance is a payer issue, a posting error, an incomplete model, or something still unexplained.

A Posted Payment Isn’t Necessarily a Correct Payment

Reimbursement validation is the process of determining whether a payer processed a service according to the reimbursement methodology and other rules applicable to that claim. This usually involves comparing a documented expected amount with the payer’s adjudicated amount, then investigating differences.

Validation can take place before payment, during posting, in an accounts receivable workqueue, or through retrospective contract-management and revenue integrity analysis. A single account may require review, or an analyst may test a carefully defined population of claims for patterns.

Amount or concept	Meaning	Question for the reviewer
Billed charge	The amount submitted on the claim for a service or item.	What did the provider charge?
Expected allowed amount	The amount calculated using the applicable contract or program methodology, subject to relevant terms.	What should the payer recognize as allowable?
Adjudicated allowed amount	The amount the payer recognized through processing, where available.	What did the payer actually allow?
Expected payer payment	The amount expected from the payer after supported cost sharing, offsets, and other applicable factors.	What does this payer owe for this adjudication?
Actual claim payment	The payment reported at claim or service-line level on the remittance.	What did the payer report paying on the claim?
EFT or check	The actual funds issued, potentially covering many claims and provider-level adjustments.	What money arrived in the bank?

These values should not be used interchangeably. The total allowed amount can be correct even when the payer payment is wrong. Conversely, the payer can correctly assign a deductible that makes the claim payment lower than the allowed amount. Neither situation can be diagnosed by comparing the charge to the EFT alone.

Where Validation Fits and Who Participates

A claim can pass through patient access, coding, charge entry, claim submission, adjudication, payment posting, and AR before an underpayment is noticed. Validation connects information from these stages without assigning every responsibility to one person.

Role or team	Typical contribution
Managed care or contract management	Confirms contract language, amendments, reimbursement exhibits, product applicability, and interpretation.
Contract configuration or decision support	Maintains approved expected reimbursement logic, rate tables, and effective dates.
Revenue integrity or reimbursement analysts	Analyze variances, trace patterns, assemble evidence, and initiate appropriate review.
Payment posting and cash application	Confirm the 835, patient-account transactions, EFT reassociation, and PLB effects.
Coding, HIM, or clinical departments	Review documentation, codes, units, modifiers, and clinical questions within their authority.
AR, payer relations, or designated recovery staff	Follow payer procedures for disputes, corrected claims, and payment follow-up.
Finance and compliance	Review exposure, reporting, controls, and legal or regulatory concerns as appropriate.

A posting analyst may discover a recurring difference but may not be authorized to change a contract model or submit a formal dispute. Their contribution is still valuable: preserve the evidence, describe the pattern, and route it to the owner of the rule or workflow.

Building a Reliable Expected Reimbursement Amount

The most common validation failure is starting with an expected amount that was never independently tested. If a system contract estimator contains the same incorrect rate, product mapping, or unit logic across hundreds of claims, its output may look consistent while remaining wrong.

Identify the governing reimbursement terms

• Confirm the payer, plan or product, provider or billing entity, location, network status, and effective service date.
• Obtain the executed agreement and applicable amendments or approved internal contract abstraction, where authorized.
• Identify whether the service follows a fee schedule, negotiated fixed fee, percentage of a benchmark, case rate, per diem, DRG/APC methodology, capitation, or another arrangement.
• Review carve-outs, multiple-procedure reductions, bilateral or component modifiers, unit limits, thresholds, and other conditions that affect the specific claim.
• Confirm which fee schedule version, geography, place-of-service basis, and date convention the contract actually names.

A commercial contract referring to “Medicare” does not necessarily mean today’s national Medicare rate. The agreement may specify a historical schedule, geographic locality, percentage factor, exclusions, or updates only on specified dates. CMS describes locality and policy adjustments in its Physician Fee Schedule lookup resources, but those public rates must not replace the terms of an executed commercial agreement.^[2]

Validate the source data before calculating

Source field	Why it matters
Date of service and effective date	Determines which version of the contract or fee schedule may apply.
CPT/HCPCS, revenue code, modifier	Can change the applicable methodology, pricing, and edit treatment.
Units and service quantity	Affects per-unit reimbursement; units must correspond to the relevant methodology.
Facility, professional, or institutional setting	May determine a different schedule, grouping system, or payment rule.
Claim and line identifiers	Support comparison and prevent mismatched or duplicate records.
Primary/secondary status and benefit information	Determine whether coordination of benefits and patient cost sharing affect payment.
Adjustment and remittance history	May show reversals, corrected adjudications, or prior amounts already applied.

Don't infer a missing field from a similar claim or force an expected payment calculation when the applicable terms cannot be established. Record the item as pending contract or source validation instead.

Common Reimbursement Methodologies

Not every agreement pays each individual CPT line at a fixed amount. The validation method needs to match the contractual payment unit, whether that is a service line, visit, case, episode, day, or other grouping.

Method	Basic calculation or approach	Key validation risk
Fixed fee per unit	Approved contracted fee × payable units, subject to the contract.	Wrong units, modifier, or effective rate.
Percentage of fee schedule	Named schedule amount × contractual multiplier.	Wrong benchmark year, locality, or excluded code.
Percent of charges	Covered contractual charge basis × specified percentage, subject to terms.	Using the wrong charge basis or ignoring caps.
Case rate or episode	Contract rate for the qualifying case or defined bundle.	Pricing excluded services separately or omitting carve-outs.
Per diem	Covered payable days × relevant day rate, subject to thresholds and rules.	Incorrect counting of days or changing rate tiers.
DRG/APC or other grouper-based model	Use the applicable group, weight, base rate, and specified payment adjustments.	Wrong grouping, fiscal-year version, or outlier logic.
Capitation or value-based arrangements	Validate the contractual payment/reporting unit and reconciliation terms.	Treating fee-for-service line payment as the only source of reimbursement.

CMS maintains several distinct Medicare fee schedules and policy resources, including physician, laboratory, ambulance, and DMEPOS schedules. Their pricing logic and applicability differ.^[3] For complex institutional and value-based arrangements, a line-by-line fee schedule comparison may be misleading unless the contracted grouping and settlement terms are accounted for.

Practical Reimbursement Validation Workflow

Step 1: Define the review population

Select a specific payer and product, service dates, billing entities, encounter types, and claim statuses. Decide whether the unit of analysis is a line, claim, payment cycle, or defined episode. Exclude or separately classify voids, reversals, test claims, and non-final adjudications when those do not belong in the target population.

Step 2: Reconstruct the payer’s adjudication

Review the EOB or 835 to confirm what the payer adjudicated: allowed amount, payment, adjustment group and reason codes, cost sharing, and any remarks. CMS explains that remittance adjustments can occur at service, claim, or provider level, with different informational and financial functions.^[1]

Step 3: Validate the contract expectation

Recalculate independently from the governing terms and validated source data. Confirm units, modifiers, rate effective dates, pricing methodology, and exclusions before treating the difference as payer error.

Step 4: Compare like with like

First compare expected allowed with adjudicated allowed. Then compare expected payer responsibility with reported claim payment after supported deductible, coinsurance, copayment, and coordination-of-benefits information. Separately compare the total remittance payment with the actual EFT after PLBs or other documented provider-level adjustments.

Step 5: Investigate rather than automatically write off

Review code accuracy, coverage rules, plan eligibility, contractual reductions, prior-payer effects, payer pricing, internal configuration, reversals, and posting history. A difference may arise from several causes, and no single amount on the remittance proves the cause.

Step 6: Establish the appropriate action

Determine whether the next action is an internal posting correction, an expected-rate configuration review, a code/documentation review, a payer inquiry, a formal contract dispute, or no correction. Confirm required evidence and deadlines with the team authorized to act.

Step 7: Track resolution and financial outcome

Log the suspected amount, supported variance, submitted dispute, payer response, revised adjudication, and any actual additional cash. Reconcile recovered funds to the resulting ERA and EFT. Don't describe disputed dollars as recovered dollars.

Step 8: Test whether the issue recurs

For repeated findings, compare affected periods and configuration changes; review representative claims; and follow the resolution through a controlled monitoring period. A corrected individual claim does not establish that a payer rule or system setup has been fixed.

Worked Example: Allowed Amount Versus Payer Payment

Illustrative contract example: A professional service is billed at $400. The applicable contracted allowed amount is $250. Under the example patient benefits, the patient has 20% coinsurance on the allowed amount, with no remaining deductible and no other applicable adjustment.

Component	Calculation	Amount
Billed charge	Submitted amount	$400.00
Expected allowed	Validated contract fee	$250.00
Contractual difference	$400.00 − $250.00	$150.00
Expected coinsurance	20% × $250.00	$50.00
Expected payer payment	$250.00 − $50.00	$200.00
Actual adjudicated allowed	Payer remittance	$250.00
Actual patient coinsurance	Payer remittance	$50.00
Actual payer payment	Payer remittance	$180.00

The allowed amount matches the contract. The actual payer payment is $20 lower than the independently calculated expectation, yet the payer-designated coinsurance accounts for only $50 of the allowed amount. That discrepancy requires additional review; it shouldn't be reclassified to patient responsibility merely to close the claim.

A reviewer would first check for claim- or service-level adjustments not included in the simplified display, any reported payment offsets, prior adjudication, or an incorrect extraction. If no legitimate adjustment explains the difference, the reviewer should route the claim for correction or payer inquiry with the supporting benefit and contract information.

Worked Example: A Contracted Percentage of a Benchmark

Illustrative commercial contract: The executed agreement specifies 140% of an identified fee schedule for a covered service. The correctly selected schedule amount for the service date, locality, and modifier is $120. The payer reports an allowed amount of $150, and the claim has no applicable patient cost sharing in this example.

Measure	Calculation	Amount
Contract benchmark	Approved schedule amount	$120.00
Expected allowed	140% × $120.00	$168.00
Payer allowed	Actual adjudication	$150.00
Potential allowed variance	$168.00 − $150.00	$18.00
Actual payer paid	Assume no other deductions	$150.00
Potential payer underpayment	Pending term and claims validation	$18.00

The $18 difference is a potential underpayment until the correct contract version, product, locality, code, modifier, and exclusions are confirmed. A rate table misconfiguration and payer mispricing can look identical on a variance report. If the payer correctly used an agreed carve-out, the flagged amount may not be recoverable.

Worked Example: Line-Level Errors Hidden by a Correct Total

Illustrative two-line claim: A contract-based model expects $160 for Service A and $90 for Service B. The payer allows $140 and $110, respectively.

Service	Expected allowed	Payer allowed	Variance: expected − actual
Service A	$160.00	$140.00	+$20.00
Service B	$90.00	$110.00	−$20.00
Total	$250.00	$250.00	$0.00

The claim-level totals agree, but both service lines differ from the model. Before proposing a correction, determine whether contract rules intentionally combine or redistribute allowed amounts at the claim level. When the agreement requires line-specific pricing, the offsetting variances warrant investigation. A balanced total is not proof that every transaction is correct.

Validating the Deposit: Claims, PLBs, and the Actual EFT

Contractual reimbursement validation and deposit balancing are connected but different controls. An ERA can report correctly adjudicated claim payments while the payer’s EFT is lower because a provider-level recovery or another PLB reduces the net transfer. CMS identifies provider-level adjustments as activity generally not tied to a single claim in the current remittance.^[1]

Remittance or cash component	Amount
Current claims paid on ERA	$800.00
Illustrative provider-level recovery	−$125.00
Expected EFT	$675.00
Bank-confirmed EFT	$675.00
Unreconciled deposit difference	$0.00

Here the deposit balances, but the $125 recovery still requires separate validation against its original payment, supporting correspondence, and previous postings. The reviewer shouldn't assign it to a current patient claim solely because it reduced the funds received. Additional PLB mechanics belong in the separate PLBs, Recoupments & Retractions foundation.

Common Variance Patterns and How to Investigate Them

Finding	Possible explanation	Validation or next step
Allowed amount below expectation	Outdated contract rate, wrong product, carve-out, payer pricing discrepancy.	Verify contract effective date, plan, rate method, and claim attributes.
Payment below allowed amount	Correct cost sharing, coordination of benefits, separate adjustments, or processing error.	Examine group codes, CARCs, RARCs, secondary status, and account history.
Expected payment matches ERA but not EFT	PLB recovery, reassociation error, incomplete remittance grouping.	Match remittance totals, TRN references, PLBs, and bank activity.
Same variance across many codes	Wrong contract multiplier, benchmark year, or system mapping.	Test independent claim samples and compare configuration effective dates.
Only one modifier varies	Modifier-specific contracted rate or incorrect submitted/posted modifier.	Validate documentation, coding, contract terms, and payer treatment.
Closed accounts show no remaining AR	Automated adjustment or contractual write-off may have absorbed variance.	Compare allowed/payment against independent expectation, not just open AR.
Secondary payer reports unexpected outcome	COB rules and prior-payer effects may affect payment.	Review primary EOB, OA-23 or other adjudication information, and secondary contract.
Payer reverses and reprocesses claim	Original and replacement adjudications may both appear in extracts.	Trace version history and net account effects before counting a variance.

A practical escalation packet

For a supported variance, a useful packet includes the claim number, service date, billed and adjudicated service details, payer and plan, applicable contract or authorized rate summary, expected calculation, EOB/ERA evidence, payment and adjustment history, and a concise explanation of the specific difference. Include the applicable reconsideration or dispute deadline and the required submission channel when established.

Sensitive contract documents and protected health information should be shared only through authorized channels. The objective is to give the responsible team enough reliable evidence to make a decision, not to circulate more information than necessary.

Financial Reporting Without Inflating Results

An identified variance isn't automatically money lost, money owed, or money recovered. Reliable revenue integrity reporting distinguishes the stage of validation.

Status	Meaning
Suspected variance	A flagged difference that still needs source or contractual validation.
Validated difference	A supported mismatch after the relevant terms and transaction history are reviewed.
Recoverable amount	A supported amount the organization may pursue, considering contract rights and deadlines.
Disputed amount	An amount formally raised with the payer or other responsible party.
Recovered cash	Additional funds actually received and reconciled.
Prevented future loss	A supported estimate of future impact from a tested corrective control, clearly separate from cash collected.

For example, an automated report may flag 100 claims at $20 each, or $2,000 in preliminary differences. After sampling and validation, some may reflect legitimate benefit or contract exclusions. Even if $800 remains supportable and is submitted for dispute, the amount actually recovered could be different. The report should retain those distinctions rather than presenting all $2,000 as recovered revenue.

Operational measures worth monitoring

• Share of reviewed claims with validated discrepancies, defined against a consistent denominator.
• Validated variance dollars by payer, service family, contract version, and source of issue.
• Disputed dollars and dispute outcomes, with aging and deadline status.
• Recovered cash supported by additional remittances and deposit reconciliation.
• Recurring errors after approved contract-model or payer corrections.

A count of closed variance cases isn't the same thing as successful reimbursement recovery. A case may close because the original expectation was wrong, because the payer corrected its payment, or because the organization accepted a supported adjustment.

Reimbursement Validation Reference Checklist

• Confirm the correct payer, plan, provider, service setting, and contract effective period.
• Identify the approved reimbursement methodology and applicable source rate.
• Validate service codes, modifiers, units, and any grouping or carve-outs.
• Calculate the expected allowed amount independently.
• Review the adjudicated allowed amount and all relevant adjustment details.
• Separate patient cost sharing and prior-payer effects from payer underpayment analysis.
• Compare expected claim payment with reported claim payment.
• Reconcile ERA totals and PLBs to actual EFT separately when necessary.
• Investigate internal configuration and posting errors before asserting payer underpayment.
• Document evidence, ownership, required deadlines, and the resolution pathway.
• Confirm recovered money in the account history and bank reconciliation.
• Monitor patterns after any authorized corrective change.

Reimbursement validation is strongest when the expectation can be explained and independently reproduced. A variance report tells the team where to look; the contract, adjudication, account records, and investigation establish what happened and what should follow.

References and Further Learning

The resources below support the technical concepts in this guide. Medicare-specific materials describe Medicare methodologies and remittances; commercial contract reimbursement must be validated against the applicable executed agreement and plan requirements.

References

Source	What It Supports
CMS: Health Care Payment and Remittance Advice	ERA claim/line adjustments, group codes, CARCs, RARCs, and PLBs.
CMS: Physician Fee Schedule Look-up Tool Overview	Fee schedule lookup, Medicare payment locality and pricing policy context.
CMS: Fee Schedules, General Information	Distinctions among Medicare reimbursement schedules and their scope.
CMS: Health Care Payment and Remittance Advice and EFT	Standardized remittance and payment transaction context.
HFMA: Healthcare Reimbursement Under Value-Based and Fee-for-Service Models	Overview of reimbursement models, contract variation, and performance.

Additional Learning

Resource	What You’ll Learn
CMS: PFS Quick Reference Search Guide	How to select fee schedule year, location, modifier, and payment information.
CMS: Physician Fee Schedule Documentation and Files	Rate data, RVUs, payment policy indicators, and source file descriptions.
CMS: Medicare Claims Processing Manual	Program-specific claim and remittance processing rules.
HFMA: Healthcare Reimbursement Models	Broader reimbursement methodology and performance context.

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

← Return to Main Category Explore Revenue Cycle Departments