Section 125 Mid-Year Election Change Rules:
When Employees Can — and Can't — Change Their Pre-Tax Elections

Section 125 mid-year election change rules are the most common compliance question HR teams field after open enrollment closes. An employee gets married, has a baby, or loses other coverage — and assumes their pre-tax election can be adjusted on the spot. The reality is narrower. Cafeteria plan elections are locked by default, and the IRS only permits changes in a limited set of clearly defined situations. This guide walks through which events qualify, how to apply the consistency rule, and what every employer needs to document to keep the savings intact.

Why Section 125 Elections Are Locked by Default

The pre-tax treatment that makes Section 125 plans valuable comes with one structural condition: the election an employee makes at the start of the plan year is binding for the entire year. This is sometimes called the irrevocability rule, and it's the trade-off Congress wrote into the Internal Revenue Code in exchange for the favorable tax treatment of pre-tax benefits. If employees could simply turn their elections on and off whenever it was convenient, the arrangement would functionally become a tax-free savings account, which is not what the cafeteria plan rules were designed to permit.

Treasury Regulation §1.125-4 is the operative authority on every exception to this default rule. It enumerates the specific categories of events that allow a mid-year change, and it sets a separate consistency requirement that constrains what the change can actually look like. Anything that isn't on that list — a change of heart, a budget squeeze, a different perception of value — is not a permitted basis for changing the election. The plan year runs its course, and the next opportunity to revisit elections is at open enrollment. For employers new to the framework, the complete guide to IRS Section 125 plans walks through how the underlying tax mechanics work.

The Six Categories of Permitted Change Events

Treasury Regulation §1.125-4 groups every permitted mid-year change into a handful of well-defined event categories. An election change is only valid if it maps to one of these and is consistent with what actually happened. The six categories every plan administrator needs to recognize on sight:

