Learn how CARC codes work in medical billing, how to interpret claim denials, pair CARCs with RARCs, identify common adjustment reasons, and improve claim resolution, denial management, and reimbursement accuracy.
May 20, 2026
.webp)

Key Takeaways
• CARC codes are HIPAA-mandated, standardized adjustment codes that explain why a claim was paid differently than billed, with the same meaning across every U.S. payer.
• The two-letter group code (CO, PR, OA, PI, CR) sits next to every CARC and decides whether the balance gets billed, appealed, or written off.
• A nonspecific CARC like CO-16 needs its paired RARC to be actionable—the RARC names the exact field, modifier, or identifier the payer flagged.
• A small subset—CARCs 16, 50, 97, and 19—drives most denied dollars, and grouping denials by CARC and payer reveals the upstream patterns that prevent future denials.
CARC codes are healthcare's universal language for explaining claim adjustments. Every payer, remittance, and denial workflow in U.S. healthcare runs on them.
Fluency in these codes is more valuable every year as denial volumes climb. Health plans sold through HealthCare.gov hit a 20% average claim denial rate in 2023, the highest since the federal marketplace launched in 2015, according to KFF’s analysis of CMS data.
The rise tracks with how payers are processing claims today: more automated edits, AI-driven claim flagging, and more aggressive medical-necessity reviews.
For RCM teams, that puts a premium on denial expertise—staff who understand reimbursement logic, payer-specific edits, and how to interpret a denial correctly the first time.
Every one of those denials carries a CARC, and reading it correctly is what separates appealed revenue from a permanent write-off.
This guide covers what CARC codes are, how they appear on remittance advice, how they pair with RARCs, the codes you'll see most often, and the workflow that turns CARC data into a denial-prevention lever.
CARC stands for Claim Adjustment Reason Code.
CARC codes are standardized denial codes that payers attach to Electronic Remittance Advice (ERA) and Explanation of Benefits (EOB) documents to explain why a claim was paid at a different amount than billed, or not paid at all.
Each CARC code comes with a group code attached to it, which signals the specific scenario the payer applied it to.
Example:
CARC Code 45 means: “Charge exceeds fee schedule/maximum allowable or contracted/legislated fee arrangement.”
This indicates the payer reduced the billed amount because it exceeded the allowed reimbursement amount under the payer’s fee schedule or contract.
The CARC codes are maintained by X12, the organization that sets U.S. standards for healthcare data exchange between insurers and providers.
Under HIPAA, every U.S. payer—Medicare, Medicaid, commercial insurers, Medicare Advantage, HealthCare.gov plans—uses the same CARC list. That standardization is extremely important operationally.
It means denial specialists, billers, and revenue cycle teams do not have to learn a completely different denial language for every payer. A CARC 197 means “authorization missing,” whether the claim came from UnitedHealthcare, Aetna, Blue Cross, or Medicare.
A universal denial coding framework allows:
After a CARC code is interpreted, the next steps are usually one of the following:
Recommended reading: How to Interpret an Electronic Remittance Advice
CARC codes explain the main reason a claim was denied or adjusted, while RARC codes provide additional details or instructions about that denial.
RARC stands for Remittance Advice Remark Code. Originally created by Medicare as a proprietary list, RARCs are now an industry standard under HIPAA and are used by most commercial payers as well.
Where a CARC tells you what category the adjustment falls into, a RARC tells you specifically what happened or what you need to do next. The active RARC list is several times larger than the CARC list because RARCs carry the detailed specificity that short numeric codes can't convey alone.
RARCs come in two types:
Here are the key differences between CARC and RARC at a glance:
A few common pairings you'll see in everyday denial work:
CARC codes appear in two places, depending on how your payer delivers remittance:
The ERA is a structured electronic file that your billing system or clearinghouse receives after claim adjudication. Within the ERA, payment adjustments are communicated using CAS (Claims Adjustment Segment) lines. A CAS segment contains:
Here's what a typical CAS line looks like, broken down piece by piece:

Note: This CAS segment means the payer reduced reimbursement by $125 because the service is considered bundled into another service and therefore not separately payable.
The EOB is the human-readable version—either a paper document mailed to providers or a PDF available via the payer portal. The CARC and its description typically appear in a "Remarks" or "Adjustment Reason" column for each service line. Some payers display the full CARC description; others display only the code number, requiring you to cross-reference the X12 code list.
When you open a remittance, pull four elements for each denied or adjusted claim line:
The X12 list contains over 350 active CARCs, but a small subset accounts for the majority of denied dollars across most specialties.
These are the codes you’re likely to be dealing with very often.
One pairing worth a closer look: CARC 45 and CARC 97. Both are write-downs against a contracted rate, but they're different problems.
1. CARC 45 is a fee schedule underpayment that needs contract-level review. C
2. ARC 97 is a bundling decision that can sometimes be resolved at the line level with the right modifier.
RARCs are most valuable on denials where the CARC alone isn't specific enough to act on—particularly CO-16, which covers everything from a missing modifier to an invalid procedure code to an absent authorization number.
This pairing matters for three reasons:
Recommended reading: Denial management playbook
CMS adds and modifies RARCs constantly.
Recent additions have focused on supporting the No Surprises Act, with new codes that identify cost-sharing calculations and out-of-network determinations subject to the Act's provisions.
Keeping denial dashboards synced with these RARC updates is essential for any provider with meaningful out-of-network volume.

