Section 125 Cafeteria Plan Rules and Permitted Election Changes

Section 125 cafeteria plans make pre-tax benefits possible by binding employees to their elections, with exceptions only in narrowly defined cases. To comply, employers must apply both the rules that bind elections and the exceptions when they handle a qualifying event. For a multi-jurisdiction workforce, automated benefits compliance monitoring belongs within a broader operating framework that maintains plan documents, tests nondiscrimination, tracks election windows, and documents permitted changes.

What Section 125 actually does and why the tax treatment depends on its architecture

Section 125 of the Internal Revenue Code is the exception in the law that allows pre-tax benefit elections. Salary reduction contributions under a qualifying plan do not count as wages for federal income tax purposes and are generally free from Social Security, Medicare, and federal unemployment tax. The savings reach both sides of payroll. Employer FICA savings run at 7.65% per dollar deducted, while the plan can also reduce FUTA and state unemployment liability.

That treatment depends on what the plan offers. Qualified benefits include group health coverage, vision and dental plans, health FSAs, dependent care assistance, HSA contributions, adoption assistance, and group-term life insurance. The boundary is consequential. Long-term care insurance, deferred compensation, transportation fringes, and educational assistance cannot be offered through the cafeteria plan. Including a non-qualified benefit can disqualify the entire plan and make all participants’ elections taxable.

The foundational requirements every Section 125 plan must satisfy before any election is valid

A written plan document is a precondition to the tax treatment. It may include benefit plans written in separate documents by referring to them, without copying every provision. A standalone health FSA document can therefore form part of the written structure. Without that structure, payroll deductions alone do not establish a compliant cafeteria plan.

Participation also has a defined employment boundary. Only common law employees may participate on a pre-tax basis. S-Corp owners with more than a 2% stake and independent contractors are ineligible, a particular trap for tech companies with mixed workforces. Contractors receive 1099 income rather than W-2 wages and do not meet the employee definition required for these elections. Allowing them to participate risks invalidating the entire plan.

Nondiscrimination testing checks eligibility, contributions and benefits, and how much of the benefits go to key employees. A failed test makes benefits taxable only for the favored group, and a health safe harbor is available for plans meeting specific coverage criteria. The plan also cannot defer compensation into a future tax year except under narrow exceptions for qualified cash or deferred arrangements. Health FSA and dependent care FSA limits require attention to annual IRS adjustments, including the applicable limits for 2026.

Why elections are irrevocable for the plan year and what that irrevocability actually means operationally

Elections must be made before the plan year begins and before the benefit period starts. Once employees make their elections, they generally must keep them for that plan year unless Treasury Regulation §1.125-4 permits a change. The commitment supports the pre-tax treatment. It prevents an employee from treating a benefit election as an amount that can be revised whenever personal preferences or expected expenses change.

An employee who elected $2,000 into a health FSA in December cannot reduce that election in February because medical expenses proved lower than expected. An employee who turned down medical coverage at open enrollment cannot enroll in June just because they now want coverage. The employer can reopen either election only if the employee has a qualifying event.

New-hire elections have a separate timing rule. An election made within the limited post-hire window may be retroactive to the date of hire only when the plan provides date-of-hire eligibility without a waiting period. A waiting period changes that result. In that case, the new employee can make only a prospective election.

HSA contributions require a distinct administrative approach. Employees may change those elections prospectively at any time without a qualifying event. Applying the general annual lock to HSA contribution changes would therefore misapply the rule.

The consistency rule — the condition that governs every permitted mid-year change

A qualifying event establishes a possible basis for change. The proposed election must correspond with what changed. For accident or health coverage and group-term life insurance, 26 CFR §1.125-4(c)(3) requires the change to be on account of and correspond with a status change affecting eligibility under the employer’s plan. Marriage can thus allow an employee to add a spouse who has become eligible for medical coverage. The regulation’s adoption example also permits family coverage retroactive to the adoption date under special enrollment rights.

The negative cases define the test more sharply. A dependent’s death or loss of eligibility cannot justify canceling coverage for the employee, spouse, or another dependent. Similarly, when a status change gives an individual eligibility under a family member’s plan, cancellation under the employer’s plan must correspond to that individual gaining the other coverage. For administration, the analytical question is whether the requested change matches the affected person and eligibility change.

Change-in-status events: the six categories the IRS recognizes and how each one operates

Legal marital status is the first of six categories recognized by §1.125-4(c)(2). It includes marriage, death of a spouse, divorce, legal separation, and annulment. Marriage can permit adding a spouse and stepchildren or dropping coverage for individuals now covered by the spouse’s plan. The marriage change is prospective under the regulation’s special enrollment example. After divorce, the eligibility rules that apply require the former spouse to be removed from coverage, even if the employee wants to keep that person covered.

Number of dependents covers birth, death, adoption, and placement for adoption. Birth or adoption can permit adding the child to medical, dental, and vision coverage. An FSA increase is not automatic. Some plans permit one when a dependent is added, but that permission depends on the plan. A dependent’s death requires removal and may support a premium adjustment for the reduced coverage tier, while coverage continues for unaffected family members.

