Where ICHRA Compliance Breaks Down After Launch

ICHRA compliance problems begin after implementation — when employee eligibility, coverage, allowances, and plan records start changing.

Sep 7, 20267 min read

Most ICHRA programs are in good shape on the day they launch. The classes were defined deliberately, the allowances were modeled, the notices went out on schedule, and every participating employee had qualifying individual coverage in place.

Then the plan year starts.

Someone is hired in April. Someone else moves to a different state in June. A third employee loses individual coverage in September and mentions it to no one. In October the employer raises the allowance for one class, updates the payroll file, and leaves the plan document alone.

Each of these is routine. Together they move the plan as administered away from the plan as designed — and compliance is measured against the second one.

This article is about that gap: where it opens, what it looks like from the employer's side, and what usually causes it. For the underlying requirements themselves — classes, notices, substantiation, documentation — start with the ICHRA Compliance Guide.

Eligibility moves faster than the records behind it

Every eligibility event carries a date, and the date does most of the work. It determines when participation begins, which allowance applies, when the employee notice had to be delivered, and from which month qualifying coverage is required.

New hires are the clearest case. An employee who becomes eligible mid-year must generally receive the ICHRA notice no later than the date participation can begin — a deadline that arrives quietly, employee by employee, rather than once a year with the rest of the open enrollment work. Terminations, waiting periods, and movement between full-time and part-time or salaried and non-salaried status each carry their own effective dates.

The difficulty is rarely the rule. It is that these events arrive through different channels: the HR system, payroll, a broker email thread, a message from a manager. Eleven months later the employer needs to state, for a specific employee in a specific month, when participation started, what allowance applied, whether the notice was delivered, and what substantiation was on file. That answer either exists as a record or it gets reconstructed from memory and inboxes.

Reconstruction is the part that goes badly.

An employee relocates, and the plan design no longer fits

Consider a 30-person employer with employees in three states, offering a flat monthly allowance to a single class. In March, one employee moves from a rating area where the lowest-cost Silver plan for self-only coverage sits comfortably below that allowance to one where it sits well above it.

Several things follow. The employee's existing individual policy generally will not carry over into the new rating area, so a plan change is usually required. The move may create a special enrollment period if the employee satisfies the applicable enrollment requirements, which can mean a new plan, a new premium, and possibly a new carrier — all mid-year.

The effect on affordability depends in part on how the employer determined it in the first place. An applicable large employer using the location safe harbor may rely on the employee's primary site of employment rather than tracking each residential move. Without that safe harbor, a change in residence may change the applicable lowest-cost Silver premium used in the analysis. A move does not retroactively invalidate a determination already made, but it can change the inputs that apply going forward. If the allowance was set close to the affordability line, that matters. You can model the effect on the Affordability Calculator.

The compliance exposure is rarely the move itself. It is that the move often reaches the employer as an address change in payroll, and stops there.

Individual coverage ends, but allowance activity continues

An employee generally must substantiate qualifying individual coverage before participating for a plan year, and again for each month in which an eligible expense is submitted. That second requirement is the one that gets thin over time.

Coverage ends in ways that produce no notification to the employer: nonpayment of premium after a change in the employee's finances, a dependent aging off, a carrier terminating a policy, a move onto a spouse's plan. The employee has little incentive to report any of it promptly, and in some cases does not immediately realize the coverage lapsed.

Once the ICHRA receives notice that qualifying coverage was cancelled or terminated, it cannot approve eligible expenses incurred on or after the effective date of that termination. What the employer owes here is process: reasonable substantiation procedures, a documented response when conflicting information appears, and a way to stop activity once a coverage loss becomes known.

The plan document stops matching the plan being administered

A plan document ages quietly. Nobody reads it until someone asks to see it — an auditor, a carrier, a plaintiff's attorney, or an HR director who inherited the program in year three.

Mid-year changes are where the divergence starts. Allowance amounts get adjusted. A class is added or redefined. The substantiation process changes when the employer switches administrators. Each of these is a legitimate business decision, and a material change may require a formal plan amendment along with participant disclosure through a Summary of Material Modifications or an updated Summary Plan Description within the applicable ERISA deadline.

The document work belongs to the change itself rather than to the next renewal. Once the written terms and the actual administration diverge, the employer has a harder time showing that eligibility and benefits were administered according to the plan.

Class definitions stop matching the workforce

The minimum class size rule is narrower than most summaries suggest, and knowing where it actually applies prevents a lot of unnecessary alarm.

It becomes relevant only when an employer offers an ICHRA to one class and a traditional group health plan to another. It reaches salaried, non-salaried, full-time, part-time, and rating-area classes smaller than a state, plus certain combinations of those — and it applies to the class receiving the ICHRA, not the class receiving group coverage. When it does apply, the minimum is 10 employees for employers under 100, ten percent rounded down for employers between 100 and 200, and 20 employees above that. Critically, the count is taken as of the first day of the plan year. A class that shrinks in July does not create a violation in July.

