OA-23 denial code: what it means and how to handle dual coverage correctly.
OA-23 isn't CO-23, and it isn't a denial at all. It's an Other Adjustment: the secondary payer's math after the primary plan already paid. Most practices misread it as a rejection. It's actually confirmation that coordination of benefits is working the way it's supposed to.
See how Needletail identifies dual coverage and confirms the correct primary/secondary billing order before every appointment.
RARC codes decoded
group codes explained (CO, PR, OA)
ranked dental scenarios
TL;DR
OA-23 uses the OA (Other Adjustment) group code, not CO. It's one of only two non-CO codes in this series.
OA-23 reflects the impact of a prior payer's adjudication: the secondary payer adjusting its payment based on what the primary plan already paid.
It's informational, not a denial. Practices frequently misread it as a rejection when it's actually coordination of benefits working correctly.
The Birthday Rule determines which parent's plan is primary for a dependent child covered under both parents: whoever's birthday falls earlier in the calendar year.
Group codes matter: CO means the provider absorbs the cost, PR means the patient is billed, and OA covers administrative or informational adjustments like COB.
The fix for OA-23 isn't an appeal. It's confirming the correct primary/secondary order and submitting the secondary claim with the primary's EOB attached.
What is the OA-23 denial code, and why isn't it a CO code?
The official definition: "The impact of prior payer(s) adjudication including payments and/or adjustments." OA-23 shows up on the secondary payer's remittance, reflecting how much the primary payer already paid and adjusting the secondary's payment accordingly.
The group code prefix matters more here than in almost any other code in this series. CO means Contractual Obligation (the provider absorbs the cost). PR means Patient Responsibility (the patient is billed). OA means Other Adjustment, a catch-all for administrative and informational adjustments that don't fit the provider-write-off or patient-bill categories. OA-23 is squarely in that third bucket.
In dental billing, OA-23 is the coordination of benefits (COB) mechanism in action. When a patient has dual coverage, two dental plans, often through their own employer and a spouse's, one plan pays first as primary and the other pays second as secondary. OA-23 is how the secondary plan's ERA documents that it adjusted its payment to account for what the primary already covered.
This is why OA-23 gets misread constantly: it looks like an adjustment code sitting next to a reduced or zero payment, which reads like a denial to anyone scanning the ERA quickly. It isn't. The claim was processed correctly; the secondary simply isn't paying twice for something the primary already covered.
Don't confuse OA-23 with CO-22
CO-22 is the CO-group signal that coordination of benefits information is needed before the claim can be processed at all (the claim stalls until COB data is supplied). OA-23 is the result after COB has already been applied and the secondary payer calculated its adjusted share. One blocks adjudication; the other is the outcome of it.
How to Fix OA-23:
proper COB claim submission.
There's no appeal here in the traditional sense. The work is making sure the coordination of benefits workflow itself was done correctly, start to finish.
Correct
COB Applied Correctly
N219, N430
Incorrect
Wrong Order or Missing EOB
N219, N430
No Action
Informational Only
N219, N430
- 1
Pull the ERA or EOB. Confirm it's the secondary payer's response.
OA-23 appears on the secondary plan's remittance, not the primary's. Confirm which payer this ERA is actually from before doing anything else.
- 2
Verify the primary/secondary order was correct.
Check which plan should have been billed first. For dependent children covered under both parents, the Birthday Rule usually determines primary status: whichever parent's birthday falls earlier in the calendar year holds the primary plan.
- 3
Confirm the primary's EOB was attached to the secondary claim.
Secondary claims need the primary payer's EOB or ERA attached to process correctly. A secondary claim submitted without it is likely to deny or process incorrectly, not because of OA-23 logic, but because the secondary payer has nothing to coordinate against.
- 4
If the order was wrong, resubmit to the correct primary first.
If billing identified the wrong plan as primary, that claim needs to be corrected and resubmitted in the right order: true primary first, true secondary second with the primary's EOB attached.
- 5
Bill the patient only for a genuine remaining balance.
After both payers have adjudicated correctly, any amount still outstanding is the patient's responsibility, same as it would be with a single payer. OA-23 itself isn't a balance to bill; it's the secondary's internal adjustment math.
| Scenario | Codes You'll See | The Fix |
|---|---|---|
| COB applied correctly (non-duplication) | N219, N430 | No action. Collect only any genuine remaining patient balance, if applicable. |
| Wrong primary/secondary order | N219, N430 | Confirm the correct order (often via the Birthday Rule) and resubmit to the correct primary first. |
| Secondary claim missing primary's EOB | N219, N430 | Resubmit the secondary claim with the primary payer's EOB/ERA attached. |
Get the primary/secondary order right the first time.
Needletail identifies dual coverage at check-in, confirms which plan is primary using the Birthday Rule and each plan's own COB provisions, and ensures the practice bills both payers correctly to maximize collections.
OA-23 RARC decoder:
what each remark code means.
OA-23 often travels with a short remark code, or sometimes no specific RARC at all, since the ERA narrative frequently explains the COB math directly.
Coordination of Benefits
| RARC | What the Payer Is Saying | Dental Context | The Fix |
|---|---|---|---|
| N219 | Payment based on coordination of benefits | Confirms the secondary payer's payment was calculated using the primary payer's EOB data | Verify the primary's EOB was correctly attached and the primary/secondary order matches the patient's actual coverage. |
| N430 | Coordination of benefits adjustment | The specific adjustment line reflecting what the secondary deducted based on the primary's payment | Check the math: secondary's allowed amount minus the primary's payment should equal what the secondary actually paid. |
Many OA-23 lines carry no specific RARC at all; the ERA/EOB narrative explains the COB math in plain language instead. If your RARC isn't in this table, pull the full code from your ERA/835 file and look it up in the official RARC code list.
Stop treating OA-23 like a problem to solve.
Needletail flags dual coverage and confirms the correct billing order before the claim is ever filed, so OA-23 shows up on the ERA exactly as expected, not as something your team has to untangle after the fact.
Common causes of OA-23
in dental practices.
OA-23 shows up whenever a patient has dual dental coverage. Ranked by how often each scenario drives it.
Dependent child covered under both parents' plans
N219, N430Birthday Rule determines primary; secondary pays the remainder up to its allowable, generating OA-23
Primary pays 100%, secondary adjusts to $0
N219, N430Non-duplication of benefits: the secondary correctly pays nothing additional since the primary already covered the full allowed amount
Secondary claim submitted without primary's EOB
N219Missing documentation causes the secondary to process incorrectly or deny outright
- When a child is covered under both parents' separate dental plans, the Birthday Rule determines which plan pays first: whichever parent's birthday (month and day, not year) falls earlier in the calendar year holds the primary plan for that child.
- A father born in March and a mother born in September means the father's plan is primary for their shared dependent, regardless of which parent is older or which plan has better benefits.
- This rule is specific to dependent children with coverage under both parents. It doesn't apply to a patient's own coverage versus a spouse's coverage on themselves, which follows a different rule: a person's own plan is typically primary for their own care.
- When the primary payer covers 100 percent of the allowed amount, the secondary payer correctly adjusts its own payment down to $0. This is OA-23 doing exactly what it's designed to do: preventing the combined payment from exceeding the actual charge.
- Billing teams sometimes treat a $0 secondary payment as a problem to chase. It isn't. Collecting nothing further from the secondary in this scenario is the correct outcome, not a missed payment.
| Trigger | What's Wrong | RARC You'll See |
|---|---|---|
| Dependent child covered under both parents' plans | Birthday Rule determines primary; secondary pays the remainder up to its allowable, generating OA-23 | N219, N430 |
| Primary pays 100%, secondary adjusts to $0 | Non-duplication of benefits: the secondary correctly pays nothing additional since the primary already covered the full allowed amount | N219, N430 |
| Secondary claim submitted without primary's EOB | Missing documentation causes the secondary to process incorrectly or deny outright | N219 |
OA-23 vs.
CO-22, CO-45, and the group code system.
Understanding OA-23 means understanding how CO, PR, and OA group codes divide responsibility differently. Here's the full picture.
| Code | Trigger | Who Owes | Type |
|---|---|---|---|
| OA-23 | Secondary payer's adjustment based on primary's payment | Informational, no new balance | Info |
| CO-22 | Coordination of benefits information needed before claim can process | Practice absorbs/stalls | Info |
| CO-45 | Charge exceeds fee schedule/contracted rate | Practice absorbs | Adjustment |
| CO-97 | Service bundled into another already-adjudicated procedure | Practice absorbs | Bundling |
The three group codes work differently: CO (Contractual Obligation) means the provider's contract makes them absorb the adjustment. PR (Patient Responsibility) means the patient can be billed. OA (Other Adjustment) covers everything else, mostly administrative or informational adjustments like coordination of benefits, where there isn't a straightforward provider-write-off or patient-bill answer.
CO-22 and OA-23 are easy to conflate because both relate to coordination of benefits. CO-22 appears when COB information is needed before the claim can even be adjudicated; it's a blocker. OA-23 appears after adjudication, reflecting the math once COB has already been applied.
CO-45 and CO-97 are unrelated mechanisms (fee schedule and bundling), included here only because they're common neighbors on a multi-insurance dental claim. Don't apply COB logic to either; they have their own fix paths.
One verification pass. Every group code handled correctly.
Whether the claim needs CO-level fee schedule confirmation, PR-level patient responsibility, or OA-level coordination of benefits, it all starts with knowing the patient's full coverage picture. Needletail's pre-appointment dental verification confirms it in one pass.
How to get COB right
before the claim goes out.
OA-23 isn't something to prevent; it's something to get right the first time, so claims don't bounce between payers over avoidable sequencing errors.
Identify dual coverage at check-in.
Confirm whether the patient has dual coverage at every visit, not just intake.
Determine the correct primary/secondary order.
Apply the Birthday Rule or relevant COB provision to confirm correct order.
File primary first, secondary second with the EOB attached.
Attach the primary's EOB to every secondary submission.
Set patient expectations about non-duplication.
Explain non-duplication of benefits to patients with dual coverage up front.
Why this matters at scale
Dual coverage is common enough in dental practices that getting the primary/secondary order wrong, or skipping the EOB attachment, creates a steady stream of avoidable rework. Verifying dual coverage and primary/secondary order at check-in, rather than discovering it on a bounced secondary claim, keeps COB claims moving through on the first submission.
Make this checklist automatic.
Needletail runs the 48-hour prevention checklist for every scheduled patient: automated eligibility pulls, subscriber matching, and NPI checks, without a biller touching a portal.
Real dental practice
scenarios.
These three come straight from dental billing teams. Two show OA-23 working correctly. One shows a submission error worth fixing.
Dependent child, Birthday Rule determines primary
A child is covered under both parents' dental plans. The father's birthday is in March, the mother's in September. D2750 (crown) is billed, and the father's plan is primary.
What comes back
Primary pays 80% of $950 ($760). Secondary processes with OA-23, paying up to its own allowable minus the primary's payment.
The fix
No fix needed if the Birthday Rule was applied correctly. Bill both payers in the right order and collect any remaining balance from the patient.
How to prevent it
Confirm both parents' birthdates at intake whenever a dependent has coverage under both plans, so the correct primary is identified before the first claim is filed.
Primary covers 100%, secondary shows OA-23 at $0
A patient with employer plus spouse dental coverage gets D0274 (bitewing X-rays). The primary plan covers it at 100%.
What comes back
Secondary processes the claim with the primary's EOB attached and applies OA-23 for $0 (non-duplication of benefits).
The fix
Nothing to fix. This is the correct and expected outcome; the secondary isn't supposed to pay when the primary already covered the full amount.
How to prevent it
Set the expectation with the patient in advance, so a $0 secondary payment on the EOB doesn't get mistaken for a processing error.
Secondary claim submitted without the primary's EOB
A practice submits a claim to the secondary payer without attaching the primary payer's EOB or ERA.
What comes back
The secondary payer denies or processes the claim incorrectly, since it has nothing to coordinate its payment against.
The fix
Resubmit the secondary claim with the primary's EOB attached, so the secondary payer can correctly apply its coordination of benefits math.
How to prevent it
Build a hard checkpoint into the billing workflow: no secondary dental claim goes out without the primary's EOB attached, every time.
What these three have in common
Two are coordination of benefits working exactly as designed. One is a documentation gap that's easy to catch before it causes a bounce.
- The Birthday Rule and the non-duplication outcome were both correct the moment the primary/secondary order was properly established.
- The missing EOB wasn't a coverage problem at all; it was a step in the submission workflow that got skipped.
- Needletail's dental verification identifies dual coverage at check-in, confirms the correct primary/secondary order, and ensures both payers get billed correctly to maximize collections.
- Getting the sequencing right the first time is what keeps dual-coverage claims from bouncing between payers.
Know the coverage picture before the claim, not after a bounce.
Needletail verifies dental eligibility and benefits before every appointment, including dual coverage and primary/secondary determination. AI voice agents and portal automation confirm the full coverage picture, and human specialists review every verification before the full breakdown goes into your PMS.
Your call is with Jofin Joseph,
Co-Founder and CEO.
Questions about this code