Claim Adjustment Reason Code

A CARC explains an adjustment reason

The official X12 CARC list defines these codes as reasons a claim or service line was paid differently than billed. A CARC can describe a denial, reduction, patient cost-share amount, contractual adjustment, or another adjudication difference. Seeing a CARC does not mean every associated claim was denied.

The code belongs to a larger remittance record. CMS Medicare guidance says line- or claim-level adjustments may use three code sets:

1. a Claim Adjustment Group Code, which categorizes the adjustment and generally assigns responsibility
2. a CARC, which gives the reason
3. a Remittance Advice Remark Code, which can supply added explanation

The adjustment amount and claim- or line-level placement matter too. Capture the full combination exactly as received.

Group codes, CARCs, and RARCs answer different questions

A group code such as contractual obligation, patient responsibility, other adjustment, or payer-initiated reduction categorizes the adjustment. The CARC explains why the amount changed. The X12 RARC list distinguishes supplemental remarks that explain a CARC from informational alerts about remittance processing.

Some CARCs require an accompanying remark. A RARC marked as an alert is informational and does not explain a specific adjustment. Read each current definition and usage note rather than assuming any remark can satisfy a required explanation.

A patient-responsibility group code is important evidence; it is not permission to bill the person automatically. Check the member explanation, benefit terms, contract, payer policy, prior payments, financial agreement, applicable balance-billing rules, and any correction or appeal in progress before changing a balance.

A CARC is separate from claim status and payment

The X12 Claim Status Code list communicates the status of a claim or service line. CARCs concern adjudication adjustments. A TA1, 999, 277CA, clearinghouse report, portal status, remittance, and payment deposit represent different transaction stages.

An ERA explains adjudication and adjustments. EFT moves funds. CMS administrative-simplification guidance states that HIPAA standard remittance uses X12-maintained CARCs and RARCs and separately describes ERA and EFT.

Match the deposit to the remittance and original claims. One payment may cover many claims, and one claim may contain several adjusted lines. Avoid treating an EFT total as a claim-level disposition.

Read the current code in the payer context

X12's External Code Lists page identifies the maintainer and last-modified date for each list. Use the official current entry, status, start or stop date, notes, and group-code restrictions. Preserve the artifact's transaction date and the payer's applicable companion or policy source.

A code meaning does not specify every next step. The payer may require a corrected claim, reopening, reconsideration, appeal, records response, coordination-of-benefits action, enrollment correction, refund, or another route. Capture the written instruction and deadline. When sources conflict, hold release and obtain payer clarification through the authorized channel.

Build a remittance-to-action record

For each adjustment occurrence, record:

• payer, product, member, claim, service line, service date, and payer control number
• received date, remittance identifier, claim status, billed, allowed, paid, and adjustment amounts
• group code, CARC, RARC, claim- or line-level scope, and exact payer text
• official code-list version plus payer policy, contract, and notice source
• authorization, eligibility, provider configuration, coding, and submission evidence
• route, deadline, owner, hold reason, submitted action, and final disposition

Preserve the original claim and clinical record. A qualified coding or billing reviewer selects the claim route. An appropriately qualified clinician owns any permitted clinical correction under documentation policy. A CARC cannot authorize altered service facts, false dates, unsupported codes, or a clinical rewrite.

A fictional CARC work queue

A fictional practice reviews 20 adjusted service lines whose review date has arrived. All 20 remain in the denominator, including held lines.

Eighteen lines have a verified match among payer, claim or line, group code, CARC, adjustment amount, and any supplied or required RARC. Context completeness is 18 of 20, or 90%. Two unmatched lines stay held while staff retrieve the remittance detail.

Fifteen of the 20 have a documented payer-defined next route, so route-determined yield is 15 of 20, or 75%. Five holds remain visible. Of 15 adjustment occurrences due for final disposition by the reporting cutoff, 12 are closed: 12 of 15, or 80%.

These are adjustment-occurrence measures. Twenty lines may belong to fewer claims. Report unique claims, service lines, adjustment occurrences, and dollars separately so repeated codes on one claim do not inflate the claim count.

Measures for a controlled workflow

Useful measures include context-complete adjustments divided by mature adjustments reviewed; route-determined adjustments divided by the same mature cohort; actions completed by deadline divided by actions due; and final dispositions by target divided by mature dispositions due. Segment by payer, product, CARC, RARC, source rule, and workflow version.

Also track recurrence, avoidable correction, appeal outcome, adjudication result, recovered amount, write-off, patient-balance change, and days to final disposition. A lower CARC count can reflect fewer claims, delayed remittances, changed coding, or workflow drift, so pair rates with counts and exposure.