Back to Blog
12 min read

CARC, RARC, and CAGC Codes: A Guide for Dental Teams

CARC, RARC, and CAGC codes on the 835 remittance tell you exactly why a dental claim was denied or adjusted. Learn how to read them, act on them, and stop guessing what payers meant.

CARC, RARC, and CAGC Codes: A Guide for Dental Teams

TL;DR

  • Three-layer code system: The 835 ERA explains every payment decision with a Claim Adjustment Group Code (CAGC), a Claim Adjustment Reason Code (CARC), and often a Remittance Advice Remark Code (RARC).
  • CAGC tells you who is responsible: Group codes like CO (contractual obligation) and PR (patient responsibility) determine who can be billed for the difference.
  • CARC tells you why: Reason codes describe the specific basis for the adjustment — but they are applied differently by different payers, so always read the remark code and the EOB context.
  • Act, don't just read: The value of decoding these codes is routing the work — appeal the denials worth appealing, fix the root causes, and stop re-adjudicating the same problems every month.

When a dental claim comes back adjusted or denied, the explanation is not a mystery — it is encoded. Buried inside the 835 remittance (or printed on an EOB) is a set of codes that, taken together, tell you three things: who the adjustment belongs to, why it was made, and what the payer wants you to do about it.

Most dental teams never learn to read this system. They see "Denied" on the ERA, open the claim, and call the payer — or worse, they guess. But the codes are standardized, which means they can be read systematically, routed systematically, and acted on systematically. This guide gives your team the map.

Where These Codes Come From

The Claim Adjustment Group Code (CAGC), Claim Adjustment Reason Code (CARC), and Remittance Advice Remark Code (RARC) are all components of the 835, the electronic remittance advice that is one of the HIPAA-adopted standard transactions. When your practice receives an ERA from a clearinghouse — typically paired with the Electronic Funds Transfer (EFT) that deposits the payment — it contains these codes on every adjusted line item.

Because the 835 is a standard transaction, the structure of the codes is consistent across payers. The meaning in practice still requires care: payers can apply the same CARC in slightly different ways, and the associated remark code usually carries the specific, claim-level detail. Under the CAQH CORE operating rules, payers are required to deliver consistent, machine-readable remittance data — which is what makes it possible for software to interpret these codes reliably and route them to the right work queue.

The Three Layers, Explained

1. CAGC: The Group Code (Who)

Every adjustment is tagged with a group code that classifies the adjustment by type. The most common group codes you will see on dental remittances:

| Group code | Meaning | Who is responsible for the balance | |---|---|---| | CO | Contractual Obligations | The provider (per the payer contract) — typically not billable to the patient | | PR | Patient Responsibility | The patient (deductibles, copays, non-covered services where the patient consented) | | PI | Payer Initiated Reductions | The payer (often corrects the payer's own prior payment) | | OA | Other Adjustments | Varies — read the reason and remark codes | | CR | Corrections and Reversals | Reverses a prior payment or adjustment |

The group code is your first filter. A CO adjustment means the provider is expected to absorb it. A PR adjustment means the patient owes it. If you see a CO adjustment you disagree with, that is an appeal candidate; if you see a PR adjustment, the question is whether the patient was properly informed of their responsibility.

2. CARC: The Reason Code (Why)

The CARC is the reason the adjustment was made. It is a separate field on the 835 from the group code: a code selected from a national list (usually numeric, such as 16, 50, or 97), maintained by the Washington Publishing Company (WPC) under the HIPAA-adopted standards. People often write the group code and reason code together as shorthand — for example, "CO-16" means group code CO paired with CARC 16 — but they are technically two different fields, and the CARC is not "CO-16" on its own. There are hundreds of CARCs, and the list is standardized — payers do not create their own reason codes inside the HIPAA-adopted set. The same official code can still appear in different payer scenarios, so read the code together with the remark code and the claim context.

A few that dental teams encounter regularly (always confirm against the current reference, because payer application varies):

  • CO + CARC 16 — "Claim/service lacks information or has submission/billing error(s)." Usually paired with a remark code explaining exactly what was missing — frequently the clinical attachment.
  • CO + CARC 97 — "The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated." The service was paid as part of another procedure rather than separately.
  • CO + CARC 50 — "These are non-covered services because this is not deemed a 'medical necessity' by the payer." The payer did not consider the service medically necessary for this patient.
  • PR group codes paired with a patient-responsibility CARC — adjustments that shift responsibility to the patient, such as a deductible or a non-covered service the patient agreed to pay.

Note that the shorthand "CO-16" or "PR-50" is common, but the group code (CO, PR, OA, PI) and the CARC number are separate fields on the 835 — think of them as "CO + CARC 16," not as a single "CARC CO-16."

The honest caveat: don't memorize the list. The CARC tells you the category of the reason; the RARC and the payer's own policy documents tell you the specifics of this claim. When your team sees a code it does not recognize, look it up in the official code list rather than assuming — and pair it with the remark code before deciding what to do.

3. RARC: The Remark Code (Details)

The RARC is a standardized remark code the payer attaches to explain the adjustment in more detail. The national list includes two series of remark codes:

  • N-prefixed claim adjustment remark codes explain common situations — for example, a code indicating that a required attachment was missing.
  • M-prefixed supplemental information codes add context for a remark or a situation.

Separately, payers may add portal notes, EOB text, or internal free-text context for details the national codes cannot express. Those messages are not part of the standardized RARC system at all — treat them as additional context, not as official RARCs.

If the CARC is the headline, the RARC is the article. A claim adjusted with CO + CARC 16 tells you the claim was missing something; the remark code tells you what was missing — the X-ray, the narrative, the perio chart — which is exactly what your team needs to know whether a simple resubmission will fix it.

Common Scenarios for Dental Teams

Here is how the layers fit together in situations you will recognize. Note that payer behavior varies, so treat these as typical patterns rather than guarantees for any specific carrier.

Scenario 1: The Missing Attachment

  • CAGC: CO
  • CARC: 16 (lacks information or submission/billing error)
  • RARC: A remark indicating the required clinical attachment was not received
  • What it means: The claim was clinically fine but arrived without the documentation the payer needed (for example, the pre-op radiograph for a crown).
  • Your move: Resubmit with the attachment, or appeal if the payer's remark conflicts with what you actually submitted. Then check your claim-scrubbing process so future claims with the same code are caught before transmission.

Scenario 2: The Frequency Limit

  • CAGC: CO
  • CARC: A frequency-related reason code (a standardized code, often paired with a remark code that explains the plan's limit)
  • RARC: A remark citing the plan's frequency limitation (for example, prophylaxis twice per calendar year)
  • What it means: The service is covered by the plan, but the patient has already received it within the plan's allowed frequency window.
  • Your move: This is usually a correct denial — the patient owes the balance if they were informed in advance. The process fix is upstream: your eligibility verification step should have caught the frequency limit before treatment.

Scenario 3: Not a Covered Benefit

  • CAGC: CO or PR
  • CARC: A not-covered reason code or a patient-responsibility code
  • RARC: A remark citing the plan exclusion (for example, adult orthodontics or a missing-tooth clause)
  • What it means: The plan does not pay for this service for this patient under these circumstances.
  • Your move: If the patient signed a financial agreement knowing the service was non-covered, bill the patient. If not, the balance may become a courtesy or practice absorbed amount — and your pre-treatment estimate process should be reviewed.

Scenario 4: Eligibility on Date of Service

  • CAGC: PR or CO
  • CARC: An eligibility-related reason code
  • RARC: A remark stating the patient was not covered on the date of service
  • What it means: The patient's coverage had terminated (or not yet begun) when treatment was rendered.
  • Your move: This is a verification failure. The patient may owe, but the real fix is benefit verification before the appointment — a step that shows up repeatedly among the top reasons for dental claim denials — plus a conversation with the patient about the surprise balance.

From Decoding to Action: The Workflow

Knowing what a code means is only half the battle. The point of decoding is routing the work. Here is a simple framework your billing team can adopt:

  1. Read the whole package. Never act on a CARC alone. Read the CAGC, the CARC, the RARC, and — when it exists — the paper EOB that came with it.
  2. Classify into one of three buckets.
    • Resubmit: Missing information or a technical submission error. Fix and resend within the timely filing window.
    • Appeal: You believe the adjustment is wrong under the contract or the documentation. Build the appeal with the evidence the remark code says was missing or insufficient.
    • Accept: The adjustment is a correct application of the plan. Write it off as contractual (CO) or bill the patient (PR) per contract.
  3. Track by code. Log every denial and adjustment by CARC so your denial management reporting can show patterns: which codes recur, which payers use them, and which procedures attract them.
  4. Attack the root cause. A code that appears once is a claim problem. A code that appears fifty times a month is a workflow problem — eligibility not verified, attachments not captured, or codes not updated.

| If you see... | Typical next action | |---|---| | CO + CARC 16 + remark about missing documentation | Resubmit with the attachment; fix the capture process | | Frequency-limit CARC | Confirm patient consent; fix upstream verification | | Not-covered CARC | Bill patient per signed agreement, or absorb; review estimates | | Eligibility CARC | Verify coverage before treatment; educate front desk | | CO code on a claim you submitted correctly | Appeal with supporting evidence |

Conclusion

The CARC/RARC/CAGC system exists so that payment decisions can be explained — and acted on — without a phone call to the payer. For dental teams, learning to read these codes turns a pile of confusing remittances into a clear work queue: resubmit the fixable, appeal the wrong, accept the correct, and fix the root causes that keep generating the same codes.

The practices that win at denial management treat codes as data, not as jargon. They know their top CARCs by payer, they know which remark codes signal an appealable error, and they have a workflow that routes each code to the right action within days — not weeks. That is the difference between a team that reacts to denials and a team that manages them, and it is the same discipline behind reducing dental claim denials in the first place.

Frequently Asked Questions

Q: Where do I find the official list of CARCs and RARCs? A: The national code lists are maintained by the Washington Publishing Company (WPC) and referenced by CMS as part of the adopted standards. Payers are required to use these standardized codes — they do not create their own CARCs or RARCs inside the official lists. Payers may add portal notes, EOB text, or internal free-text context, but those are separate from the official codes. Your clearinghouse or PMS documentation often includes searchable copies as well.

Q: Do all dental payers use CARCs and RARCs? A: Payers that send the standard 835 ERA use the CARC/RARC system by definition, because it is part of the HIPAA-adopted transaction. The code lists are standardized, but the same official code can still appear in different payer scenarios — the way a payer applies a code can differ from another payer — which is why you should always read the code together with the remark text and the claim context, not just the reason code alone.

Q: What is the difference between CO and PR group codes? A: CO (Contractual Obligations) means the provider is expected to absorb the adjustment under the payer contract — typically not billable to the patient. PR (Patient Responsibility) means the patient owes the amount, subject to the patient's financial agreement and your state's billing rules.

Q: Can software help my team act on these codes? A: Yes. Because the 835 is a standard transaction, software can read CARCs and RARCs automatically, categorize denials, and route them to the right work queue — for example, flagging an appeal candidate as soon as it returns from the clearinghouse. That is exactly the kind of workflow that denial management automation — such as Curo's denial handling for dental RCM — is built around. The human still decides whether to appeal and drafts the clinical argument.

References and further reading

Automate Your Practice Today

Join hundreds of clinics using Curo to increase case acceptance and streamline their prior authorization process.

Book a Demo