CO-23 shows up on secondary insurance claims and behaves differently from most other adjustment reason codes. The majority of CARC codes flag a problem with the claim. CO-23 describes a calculation: the secondary payer is crediting what the primary already paid and showing you what it owes after that credit. When the math is right, there is nothing to dispute. When it isn't, you have a specific and correctable revenue leak hiding in your coordination-of-benefits workflow.
What CO-23 means on a secondary claim
The X12 adjustment reason code 23 is "The impact of prior payer(s) adjudication including payments and/or adjustments." In plain language: the secondary payer saw the primary's payment, subtracted it from its own maximum liability, and is posting that subtraction as CO-23.
A concrete example helps. Say you bill $300 for a service. The primary allows $200 and pays $160 after applying the patient's $40 deductible. The secondary then receives the same claim plus the primary's explanation of benefits. The secondary's allowed amount is also $200. Its responsibility is to cover the $20 of the patient's cost-sharing that remains after the deductible. It credits the primary's $160 payment via CO-23 and pays $20 itself. That CO-23 for $160 is not lost money. It is the accounting entry confirming the primary's payment was applied.
When a $0 secondary payment with CO-23 is correct
A secondary paying $0 with CO-23 is not automatically wrong. It happens legitimately when the primary's payment meets or exceeds the secondary's maximum allowed amount.
- Primary paid more than secondary's allowed. If the primary allowed $200 and paid $185 while the secondary's own allowed amount is $180, the primary's payment has already covered everything the secondary would have owed. The secondary applies CO-23 for $180 and pays $0. This is coordination working as designed.
- Both plans carry the same contractual rate. When two commercial plans use the same fee schedule for a code, the primary's full payment often satisfies the secondary's entire liability, leaving $0 for the secondary to pay.
- Patient deductible fully satisfied by primary. If the primary's payment covered both the primary's share and the patient's cost-sharing, the secondary may have nothing left to contribute.
Before assuming an error, compare the CO-23 amount to the primary's actual paid amount. If they match, the secondary processed correctly.
When to investigate a CO-23 adjustment
CO-23 becomes a problem when the secondary's calculation is built on bad data. Three patterns are worth checking on any secondary claim where the payment seems too low.
- CO-23 amount doesn't match the primary's actual payment. Pull the primary's 835 and compare the primary paid amount to the CO-23 on the secondary's 835. If the secondary applied a CO-23 for $200 but the primary only paid $120, the secondary over-adjusted by $80. File a reconsideration with the corrected primary EOB attached.
- Missing or incomplete COB data on the secondary claim. The secondary claim must carry the primary payer ID, the primary claim number, and the primary paid amount in the COB loop. If your billing system submitted incomplete or stale COB fields, the secondary may have estimated the primary payment incorrectly. Review the outbound 837 for the secondary claim before disputing the result.
- Secondary processed before the primary finalized. Occasionally a crossover claim reaches the secondary before the primary's final 835 is available. The secondary may use a preliminary or estimated primary payment amount. Once the primary's final EOB posts, resubmit the secondary claim with the corrected data.
CO-23 versus CO-22
Both codes relate to coordination of benefits, but they fire at different stages.
- CO-22 fires at the primary stage. The payer believes another plan may owe first and is flagging the claim before or instead of paying its share. COB order has not been confirmed. The claim needs to be rerouted to the correct primary payer and resubmitted.
- CO-23 fires at the secondary stage. The primary has already paid. The secondary is crediting that payment and calculating its own share. CO-23 means the coordination pipeline is working; the only question is whether the credit amount reflects the primary's actual payment.
A claim that initially triggered CO-22 and was corrected will eventually produce CO-23 on the secondary claim once the primary pays and you resubmit downstream.
CO-23 and your secondary billing workflow
Every secondary claim with a CO-23 adjustment confirms that COB data reached the secondary payer. Practices with high secondary-claim volumes should run a quarterly audit: pull secondary claims with CO-23 adjustments, compare each CO-23 amount to the primary's paid amount on the primary's 835, and flag gaps above a threshold for reconsideration. Most amounts will match. The ones that don't are recoverable.
Timing matters here too. Secondary timely-filing windows are often measured from the primary's payment date, not the date of service. A slow COB workflow that delays the secondary submission can forfeit a payable claim entirely, even when the CO-23 math would have been correct. For a broader look at how coordination errors and secondary claim gaps compound into revenue leakage, that guide covers the full picture.
The bottom line
CO-23 is the secondary insurance system functioning as designed. It credits the primary's payment so the secondary doesn't pay twice. A $0 result is sometimes correct and sometimes an error rooted in bad COB data. The way to tell them apart is a direct comparison: what did the primary actually pay versus what the secondary applied as CO-23. If the numbers match, there is nothing to recover. If they diverge, resubmit the secondary claim with the correct primary EOB and the discrepancy closes.