OA-23 Denial Code: 2026 Resolution Guide for Coordination of Benefits Denials

Your secondary claim came back with a $0 payment. The remittance shows OA-23, and the claim adjustment dollars don’t match what your auto-posting logic expected. Now your team’s stuck deciding whether to bill the patient, write it off, or appeal.

The oa 23 denial code isn’t a true denial. It’s a coordination of benefits adjustment. The secondary payer reviewed what the primary payer already paid plus adjusted, then calibrated reimbursement accordingly.

X12 maintains the official CARC 23 definition under External Code List 139, last modified November 1, 2025. CMS Change Request 8297 governs how Medicare applies it on secondary claims.

This guide covers what OA-23 actually means, how to read it on the ERA, who pays, the X12 RFI #2570 auto-posting rule most billers don’t know, and the 2026 resolution workflow that protects your timely filing window.

Quick Answer: What Is the OA-23 Denial Code?

The OA-23 denial code is the combination of Claim Adjustment Group Code OA (Other Adjustment) and Claim Adjustment Reason Code 23, which X12 defines verbatim as “the impact of prior payer(s) adjudication including payments and/or adjustments. (Use only with Group Code OA).” It appears on the 835 ERA when a secondary or tertiary payer adjusts reimbursement based on what the primary payer already paid and adjusted. OA-23 is generally not patient billable.

What Is the OA-23 Denial Code? Official X12 + CMS Authority Definition

The OA-23 denial code sits at the intersection of two standards-body frameworks: the X12 Claim Adjustment Reason Code system and the CMS coordination of benefits processing rules. Most billers search for the oa 23 denial code description because the ERA shows a zero-payment line without context. Here’s the context.

The X12 Definition (CARC 23 Verbatim)

X12, the standards body that maintains all Claim Adjustment Reason Codes under HIPAA, defines CARC 23 as “the impact of prior payer(s) adjudication including payments and/or adjustments. (Use only with Group Code OA).”

That definition lives on X12’s External Code List 139, last modified November 1, 2025. You’ll find the active version on the X12 CARC official list. CARC 23 has been active since the original list was established. It hasn’t changed.

The operational interpretation: “impact” means the secondary payer’s reimbursement gets reduced by what the primary already paid and adjusted. The oa 23 denial code description is the secondary payer doing math, not making a coverage determination.

The claim adjustment reason code framework is what makes this HIPAA-mandated, not optional. Every payer using X12 835 transactions must express adjustments using X12-maintained claim adjustment reason codes. The secondary payer can’t invent its own code , it uses CARC 23 with Group Code OA because that’s what the standard specifies.

Why CMS Calls It “OA-23”: Group Code OA Explained

CMS Change Request 8297 modifies Medicare claims processing systems to apply Claim Adjustment Reason Code 23 with Group Code OA when reporting the impact of a prior payer’s adjudication on Medicare secondary claims.

Group Code OA stands for “Other Adjustment” in the X12 group code framework. OA is the residual category: it gets applied when CO (Contractual Obligation), PR (Patient Responsibility), PI (Payer Initiated Reduction), and CR (Correction and Reversal) don’t fit.

The pairing rule: CARC 23 must always pair with Group Code OA per X12’s “Use only with Group Code OA” instruction.

This is why you see “OA-23” formatted that way. It’s the Group Code + Reason Code combination, not a single code. Practices managing high-volume secondary claims need denial management services that distinguish OA-23 from true denials at intake.

Why the Term “Denial Code” Is Technically Wrong

Here’s why that matters for your workflow. OA-23 is technically a claim adjustment reason code, not a denial code. CARCs explain why a payer adjusted a claim from the billed amount , sometimes the adjustment is a denial, sometimes it’s a coordination offset, sometimes it’s a contractual write-off.

The industry calls all CARCs “denial codes” colloquially. X12 and CMS classify them as adjustment codes. Misclassifying OA-23 as a denial sends it to the wrong workflow queue.

How OA-23 Appears on the 835 Electronic Remittance Advice

The oa23 denial code doesn’t live on the claim form. It surfaces after adjudication on the X12 835 Health Care Claim Payment/Advice transaction. Reading it correctly requires understanding three structural components of the ERA. Here’s the part most billers miss: the oa 23 remark code terminology is a category error , OA-23 isn’t a remark code at all.

The CAS Segment , Where OA-23 Lives on the ERA

Payers transmit OA-23 through the X12 835 Health Care Claim Payment/Advice transaction (version 005010X221A1), the HIPAA-mandated electronic remittance format. The adjustment lives in the CAS segment , short for Claim Adjustment Segment , at either the service line level or the claim level.

Per CMS Health Care Payment and Remittance Advice, the exact CAS segment notation looks like this:

CAS*OA*23*[adjusted dollar amount]~

Each CAS segment carries three required elements: the Group Code (OA), the Reason Code (23), and the monetary value. The CMS MSP Manual shows this exact notation in its abbreviated Medicare secondary example: CAS*OA*23*630~. Your billing system parses these elements to auto-post adjustments. When auto-posting fails on oa23, the CAS segment is usually where the breakdown lives.

CARC vs RARC , Why OA-23 Is a CARC, Not a Remark Code

