New Hires and Eligibility

Terminations are the most common reconciliation problem. New hires and eligibility are the hardest - because eligibility isn't a stored value, it's a calculation, and the inputs come from four different places.

An employee is eligible when a waiting period has elapsed, they belong to an eligible class, they meet an hours threshold, and they haven't triggered a rule that resets any of it. Change any input and the answer changes retroactively.

Why this is harder than terminations

A termination is a single event on a single date. Eligibility is a derived state depending on:

Input	Where it lives	How it goes wrong
Hire date	HR	Rehires, acquisitions, transfers between entities
Waiting period	Plan document	Different by class; measured from hire, from first of month following, or from a fixed date
Employee class	HR, sometimes payroll	Full-time, part-time, seasonal, union, location-based - and classes change
Hours worked	Timekeeping or payroll	Variable-hour employees; the threshold is measured over a period, not a moment
Election	Enrollment system	Made, not made, or made late
Effective date	Derived	The output of all of the above

Six inputs, four systems, one derived answer - recalculated every time any input changes.

Where new hire reconciliation fails

The enrollment never reached the carrier. The employee elected, payroll started deducting, and the carrier was never told. Nothing surfaces this until a claim is denied.

Deduction started before coverage. Payroll picks up the election on the next available cycle; coverage starts on the plan's effective date. If the deduction runs first, you are withholding for coverage that doesn't exist yet.

Coverage started before the deduction. The reverse - the employer silently absorbs the employee share, sometimes for months.

The effective date was calculated differently in two systems. "First of the month following 30 days" is unambiguous in the plan document and interpreted three different ways in practice. Payroll computes one date, the enrollment system another, the carrier a third.

The waiting period restarted on a rehire when it shouldn't have - or didn't when it should. Rehire rules are plan-specific and rarely encoded anywhere but the plan document.

A class change moved someone into or out of eligibility and nobody noticed. Part-time to full-time is an eligibility event. It usually arrives as a payroll change.

Variable-hour employees crossed the threshold during a measurement period. That's a calculation over time against timekeeping data, and it isn't visible in any single record.

Why this becomes unmanageable in a spreadsheet

New hire reconciliation is the point where spreadsheets stop scaling, and the reason is specific.

Eligibility is recalculated, not looked up. A spreadsheet stores an answer. When an input changes - a corrected hire date, a class change, a rehire - the stored answer is silently wrong and nothing flags it.

The comparison is date-range against date-range, not value against value. You aren't asking "does A equal B," you're asking "was this person eligible, enrolled, covered and deducted for every day of this period, and do the boundaries line up." Spreadsheets do that badly.

Corrections are retroactive but the file isn't versioned. Fix a hire date and every downstream date changes - for every prior month, in a file that was already reconciled and signed off.

Each new class or carrier multiplies the rules, and rules encoded as nested formulas become unmaintainable well before they become wrong.

The practical signal: when your reconciliation spreadsheet has a column whose formula nobody can explain, eligibility is why.

Election change windows

Employees change elections mid-year, and each change is a reconciliation event. Two things about the rules are commonly misstated:

A cafeteria plan is not required to permit any mid-year change. The regulation is explicit - elections are irrevocable, and the permitted change events are optional plan design. Your plan document controls, not the general list.

The "30-day window" is not a Section 125 requirement. It doesn't appear as a deadline in the cafeteria plan regulation at all. Where 30 days is legally grounded is as a statutory minimum for HIPAA special enrollment - a plan must allow at least 30 days after loss of other coverage, or after marriage, birth, adoption or placement for adoption. For Medicaid and CHIP events the statutory minimum is 60 days - both for losing that coverage and for becoming eligible for assistance.

For change-in-status events not tied to special enrollment, there is no regulatory window and the plan document sets it. Plans may be more generous than the minimums; they cannot be shorter where a statutory floor applies.

The consistency rule requires the change to correspond with the event. A specific limitation worth knowing: on divorce, or when a dependent becomes ineligible, dropping coverage for other, unaffected dependents fails the consistency test.

Retroactive versus prospective

This matters for billing, and the answer isn't uniform.

Most election changes are prospective only. The regulation is consistent on this - prospective election change, prospective increase or decrease.

The clear exception is birth, adoption, or placement for adoption, where coverage begins on the date of birth or no later than the date of adoption or placement - genuinely retroactive, with retroactive premium and retroactive claims liability.

Marriage and loss of other coverage take effect no later than the first day of the first calendar month after the request is received.

So a late-processed birth enrollment legitimately produces retroactive premium. A late-processed marriage generally does not.

What to do about it

Store the effective date, don't derive it repeatedly. Calculate it once, in one place, and let every system read it.

Reconcile the boundaries, not the balances. For each person: eligibility start, coverage start, first deduction, and the corresponding end dates. Misalignment at a boundary is the error.

Treat class changes as eligibility events with the same rigour as hires and terminations.

Audit new hires at 30, 60 and 90 days. Most new-hire errors are visible within 90 days and invisible thereafter.

Reconcile before the first claim, not after. A new hire who isn't with the carrier finds out at the pharmacy counter.

Frequently asked questions

Why is eligibility harder than termination?

Termination is one date. Eligibility is calculated from a hire date, a waiting period, a class, an hours threshold and an election - and recalculates whenever any of them changes.

Are we required to allow mid-year election changes?

No. Permitted change events are optional plan design. Your plan document controls.

Is there a 30-day rule for election changes?

Not in the cafeteria plan regulation. Thirty days is the statutory minimum for HIPAA special enrollment; 60 days applies to Medicaid and CHIP events. For other status changes the plan sets the window.

Can an election change be retroactive?

Generally no. Birth, adoption and placement for adoption are the clear exception - coverage begins at the date of the event.

An employee moved part-time to full-time. Is that a reconciliation event?

Yes. It's an eligibility event, and it usually arrives as a payroll change rather than a benefits one.

When should we audit new hires?

At 30, 60 and 90 days. Most errors are findable in that window and effectively invisible afterward.

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.