CARC and RARC Denial Codes: A Remittance-Based Workflow for US Billing Teams
A denial queue is only as useful as its source data. US billing teams should use the remittance advice itself—group code, CARC, RARC and claim context—before assigning a root cause or next action.
The direct answer
For Medicare remittance, use the claim adjustment group code to understand the adjustment category and responsibility, the CARC to identify the overall adjustment reason, and the RARC when additional explanation is supplied. Do not collapse those fields into one free-text “denial reason” if you want reliable routing and trend analysis.
What each remittance code contributes
| Field | What it tells you | How to use it operationally |
|---|---|---|
| Claim Adjustment Group Code | The general adjustment category and financial responsibility context. | Keep it separate from the reason code; it changes how the balance should be interpreted. |
| CARC | The overall reason for a financial adjustment at claim or service-line level. | Use it as a controlled classification input, not as the entire root-cause diagnosis. |
| RARC | Additional explanation or informational detail when applicable. | Use it with the CARC and claim context to determine the correct next action. |
| PLB | Provider-level adjustments not tied to one specific claim. | Keep PLB reconciliation out of claim-denial queues so payment posting remains auditable. |
A six-step denial-routing workflow
- Import or capture the ERA/SPR without losing the original codes.
- Separate rejected claims from adjudicated claims and provider-level adjustments.
- Classify the CARC/RARC combination into an internal reason family such as eligibility, authorization, coding, duplicate, coverage, bundling or filing-limit exposure.
- Validate the claim, payer policy and supporting documentation before assigning root cause.
- Set the next action, owner and payer-specific deadline.
- Feed repeatable causes back into front-end edits, provider education or payer configuration.
Why code maintenance matters
CARC and RARC lists are updated over time. CMS issued a 2026 recurring update implemented July 6, 2026, and another scheduled for October 2026. Billing software, work queues and internal mappings should not assume that a static code list will remain current indefinitely.
Patient responsibility requires disciplined interpretation
For Medicare remittance, CMS explains that group codes communicate financial responsibility and that beneficiary billing is tied to the applicable patient-responsibility coding. Teams should not move a balance to the patient merely because a claim is unpaid; the remittance, coverage rules and applicable notice requirements must support that action.
Connected Neeraj RCM services
See medical billing and coding, claim submission and scrubbing, denial management and appeals, prior authorization support and RCM analytics.
Authoritative references
- CMS Health Care Payment and Remittance Advice
- CMS July 2026 CARC/RARC update, R13666CP
- CMS EFT and Remittance Advice operating rules
About the reviewer
Prateek Singh, CPCS reviews Neeraj RCM operational guidance for scope clarity, source attribution and separation of administrative work from payer, legal, coding and clinical decisions.