OA-23 is a Claim Adjustment Reason Code (CARC), not a Remittance Advice Remark Code (RARC). The two serve different functions on the 835. CARCs explain the primary reason a payer adjusted a claim. RARCs supplement CARCs with additional detail and appear in the LQ segment at the service line level or the MIA/MOA segments at the claim level.

This answers the “What is the OA 23 remark code?” question directly. OA-23 is a CARC, not a remark code. The oa23 remark code description searches want supplemental context, which lives in the RARC layer.

When your AR follow-up team misreads CARC and RARC roles on the 835, it routes the claim to the wrong resolution queue. The AR follow-up team needs to read the full three-code stack , group code, CARC, and RARC , before deciding the next action.

The X12 RFI #2570 Auto-Posting Rule (Most Billers Miss This)

X12 Request for Interpretation #2570 , the current standards-body interpretation governing OA-23 auto-posting , clarifies three rules billers consistently miss.

First, the COB “impact” is one adjustment, reported at either the claim OR service line level , never both. Reporting it at both levels adjusts the same dollars twice, which X12 explicitly prohibits.

Second, when CARC 23 is used, it must include the sum of both the prior payer’s payment(s) and adjustment(s) combined. Splitting the prior paid amount and prior adjustment into separate CAS segments is not permitted.

Third, payers that send OA-23 inconsistently across both claim and line levels create auto-posting failures that force manual review. That’s an EDI normalization issue, not a coding error , and the resolution path is to escalate to the payer’s EDI team referencing RFI #2570 directly.

Practices that see the oa 23 denial code alongside CO-22 denial code patterns are looking at COB-data integrity issues that need front-end fixes, not back-end appeals.

OA, CO, PR, PI, and CR: Understanding the Five Group Codes That Determine Who Pays

What does oa mean on an eob, and what does oa stand for in billing? It depends on which claim adjustment reason code follows it. The Group Code prefix on every ERA adjustment line answers one question: who absorbs this dollar amount?

The Reason Code that follows answers why. Understanding this framework is what separates billers who resolve OA-23 efficiently from those who route it to appeals and wonder why nothing comes back.

The Five Group Code Framework

X12 defines five Claim Adjustment Group Codes: OA (Other Adjustment), CO (Contractual Obligation), PR (Patient Responsibility), PI (Payer Initiated Reduction), and CR (Correction and Reversal). The Group Code prefix tells you who absorbs the dollar amount being adjusted. The Reason Code that follows tells you why.

What does oa stand for in billing? OA is the residual category in the five-code framework. Here’s the full breakdown, including how each code interacts with OA-23:

We covered this exact framework for reason code 96 in our CO-96 denial code framework guide, which walks through CO-96, PR-96, PI-96, and OA-96 with full operational detail. The logic is identical across reason codes. Only the “why” changes.

Why OA Is the “Residual” Group Code

OA is the residual category in the X12 group code framework. Payers assign OA only when CO, PR, PI, and CR don’t fit. That’s why X12’s CARC 23 instruction reads “Use only with Group Code OA.”

The impact of prior payer adjudication isn’t a contractual issue (CO), isn’t patient liability (PR), isn’t a payer-initiated reduction (PI), and isn’t a correction (CR). It’s a coordination offset, full stop.

This residual-category framing is what makes OA-23 different from every other “23” variant. The X12 Claim Adjustment Group Codes list explains the framework for all five group codes.

When you see OA on any reason code, your first question should be: “Is this a coordination of benefits issue?” That’s the most common OA trigger. The oa 23 denial reason almost always traces back to a COB calculation. The denial code oa 23 meaning becomes clear once you understand OA is the “everything else that doesn’t fit a contract” bucket.

CO-23 vs OA-23: The Distinction That Changes Your Workflow

CO-23 and OA-23 are not the same code. They share Reason Code 23, but the Group Code prefix changes the financial responsibility entirely.

CO-23 means the payer is applying the impact of prior payer adjudication as a contractual obligation: the provider absorbs it as a write-off per the payer agreement.

OA-23 means the payer is applying the same impact as a coordination offset, which doesn’t fall under any contractual write-off, patient liability, or payer-initiated reduction category. The OA group code makes this a pure between-payers adjustment.

Here’s the side-by-side comparison that changes your workflow in practice:

The co 23 denial code in medical billing is frequently confused with OA-23 because they share the same reason code number. That confusion sends CO-23 claims through COB resolution workflows and sends OA-23 claims through contract review. Both routes reach the wrong destination.

The co 23 denial code result: the provider absorbs it as a contractual write-off under the network agreement. The OA-23 result: the provider absorbs it as a coordination offset, separate from contract terms.

The same group code logic applies one digit down. Our CO-22 denial code guide walks through the CO-22/PR-22/OA-22/PI-22 framework that mirrors what we’ve covered for reason code 23.

PR-23: Why You Almost Never See It

PR-23 (Patient Responsibility, Reason Code 23) exists in theory but is operationally rare. The X12 CARC 23 definition contains the explicit instruction “Use only with Group Code OA,” which means PR-23 violates the standard. If a remittance shows PR-23, it’s almost certainly a payer error. The adjustment should have been OA-23.

Don’t accept PR-23 as patient-billable without confirming the payer’s coding logic. What is oa 23 denial code patient responsibility? OA-23 is not patient responsibility. The OA group code signals that the adjustment falls outside patient liability.

