CO-23 Denial Code: Resolving Prior Payer Adjudication Errors

:::info Quick answer The CO-23 denial code indicates a math error or missing data regarding a primary payer's processing. The secondary payer is rejecting the claim because the primary payment plus all adjustments (contractual write-offs, deductibles, coinsurance) do not perfectly equal the total billed amount. :::

Secondary claims are a headache on a good day. You fought to get the primary insurance to pay, waited three weeks for the electronic remittance advice (ERA), and finally pushed the balance to the secondary payer. Then the claim bounces back with a CO-23 denial code.

Code CO-23 stands for: The impact of prior payer(s) adjudication including payments and/or adjustments.

Translated from insurance-speak, this means your math doesn't add up. The secondary payer is looking at the claim and saying, "You billed us for this service, but you didn't accurately tell us what the first guy did." Secondary payers will not pay a dime until they know exactly how much the primary payer allowed, how much they paid, and what specific adjustment codes (like patient responsibility or contractual write-offs) were applied to the balance.

Now that we are operating under stricter 2026 clearinghouse validation rules, resolving a CO-23 denial requires precision. A single penny off in your balancing equation will cause an instant automated rejection. Here is how to track down the math error, fix your electronic claim loops, and get your secondary claims paid.

What the CO-23 Denial Actually Means

When you submit a secondary claim electronically via the 837 EDI format, you aren't just sending a bill. You are sending a highly structured mathematical equation detailing exactly what happened at the primary level.

The secondary payer needs to know the allowable amount so they can determine their own liability. To do this, they rely on Claim Adjustment Segment (CAS) codes transferred from the primary EOB to the secondary claim.

For a secondary claim to process cleanly, the numbers must follow this exact formula:

Total Billed Amount = Primary Paid Amount + Patient Responsibility (PR) + Contractual Obligations (CO) + Other Adjustments (OA)

If that equation does not balance perfectly, the clearinghouse or the secondary payer's adjudication engine triggers a CO-23. They are telling you that the prior payer's adjudication data is either missing, incomplete, or mathematically impossible based on the total charge you submitted.

Let's look at a concrete example.

You bill $200.00 for a 99214. Medicare (Primary) allows $130.00. Medicare pays 80% of the allowable: $104.00. Medicare assigns a 20% coinsurance (PR-2): $26.00. Medicare applies a contractual write-off (CO-45) for the difference between your billed charge and their allowable: $70.00.

If you submit that claim to Medicaid (Secondary), the math must look like this: $104.00 (Paid) + $26.00 (PR) + $70.00 (CO) = $200.00 (Total Billed).

If your billing software accidentally drops the $70.00 CO-45 write-off during the crossover process, the secondary payer sees $130.00 in total accounting against a $200.00 charge. They issue a CO-23 denial because $70.00 is completely unaccounted for.

Why You Get Hit With a CO-23

The CO-23 denial code is almost entirely a symptom of bad data transfer. The primary payer usually processed the claim correctly, but the information broke down on its way to the secondary payer. Here are the specific triggers.

Manual Payment Posting Errors

If your practice still manually posts paper EOBs, human error is your biggest enemy. A biller might type in the primary payment and the patient coinsurance, but forget to manually enter the contractual adjustment. When they click "bill secondary," the practice management system generates a claim missing the CO-45 adjustment segment. The secondary payer immediately flags it.

Auto-Crossover Glitches

Medicare and many commercial payers have automated crossover agreements with state Medicaid programs and major supplemental plans (like AARP/UnitedHealthcare). Usually, these work beautifully. But in 2026, we are seeing an uptick in crossover failures when multiple adjustment codes are applied on a single line item—such as a Medicare sequestration cut (CO-253) combined with a standard write-off (CO-45) and a primary care physician bonus adjustment. The clearinghouse mapping drops one of the lesser-used CAS codes, unbalancing the claim.

EDI Loop 2320 and 2430 Failures

For the tech-savvy biller, the actual breakdown happens in the raw EDI file.

• Loop 2320 (Other Subscriber Information): This loop carries the claim-level primary adjudication details, including the primary payer's paid amount.
• Loop 2430 (Line Adjudication Information): This loop carries the line-level CAS codes (the specific write-offs and coinsurance amounts per CPT code).

If your billing software aggregates the adjustments at the claim level (Loop 2320) but the secondary payer requires them broken out by line item (Loop 2430), the secondary payer's system cannot read the data properly. They will hit you with a CO-23 because, to their computer, the adjustment data simply doesn't exist where it's supposed to be.

Medicare Advantage Coordination Issues

Medicare Advantage plans (Part C) have distinct payer IDs. We frequently see billers send secondary claims to Medicaid listing standard traditional Medicare as the primary payer, rather than the specific Medicare Advantage plan (e.g., Humana Gold Plus). When the secondary payer attempts to verify the prior adjudication impact against the stated payer ID, the mismatch triggers a CO-23.

Step-by-Step Resolution Workflow

Fixing this denial requires tracking down the original primary ERA or paper EOB and comparing it against the claim data your software sent to the secondary.

Step 1: Pull the Primary EOB Do not guess at the numbers. Go into your clearinghouse (like Waystar, Availity, or Optum) or your practice management software and pull the exact ERA from the primary payer. Print it out or put it on a second monitor.