• Change in status events — marriage, divorce, legal separation, annulment, birth, adoption, placement for adoption, death of a spouse or dependent, change in employment status (including a spouse's job change), and a dependent ceasing to satisfy eligibility requirements.
• HIPAA special enrollment rights — loss of other group health coverage, acquisition of a new dependent through birth, adoption, or marriage, or eligibility for premium assistance under Medicaid or CHIP.
• Judgments, decrees, and orders — including Qualified Medical Child Support Orders (QMCSOs) that require an employee to provide coverage for a child.
• Medicare or Medicaid entitlement — when the employee, spouse, or dependent becomes entitled to or loses entitlement to coverage under Medicare or Medicaid.
• FMLA leave — employees taking leave under the Family and Medical Leave Act can revoke or change elections under specific FMLA rules.
• Significant cost or coverage changes — material increases or decreases in the cost of coverage, significant curtailment of coverage, or the addition or elimination of a benefit option (this exception does not apply to health FSAs).

The IRS publishes the underlying regulation in full at IRS guidance on cafeteria plan election changes, which administrators should keep on hand as a reference. Every event listed above has additional sub-conditions and timing rules, so the categories function as a starting filter — not a guarantee that any given fact pattern qualifies.

The Consistency Rule — and Why Most Errors Happen Here

Identifying a qualifying event is only the first gate. The bigger source of compliance errors is the consistency requirement: the election change must be consistent with the event that triggered it. An employee whose child is born can add dependent coverage. The same employee cannot use that event to drop dental, switch FSA elections, or add coverage for a non-affected dependent. The rule sounds intuitive in plain language, but in practice it's where most plan administrators slip because the consistency analysis isn't always obvious.

Consider an employee whose spouse loses employer coverage. The consistency rule permits the employee to add the spouse (and any children losing coverage with them) to the cafeteria plan. It does not permit the employee to increase their own coverage tier from "employee + spouse" to "family" if the affected dependents already had coverage from another source. The rule looks at what the event actually changed and limits the election change to that scope. Employers running their own administration without a third-party administrator are especially exposed here — the consistency analysis is rarely captured by a generic enrollment form, and after-the-fact reconstruction during an audit is difficult.

A Worked Example: Three Employees, Three Different Outcomes

Consider a 200-employee company with three mid-year change requests in the same month. Each scenario maps to a different category and a different consistency outcome.

Employee A — Birth of a child. Eligible event under both the change-in-status and HIPAA special enrollment rules. The employee can add the newborn to medical coverage, increase the dependent care FSA to reflect new childcare expenses, and may increase health FSA contributions. Election change is consistent because each adjustment directly responds to the new dependent.

Employee B — Spouse changes jobs and loses dental coverage. Eligible event under change-in-status. The employee can add the spouse to the cafeteria plan's dental option. The employee cannot use the same event to drop their own vision election or change their pre-tax 401(k) deferral, because those changes don't respond to what actually happened. A request to add the spouse to medical (which the spouse still has through their new employer) would also fail the consistency test.

Employee C — Decides the FSA election was too high after looking at year-to-date spending. No qualifying event. The election is locked for the remainder of the plan year. The unspent FSA balance is subject to the plan's use-or-lose rule. For the company, blocking this third request — even when the employee is frustrated — is what protects the pre-tax treatment of the elections everyone else is making. The annual payroll tax savings on a workforce of 200 averages roughly $136,000 at $680 per employee, and that math only holds if the elections actually stay intact for the year. Run your own scenarios in the Benefits TaxShield savings calculator.

The Documentation Every Employer Must Keep

The strength of a mid-year change isn't measured at the moment it's processed — it's measured during an IRS examination or a Department of Labor compliance review two years later. Plans that handle the paperwork correctly survive audits without adjustment; plans that don't typically owe back FICA and have to issue corrected W-2s. The documentation discipline isn't optional. For every permitted mid-year change, employers should retain:

1. A dated, signed election change form from the employee, specifying the event and the requested change.
2. Third-party proof of the qualifying event — marriage certificate, birth certificate, court order, coverage loss notice from another carrier, FMLA leave designation, or equivalent documentation.
3. A consistency analysis documenting how the requested change is consistent with the event. This can be a short administrator note; what matters is that it exists in writing.
4. Confirmation that the request was submitted within the plan's deadline — typically 30 days from the event, or 60 days for HIPAA special enrollment births and adoptions.
5. A payroll record showing the date the new election took effect and the resulting pre-tax deduction amount.

These records should be kept with the plan files for at least seven years. The Department of Labor HIPAA enforcement materials make clear that special enrollment rights are subject to documentation reviews, and the IRS applies similar expectations during cafeteria plan audits.

What Happens When a Wrong Change Slips Through

An impermissible mid-year election change isn't a paperwork problem — it's a tax problem. When the IRS determines that an election change didn't qualify under §1.125-4, the consequence is that the pre-tax treatment of the entire election is disregarded for the year. The employee's contributions become taxable wages. The employer owes the FICA share on those amounts. Form W-2 has to be corrected for the affected year, and depending on when the error is identified, the employee may owe federal income tax that was never withheld.

The scope of the damage depends on how the error is discovered. A single wrongly processed change caught during the plan year can often be reversed cleanly — the original election is reinstated, payroll catches up, and no further action is needed. An error that runs the full year and surfaces during an audit is more expensive because corrections must be made retroactively, sometimes for multiple plan years if the same administrative pattern was repeated. The top Section 125 plan setup mistakes guide covers how these audit exposures compound when basic plan administration breaks down.

How to Make Mid-Year Changes a Non-Event

The employers who handle mid-year election changes without incident have built three habits into how they administer the plan. First, they treat the 30-day request window as a strict deadline rather than a guideline — late requests are denied as a default, with rare exceptions documented in writing. Drift on the deadline is what creates audit exposure, because once a plan starts processing 45-day or 60-day requests as a courtesy, the consistency of plan administration becomes harder to defend.

Second, they require third-party documentation before processing any change, not after. A marriage certificate, a birth certificate, a coverage termination letter from another carrier — whatever the event is, the evidence comes in first and gets attached to the change file. Verbal confirmations from employees, even highly trusted ones, don't survive an audit. Third, they run a quick consistency analysis on every request and write it down. Even a one-line administrator note ("birth of dependent — adding child to medical and DCFSA; consistent") is enough to demonstrate that the question was asked and answered. Plans administered by Benefits TaxShield include automated change-event workflows that capture all three habits by default, which is what keeps the underlying payroll tax savings — and the broader benefits package — operating without disruption.

Section 125 Mid-Year Election Changes — Frequently Asked Questions

Can an employee change their Section 125 election mid-year without a qualifying event?

No. The default rule under IRC §125 is that elections are irrevocable for the entire plan year. The only exceptions are the specific permitted events listed in Treasury Regulation §1.125-4 — change in status, HIPAA special enrollment, judgments and orders, Medicare or Medicaid entitlement, FMLA leave, and certain cost or coverage changes. Without one of those events, the employee must wait until the next open enrollment period to adjust their elections.

How long does an employee have to request a mid-year election change after a qualifying event?

Most Section 125 plans require the employee to request the change within 30 days of the qualifying event, although HIPAA special enrollment rights triggered by birth, adoption, or placement for adoption extend the window to 60 days. The exact deadline must be specified in the plan document. Employers should treat the window as strict — requests received after the deadline generally cannot be honored even if the underlying event was a valid qualifying event.

Does a spouse losing other employer coverage qualify as a permitted election change event?

Yes, under the change-in-status rules in Treasury Regulation §1.125-4(c)(2). When an employee's spouse loses eligibility for coverage under their own employer's plan, the employee may elect or increase pre-tax coverage under their cafeteria plan to add the spouse and any newly uncovered dependents. The election change must be consistent with the event — meaning the employee can add the affected family members but cannot use the event to make unrelated changes to other elections.

Can an employee revoke a Section 125 health FSA election mid-year?

Health FSAs follow more restrictive change rules than other cafeteria plan benefits. The cost-change and coverage-change exceptions in Treasury Regulation §1.125-4(f) do not apply to health FSAs. An employee can change a health FSA election mid-year only for change-in-status events under §1.125-4(c), HIPAA special enrollment, judgments and orders, or Medicare and Medicaid entitlement — and the new election cannot be less than amounts already reimbursed under the plan.

What documentation does an employer need to keep for a mid-year election change?

Employers should retain three items for every mid-year change: a written employee request submitted within the plan's deadline, third-party proof of the qualifying event (marriage certificate, birth certificate, divorce decree, or coverage loss notice), and a record showing the requested election change is consistent with the event. These records should be kept with the plan files for at least seven years and made available during an IRS audit or plan compliance review. See our Section 125 nondiscrimination testing guide for adjacent documentation requirements that apply at the plan-year level.