The more common post-launch problem is a different one. Class definitions are built on a snapshot of the workforce, and the workforce does not hold still. Roles get reclassified between part-time and full-time. A new office opens in a different rating area. A staffing arrangement described as temporary becomes indefinite. The definitions on paper stay where they were, and the population inside them changes underneath.

That drift can create an immediate administration issue when an employee ends up in the wrong class or when the terms of a class are not applied after a status change. Even where the first-day class-size test holds for the current plan year, the changed workforce should be reviewed before renewal so the next plan design starts from accurate classifications. The employee class rules are worth revisiting annually for that reason alone.

An employee switches to Marketplace coverage, and payroll stops working

Employees frequently pay part of a premium themselves when the allowance does not cover the full cost, and many employers arrange for that remainder to be paid on a pre-tax basis through a cafeteria plan. That arrangement is only available for qualifying individual coverage purchased outside the Marketplace. Premiums for Marketplace coverage cannot be paid through cafeteria plan salary reduction.

This is a design decision at launch and a live risk afterward. An employee who changes coverage mid-year through a special enrollment period may land on a Marketplace plan, and the pre-tax payroll arrangement that worked in January is no longer available for that premium in July.

Payroll is usually the last function to hear about a coverage change, if it hears at all.

Opt-out is handled without the tax-credit consequence

Eligible employees must be given the opportunity to opt out of the ICHRA. The mechanics are simple; the consequence is not, and it is routinely explained to employees incorrectly.

If the ICHRA offer is considered affordable, the employee generally cannot receive premium tax credits for Marketplace coverage for the same period. That holds even when the employee opts out and takes no allowance. Employees often assume the opposite — that declining the employer's arrangement restores their eligibility for subsidized Marketplace coverage — and act on that assumption during open enrollment.

Employers should be careful here in both directions. Telling an employee they will qualify for financial assistance, or that they will not, moves the employer into territory that depends on the terms of the ICHRA, the applicable individual-market premium, household circumstances, and federal tax rules. The accurate position is that the offer affects eligibility, and the employee's own situation determines the outcome.

Federal rules require an opportunity to opt out and waive future ICHRA benefits at least annually. On termination of employment, remaining amounts generally must either be forfeited or the participant must be allowed to opt out permanently. Whether any additional mid-year opt-out opportunity exists depends on the terms of the plan — which is worth stating in the notice, before someone tries.

A post-launch compliance review

Most of the failures above share a shape: something changed, and only part of the system found out. A short review at mid-year and again before renewal catches most of it.

  • Which employees became eligible or lost eligibility since launch, and on what dates?

  • Was an ICHRA notice delivered to each newly eligible employee before participation began, and can that delivery be evidenced?

  • For each month with allowance activity, is there substantiation of qualifying coverage on file?

  • Have any employees changed primary residence or work location, and does anyone own that information outside of payroll?

  • Have allowance amounts, eligibility terms, or substantiation procedures changed since the plan document was last executed, and was the required participant disclosure made?

  • Do the current employee classes still describe the current workforce?

  • If a class structure depends on a minimum class size, was the count documented as of the first day of the plan year?

  • Are pre-tax payroll arrangements still limited to employees with coverage purchased outside the Marketplace?

  • Who inside the organization is responsible for legal, tax, and fiduciary decisions about the plan?

How Lirvion supports ongoing administration

Lirvion brings the operational details of ICHRA administration into one structured platform. Employee eligibility and effective dates, allowance amounts by class and month, coverage verification records, enrollment activity, and administrative history are organized around each employer program. This gives employers and benefits professionals a clear record of what occurred, when it occurred, and what may require attention.

The platform also helps teams manage events that depend on information received from employees, carriers, or other outside parties. When a coverage change, termination, or employee update is reported, Lirvion makes the event visible, preserves the supporting history, and helps the appropriate parties follow it through resolution. Instead of relying on disconnected emails, spreadsheets, and manual investigation, administrators have a consistent operational record for ongoing oversight.

Lirvion does not provide legal or tax advice. Employers should work with qualified legal, tax, and benefits professionals to determine which requirements apply to their organization and plan.

Compliance is a record, not a launch task

The strongest ICHRA programs are not the ones with the most careful launch. They are the ones where the plan document, the eligibility records, the allowance history, and the coverage verification still agree with each other in month nine.

If you are designing a program now, the sequencing questions come earlier than this — how the mechanics work and how to evaluate a plan design both come before the administration does.

Request a Demo to see how ongoing ICHRA administration is tracked in Lirvion.