CO-32: Patient Not Eligible as Dependent

What Does CO-32 Mean?

CO-32 indicates the payer attributes the dependent eligibility failure to a provider-side issue — most commonly a claim submission error such as an incorrect relationship code, a wrong subscriber ID, or reversed subscriber and patient fields. The payer is saying: we cannot process this claim because the data does not match a valid dependent relationship in our system, and the provider needs to fix and resubmit. The patient cannot be billed for a CO-32 amount.

When CARC 32 appears on a remittance, the payer is telling you that the patient does not qualify as a dependent under the subscriber's insurance policy. The payer checked the patient's enrollment record and either found no dependent relationship to the subscriber, found that the dependent relationship has ended, or found that the patient was never formally added to the plan.

The most common real-world trigger is a dependent aging out of coverage. Under ACA rules, most plans cover dependents until age 26, but some legacy plans or specific plan types have different cutoffs. Divorce, legal separation, or the subscriber dropping dependent coverage during open enrollment also cause this denial. Less frequently, it appears when the subscriber assumed a family member was covered but never completed the enrollment paperwork.

The group code pairing determines your next step. PR-32 is the most common and means the patient is financially responsible — the payer confirmed the service was processed correctly, but the patient simply is not covered as a dependent. CO-32 indicates a data issue on the provider's side, such as an incorrect relationship code or subscriber ID mismatch, and requires correction and resubmission. In either case, confirming the patient's current coverage status through an eligibility inquiry is the essential first step.

Common Causes

How to Resolve

Verify the patient's dependent eligibility status, determine whether the denial is a data error or a genuine coverage gap, then either correct and resubmit or bill the patient.

1. Identify the data mismatch Run an eligibility check and compare the subscriber ID, patient name, date of birth, and relationship code on the claim against the payer's response. Pinpoint the exact field that does not match.
2. Correct the claim and resubmit Update the incorrect field — relationship code, subscriber ID, or patient demographics — in your PM system and submit a corrected claim. Verify that the payer's eligibility system confirms the patient as an active dependent before resubmitting.
3. Appeal if the payer's records are wrong If you have documentation proving the patient is an eligible dependent (e.g., the subscriber's benefits summary showing active dependent coverage), file an appeal with the supporting documentation.

Common RARC Pairings

The RARC code tells you exactly what triggered the CO-32:

How to Prevent CO-32

• Verify dependent eligibility at scheduling and check-in, specifically confirming the subscriber-dependent relationship code matches payer records
• Implement PM system edits that flag relationship code mismatches between the eligibility response and the claim before submission
• Update patient records at every visit, asking whether the subscriber or dependent relationship has changed

General Prevention

• Run eligibility verification at scheduling and check-in for every patient, specifically confirming dependent status and the subscriber-dependent relationship
• Verify the relationship code (spouse, child, domestic partner) matches what the payer has on file before claim submission
• Update patient records at every visit — ask whether insurance coverage or subscriber information has changed since the last visit
• Implement automated eligibility checking that flags patients whose dependent coverage may be approaching age limits

Also Filed As

The same CARC 32 may appear with different Group Codes:

Related Denial Codes