Last Updated on October 21, 2026
Denial Code OA 23 identifies the impact of prior payer adjudication, including payments and adjustments, on a claim. It commonly appears when a secondary payer processes a claim after the primary insurer has already determined its payment responsibility.
In medical billing, OA 23 is frequently associated with coordination of benefits (COB), particularly when patients have multiple insurance plans. However, OA 23 is not automatically a denial. It may represent an expected adjustment rather than a claim processing error.
What makes OA 23 challenging is determining whether the adjustment is correct. Gaps in policy details, patient coverage updates, or primary payment data can complicate secondary claim processing. Billing teams that understand these discrepancies can avoid unnecessary resubmissions, resolve outstanding claims, and maintain more accurate reimbursement records.
Table of contents
- What Is Denial Code OA 23?
- When Does OA 23 Require Follow-Up?
- Common Causes of OA 23-Related Claim Discrepancies
- How to Identify OA 23 Adjustments in Your System
- How to Fix OA 23 Claim Discrepancies
- Preventive Measures to Reduce COB-Related Claim Issues
- Financial and Operational Impact of OA 23-Related Delays
- Improve Secondary Claim Accuracy With AnnexMed
- FAQs
What Is Denial Code OA 23?
OA 23 is used when a payer reports an adjustment reflecting the impact of previous payer adjudication. It commonly appears in coordination-of-benefits situations where primary and secondary insurers process the same claim.
The code has two components:
- Group Code OA (Other Adjustment): Identifies an adjustment that is not classified as contractual obligation or patient responsibility.
- Reason Code 23: Identifies the impact of prior payer adjudication, including payments and adjustments.
When OA 23 appears, the secondary payer may be accounting for amounts already processed by the primary insurer. This does not necessarily mean the primary Explanation of Benefits (EOB) is missing or that the claim must be resubmitted.
Billing teams should review the primary EOB or Electronic Remittance Advice (ERA), secondary payer adjustments, and remaining claim balance before determining whether corrective action is required.
When Does OA 23 Require Follow-Up?
Key consideration: OA 23 alone does not establish that a claim was incorrectly processed.
Common Causes of OA 23-Related Claim Discrepancies
Coordination-of-benefits discrepancies can complicate secondary claim processing. Although these issues may occur alongside OA 23, they do not necessarily cause the adjustment code itself.
1. Incorrect Insurance Sequence
- Primary and secondary plans listed in the wrong order
- Medicare and commercial coverage sequenced incorrectly
- COB updates not captured during registration
Incorrect sequencing may cause claims to be submitted to the wrong payer first, delaying secondary processing.
2. Missing Primary EOB (Explanation of Benefits)
- Primary adjudication information not included when required
- EOB details containing incomplete line items or mismatched amounts
- Delays while primary payer processing information remains unavailable
Secondary payers need applicable primary payment and adjustment details to determine their own payment responsibility.
3. Outdated Policy Information
- Previous employer coverage remaining active in the system
- New plan effective dates not updated
- Terminated policies still recorded as active
Outdated insurance information can create inconsistencies between patient records and payer coverage systems.
4. Coverage Changes Not Communicated
- Patients switching insurance plans mid-year
- COB questionnaires not completed
- Spouse or dependent coverage changes not documented
Regular eligibility and benefit verification helps identify changes that may affect payer sequencing and secondary claim submission. When coverage changes are not updated during registration, they can affect payer sequencing and secondary claim processing. Regular eligibility and benefit verification helps identify these discrepancies before claims reach the payer.
5. Data Mismatches in Claim Details
- Incorrect subscriber identification number
- Wrong insurance group number
- Patient demographics that do not match payer records
Even minor discrepancies can complicate claim matching and payment reconciliation.
6. Dual-Coverage Patients Without Updated COB Records
Patients with multiple active insurance plans require accurate coordination records. Workers’ compensation, automobile liability, and employer coverage transitions may involve additional payer-order requirements.
When coverage changes are not recorded, billing teams may face repeated secondary claim delays.
How to Identify OA 23 Adjustments in Your System
Identifying OA 23 requires reviewing the remittance and determining whether the adjustment represents expected payer processing or an unresolved claim discrepancy.
1. Start With Your ERA or EOB
Look for:
- Group Code: OA
- Reason Code: 23
- Associated payment and adjustment amounts
- Additional remark or adjustment codes
These details help determine how prior payer adjudication affected the claim.
2. Check Your Denial Work Queue
OA 23-related claims may appear under:
- Coordination of Benefits
- Secondary Claim Review
- Other Adjustment
- Unresolved Secondary Balances
A sudden increase in unresolved secondary claims may indicate outdated COB records or processing discrepancies.
3. Review Payer Remark Codes
Review accompanying remittance advice remark codes and payer explanations.
Messages concerning missing primary payment information, incomplete COB details, or documentation requirements should be evaluated separately from the OA 23 adjustment itself.
4. Validate Insurance Sequence in the Patient Profile
Confirm:
- Is the correct plan marked as primary?
- Are the policy effective dates accurate?
- Has the patient recently updated insurance coverage?
Correct payer sequencing is essential for accurate secondary claim processing.
5. Look for Recurring Patterns
Billing teams may identify:
- Specific employer plans associated with repeated COB discrepancies
- Medicare secondary claims accumulating in AR aging
- Dual-coverage patients requiring frequent insurance updates
Monitoring these patterns helps identify workflow gaps requiring corrective action.
How to Fix OA 23 Claim Discrepancies
Not every OA 23 adjustment requires correction. The first step is confirming whether the secondary payer accurately accounted for prior payer adjudication.
Step 1: Confirm the Correct Insurance Order
Review the patient’s primary, secondary, and applicable tertiary coverage. Verify payer sequencing and policy effective dates.
If the insurance order is incorrect, update the patient record and determine whether the claim requires further action.
Step 2: Retrieve the Primary Payer EOB
Obtain the primary payer’s EOB or ERA and review:
- Payment amounts
- Adjustments
- Patient responsibility
- Claim and service-line details
The primary adjudication information should match the details used for secondary claim processing.
Step 3: Compare Claim and Payment Details
Compare the primary remittance with the secondary claim.
Validate billed units, payment amounts, adjustments, and patient demographics. Investigate discrepancies before deciding whether a correction is necessary.
Step 4: Update Coordination of Benefits Information
Correct outdated policyholder details, coverage dates, or plan hierarchy when required.
This is particularly important for patients with dual coverage or recent insurance changes.
Step 5: Determine Whether Resubmission Is Necessary
If OA 23 reflects a valid adjustment, reconcile the remaining balance without unnecessary resubmission.
If an actual discrepancy is identified, follow the secondary payer’s requirements for corrected claims, updated COB information, reconsideration, or appeal.
Provide primary adjudication documentation when required by the payer.
Step 6: Monitor the Claim Until Resolution
Track unresolved claims through secondary aging reports and payer follow-up queues.
Confirm applicable timely filing limits and document corrections, adjustment decisions, and payment outcomes.
Structured accounts receivable management supports follow-up on unresolved secondary balances and helps prevent avoidable claim aging.
Resolve Secondary Claims Delayed by COB Discrepancies
AnnexMed helps billing teams validate payer sequencing, reconcile primary payment details, and follow up on unresolved secondary claims.
Request a Secondary Claims ReviewPreventive Measures to Reduce COB-Related Claim Issues
A strong prevention plan improves consistency across insurance verification, documentation, and secondary claim review.
Strengthen Staff Competency
Regular training helps registration and billing teams stay current on payer updates, COB requirements, and secondary claim submission procedures.
Periodic refresher sessions can reduce errors caused by outdated insurance information or inconsistent verification practices.
Adopt Automated Verification Tools
Claim scrubbing and eligibility verification tools can help identify missing COB details, outdated policy information, and claim inconsistencies before submission.
Automated checks reduce manual review requirements, although payer-specific validation remains necessary.
Run Internal Quality Audits
Routine audits help identify recurring discrepancies in secondary claims.
Review sampled claims each month to evaluate documentation completeness, payer sequencing accuracy, and compliance with submission requirements.
Integrating these preventive controls into broader revenue cycle management services connects front-end verification with claim submission, payment reconciliation, and follow-up.
Financial and Operational Impact of OA 23-Related Delays
OA 23 itself may be a routine adjustment. However, unresolved COB discrepancies can delay secondary payments, increase staff workload, and affect revenue cycle performance.
Snapshot of the Impact
When these issues accumulate, they create uneven payment patterns and additional administrative pressure.
Consistent monitoring helps distinguish expected OA 23 adjustments from unresolved secondary claim problems.
Billing teams should track secondary claim aging, recurring COB discrepancies, correction rates, and outstanding balances by payer.
Improve Secondary Claim Accuracy With AnnexMed
OA 23 does not automatically indicate a denied claim. Accurate interpretation requires reviewing prior payer adjudication, validating COB information, and confirming whether the secondary payer’s adjustment is appropriate.
AnnexMed supports providers with eligibility verification, secondary claim follow-up, payment reconciliation, and denial management services. By connecting these processes, healthcare organizations can reduce unnecessary rework and address unresolved reimbursement issues more efficiently.
When secondary claim discrepancies remain unresolved, structured denial management services can support payer investigation, appropriate appeals, and root cause analysis.
Strengthen Your Secondary Claims Workflow
Identify recurring COB discrepancies, improve secondary payer follow-up, and reduce avoidable reimbursement delays with AnnexMed’s revenue cycle support.
Discuss Your COB Billing ChallengesFAQs
OA 23 may appear because the primary payer has already adjudicated the claim. It reflects the impact of prior payments and adjustments on subsequent payer processing. Its presence does not automatically indicate an error.
OA 23 itself does not determine timely filing. However, delays in obtaining primary adjudication information or correcting COB discrepancies may cause secondary claims to approach payer filing deadlines.
Review the primary payer’s EOB or ERA, secondary remittance, updated COB information, and relevant claim details. Additional documentation depends on the payer’s requirements.
Patients with two active insurance plans may experience coverage changes, employer updates, or outdated coordination records. These discrepancies can complicate secondary processing, although OA 23 may still represent a valid adjustment.
Yes. Eligibility verification tools, automated COB checks, and claim scrubbers can flag missing or inconsistent insurance information before submission, helping reduce preventable secondary claim rework.



