Dependent Eligibility and the Carrier Invoice

Dependents are billed, and they are almost never reconciled.

Employee records get attention because employees interact with payroll every cycle. A dependent generates no signal at all. Nobody notices when a child ages out, when a divorce should have removed a spouse, or when a step-child stopped being a dependent three years ago.

So they stay on the invoice. Sometimes for years.

Why dependents are harder

No independent record. A dependent exists only as an attachment to an employee record, and often only inside the enrollment system.

Eligibility changes without an event you'd see. A child aging out is a birthday. Nothing happens in payroll, nothing happens in HR, and nobody files anything.

The employee has to tell you. Divorce, a child losing student status, a step-child leaving the household - none of these surface unless reported. And the employee has a financial reason not to report them.

Tier billing hides the detail. Many carriers bill by tier, so employee-plus-family costs the same whether there are two dependents or five. The invoice gives you no dependent-level detail to reconcile against - the error is invisible on the bill by construction.

Documentation is collected once and never revisited. Eligibility verified at enrollment, then assumed permanently.

Where the errors are

Situation	Why it persists
Child aged out	Birthday with no process attached
Ex-spouse still covered	Divorce is reported late or not at all
Step-child after the relationship ends	Ambiguous eligibility, nobody asks
Child no longer a full-time student	Where the plan requires it, status is never re-verified
Dependent covered under two employees	Both parents work for you and both enrolled the child
Deceased dependent	Rarely reported
Never eligible at all	Documentation never collected at enrollment

The age-out is the most common, and the most preventable

A plan defines a maximum age for dependent children. The child reaches it. Coverage should end per the plan's terms.

Nothing triggers it automatically unless someone built the trigger. And because tier billing masks the change, the invoice looks identical the month before and the month after.

This is the clearest case for a scheduled check rather than an event-driven one. Run a report of dependents reaching the limit in the next 90 days, every month. It's the highest-yield reconciliation task in this whole cluster relative to effort.

What happens on divorce

Divorce or legal separation is a permitted election change event if your plan allows it - the cafeteria plan regulation is explicit that permitting mid-year changes is optional plan design, not a requirement.

Two things reconciliation needs to know:

The consistency rule constrains what can change. On divorce, dropping coverage for other, unaffected dependents fails the consistency test. The change must correspond to the event.

Divorce is also a COBRA qualifying event for the spouse, with a 36-month maximum coverage period. And the qualified beneficiary has at least 60 days to notify the plan - running from the latest of the event, the loss of coverage, or the date they were informed of the notice obligation and the plan's procedures.

So a divorce reported late is both a billing problem and a COBRA problem, and the COBRA side carries the larger consequence.

You usually can't take the coverage back

The same rule that governs terminated employees governs ineligible dependents.

Retroactive cancellation of coverage is generally prohibited absent fraud or an intentional misrepresentation of material fact. An administrative failure to remove an aged-out dependent is neither. The coverage generally stands, termination is prospective, and the premium is generally owed.

Where it may be different: if the employee failed to report a change they were required to report, and did so knowingly, the intentional-misrepresentation exception may be in play. That is a genuinely different fact pattern - and one to route through counsel rather than through the reconciliation process.

The practical conclusion: prevention is the entire strategy. The money is not recoverable after the fact in most cases, so the value is in catching it early.

Dependent eligibility audits

A periodic audit asks employees to re-verify each dependent with documentation - marriage certificates, birth certificates, tax returns, proof of student status where relevant.

Reconciliation notes:

• Give employees adequate time and a clear process. Removals should be prospective, on a stated future date.
• Removals are COBRA qualifying events for the affected dependents. Build the notices into the project from the start, not afterward.
• Expect a meaningful removal rate. That's the point - it also tells you how much your ongoing process is missing.
• Audit findings should feed process changes, not just removals. A high age-out count means you need the 90-day report, not another audit in three years.

What to build

A dependent-level census, maintained independently of the tier on the invoice. If your carrier bills by tier, this is the only place dependent-level truth exists.

A scheduled age-out report - 90 days forward, run monthly.

Student status re-verification on a schedule, where the plan requires it.

A duplicate-coverage check across employees, which finds children enrolled by two parents.

Documentation retention tied to the dependent record rather than to the enrollment event.

Frequently asked questions

Why don't dependent errors show up on the invoice?

Most carriers bill by tier. Employee-plus-family costs the same regardless of dependent count, so the invoice shows nothing.

Can we remove an aged-out dependent retroactively?

Generally no. Retroactive cancellation is prohibited absent fraud or intentional misrepresentation. Removal is prospective.

What if the employee never told us about a divorce?

Depending on the facts, the intentional-misrepresentation exception may apply - but that's a legal question, not a reconciliation one. Route it accordingly.

Is divorce a COBRA event?

Yes, for the spouse, with a 36-month maximum. The beneficiary has at least 60 days to notify the plan.

Do we have to allow a mid-year change on divorce?

Only if your plan permits it. Permitted change events are optional plan design.

How often should we run a dependent eligibility audit?

Periodically - but the monthly age-out report prevents more than any audit recovers.

Can an employee drop other children when they divorce?

No. That fails the consistency rule.

How Praisidio fits

Praisidio connects payroll, HRIS and benefits data and runs the invoice-to-enrollment-to-deduction match on a schedule, so the exceptions arrive as a list rather than a discovery. See the reconciliation pillar or book a demo.