Terminated Employees Still on the Invoice

The most common benefits billing discrepancy is an employee who left the company still appearing on the carrier invoice.

Most guidance treats this as a data problem - report terminations faster and it goes away. That's half right. The other half is a rule most employers don't know, and it changes what you can actually do about it:

Federal law generally prohibits retroactively cancelling coverage.

The rescission rule

A rescission is a cancellation or discontinuance of coverage with retroactive effect. Group health plans and issuers must not rescind coverage unless the individual performed an act or omission constituting fraud, or made an intentional misrepresentation of material fact. Where a rescission is permitted, the plan must give at least 30 days advance written notice to each affected participant.

Three things are carved out of the definition and therefore still allowed:

• A cancellation with only prospective effect
• A cancellation attributable to failure to timely pay required premiums or contributions
• A cancellation initiated by the individual

The regulation contains an example that is precisely this situation. An employer reassigns an employee from full-time to part-time but mistakenly continues coverage. The conclusion: the plan cannot rescind the coverage, because there was no fraud or intentional misrepresentation. It may cancel prospectively.

What that means in practice

An employee terminated in March, discovered in July, still on every invoice since:

• You cannot simply void the coverage back to March
• The person was covered during those months, as far as the plan is concerned
• Termination is prospective
• You likely owe the premium

This is why carriers push back on deep retroactive terminations, and why "just credit it back" isn't always available. The constraint isn't only carrier policy - there's a regulatory floor underneath it.

The exception that matters: cancellation attributable to non-payment of premium is expressly not a rescission. Where an employee stopped paying their share, retroactive termination to the paid-through date may be available. That's a different fact pattern from an administrative miss, and worth distinguishing carefully.

How far back a given carrier will process a retroactive termination is contract practice, not regulation - it varies, and no authoritative source publishes a standard window. Check your contracts rather than assuming a common figure.

When does coverage actually end?

The plan document decides, and both designs are permitted.

The regulations expressly contemplate that a loss of coverage need not occur immediately after the qualifying event, so long as it occurs before the end of the maximum coverage period. That's the basis for the near-universal "coverage runs to the end of the month" design - but it is a plan choice, not a legal default.

Reconciliation has to know which convention your plan uses. Under end-of-month, an employee terminating on the 2nd is legitimately billed for the full month, and treating that as a discrepancy generates a false exception every month.

Why terminations get reported late

• Final pay is processed before the termination reaches benefits
• The termination date in the HR system is the last day worked; the coverage end date is different
• Rehire-eligible or leave-status separations sit in an ambiguous state
• Multi-entity employers route terminations through different paths
• The carrier's cut-off date precedes the pay date

Only the last is a timing artifact. The rest are process gaps.

What to do about it

Reduce the lag. Report terminations to carriers on a defined cadence, not when someone remembers.

Reconcile monthly. A termination missed for one cycle costs one month of premium. Missed until renewal, it costs eleven.

Separate the two dates. Termination date and coverage end date are different fields and should be stored separately. Deriving one from the other is where most errors start.

Track expected credits to receipt. A credit promised is not a credit received. Carry it as an open item until it appears.

Escalate deep retro requests deliberately. Anything beyond a couple of cycles needs a conversation, not a spreadsheet entry - the answer may legitimately be no.

Fix the process when a category dominates. If terminations are most of your monthly exceptions, the offboarding workflow is the fix.

Don't forget the COBRA clock

A termination is a COBRA qualifying event, and the notification clock starts at the qualifying event or the loss of coverage depending on plan design. A termination discovered four months late is also a COBRA notice discovered four months late - with separate and considerably larger consequences than the premium.

Frequently asked questions

Can we back out premium for someone who left months ago?

Often no. Retroactive cancellation of coverage is generally prohibited absent fraud or intentional misrepresentation. Termination is usually prospective, and the premium may be owed.

What if the employee stopped paying their share?

Different situation. Cancellation attributable to failure to timely pay premiums is expressly excluded from the rescission prohibition.

When does coverage end - date of termination or end of month?

Whatever your plan document says. Both are permitted; there's no legal default.

How far back will a carrier process a termination?

Contract-specific. Check your agreements; there's no published standard.

We found six months of billing for a terminated employee. What now?

Terminate prospectively, request the credit, expect it may be limited, and check whether the COBRA notice was also missed - that's the larger exposure.

Is this really the most common discrepancy?

In most reconciliations, yes - because termination is the only event where the employee stops interacting with the system entirely, so nothing else surfaces the error.

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.