Impact of Prior-Payer Adjudication (OA-23 / narrow Medicare CO-23) & the "Recoupment Denial"
CARC 23 reports the impact of the prior payer's adjudication — payments and adjustments — and X12 defines it for use only with group code OA. On its own it is informational, not a denial, and not a reason to rebill. Some teams call it the "recoupment denial," but a true provider-level takeback appears separately in the 835 provider-level balance (PLB) section. Medicare also has a narrow conditional-payment implementation that uses CO-23 with M32 and N4.
Guided troubleshooter available for this denial
Answer a few questions to reach the correct disposition. No patient or claim identifiers requested.
In plain language
CARC 23 tells you what the prior payer's adjudication already did to this claim — what it paid and what it adjusted — so the current payer's math is understandable and those dollars are not posted a second time.
Start here
Read the group code first — OA is standard prior-payer impact; CO-23 requires a verified Medicare conditional-payment context.
Who resolves it
Billing/Follow-Up (with Payment Posting / ERA reconciliation)
Who prevents it
Payment Posting & Billing — complete primary 835 posting and COB balancing edits before any secondary claim is released.
How to resolve this denial, step by step
- 1
Read the group code first
OA is standard prior-payer impact; CO-23 requires a verified Medicare conditional-payment context.
- 2
Reconcile the amounts across the primary EOB/835 and the secondary 835 before touching the claim.
- 3
Check the PLB section separately for a WO or other provider-level recovery, and route any true takeback to the overpayment process.
- 4
Confirm the primary payer actually adjudicated, and that the prior-payer data posted completely.
- 5
Compare the archived outbound secondary 837 against the posted ERA to catch dropped or mis-mapped COB data.
- 6
Verify crossover status before creating any manual secondary claim.
- 7
Verify payer order and the payer's COB/MSP record for the coverage period.
- 8
Document the finding, then take only the path the finding supports — no rebill, corrected secondary claim, COB update request, EDI escalation, or overpayment handling.
Then choose the correct disposition
No rebill
standard OA-23, normal secondary calculation, amounts reconcile, no separate PLB event; recognize it as informational prior-payer impact.
Obtain evidence first
primary adjudication or EOB missing, or N4 present: get the primary evidence, then build the appropriate secondary claim.
Secondary or corrected secondary claim
outbound 837 missing or imbalanced prior-payer data, once the transaction content is fixed.
EDI escalation first
posting is correct but the outbound 837 dropped or mis-mapped COB data; then submit the lifecycle-appropriate claim.
Reconsideration / COB update request
the payer's COB/MSP record is wrong while the claim is correct.
Reconciliation escalation
the OA-23 amount does not reconcile: payment posting / ERA reconciliation and contract analysis before any rebill or write-off.
Overpayment process
PLB WO present: follow the organization's overpayment and refund procedure.
MSP / Compliance routing
CO-23 with M32 in a verified Medicare conditional-payment context; conditional payments may be subject to later refund.
Verify before disputing
CO-23 outside a verified conditional-payment context, or an unknown group code: confirm the actual remittance and payer policy first.
Stop and escalate when
- The OA-23 amount does not reconcile against the primary and secondary remittances.
- A PLB WO or other provider-level recovery is present on the remittance.
- CO-23 appears with M32 in a Medicare conditional-payment context, or with an unexplained group code.
- The posted ERA looks correct but the archived outbound 837 is missing or imbalanced COB data (EDI/interface defect).
- The payer's COB/MSP record remains wrong after an update request.
What Needs to Be Corrected
- Often nothing on the claim: if amounts reconcile and no separate PLB event exists, OA-23 is informational prior-payer impact.
- Transaction content: 837P Loop 2320 CAS/AMT prior-payer adjudication, Loops 2330A/2330B other subscriber and other payer, 2330B DTP prior-payer adjudication date, and 2430 SVD/CAS service-line prior-payer adjudication where applicable.
- Posting: complete primary 835 data must be posted before secondary billing, so the OA-23 impact reconciles.
- Payer records: if the payer's COB/MSP record is wrong for the coverage period, request a record update and reprocessing rather than rebuilding the claim.
Do Not Do This
- Do not rebill solely because OA-23 appears.
- Do not post OA-23 as a fresh contractual write-off without reconciling prior-payer adjudication — those dollars may already be posted.
- Do not bill the patient solely because OA-23 leaves a remaining balance.
- Do not alter primary-paid or adjustment amounts to make the secondary payer pay.
- Do not confuse claim/service CAS with provider-level PLB recoupment.
- Do not assume CO-23 is universally valid; the X12 standard is OA-23, with the limited CMS conditional-payment exception.
- Do not manually submit a secondary claim when crossover already occurred.