🚀 Live & improving daily! New courses, features, and content added every day.
DenialPro
HomeDenial Code HubOA-94
OA-94OA CodeOverpaymentFrequency: Low Last Reviewed August 2026 Source: X12 / WPC

OA-94 — Processed in Excess of Charges

The payer paid more than what was billed. This is an overpayment — you are legally and contractually obligated to return the excess. Do not spend it. Investigate promptly and process the appropriate refund or offset.

Resolution Steps Appeal GuidanceFAQ

Official Definition

Processed in excess of charges.

Code Type
OA — Other Adjustment
Category
Overpayment
Impact Level
Medium

What This Code Means

The payer paid more than what was billed. This is an overpayment — you are legally and contractually obligated to return the excess. Do not spend it. Investigate promptly and process the appropriate refund or offset.

Status

Payment Adjustment

Recommended Action

1Review the denial message and full ERA/EOB.
2Verify the adjustment amount and confirm the claim is final, not pending or still recoverable.
3Reconcile the remaining balance before adjusting.
4Apply or request the adjustment per your organization's workflow.
5Do not bill the patient for contractual adjustments.

Same standard code · different claim context

How OA-94 can be investigated across specialties

CARCs and RARCs are not separate code sets for radiology, gastro, hospital, or professional billing. The code meaning stays standardized; the claim fields, documentation, payer rules, and next checks change by setting.

Professional / Office

Check CMS-1500/837P fields, rendering/billing NPI, diagnosis, modifier, place of service, authorization, and payer policy.

Hospital / Facility

Check UB-04/837I bill type, revenue code, status, inpatient/outpatient rules, authorization, and line-level ERA detail.

Radiology

Check 26/TC component billing, imaging authorization, medical necessity, site of service, same-day edits, and referring provider data.

Gastroenterology

Check procedure relationships, screening vs diagnostic context, modifiers, pathology/anesthesia relationships, authorization, and payer edits.

Behavioral Health

Check provider credential, behavioral-health carve-out, authorization, units/time, telehealth, place of service, and plan-specific rules.

Therapy / Rehab

Check therapy modifiers, timed units, benefit limits, authorization, plan of care/documentation, and NCCI/payer edits.

DME / Supplies

Check HCPCS, modifiers, same/similar equipment, medical necessity, proof of delivery, authorization, and supplier enrollment.

Lab / Pathology

Check CLIA, ordering/referring data, diagnosis support, frequency, panel bundling, specimen/documentation, and payer medical policy.

Financial Impact

Avg. Denial Rate
Less than 1% of claims
Days to Resolve
30–90 days to reconcile and return
Appeal Success Rate
N/A — this is an overpayment, not a denial
Revenue Risk
Medium — failure to return overpayments creates compliance and audit risk

Should This Go to Coding?

USUALLY NOT CODING

Do not send every denial to Coding. Coding is appropriate only when the resolution requires coding judgment rather than an administrative or payer follow-up action.

Send to Coding When

A CPT/HCPCS, ICD-10, modifier, NCCI edit, code pair, sequencing rule, or documentation-to-code decision must be reviewed.

Do Not Send to Coding When

Eligibility or member ID issue.
COB or wrong payer.
Missing authorization with no coding question.
Timely filing.
Contractual adjustment such as validated CO-45.
Deductible, coinsurance, or copay after secondary coverage is checked.

Simple rule: If you would have to choose, change, or defend a CPT/HCPCS, ICD-10, modifier, code pair, NCCI edit, or documentation-to-code decision, Coding should review it.

Corrected Claim, Reconsideration, Appeal, or Something Else?

RESEARCH FIRST

Use the ERA/EOB, RARC, payer portal, policy, claim history, and internal workflow to decide between corrected claim, reconsideration, appeal, coding review, payer follow-up, patient responsibility, or adjustment.

Corrected claim: use when your original claim data was wrong or incomplete.
Reconsideration: use when the claim was processed but the payer should review it again, often with added information.
Appeal: use when you disagree with the payer decision and have evidence supporting payment.
Do not duplicate: do not send multiple paths at once unless the payer specifically instructs you to.
See payer-specific submission methods

Should I Adjust This Balance?

POSSIBLE ADJUSTMENT — VERIFY FIRST

This code may support an adjustment, but the code alone is not enough. Validate the full remittance, remaining balance, contract/policy, and whether any recovery path is still available.

Confirm final adjudication on the ERA/EOB and payer portal.
Reconcile billed, allowed, paid, patient responsibility, prior adjustments, and remaining balance.
Confirm there is no secondary payer, corrected claim, reconsideration, appeal, coding, authorization, or enrollment action still available.
Follow your organization's adjustment authority and approval threshold.