Legitimate patient-responsibility denials follow the PR group code framework. See our PR-27 denial code guide for the operational example of a genuine PR-prefix adjustment.

Who Pays for OA-23? The Patient-Billing Compliance Rule

OA-23 is not patient billable. This is the most important compliance sentence in this entire guide. The OA group code explicitly signals an adjustment that doesn’t transfer to patient liability. Billing patients for OA-23 amounts creates compliance exposure across every payer type. Here’s why, and here’s the narrow exception you need to know.

OA-23 Is Not Patient Billable: Here’s Why

OA-23 is not patient billable. Unlike PR group code adjustments (which can transfer to patient liability for deductible, coinsurance, or copay amounts), the OA group code signals an adjustment outside patient responsibility.

The dollars adjusted under OA-23 are coordination offsets between payers. The patient owes nothing on the OA-23 line item itself.

This directly answers the “oa 23 denial code patient responsibility” question. The X12 standard is explicit: “Use only with Group Code OA” means the standard excludes PR group code application by design. The operational rule: never transfer an OA-23 dollar amount to a patient statement without separate PR-coded amounts on the same claim.

The Functional Outcome: Provider Write-Off

In practice, OA-23 results in a write-off on the provider’s books. But the classification matters for compliance and reporting. There’s an important distinction between the two write-off types:

CO-23: contractual write-off. The provider absorbs it per network contract. OA-23: coordination write-off. The provider absorbs it because no other party owes it.

Both functionally reduce A/R. But OA-23 isn’t a contract concession. It’s a COB outcome. Misclassifying OA-23 as a contractual write-off skews your contracted-rate analytics. The oa 23 denial isn’t telling you the contract rate was less than billed. It’s telling you the prior payer already covered what this payer would have paid.

Compare this to legitimate patient-responsibility denials like PR-27 patient responsibility for terminated coverage , those truly transfer to the patient under specific conditions.

When You Might See PR Amounts on the Same Claim Line

The entire claim line isn’t always 100% OA. The same claim can carry OA-23 alongside separate PR amounts. Example: secondary payer applies OA-23 to the prior-payer impact AND PR-1 (deductible) to the patient’s secondary-plan deductible portion.

Always read the full CAS segment stack for a claim line. Don’t make billing decisions on the OA-23 line alone. If the remittance shows OA-23 and PR-1/PR-2/PR-3 on the same line, the PR amounts go to the patient. The OA-23 amount does not.

What is oa 23 denial code patient responsibility in this scenario? The PR amounts are patient responsibility. The OA-23 amount is not.

The Compliance Risk of Misclassifying OA-23

Practices that bill patients for OA-23 amounts create compliance exposure. For Medicare patients specifically, this can constitute a Medicare billing violation. For commercial patients, it triggers patient complaints, payer audits, and potential contractual breaches.

Systematic oa 23 denial code classification at remittance posting is the front-line defense. Practices that systematically misclassify OA-23 as patient-billable need denial management services that catch the error at posting, not at the patient-statement stage.

OA-23 in the Real World: Three Coordination of Benefits Worked Examples

The best way to understand an oa 23 denial code example is to walk through the dollar movement from primary to secondary to final outcome. Most COB explanations stop at “secondary pays less because primary already paid.” The worked examples below show exactly why, and where the OA-23 appears in the math.

Example 1: Commercial Primary, Commercial Secondary ($400 Office Visit)

A patient has Aetna as primary and BCBS as secondary. The provider bills a $400 office visit.

Aetna processes (primary): Allowed amount $200, contractual adjustment CO-45 $200, Aetna pays $160, patient deductible PR-1 $40.

Provider sends secondary claim to BCBS with Aetna’s EOB attached.

BCBS reviews: BCBS’s allowed amount for the same service is $180. Aetna already paid $160 and assigned $40 deductible.

BCBS calculates secondary liability: $180 BCBS allowed minus $160 Aetna paid equals $20 remaining within BCBS’s allowable.

BCBS adjudicates: Pays $20 toward the patient’s $40 Aetna deductible. Remaining $20 of the deductible stays as PR-1. The original $200 contractual adjustment carries forward.

Where OA-23 appears: If BCBS’s allowed amount had been lower than what Aetna already paid, the entire BCBS portion would post as OA-23. The impact of Aetna’s prior adjudication exhausted BCBS’s liability. That’s the oa 23 denial code example in its cleanest form.

Example 2: Medicare Primary, Commercial Secondary ($1,500 Cataract Surgery)

A 67-year-old patient has Medicare as primary and a commercial Medigap policy as secondary. The provider bills CPT 66984 (cataract surgery) at $1,500.

Medicare processes (primary): Approved amount $1,200, sequestration adjustment CO-253 $24, Medicare pays $952, patient deductible/coinsurance PR $224.

Provider sends crossover claim to Medigap secondary through the COBA crossover process.

Medigap reviews: Medigap’s coverage covers the Medicare patient liability of $224.

Medigap pays $224 toward PR amount. Patient owes $0.

The OA-23 scenario: If the secondary had been a non-Medigap commercial plan with a lower allowable than Medicare’s approved amount, the secondary would post the difference between its allowable and Medicare’s paid amount as OA-23. This is the oa23 denial reason that surfaces on Medicare secondary claims most often.

Example 3: Commercial Primary, Medicaid Secondary ($600 Outpatient Procedure)

