PR-32: Patient Not Eligible as Dependent
The patient is not a covered dependent. The balance is their responsibility. Bill the patient and help them identify alternative coverage.
What Does PR-32 Mean?
PR-32 means the patient genuinely does not qualify as a dependent under the subscriber's plan, and the resulting balance is the patient's financial responsibility. The payer processed the claim correctly — the patient is simply not covered. Common scenarios include dependents who aged out at 26, dependents dropped from the plan during open enrollment, or individuals who were never formally enrolled as dependents. The provider is expected to collect this amount from the patient.
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
| Cause | Frequency |
|---|---|
| Dependent aged out of coverage The patient exceeded the maximum age for dependent coverage under the plan — typically age 26 under ACA provisions, though some plans have different age limits for student or disabled dependents | Most Common |
| Life event changed dependent status A divorce, marriage, or legal separation removed the patient from dependent eligibility, but the subscriber did not update the insurance plan | Common |
| Insufficient documentation of dependent relationship The payer requires proof of the dependent relationship (birth certificate, adoption papers, marriage certificate) and the subscriber has not provided the required documentation | Common |
| Subscriber did not add dependent to plan The subscriber assumed a family member was covered but never formally enrolled them as a dependent during open enrollment or a qualifying life event | Occasional |
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.
- Confirm the coverage gap Verify with the payer exactly why the patient is not an eligible dependent — age limit, enrollment status, or subscriber change. This helps you explain the situation clearly to the patient.
- Transfer the balance to patient A/R Move the denied amount from insurance receivables to the patient responsibility ledger. Generate and send a patient statement clearly showing that the claim was denied because dependent eligibility could not be confirmed.
- Contact the patient Inform the patient of the denial and the specific reason. Ask whether they have obtained their own insurance coverage. If they have, collect the new insurance details and submit a new claim to that payer.
- Offer payment options For patients without alternative coverage, provide self-pay pricing, payment plan options, and information about financial assistance programs if applicable.
This adjustment is correct per the patient's benefit plan. The amount is the patient's financial responsibility. Collect from the patient rather than appealing.
Common RARC Pairings
The RARC code tells you exactly what triggered the PR-32:
| RARC | Description |
|---|---|
| N321 | Alert: Missing or invalid information. |
| N517 | Alert: Payment based on the information available at the time of adjudication. |
How to Prevent PR-32
- Ask patients about upcoming life events that may affect dependent coverage — turning 26, divorce, or subscriber employment changes
- Inform patients at registration about dependent age limits and encourage them to verify their own coverage status before appointments
- Collect an Advance Beneficiary Notice or financial responsibility acknowledgment when dependent eligibility cannot be confirmed in real time
General Prevention
- Inform patients at registration about dependent age limits and upcoming coverage changes so they can plan for their own coverage
- Ask patients about recent life events (marriage, divorce, dependent turning 26) that may affect their coverage status
- Advise subscribers to confirm dependent enrollment with their employer or insurer well before the dependent's coverage end date
- Collect an Advance Beneficiary Notice or financial responsibility form when dependent eligibility cannot be confirmed before service
Also Filed As
The same CARC 32 may appear with different Group Codes:
Related Denial Codes
Sources
- https://www.mdclarity.com/denial-code/32
- https://denialcode.com/32
- https://www.trytwofold.com/medical-codes/pr-32-denial-code
- Codes maintained by X12. Visit x12.org for official definitions.