OA-32: Patient Not Eligible as Dependent

What Does OA-32 Mean?

OA-32 appears when the dependent eligibility issue does not clearly fall on the provider or the patient. This typically occurs in coordination of benefits situations where one payer recognizes the patient as a dependent but another does not, or when there is a dispute about which subscriber's plan should carry the dependent. The financial resolution depends on the specific COB circumstances.

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. Verify dependent status with each payer Run eligibility checks with all payers involved in the COB arrangement to determine which plan recognizes the patient as an eligible dependent.
2. Redirect the claim to the correct payer If one payer confirms dependent eligibility, submit or redirect the claim to that payer with the correct COB order.
3. Escalate COB disputes to the patient If neither payer recognizes dependent coverage, advise the patient to contact their employer or plan administrator to resolve the enrollment issue.

Common RARC Pairings

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

How to Prevent OA-32

• Collect all insurance information — primary and secondary — at registration and verify COB order before claim submission
• When multiple payers are involved, run dependent eligibility checks with each payer to confirm which plan covers the patient

Also Filed As

The same CARC 32 may appear with different Group Codes:

Related Denial Codes