A patient has BCBS as primary and Medicaid as secondary (payer of last resort). The provider bills a $600 outpatient procedure.

BCBS processes (primary): Allowed amount $400, contractual adjustment $200, BCBS pays $320, patient coinsurance PR $80.

Provider sends secondary claim to Medicaid with BCBS EOB attached.

Medicaid reviews: Medicaid’s allowed amount for this procedure is $350 (state fee schedule). BCBS already paid $320.

Medicaid calculates: $350 Medicaid allowed minus $320 BCBS paid equals $30 within Medicaid’s liability range. Medicaid covers patient liability up to its allowed amount.

Adjudication outcome: Medicaid pays $30 toward the $80 patient coinsurance. The remaining $50 posts as OA-23 because Medicaid’s payer-of-last-resort calculation exhausted its liability. The patient owes $0. This is the oa 23 denial code medicaid scenario that catches practices off guard the first time they bill dual-coverage Medicaid patients.

The Pattern Across All Three

Every one of these examples shares the same operational signature. The secondary payer’s calculation determined that the primary payment plus adjustments already met or exceeded the secondary’s allowable. Here’s what every one of these examples has in common: none of these scenarios transfer the OA-23 amount to the patient.

The OA-23 dollar amount is always the gap between what the secondary would have paid alone and what was already paid by the primary. The oa 23 denial shows you the arithmetic. The write-off is the correct resolution. Practices that handle high COB volume rely on medical billing services that automate this calculation across primary, secondary, and tertiary payers.

How to Resolve an OA-23 Denial: The 7-Step Workflow

Before you touch the resolution workflow, ask one question: did the secondary payer apply OA-23 because the primary payer’s adjudication exhausted secondary liability, or because the COB data was incomplete? The first scenario doesn’t need a workflow , it needs accurate posting. The second scenario is what the oa 23 denial code resolution steps below address.

Step 1: Pull the Primary Payer’s Remittance Advice

Start by retrieving the primary payer’s full ERA or EOB. You need the exact paid amount, contractual adjustments (CO-45 or similar), patient responsibility amounts (PR-1, PR-2, PR-3), and any companion RARCs. The secondary payer’s OA-23 calculation depends on this data being captured correctly. Missing or partial primary data is the single most common root cause of unresolvable OA-23 denials.

Step 2: Verify the Insurance Sequence

Confirm the COB order in the patient’s record. The primary plan has to be billed first, regardless of which plan the patient prefers. For Medicare patients, run the BCRC check before assuming Medicare is primary. For commercial-commercial dual coverage, apply the Birthday Rule for dependent children.

A systematic eligibility verification process at the front end catches sequencing errors before claims go out.

Step 3: Match the Primary EOB to the Original Claim

Compare the primary EOB against the original claim line by line. Match billed units, allowed amounts, patient demographics, and the rendering provider’s NPI. Even a one-cent rounding difference can trigger COB balancing errors at the secondary payer. Discrepancies at this stage are why the claim’s stuck on OA-23 instead of paying through normally.

Step 4: Validate the 835 CAS Segment Auto-Posting Result

Check whether OA-23 posted at the claim level or service line level , and whether your auto-posting logic accepted both. Per X12 RFI #2570, the COB impact should appear at one level only. If your ERA shows OA-23 at both claim and line levels, treat that as a payer EDI normalization issue and escalate to the payer’s EDI team. Don’t just keep manually posting it.

Step 5: Resubmit the Secondary Claim with Complete COB Loops

If the OA-23 traced back to incomplete COB data on the original secondary submission, resubmit with the X12 837 Loop 2320 (other payer information) and Loop 2330A (other payer subscriber data) fully populated.

The clearinghouse rejects empty COB loops automatically. But some payers accept incomplete loops then deny with OA-23 downstream. Both routes lead to rework. Resubmission with complete loops avoids the loop-rejection cycle.

Step 6: Track Both Primary and Secondary Timely Filing Windows

OA-23 resolution delays compound timely filing risk. If the primary takes 30 to 60 days to adjudicate and the secondary’s filing window is 90 to 180 days from date of service, you can lose secondary collection rights before the primary claim closes.

Track both windows on every OA-23 claim. Set 14-day follow-up alerts. OA-23 claims that age out hit the secondary’s CO-29 timely filing wall. At that point, the recovery options narrow to formal appeal.

Step 7: Appeal When the Payer’s COB Determination Is Wrong

Most OA-23 denials resolve through corrected resubmission, not appeal. Appeal only when the payer’s coordination calculation is factually incorrect , for example, if the secondary applied OA-23 but the primary EOB shows the secondary should have paid additional dollars.

The appeal letter cites the primary EOB amounts, the secondary’s allowable per the patient’s plan, and the gap. Strong appeals win. Boilerplate appeals lose.

When the 7-Step Workflow Doesn’t Resolve It

Some OA-23 denials don’t resolve because the underlying COB data conflict requires the patient to update their insurer’s records directly. For Medicare beneficiaries, this means calling the BCRC at 1-855-798-2627. Practices that work high OA-23 volume rely on a dedicated AR follow-up team that monitors the timely filing exposure across every COB-flagged claim.

The 10 Real Causes of OA-23 Denials (And Why Generic Lists Get This Wrong)

