Claim Adjustment Reason Code (CARC)

What a Claim Adjustment Reason Code is

Claim Adjustment Reason Codes are standardized numeric codes created and maintained by X12 that describe why a payer changed the billed amount on a claim. Each CARC pairs with a claim adjustment group code such as CO, PR, OA, or PI to indicate who is financially responsible and why.

CARCs appear on electronic remittance advice (ERA 835) and on paper remittance advice and explanation of benefits. Codes such as 45 (charge exceeds fee schedule or maximum allowable), 96 (non-covered charge), or 197 (precertification or authorization not obtained) are common examples.

In practice, CARCs are the payer's official language for denials, underpayments, and adjustments. Accurate reading and mapping of those codes is the foundation for denial workflows, appeal strategies, and contract variance analysis.

Why CARCs matter operationally

Cash, days, and risk all flow through CARCs. Every unpaid dollar on an ERA is tied to a CARC and a group code, which determines whether the balance is collectible, appeals-eligible, or must be written off.

Operationally, CARCs drive:

• Workqueues: which denials go to auth specialists, benefits-verification teams, clinicians, or front-desk staff.
• Write-off logic: what is contractual (CO-45) versus appealable payer behavior versus patient responsibility (PR-1, PR-2, PR-3, PR-96).
• Root-cause reporting: which issues are front-end (CO-16, MA130), clinical/auth (CO-197), or benefit design (CO-96, N130).
• Audit and compliance risk: repeated use of certain codes such as CO-22 (payment adjusted due to workers' comp or other coverage) can flag coordination-of-benefits or eligibility breakdowns.

Poor CARC mapping or shallow reporting has a direct cost. For example, treating every CO-197 like a simple prior-auth miss hides patterns where the payer is misapplying length-of-stay rules or ignoring existing authorizations. That can quietly drain high-dollar residential and PHP revenue while reports still look like "front-end error" problems.

How CARCs are used and read

On an ERA 835, each impacted service line or claim-level adjustment will show:

• A claim adjustment group code that signals who is responsible (for example, CO for contractual obligation, PR for patient responsibility, OA for other adjustment, PI for payer-initiated).
• One or more CARCs that specify the reason for the adjustment (for example, CO-45, CO-96, PR-1).
• Often a Remittance Advice Remark Code (RARC), such as N130 or MA130, that provides supplemental narrative detail.

Teams should read CARCs in context:

• CO-45 often means expected contractual discount, so no appeal and no rebill, but important for contract modeling.
• CO-16 or MA130 generally means claim is unprocessable due to missing or invalid data, so corrected claims are needed, not appeals.
• CO-197 paired with a remark code can mean lack of authorization, expired or exhausted auth, or services billed outside the authorized dates or units.
• CO-96 or PR-96 flags non-covered services, which might be due to benefit design, policy exclusions, or experimental/Investigational determinations.

Most billing systems store CARCs and RARCs but many teams only see plain-text descriptions or payer-specific narratives. Mature operations normalize CARCs into internal reason categories, build denial workqueues off those categories, and use them to drive payer conversations and contract discussions.

• Treating all CO-197 denials as "no auth on file" when many are actually for exceeding authorized units or dates on later days of a residential stay, which drives unnecessary write-offs instead of corrected billing or concurrent reviews.
• Writing off all CO-45 adjustments as pure contractual without checking for incorrect rates or units, especially on per-diem PHP/IOP codes where the payer sometimes applies the wrong fee schedule.
• Lumping CO-16, MA130, and other unprocessable-claim CARCs into denial-rate metrics, which makes the denial picture look worse and hides simple front-end data issues that need clearinghouse or EHR template fixes.
• Ignoring accompanying RARCs such as N130 and relying only on the CARC description, which causes the team to miss payer-specific policy references and appeal angles for behavioral-health exclusions.
• Not separating PR-96 patient-responsibility non-covered amounts from CO-96 payer non-covered amounts in reports, which leads to incorrect balance transfers to patients and compliance risk for aggressive collections.

Behavioral-health providers see CARCs clustered around carve-outs, authorization, and benefit design quirks that look different from medical-surgical practices. For example, Medicaid MCOs and commercial plans frequently use CO-197 with RARCs to cut days beyond the authorized length of stay for ASAM-mapped residential or PHP levels of care, even when the clinical record supports continued treatment.

Carve-out behavioral-health payers often apply CO-96 and N130 when a service is covered under the medical plan or requires a different vendor, such as separate SUD vs MH managers. Without accurate CARC mapping, staff may repeatedly bill the wrong plan or wrong entity, adding weeks of AR days for each episode.

Long per-diem episodes such as residential, PHP, and IOP are especially exposed. CARCs on day 21 or day 45 may represent multiple failure points: exhausted auth units, hitting benefit maximums, or payer policy denials for "custodial" level of care. If your system does not link CARCs back to the specific span of days and associated authorizations, the pattern stays invisible and concurrent-review teams cannot push back.

State Medicaid and Medicaid MCO behavioral-health programs also generate state-specific CARC/RARC combinations for eligibility quirks, spend-down, and hard visit limits. Misreading those into generic categories like "non-covered" can drive incorrect patient billing for services that are actually appealable or billable to another funding program such as county mental health or block-grant dollars.

AI can help with Claim Adjustment Reason Codes by reading every ERA 835, capturing each CARC and RARC combination, and assigning clear, consistent internal denial categories. Agents can learn your payer-specific patterns, such as how a particular Medicaid MCO uses CO-197 across residential vs IOP, and route items into the right workqueues for authorization follow-up, corrected claims, or true appeals.

Supabill's denials agent is designed to ingest remits, interpret CARC and RARC combinations like CO-16 with MA130 versus CO-197 with N130, and tag them with operational reasons such as "missing clinical documentation," "exceeded auth units," or "bill to carve-out." Humans still own judgment-heavy work such as deciding whether the clinical story supports an appeal or when to escalate patterns to payer reps. AI also cannot replace contract interpretation or legal strategy, so your revenue leader and compliance team still make the final calls on write-off policies and dispute posture.

How are Claim Adjustment Reason Codes different from Remittance Advice Remark Codes (RARCs)?

Claim Adjustment Reason Codes describe the financial reason for an adjustment to the claim line or claim, such as "charge exceeds fee schedule" (45) or "precertification or authorization not obtained" (197). Remittance Advice Remark Codes provide additional narrative context, such as referencing a benefit document, policy exclusion, or medical necessity guideline. CARCs always pair with a group code to show financial responsibility, while RARCs never carry dollars on their own. Both are standardized code sets maintained by X12 and referenced by CMS on remittance advice. Source

Where can I find the official list and descriptions for CARCs my behavioral-health practice is seeing?

The official, up-to-date list of Claim Adjustment Reason Codes is maintained by X12 and is accessible on the X12 code list page. CMS also republishes CARC and RARC information for Medicare remittances and explains how they appear on the ERA 835. For payer-specific twists, especially Medicaid MCOs, reference state Medicaid manuals and payer bulletins in addition to the base X12 list. Source

How should CARCs be used in denial reporting for behavioral-health programs with long episodes of care?

Behavioral-health programs with residential, PHP, or IOP care should group CARCs by operational root cause and by episode segment. For example, separate CO-197 denials at admission from CO-197 denials mid-stay or at step-down to IOP, and separate CO-96 non-covered codes that reflect benefit exclusions from CO-96 tied to policy-specific limits, such as day caps. Use those groupings to see where authorizations break down across the stay and where your utilization management or scheduling practices need adjustment rather than only looking at claim-level denial rate.

What is the role of CARCs in coordinating benefits between medical and behavioral-health carve-out plans?

CARCs often signal when a claim was paid under the wrong plan or benefit structure, for example when a behavioral-health service was billed to the medical plan instead of a behavioral carve-out vendor. Codes like CO-22, CO-96, and N130, when read together, can indicate that another payer is primary, a service is covered under a different benefit, or plan rules require submission to a specific behavioral-health administrator. Billing teams should use these patterns to refine eligibility workflows and payer selection rules, not just handle each denial as a one-off. Source

Can CARCs alone tell me whether to appeal or write off a denial?

CARCs provide a strong starting point but should not be the only input for appeal decisions. Codes like CO-45 are usually pure contractual adjustments and not appealable, while CO-197 or CO-96 might be appealable depending on the coverage policy, benefit limits, and clinical documentation. For behavioral health, medical-necessity and level-of-care disputes are often hidden behind generic non-covered or medical-policy CARCs. Best practice is to combine CARCs, RARCs, payer policies, and your clinical record to decide whether an appeal has merit.

• X12, Claim Adjustment Reason Codes
• Medicaid.gov, Managed Care