CO-33: Insured Has No Dependent Coverage

What Does CO-33 Mean?

CO-33 indicates the payer attributes the denial to a provider-side submission issue. This typically means the claim was filed under a subscriber whose plan does not include dependent coverage, and the provider should have verified this before submission or before rendering services. The amount is a contractual write-off unless the provider can redirect the claim to the correct payer.

When CARC 33 appears on a remittance, the payer is telling you that the subscriber's insurance plan does not extend coverage to any dependents. Unlike CARC 32 (which says this specific patient is not eligible as a dependent), CARC 33 is broader — the subscriber's plan design itself has no dependent benefit at all. The policy covers only the enrolled subscriber.

This denial surfaces most often when a subscriber selected an employee-only or individual plan tier during open enrollment, either to save on premiums or because their employer's plan does not offer dependent coverage. The subscriber may not fully understand that their plan excludes family members, leading them to present the insurance card for a dependent's visit. It also occurs when a subscriber downgrades from a family plan to an individual plan at renewal and does not inform their dependents.

Under PR, this is a straightforward patient responsibility situation — the service was rendered but no insurance coverage exists for the dependent. Under CO, the provider likely filed under the wrong subscriber or plan, and correction is needed. In either case, the immediate priority is determining whether the patient has any other source of coverage, such as their own employer plan, a marketplace policy, or Medicaid eligibility.

Common Causes

How to Resolve

Confirm the subscriber's plan does not include dependent coverage, then either redirect the claim to the patient's own insurance or bill the patient directly.

1. Verify the subscriber's plan type Confirm with the payer that the plan is employee-only. If the patient is a dependent under a different subscriber or payer, gather the correct information and resubmit.
2. Redirect to the correct coverage If the patient has their own insurance, file a new claim under the patient's own policy rather than as a dependent under the subscriber's plan.
3. Write off if no alternative path exists If no other coverage source can be identified and the error is purely on the provider side, post the contractual adjustment. Do not transfer CO-33 balances to the patient.

Common RARC Pairings

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

How to Prevent CO-33

• Configure eligibility checks to verify not just patient identity but also the subscriber's plan tier — specifically whether it includes dependent coverage
• Flag employee-only and individual plans in your PM system so front-desk staff know dependent claims cannot be filed under these plans
• Update plan type information at every visit, especially after open enrollment periods when subscribers may have changed coverage tiers

General Prevention

• Verify not just that the patient is a dependent but that the subscriber's plan type includes dependent coverage as part of the eligibility check
• Configure your eligibility verification system to flag subscriber-only or employee-only plans that cannot cover dependents
• Update plan type information in your PM system at every visit, particularly at the start of each plan year when subscribers may have changed coverage levels

Also Filed As

The same CARC 33 may appear with different Group Codes:

Related Denial Codes