Most OA-23 cause lists conflate operational triggers with root causes. Coding errors don’t directly cause OA-23. They cause primary denials that propagate forward into secondary OA-23 outcomes.

Cause 1: Primary Payer’s Allowable Already Exceeded Secondary’s Allowable

The most common operational trigger. Primary paid and adjusted enough that the secondary’s calculation determines no additional reimbursement is due. This isn’t an error. It’s the system working as designed. Post as OA-23 write-off. No resolution needed.

Cause 2: Missing or Incomplete Primary EOB on Secondary Submission

The secondary needs primary’s full adjudication breakdown. Submission without the primary EOB triggers OA-23 with companion RARCs (often N23 or MA04). Resolution requires retrieving the primary EOB and resubmitting with complete COB loops.

Cause 3: Coordination of Benefits Order Error (Wrong Primary)

Provider billed the secondary first because the patient’s record had outdated COB. The secondary detects another active coverage and adjudicates as if the primary impact already applied. Triggers OA-23 even though no primary actually paid. Fix the COB order, bill the actual primary, then resubmit secondary.

Cause 4: Birthday Rule Misapplication for Dependent Children

When both parents have coverage, the parent with the earlier birthday in the calendar year holds primary. Misapplying this rule causes the wrong plan to be billed first. The “secondary” plan adjudicates with OA-23 because its system shows the other plan should have paid first. CO-22 denial code patterns alongside OA-23 signal this exact Birthday Rule error.

Cause 5: Medicare Secondary Payer (MSP) Misclassification

Patient has employer coverage at a 20-plus employee company AND Medicare. Provider bills Medicare first, but MSP rules require the employer plan as primary. Medicare adjudicates with OA-23 to signal the prior payer impact should have come from the employer plan.

Cause 6: 835 Auto-Posting Failure on Same-Dollar Adjustments

Per X12 RFI #2570, OA-23 must appear at claim level OR line level, never both. Payers that send it at both levels cause auto-posting logic to apply the same adjustment twice, triggering manual review queues. The denial isn’t the problem , the EDI normalization is.

Cause 7: Workers’ Compensation or Auto Liability Confusion

Liability carriers and group health plans share responsibility for the same episode of care. COB rules between liability and group health aren’t applied uniformly. OA-23 surfaces when one payer believes the other should be primary. Verify the liability coverage before billing either plan.

Cause 8: Outdated Patient Coverage Records

Front desk missed a coverage change at registration. Patient’s primary terminated; new primary not entered. The “secondary” plan is now functionally primary, but the system still routes the claim with stale sequencing. Insurance eligibility verification at every visit catches coverage changes before they propagate forward into OA-23 volume.

Cause 9: Coding Errors That Cascaded Through Primary Adjudication

The original claim had a coding issue that the primary payer adjusted around (often via CO-45 or CO-97). The adjusted amount carries forward to the secondary, which sees the impact and applies OA-23. Practices with high CO-236 NCCI edit denial code volume on primary claims see corresponding OA-23 spikes on secondaries weeks later.

Cause 10: Payer System Errors and EDI Normalization Issues

Sometimes the secondary payer’s adjudication engine produces OA-23 output that doesn’t match the actual coordination math. Resolution requires escalating to the payer’s EDI team with the supporting calculation. CO-151 denial code patterns sometimes coincide with payer system errors that produce OA-23 on claims where supporting documentation was submitted but wasn’t processed correctly.

Medicare-Specific OA-23: MSP Rules, COBA, BCRC, and the 2026 Medicare Update

Medicare applies OA-23 under a specific regulatory framework that differs from commercial COB. Understanding the MSP rules, the COBA crossover process, and the March 9, 2026 MAC guidance update is essential for any practice billing Medicare secondary claims.

How Medicare Applies CARC 23 , CMS Change Request 8297 Authority

CMS Change Request 8297 modifies Medicare claims processing systems to apply CARC 23 for reporting the impact of prior payer adjudication on Medicare secondary claims. The CR specifies that Medicare uses CARC 23 with Group Code OA when adjudicating as a secondary payer behind another insurer.

The CMS MSP Manual contains the canonical example: CAS*OA*23*630~ on the Medicare 835. Medicare requires providers to take CAS adjustments from the primary payer’s remittance and report them on the 837 when sending the claim for secondary payment.

The technical workflow: primary 835, then CAS data extracted, then 837 secondary submission populated with primary CAS data, then Medicare adjudication applies OA-23 to reflect the prior adjudication impact.

Medicare 835s commonly carry both CO-253 Medicare sequestration adjustments and OA-23 in the same remittance. The codes serve different purposes but appear together on Medicare-as-secondary claims.

Medicare Secondary Payer (MSP) Rules That Trigger OA-23

MSP rules under 42 U.S.C. 1395y(b) determine when Medicare pays secondary. The four primary MSP scenarios are: working aged (employer with 20-plus employees), End Stage Renal Disease (ESRD) provision, no-fault and liability insurance, and Workers’ Compensation.

Working aged: Patient is 65-plus, employed at 20-plus employee company. Employer plan primary, Medicare secondary. ESRD: During the 30-month coordination period, group health plan primary, Medicare secondary. No-fault/liability: Auto, homeowner’s, or liability carrier primary; Medicare secondary. Workers’ Comp: WC carrier primary; Medicare secondary.

