Skip to content
ContractualCARCNot billable to patient

CO-63 denial code

Correction to a prior claim

An adjustment reflecting a correction the payer applied to earlier processing.

How to fix it

Reconcile against the original claim to confirm the net result is correct. Usually informational.

How to prevent it

Post adjustments against the original claim rather than as standalone transactions so the audit trail survives.

The CO prefix marks this a contractual obligation. The balance is absorbed by the provider under the payer agreement and cannot be transferred to the patient.

In practice

A remittance arrives carrying CO-63 against a claim that was paid four months ago. Nothing about the current billing changed, and the adjustment appears without explanation.

The payer has revisited its earlier processing and applied a correction. This can move money in either direction — recovering an overpayment or releasing an additional payment — and the remittance line alone does not always make clear which.

The work is reconciliation rather than appeal. Find the original claim, apply the adjustment against it, and confirm the net result across both transactions is correct. Posting the adjustment as a standalone entry destroys the trail that makes the account explicable later.

What sits behind it

Retroactive corrections come from a handful of recognisable sources: a fee schedule loaded late and then applied backward, a coordination of benefits discovery that changes payer order, an enrolment correction that reprices historical claims, or a payer-side reprocessing project covering a whole cohort.

The pattern is more informative than the individual line. A single correction is routine; dozens arriving together indicate a bulk reprocessing, and identifying the driver tells you whether more is coming and whether the direction favours you.

Where a correction recovers money, the recovery mechanism matters for reconciliation. Some payers offset against future remittances rather than requesting repayment, which means the money disappears from an unrelated payment and looks like an underpayment on a different claim entirely.

Related codes

Terms used here — Payment Posting · ERA · Contractual Adjustment

How we handle it — Revenue Cycle Management · AR Management · Practice Analytics

Primary sources

The rules behind CO-63, at the bodies that publish them.

Looking for a different code? Search all 190 CARC and RARC codes

Questions about CO-63

No, it is an adjustment to processing the payer already performed, and it can move money in either direction. Treat it as a reconciliation item: locate the original claim, apply the adjustment against it, and verify the combined result is correct.

Common causes are a fee schedule loaded late and applied retroactively, a coordination of benefits discovery changing payer order, an enrolment correction repricing history, or a payer reprocessing project covering many claims at once. A cluster of these arriving together points to the last.

Against the original claim, never as a standalone transaction. Posting it separately breaks the audit trail and makes the account impossible to explain later, particularly where the payer recovered the money by offsetting against an unrelated remittance.

Find out what your denials are costing you

A free billing audit reviews your denial rate, AR aging and clean claim rate against industry benchmarks. Takes about two minutes to request. No sales pitch.

No setup fees · You pay when we collect · Pricing from 3% of net collections