Collections rule: A denial code by itself does not automatically mean write-off. Work the claim for payment first when a valid recovery path exists.

What Should My Account Note Say?

4-Part Note Formula

WHAT HAPPENED + WHAT YOU REVIEWED/DID + WHY THAT ACTION WAS CORRECT + WHAT HAPPENS NEXT

General Denial Note

REVIEWED ERA/EOB FOR OA-94. PAYER PROCESSED/DENIED $[AMOUNT] DUE TO [DENIAL REASON + CARC/RARC]. VERIFIED [PORTAL/ELIGIBILITY/CLAIM HISTORY/POLICY/CODING/AUTHORIZATION]. [ACTION TAKEN] BECAUSE [WHY THIS ACTION IS SUPPORTED]. REMAINING BALANCE $[BALANCE]. WILL FOLLOW UP IN [TIMEFRAME] OR NO FURTHER PAYER ACTION REQUIRED.

Adjustment Note

REVIEWED ERA/EOB FOR OA-94. PAYER APPLIED $[AMOUNT] AS [CONTRACTUAL/NONPAYABLE REASON]. VERIFIED FINAL ADJUDICATION, [CONTRACT/POLICY/CODING REVIEW], AND NO ADDITIONAL RECOVERY PATH. ADJUSTED/REQUESTED ADJUSTMENT OF $[AMOUNT] PER ORGANIZATIONAL WORKFLOW. REMAINING BALANCE $[BALANCE]. [FOLLOW-UP OR RESOLVED].

Current decision: POSSIBLE ADJUSTMENT — VERIFY FIRST. Do not document an action you did not actually perform. Do not say a payment was posted unless you personally posted it.

How to Investigate

Investigation Checklist

Step-by-Step Workflow

1Compare the paid amount on the remittance to the billed charge
2Identify the specific claim and service line where the overpayment occurred
3Verify the overpayment is real — confirm it is not a legitimate allowable that exceeds your billed charge
4Determine whether the payer has issued a formal overpayment demand letter
5Check if a prior period adjustment (PPA) or takeback will offset future claims automatically

Common Causes

1
Payer system or fee schedule error resulted in excess payment
2
Duplicate claim processed twice by the payer in error
3
Benefit plan recalculation after initial payment issued too much
4
Coordination of benefits miscalculation resulted in over-reimbursement
5
Manual override or exception payment exceeded billed amount

Related Denial Codes

OA-23CO-45

Step-by-Step Resolution

If overpayment is confirmed: do not post the excess as revenue — hold it pending resolution
Contact the payer to initiate the return process or confirm their preferred method
Issue a refund check to the payer or allow a future claim offset (takeback)
Document all communications with the payer regarding the overpayment
Update your AR records to reflect the correct payment amount

Appeal Guidance

Appeal Grounds

OA-94 is not typically appealed. Only dispute if the payer incorrectly labeled a legitimate payment as an overpayment.

Appeal Letter Template

We are disputing the OA-94 overpayment determination for [patient], DOS [date]. Our review shows the payment of $[amount] is within the contracted allowable rate per our provider agreement dated [date]. Attached is our fee schedule reference. We request a review of the overpayment calculation before any recovery action.

Required Documentation Checklist

Remittance showing OA-94 and payment amount
Original claim with billed charge
Fee schedule or contract showing correct allowable
Payer overpayment demand letter if received

Real-World Examples

Fee Schedule System Error

Resolved
Situation

Payer system glitch paid a 99215 at $350 when contracted rate is $175. OA-94 noted on the remittance. Payer issued a takeback notice.

Outcome

Confirmed the overpayment. Allowed automatic offset against next claim cycle. No refund check needed.

Disputed Overpayment

Won
Situation

Payer flagged $200 as OA-94 overpayment. Provider reviewed contract — the $200 was correct per a fee schedule update effective January 1.

Outcome

Disputed with copy of updated fee schedule. Payer withdrew the overpayment demand. Revenue retained.

Frequently Asked Questions About OA-94

Educational Platform Notice

DenialPro is an educational platform designed to teach medical billing denial management.

Do not submit Protected Health Information (PHI), personally identifiable information (PII), patient names, member IDs, claim numbers, dates of birth, medical record numbers, or confidential healthcare information.

Always verify guidance with official payer policies, CMS guidance, coding guidelines, and applicable regulations.

Need More Help?

Take the next step toward mastering denial management.

Learn in DenialPro Academy

Interactive courses with quizzes, practice labs, real-world scenarios, and certification.

Browse Courses

Practice This Denial

Code lookup is free. Hands on account labs, graded practice, and simulators are premium.

Open Practice Center

Get DenialPro Services

Expert denial management consulting and done-for-you appeal services.

Explore Services