When a provider bills Medicare first in any of these scenarios, Medicare’s system flags the other coverage and applies OA-23 to signal that the primary impact should already have been applied. MSP misclassification commonly produces both CO-22 denial code Medicare patterns and OA-23 together on the same remittance.

The Automatic Crossover Process , COBA and BCRC

CMS coordinates Medicare benefits through the Benefits Coordination and Recovery Center (BCRC). The Coordination of Benefits Agreement (COBA) program establishes a national contract between the BCRC and other health insurance organizations for transmitting enrollee eligibility and Medicare-paid claims data.

When Medicare processes as primary and the patient has Medigap or supplemental coverage, the BCRC automatically crosses over the claim to the secondary. COBA-participating supplementals receive the Medicare 835 plus crossover claim, then adjudicate.

When the COBA crossover fails (data mismatch, member not on file), the secondary may apply OA-23 incorrectly because it lacks the full Medicare adjudication picture. Resolution: contact BCRC at 1-855-798-2627 to verify the COBA record.

For more detail on the full coordination process, see CMS Coordination of Benefits guidance.

The March 9, 2026 MAC Guidance Update

Medicare Administrative Contractor guidance updated March 9, 2026 reiterates the MSP submission protocol: providers submit to Medicare for secondary consideration only after the primary processes. For hardcopy MSP claims, the primary payer’s RA or EOB must accompany the submission.

The March 2026 update reinforces existing MSP rules. No policy changes. Just operational reminders. For electronic MSP claims, the 837 must include CAS data from the primary’s 835 in the appropriate loops (2320 and 2330). Practices that batch MSP claims should verify each claim has primary CAS data populated before submission to avoid OA-23 cycles.

When Medicare Is Primary and OA-23 Still Appears

Edge case: Medicare is primary, and the secondary commercial plan adjudicates with OA-23. This means the secondary’s allowable was lower than what Medicare already paid plus adjusted. The secondary covers nothing because the prior adjudication impact, Medicare’s payment, exhausted secondary liability. Patient typically owes nothing on the OA-23 line, though Medicare’s PR amounts may still apply separately.

Payer-Specific OA-23 Patterns: How Each Major Payer Handles CARC 23

OA-23 appears across every major payer, but the operational pattern varies by plan type, COB database quality, and EDI normalization consistency. Here’s how each major payer typically applies CARC 23 and what resolution looks like in practice.

Medicare OA-23: MSP, Crossover, and Sequestration Stack

Medicare as secondary generates the oa 23 medicare denial code most often through MSP misclassification or COBA crossover failures. The oa 23 denial code medicare pattern typically signals either a billing sequence error (Medicare billed first when another payer should have been primary) or a crossover data mismatch at the BCRC level.

Resolution first step: confirm MSP status. Second step: verify the COBA crossover record if this is a Medicare-primary supplemental scenario. Third step: check whether the prior payer’s CAS data is fully populated in the 837 COB loops.

Medicaid OA-23: The Payer-of-Last-Resort Rule

Medicaid operates as the payer of last resort under federal law. When Medicaid receives a claim with OA-23, it means the program identified prior payer impact (typically from Medicare or commercial coverage) and Medicaid’s calculation determines no additional payment is due.

The oa 23 denial code medicaid signal requires confirming all non-Medicaid coverage was billed first and the EOBs are attached.

State Medicaid programs vary slightly in how they format CARC 23, but the underlying rule is uniform. Some state programs produce OA-23 even when Medicaid would owe a small balance. These require state-specific provider portal escalation.

BCBS OA-23: BlueCard and Multi-Plan Coordination

BCBS plans use the BlueCard program for inter-plan coordination. For patients with BCBS in multiple states, the home plan typically processes first and the host plan processes second. OA-23 surfaces when one BCBS plan adjudicates with the other BCBS plan’s impact already applied.

BCBS COB databases are notoriously slow to update. Verify the patient’s current home plan before billing. Contact BCBS provider relations for plan-specific COB sequencing.

The oa 23 denial code bcbs scenario usually traces to a BlueCard routing issue rather than a true coverage dispute. The bcbs denial code oa-23 result: the host plan saw the home plan’s adjudication and applied OA-23 to the difference.

UHC, Aetna, Cigna, Humana OA-23: Commercial Payer Patterns

Major commercial payers cross-reference COB databases against employer enrollment data. Phone calls rarely update the file permanently , use provider portals for COB updates.

UnitedHealthcare often produces OA-23 alongside the prior payer’s RA reference. Aetna pairs OA-23 frequently with N23 RARC for COB-context clarification. The aetna denial code oa 23 pattern almost always includes N23.

The oa 23 denial code aetna resolution: verify COB through the Aetna provider portal and resubmit with complete primary adjudication data. Cigna applies OA-23 cleanly when COB data is current and produces CO-22 when COB data is stale. Humana requires explicit primary EOB documentation for MSP-related OA-23.

CY 2026 Medicare Appeal Thresholds (Federal Register Update)

For Calendar Year 2026 Medicare appeals filed on or after January 1, 2026, the Administrative Law Judge (ALJ) hearing threshold is $200 per the Federal Register CY 2026 AIC Adjustment, up from $190 in CY 2025. The Federal District Court threshold is $1,960, up from $1,900.