Before reading the numeric CARC, read the group code—it immediately tells you whether the denial requires action or is a write-off.
CO denials need investigation: some are contractual write-offs (CO-45), others are correctable errors (CO-16). PR means bill the patient; no payer action needed. OA warrants investigation, often involving Medicare Secondary Payer or coordination issues. PI (payer-initiated reduction) can sometimes be disputed if it doesn't align with your contract terms.
These are also the first signals that feed into revenue cycle management metrics like clean claim rate and denial rate by payer.
Group your denials into categories before working individual claims— claim-by-claim review is how backlogs form.
The categories most dashboards use are administrative (CO-16, CO-18, CO-29), clinical (CO-50, CO-11), bundling and coding (CO-97, CO-4), coverage and COB (CO-22, CO-96), and patient responsibility (PR-1, PR-2, PR-3). Seeing denials at the category level lets you prioritize by dollar volume and by what the team can actually move this week.
For any CARC that's nonspecific—especially CO-16—pull the paired RARC before touching the claim.
Resubmitting without reading the RARC means guessing at the fix, and guessing costs timely filing days and staff hours. This is also where payer-specific language matters: some payers attach proprietary descriptions alongside the standard CARC, so the team needs a clean translation back to the standardized code.
Different CARC categories belong to different resolution owners.
Administrative errors like CO-16 and CO-18 sit with the billing team, while coding errors (CO-97, CO-4, CO-11) belong with the coding team—often signaling a need for a medical coding audit.
Medical-necessity denials (CO-50) go to clinical documentation or appeals staff. Timely filing denials (CO-29) belong with AR follow-up, and COB or coverage issues (CO-22, CO-96) route back to eligibility. Smaller practices may consolidate roles, but the principle holds: the person fixing the claim should be the person closest to the underlying error.
A denial that sits for 30 days is a denial that may never recover.
Common turnaround targets that high-performing denial management teams tend to converge on: administrative fixes within 48–72 hours, COB investigations in 3–5 business days, and appeal preparation for medical-necessity denials (CO-50) in 5–7 business days.
Timely filing appeals are most urgent; they should go out within 48 hours of identification, with documentation attached. These aren't industry-mandated SLAs; specific payer contracts may set firmer deadlines that take precedence.
Resolution without tracking is how the same denial recurs next month.
Log each denial by CARC code, payer, provider, and resolution outcome. A monthly review of this log surfaces the patterns that drive upstream fixes—a CARC 197 spike that traces to one payer means your prior authorization process needs attention; a CARC 16 spike at a specific clinic site means your registration training does. This is where revenue cycle analytics earns its keep—denial-by-denial firefighting won't surface those patterns, but trend data will.
Denial teams typically process hundreds of CARCs a week. At that scale, manual interpretation leads to mistakes such as claims being routed to the wrong workflow, RARC details being missed in the rush, and so on.
AI-powered denial analytics platforms solve this problem by mapping every denial by CARC category, payer, provider, and dollar impact.
CombineHealth's Taylor (AI denial analytics solution) automates this work in real time. Rather than tagging claims as denied or paid, Taylor categorizes every denial across your book of business and surfaces the patterns in a live analytics dashboard.
The dashboard shows denial volume and dollar impact by CARC category, trends by payer and provider, first-pass resolution rates, and patterns that indicate upstream process failures.
Taylor also reads both paper and digital EOBs, extracting CARC and RARC codes that would otherwise require manual review.
As a result, you can spend less time pulling individual remittances and more time on the patterns that move the needle.
Book a demo to see what Taylor can surface in your CARC and RARC data—by payer, by provider, by dollar impact!
1. What is a CARC code in medical billing?
CARC stands for Claim Adjustment Reason Code, a standardized code payers attach to ERA and EOB documents to explain why a claim was paid at a different amount than billed, or denied entirely. Required under HIPAA for all electronic healthcare transactions.
2. What's the difference between a CARC and an RARC?
A CARC identifies the primary reason for a claim adjustment and is present on every adjusted claim. A RARC (Remittance Advice Remark Code) provides supplemental detail but doesn't appear on every claim.
3. How many CARC codes are there?
The X12 active list contains hundreds of CARCs at any given time, with codes added, modified, and deactivated three times a year by the Claim Adjustment Status and Reason Code Maintenance Committee.
4. Is a CARC the same as a denial code?
Not exactly. Every denial carries a CARC, but not every CARC is a denial. CARCs also explain contractual write-downs, patient responsibility, bundling, and other non-denial adjustments. Treating every CARC as a "denial" inflates your denial rate and misroutes claims.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.