Skip to main content
Call
CARC 32 · CO-32

CARC 32 Denial: Our records indicate that this dependent is not an eligible dependent as define… — How to Fix and Appeal

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

TL;DR

CARC 32 (X12 Our records indicate that this dependent is not an eligible dependent as defined). CARC 32 denies because the patient is not currently listed as an eligible dependent on the policy.

Official X12 description

“Our records indicate that this dependent is not an eligible dependent as defined.”

Source: X12 Claim Adjustment Reason Codes. The X12 External Code Lists are the single authoritative source for every CARC descriptor — always verify against the current release before building a claim-scrub rule.

What CARC 32 actually means

CARC 32 denies because the patient is not currently listed as an eligible dependent on the policy. Confirm dependent status with the member, then update the payer's enrollment (for qualifying events) or shift to a different plan/payer. Not usually appealable on clinical grounds.

Common root causes

  • Dependent age-limit exceeded (college-graduate drop from a parent's plan).
  • Stepchild/domestic-partner relationship not documented to the plan.
  • Adoption or custody change not yet reflected in enrollment.

Prevention checklist

  • Dependent-eligibility snapshot at each appointment via 270/271.
  • Age-26 triage for young-adult dependents.

Appeal strategy — step by step

Most CARC 32 denials clear faster with the right remediation than with a formal appeal. Work the steps in order and escalate only when a lower-effort path has been ruled out.

  1. 1Update enrollment (qualifying-event window) and resubmit.
  2. 2If the dependent is genuinely ineligible, shift to self-pay or correct payer.
Sample appeal-letter language for CARC 32
[Provider letterhead] Re: Appeal of CARC 32 — Claim #{claim_number} Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} On {remittance_date} this claim was adjusted with CARC 32: "Our records indicate that this dependent is not an eligible dependent as defined." We respectfully request reconsideration. The X12 External Code List definition of CARC 32 does not apply to this claim for the following reasons: 1. [Cite the clinical / coding / policy fact that rebuts the adjustment] 2. [Cite the supporting documentation attached — op note, EOB, LCD/NCD citation, NCCI edit indicator, modifier rationale] 3. [Cite the payer's own policy where applicable] Attached: {list supporting documents} Please process payment under the member's benefits. If additional information is required, contact the billing office at {provider_phone} or {provider_email}. Sincerely, {billing_manager_name}, {credentials}

Edit the bracketed fields before sending. This template is a starting point; a payer-specific appeal form may still be required — check the provider portal first.

Payer-specific notes

Payer-specific behavior for CARC 32 publishes here as the QuickIntell anonymized denial ETL ingests sufficient volume. In the meantime, consult the payer directory for the relevant provider manual and appeal form.

How common is CARC 32?

Search demand rank
#67

Out of 306 seeded CARCs, ranked by combined US monthly search volume for "CARC 32", "CO-32 denial", and "denial code 32".

Platform frequency
Pending ETL

Platform frequency ranks publish once the anonymized denial-rate pipeline reaches the publication threshold (strategy §12 Phase 2).

How QuickRCM prevents CARC 32

QuickRCM catches the root causes above before the 837 leaves the clearinghouse:

  • Claim-scrub rules fire on every root cause listed above — the scrub references the same X12 CAS segment logic that drives the denial, so what the payer checks, QuickRCM checks first.
  • When a denial lands, QuickRCM routes it to the correct worker with the documentation bundle already attached (op note, LCD citation, modifier rationale, EOB, primary 835).
  • Appeal templates tuned to each CARC (including this one) pull the supporting facts from the claim and fill the bracketed fields automatically.
See QuickRCM →Book a demo

Frequently asked questions — CARC 32

What does CARC 32 mean?

CARC 32 is an X12 Claim Adjustment Reason Code. The official definition is: "Our records indicate that this dependent is not an eligible dependent as defined." In plain English, the payer is telling you cARC 32 denies because the patient is not currently listed as an eligible dependent on the policy. Confirm dependent status with the member, then update the payer's enrollment (for qualifying events) or shift to a different plan/payer. Not usually appealable on clinical grounds.

How do I resolve a CARC 32 (CO-32) denial?

Start with the most common root cause: Dependent age-limit exceeded (college-graduate drop from a parent's plan). First step: Update enrollment (qualifying-event window) and resubmit. See the full remediation and appeal checklist on this page before filing a formal appeal.

Is CARC 32 patient responsibility?

No — CARC 32 is typically carried under CO (Contractual Obligation) or OA (Other Adjustment), which means it is the provider's responsibility, not the patient's. Do not bill the patient unless the 835 CAS group code is PR.

What does CARC 32 look like on an EOB or 835 remittance?

On the 835 ERA, CARC 32 appears in Loop 2110 CAS segment as "CAS*CO*32*{amount}". On a paper EOB the same code prints in the Adjustment/Denial Reason column with the X12 description: "Our records indicate that this dependent is not an eligible dependent as defined." — usually paired with one or more RARC remark codes in the same remittance line for additional context.

Which RARC is paired with CARC 32?

CARC 32 is commonly observed with RARC N30. The RARC narrows the reason — for example, pointing at a missing modifier, an LCD citation, or a specific policy. Fix the underlying CARC first; the RARC usually clears with the corrected claim.

Disclaimer

This page is operational reference for medical-billing professionals. It is not legal, clinical, or contractual advice. X12 code descriptors are maintained by the X12 External Code Lists; always verify against the current X12 release and the payer's own published policy before submitting or appealing a claim.