Claims may be aggregated to meet the threshold at each appeal level. For OA-23 appeals where the disputed amount falls below $200, redetermination through the Medicare Administrative Contractor (Level 1) and reconsideration through the Qualified Independent Contractor (Level 2) are the available paths before reaching the ALJ threshold. Aggregate small-dollar OA-23 disputes within the same payer to clear the threshold.

See CMS Medicare Claims Processing Manual Chapter 29 for the full appeals framework. Practices with high payer-mix complexity benefit from a periodic medical billing audit that surfaces OA-23 patterns by payer and identifies systemic COB gaps.

Companion CARCs and RARCs That Appear Alongside OA-23

OA-23 rarely travels alone. Understanding the companion codes that appear alongside it tells you the full operational story of the secondary claim , and points you toward the correct resolution path faster than reading OA-23 in isolation.

N23: The Most Common RARC Paired with OA-23

RARC N23, “Patient liability may be affected due to coordination of benefits with other carriers,” is the most frequently observed companion remark code for OA-23 on commercial payer remittances. The n23 denial code description signals COB context from the secondary payer.

N23 doesn’t change the OA-23 outcome. It provides COB context the secondary payer is signaling. When you see OA-23 plus N23 together, the secondary is confirming COB-driven adjudication occurred. Resolution path is the same as standalone OA-23. No separate workflow for the n23 denial code layer.

CARC 22: Adjacent COB Code

CARC 22: “This care may be covered by another payer per coordination of benefits.” CARC 22 means the payer suspects another plan should be primary. CARC 23 means another plan was already primary and its impact is being applied.

The two codes appear in different stages of the COB workflow: CARC 22 at the front-end suspicion stage, CARC 23 at the post-primary adjudication stage. Our CO-22 denial code guide walks through the full COB workflow for CARC 22 , including the resolution paths and the front-end controls that prevent it.

OA-18: Duplicate Claims/Services

OA-18: “Exact duplicate claim/service.” The oa 18 denial code appears when the secondary payer flags a duplicate submission. OA-18 plus OA-23 on the same claim run usually means the resubmission was treated as duplicate while the original is still in adjudication queue. Resolution: confirm only one claim is open at the secondary. Void duplicates before resubmitting.

OA-45: Charges Exceed Allowable

The oa 45 denial code: “Charge exceeds fee schedule/maximum allowable or contracted/legislated fee arrangement.” OA-45 sometimes appears alongside OA-23 when the secondary payer’s allowable cap is being applied in addition to the COB impact. Post both adjustments. Neither transfers to patient.

The oa 96 denial code follows the same OA-prefix logic but for non-covered charges , a different reason code under the same group code framework.

A3: Acknowledgment/Returned Claim

A3 indicates the claim was returned without entering adjudication. A3 plus OA-23 appearing on follow-up often means the resubmission still lacks complete COB data. Resolution: complete the COB loops before resubmitting.

MOA Segment Codes (Claim-Level Remarks)

The MOA segment carries claim-level remark codes on the 835 (versus the LQ segment, which carries service-line remarks). Common claim-level codes: MA01 (appeal rights) and MA04 (“Secondary payment cannot be considered without the identity of or payment information from the primary payer”).

For OA-23 specifically, the MOA segment may carry MA04 when the OA-23 was triggered by missing primary EOB data. Read the full MOA stack alongside OA-23 , the resolution path depends on which RARCs accompany the CARC. When OA-23 appears with MA04, the resolution mirrors the CO-16 denial code workflow for missing-information denials.

How to Prevent OA-23 Denials: The Front-End Control System + 2026 Compliance Calendar

OA-23 prevention is a front-end discipline. Most OA-23 volume traces back to intake-level decisions made before the first claim is ever submitted. The prevention system has three components: COB verification at intake, real-time eligibility on date of service, and claim scrubbing rules for secondary submissions.

The 6-Point COB Verification Protocol at Patient Intake

Run this verification at every patient encounter, not just new patients:

1. Confirm primary insurance: name, member ID, group number, payer ID
2. Confirm secondary insurance presence , explicit yes/no question
3. Capture secondary insurance details if present
4. Verify the COB order with the patient (which plan they consider primary)
5. Run real-time eligibility (EDI 270/271) on both plans
6. Flag any work-injury, auto-accident, or liability situation that changes COB sequencing

Real-Time Eligibility Checks on Date of Service

Eligibility records change daily. Registration data is stale within days. Run EDI 270/271 checks on the date of service, not just at registration. Specifically check the COB segment of the eligibility response , most eligibility tools surface this. Practices with systematic insurance eligibility verification protocols at the date-of-service level catch OA-23 triggers before claims go out.

Claim Scrubbing Rules for Secondary Submissions

Configure your clearinghouse or PMS to block secondary claim submissions when primary EOB fields are empty. This single rule eliminates the entire MA04 plus OA-23 denial scenario before the claim leaves your system. Add a scrub rule for X12 837 Loop 2320 plus Loop 2330A completeness on every secondary submission.

The 2026 Compliance Calendar: CMS-0057-F and What’s Coming

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) requires impacted payers , Medicare Advantage, Medicaid, CHIP, and federally facilitated marketplace QHPs , to implement operational PA transparency provisions by January 1, 2026 and the FHIR Prior Authorization API by January 1, 2027.