Employment status includes commencement or termination of employment, strike or lockout, unpaid leave or return from it, and worksite changes. It extends to the employee, spouse, or dependent. The regulation gives a salaried-to-hourly switch that ends plan eligibility as an example of a qualifying employment change. A change in employment status that does not affect coverage eligibility cannot, by itself, justify a health coverage change under the consistency rule.

Dependent eligibility is a separate category covering attainment of age, changes in student status, or similar circumstances. A dependent who ceases to satisfy eligibility requirements can be removed from coverage. Other family members are not swept into that change. Removing an eligible spouse because a dependent aged out would fail the consistency rule.

Residence covers a move by the employee, spouse, or dependent. A move can support a corresponding coverage election change when it affects eligibility. The address change alone is not enough. A request to cancel unaffected coverage would lack the required connection between the move and the election.

Adoption assistance covers commencement or termination of an adoption proceeding. Its scope is specific to that benefit. Starting or ending a proceeding can support a corresponding adoption assistance election change, but it is not blanket permission to revise unrelated benefits. Across all six categories, the event must be recognized, the requested change must satisfy the consistency rule, and the employee must act within the plan’s election change window.

The other two categories of permitted mid-year changes: cost and coverage changes, and changes triggered by other laws

Significant cost or coverage changes can also allow employees to change their elections. A significant cost decrease may allow an employee to begin participation in the affected option. Minor adjustments do not trigger that same permission. A significant increase may allow revocation and election of another option providing similar coverage, or cancellation if no similar option is available. Significant curtailment or cessation of coverage can also support a change, while adding a benefit package option mid-year may permit employees to elect it.

Other federal laws can also supply a basis for a corresponding election change. Section 1.125-4(b) covers HIPAA special enrollment rights under section 9801(f) and gives examples of marriage and adoption. That provision concerns special enrollment specifically. It does not establish a general category covering every change required or permitted by another law.

The employer’s plan document determines which regulatory permissions it adopts. Section 125 does not require a cafeteria plan to allow every change that the regulation permits. Permission is not a universal employee entitlement. Administration must therefore distinguish between an election change the regulation allows and one the particular cafeteria plan authorizes, while accounting for applicable special enrollment rights.

How mid-year change mismanagement produces compliance failures — and what they cost

One procedural failure is allowing a change for employee convenience without a qualifying event. Another is accepting a genuine event but approving a change that does not correspond with it. A third is processing a request without establishing that it arrived within the plan’s window. These are separate defects, so evidence of a valid event does not cure an unrelated change or a late request.

Documentation creates another point of exposure. Without retained evidence of the qualifying event, the employer cannot demonstrate why the change was permitted. An IRS audit can then retroactively disqualify pre-tax treatment. The consequences include taxable income for affected employees, potential employer payroll tax liability, and possible employee claims over lost tax advantages or incorrect benefit allocations.

In an acquisition, non-compliance with plan documents or nondiscrimination requirements is a discoverable liability. It can reduce deal attractiveness or extend negotiation. For a growing tech company, an unresolved workflow for elections can affect a deal as well as require a payroll correction.

What ongoing Section 125 administration actually requires across the plan year

The operating response is a defined annual, mid-year, and new-hire cadence. Before the plan year begins, the written document must be in place and open enrollment must collect elections. Amendments must be written and operate prospectively. Enrollment forms should explain irrevocability and when changes are allowed, and a vendor or administrator must be assigned to run annual nondiscrimination testing.

Mid-year handling calls for three decisions on each qualifying event request. The administrator should establish whether the event is recognized, whether the proposed change corresponds with it, and whether the request is timely. Documentation should be collected and retained when the change is processed. HSA contribution changes need their separate prospective workflow without a qualifying-event requirement.

New-hire administration runs outside the open enrollment cycle. The employer should track the election window that applies and check whether the plan has date-of-hire eligibility or a waiting period. A 30-day window is an operational variable governed by plan terms. Rapid hiring across multiple states makes those distinctions especially important. For a multi-jurisdiction workforce, employers must track that timing as part of their broader checks on compliance with federal, state, and local rules.

How can benefits infrastructure handle Section 125 administration without adding employer workload?

A PEO absorbs Section 125 administration into its master plan document and shared compliance infrastructure. Plan maintenance, nondiscrimination testing, and annual elections are handled within that arrangement. This is a genuine early-headcount advantage. On leaving a PEO, however, the employer must reconstitute those functions through a standalone plan document, arranged testing, and a mid-year change workflow. Leaving without those elements puts the employer out of compliance right away.

A traditional broker relationship does not necessarily replace that infrastructure. Brokers are typically paid to place coverage rather than administer cafeteria plan documents or qualifying event workflows. That leaves the employer responsible for the work. The relevant comparison is not simply who sources insurance, but who performs the continuing compliance work.

For a post-PEO company, the capability framework is concrete. A benefits partner can maintain the plan document, run annual nondiscrimination testing, administer documented qualifying events, track new-hire election windows, and monitor obligations across jurisdictions without replacing the existing HRIS or payroll infrastructure. Automation has a defined role within that service. With around-the-clock support for employees’ benefits questions, including mid-year inquiries, it helps address election windows that are missed and changes that go undocumented. The useful distinction is between monitoring that leaves the employer to administer every response and infrastructure that also performs the required plan operations.