Step 2: Check the Line-Item Math Look at each individual CPT code on that claim. Do not look at the claim total; look at the line items. Add the primary paid amount, the patient responsibility (copay/coinsurance/deductible), and the contractual write-offs. Does that exact number match the billed amount for that specific CPT code? If you billed $150.00 for the line, the adjustments and payments must equal exactly $150.00.

Step 3: Audit Your Patient Accounting System Go to the payment posting screen for that specific date of service in your software (Epic, Athena, Kareo, etc.). Compare what is posted in the system to the primary EOB.

Look for missing adjustment codes. Did the system post the CO-45? Did it post the CO-253 (Sequestration)? Did it post a CO-2 (Coinsurance) as a CO-3 (Copay)? Correct any data entry errors directly in the ledger.

Step 4: Regenerate the Claim Once the math balances in your software, regenerate the secondary claim. If your software has an EDI scrubber, run it through the scrubber to ensure it passes the balancing validation.

Step 5: The Paper Claim Fallback If you have corrected the math, but the electronic claim continues to reject for CO-23 at the clearinghouse level due to an unresolvable Loop 2430 mapping error, drop the claim to paper. Print a CMS-1500 form. Black out any other patients on the primary EOB to maintain HIPAA compliance, staple the primary EOB to the back of your CMS-1500, and mail it to the secondary payer. A human processor at the secondary payer will read the EOB and process the coordination of benefits manually.

Common CO-23 Causes and Fixes

The 2026 CO-23 Appeal and Correction Timeline

When dealing with secondary claims, the clock starts ticking the moment the primary payer processes the claim, not the date of service.

Under 2026 guidelines, timely filing for secondary claims varies aggressively by payer type. You do not have unlimited time to fix a CO-23 math error.

• State Medicaid (Secondary): Medicaid is historically the payer of last resort. Most state Medicaid programs give you between 90 and 180 days from the date on the primary EOB to submit a clean secondary claim. If you spend 60 days fighting a clearinghouse rejection, you might miss the window.
• Commercial Payers (Secondary): Payers like Blue Cross Blue Shield or UnitedHealthcare generally allow 90 to 120 days from the primary EOB date.
• Medicare (Secondary): If Medicare is secondary (e.g., the patient is still working and has primary employer coverage), you typically have 1 calendar year from the date of service, or 6 months from the primary payment date, depending on the specific MAC's current ruling.

Since a CO-23 is usually a clearinghouse rejection or an instant front-end denial, you do not need to write a formal appeal letter. You simply need to correct the math in your system and submit the claim as a corrected claim (using claim frequency code 7) or as a fresh secondary submission if the previous one never made it past the payer's front door.

Prevention Strategies

The best way to handle this denial is to prevent the math errors from occurring in the first place.

Mandate ERA Auto-Posting If your practice is still manually posting primary payments in 2026, you are losing money to administrative overhead and human error. Set up Electronic Remittance Advice (ERA/835) feeds for all major payers. ERAs automatically pull the correct CAS segments (PR, CO, OA) into your system perfectly balanced down to the penny. This entirely eliminates manual math errors on secondary claims.

Implement Secondary Scrubbing Rules Configure your clearinghouse or practice management system to hard-stop any secondary claim where the primary payment plus adjustments does not equal the total charge. A biller should never be able to hit "send" on a mathematically unbalanced claim. By forcing the software to flag these before batching, you keep the problem in-house rather than waiting two weeks for a payer denial.

Audit Crossover Reports Weekly Do not assume that an automated Medicare crossover actually made it to the secondary payer. Review your daily or weekly crossover reports from your Medicare MAC (like Novitas or NGS). If a claim fails to cross over due to an internal payer glitch, you need to know immediately so you can generate a secondary claim from your own system before hitting timely filing limits.

Frequently asked questions

What is the difference between a CO-23 denial and a PR-23 denial?

A CO-23 denial assigns financial liability to the provider (Contractual Obligation), meaning you cannot bill the patient for the unbalanced amount until you correct the secondary claim. If it were billed as PR (Patient Responsibility), the payer is indicating the patient owes the balance, but CO-23 specifically points to a provider billing or data transfer error.

Do I need to send the primary EOB to fix a CO-23?

If you are submitting electronically, you do not send the physical EOB; you simply ensure the primary payment and adjustment data (CAS segments) are accurately filled out in the EDI file. If the electronic file keeps failing due to mapping errors, you must drop a paper CMS-1500 claim and physically attach the primary EOB.

Why did my Medicare crossover claim deny with CO-23?

Crossover claims usually deny for CO-23 when Medicare applies a rare adjustment code (like a specific sequestration or penalty cut) that the secondary payer's system is not programmed to recognize, causing the secondary payer's math equation to fail.

How do I fix a CO-23 denial in Epic or Athenahealth?

Go to the original charge ledger for that date of service. Review the primary insurance payment posting. You will likely find that a contractual write-off was not entered. Update the payment line to include all adjustments shown on the primary ERA, balance the line to zero, and regenerate the secondary claim.

Does the CO-23 denial mean the primary insurance took back their money?

No. The primary insurance payment is safe and finalized. The CO-23 denial strictly comes from the secondary payer, who is simply refusing to process their portion of the bill until you clarify the primary payer's numbers.