The 2026 PA transparency provisions improve COB data flow between payers, which should reduce OA-23 incidence over time. The 2027 FHIR API will standardize prior authorization data exchange, including COB-related authorization context. Through 2026, COB data inconsistency remains a primary OA-23 driver.

Post-2027, the FHIR API standardization should reduce , but not eliminate , OA-23 volume. See the CMS Interoperability and Prior Authorization Final Rule for the full implementation timeline.

OA-23 prevention is one piece of the broader 2026-2027 compliance calendar. The ICD-11 transition roadmap covers another major piece practices need on their radar.

Related Codes and the “23” Disambiguation

Not every search for “23” is about OA-23. Multiple medical billing code systems use the number 23 for unrelated purposes. Here’s the quick disambiguation.

Related CARC Cluster

For the full CO-22 coordination of benefits guide that mirrors this OA-23 framework, see our CO-22 coordination of benefits guide. The CO-96 group code framework covers the parallel CO/PR/PI/OA breakdown for reason code 96.

POS 23 vs POS 22 vs POS 24: Place of Service Disambiguation

POS 23 = Emergency Room, Hospital. POS 22 = On Campus-Outpatient Hospital. POS 24 = Ambulatory Surgical Center. These are Place of Service codes used on the CMS-1500 claim form , completely unrelated to CARC 23. POS codes appear on Box 24B of the CMS-1500. CARC 23 appears on the 835 ERA after claim processing.

Our POS 22 in medical billing guide covers the on-campus outpatient hospital place of service in detail. Different codes, different transactions, different purposes.

Modifier 23: A Different Code Entirely

CPT Modifier 23 = “Unusual Anesthesia.” Appended to anesthesia procedure codes, not a denial code. Some search engines bundle Modifier 23 with CARC 23 due to numerical similarity. They have nothing operationally in common.

ICD-10 Z23: Not a Denial Code

Z23 = “Encounter for immunization” in ICD-10-CM. A diagnosis code, not a denial code. Shows up in search results due to “23” pattern matching but is entirely unrelated to OA-23.

Frequently Asked Questions: OA-23 Denial Code

What does the OA-23 denial code mean?

The OA-23 denial code is the combination of Group Code OA (Other Adjustment) and Claim Adjustment Reason Code 23, which X12 defines as “the impact of prior payer(s) adjudication including payments and/or adjustments.” It appears on the 835 ERA when a secondary payer adjusts reimbursement based on what the primary payer already paid. OA-23 is generally not patient billable.

Is OA-23 a write-off?

Functionally yes. OA-23 amounts result in provider write-offs because the dollars can’t be billed to the patient and don’t transfer to a contractual write-off category. The OA group code signals a coordination offset between payers. The provider absorbs the OA-23 amount as part of normal COB operations, except where separate PR amounts appear on the same claim line.

What is the difference between OA-23 and CO-23?

Both share Reason Code 23 (“impact of prior payer adjudication”) but differ by Group Code. OA-23 means the adjustment is a coordination offset between payers. CO-23 means the same impact is being applied as a contractual obligation per the payer-provider contract. Neither is patient billable, but the financial classification and appeal paths differ.

What does OA mean on an EOB?

OA stands for Other Adjustment, one of five Claim Adjustment Group Codes defined by X12 (alongside CO, PR, PI, and CR). OA is the residual category. It’s used when the adjustment doesn’t fit Contractual Obligation, Patient Responsibility, Payer Initiated Reduction, or Correction/Reversal categories.

Can a patient be billed for OA-23?

No. OA-23 is not patient billable under standard X12 group code rules. The OA group code signals an adjustment that doesn’t transfer to patient liability. Billing the patient for OA-23 amounts creates compliance exposure. Only PR group code amounts on the same claim line can be billed to the patient.

What is the OA 23 remark code?

OA-23 is a Claim Adjustment Reason Code (CARC), not a remark code. Remark codes (RARCs) appear in the LQ segment for service lines or MIA/MOA segments for claims, while CARCs appear in the CAS segment. The most common RARC paired with OA-23 is N23 (“Patient liability may be affected due to coordination of benefits with other carriers”).

What is the reason for OA-23?

OA-23 surfaces when a secondary or tertiary payer’s allowable amount is at or below what the primary payer already paid plus adjusted. The most common operational triggers are missing primary EOB on secondary submission, COB sequencing errors, MSP misclassification on Medicare claims, and 835 auto-posting failures from inconsistent same-dollar adjustments at claim and line levels.

How do I fix an OA-23 denial?

Pull the primary payer’s full ERA, verify the COB sequence is correct, match the primary EOB against the original claim line by line, validate the 835 CAS segment posted correctly, and resubmit the secondary claim with complete X12 837 Loop 2320 and Loop 2330A data. Track timely filing windows on both primary and secondary throughout.

Does OA-23 mean the claim was denied?

Technically no. OA-23 is a claim adjustment reason code, not a denial code. The claim was processed and the payer adjusted reimbursement based on prior payer impact. The dollar amount adjusted may be functionally similar to a denial, but the operational workflow is COB resolution, not appeals.

Can OA-23 be appealed?

Yes, when the payer’s coordination calculation is factually incorrect. Appeal when the secondary applied OA-23 but the primary EOB shows the secondary should have paid additional dollars. Most OA-23 denials resolve through corrected resubmission rather than formal appeal. Appeal only when the payer’s COB data or calculation is wrong.