The Section 125 Consistency Rule for Mid-Year Election Changes

The Section 125 consistency rule says that a mid-year change to your cafeteria plan elections will only be approved if the change is caused by a qualifying life event and logically matches what that event did to your coverage needs. Having a qualifying event is necessary but not sufficient. The election you request has to be “on account of and correspond with” the event itself, and if it doesn’t, the plan administrator must reject it even when the event clearly happened.¹

That two-part test is where most rejected requests fall apart. Employees focus on whether they had a qualifying event and stop there. Administrators focus on whether the specific change being requested tracks the event. Understanding how they apply the test is the difference between a change that goes through and one that waits until open enrollment.

What “On Account Of and Correspond With” Means

The phrase does real work. It requires two things to be true at the same time: the change is caused by the event, and the change makes sense in light of the event.

For health insurance and group-term life insurance, the regulation is more specific. A change in status is consistent only if the event affects eligibility for coverage under the employer’s plan, meaning it increases or decreases the number of family members who can benefit from that coverage.¹ Marriage adds an eligible person. Divorce removes one. A birth adds one. A child aging out removes one. The election change you request has to move in the same direction as the eligibility shift.

That framing rules out a lot of intuitive-sounding requests. A qualifying event doesn’t unlock the whole benefits menu. It unlocks changes that follow from the event’s specific effect.

Consistent and Inconsistent Changes, Side by Side

Working through actual scenarios is the fastest way to see how administrators apply the rule.

Consistent changes:

You get married and add your new spouse to your health plan. The event created a new eligible person, and the election change directly enrolls that person.
You have a baby and increase your health FSA election. The new dependent will generate medical expenses, so raising the FSA tracks the event.
Your child ages out of coverage and you drop that child from your plan. The event ended one person’s eligibility and the change removes that same person.
Your spouse loses a job that provided family coverage, and you add your spouse and children to your employer’s plan. The loss of other coverage is the triggering event, and the enrollment fills the resulting gap.

Inconsistent changes:

You have a baby and try to drop your own dental coverage. A new dependent doesn’t reduce your need for dental insurance, so the change doesn’t correspond to the event.
Your spouse gets a new job with benefits, and you use that event to change your own life insurance election. Unless the spouse’s new plan specifically affects your life insurance eligibility, there is no connection.
Your child ages out and you cancel coverage for yourself or your remaining dependents. The event only ended one person’s eligibility; the regulation is explicit that you cannot use a loss-of-dependent event to drop coverage for people whose eligibility was not affected.
You divorce and drop coverage for your other children along with the ex-spouse. Same problem: the event removed the spouse’s eligibility, not the children’s.

The pattern is consistent across events. If the event added a person, the change can add that person. If the event removed a person, the change can remove that person. Changes to unrelated benefits, unrelated coverage tiers, or unrelated family members fail the correspondence test.

Cost and Coverage Changes Follow the Same Logic

The regulation also treats significant changes in a plan’s cost or coverage as events that can justify an election change. If your employer or insurer raises premiums substantially, you may switch to a comparable option, or drop coverage entirely if nothing comparable exists.² If a benefit option is significantly curtailed or eliminated, you may move to another option. If a new option becomes available, you may elect it.

The consistency rule still governs. A premium hike on your medical plan lets you adjust that medical election, not your unrelated dependent care FSA. A new PPO option launching mid-year lets you switch into that PPO, not change your life insurance amount.

One limit is worth flagging directly: the cost-change rules do not apply to health flexible spending accounts. If you elected $2,000 in your health FSA at open enrollment and premiums rise mid-year, that FSA election stays put regardless of the cost event.

Dependent Care FSAs Use a Different Correspondence Test

The consistency rule for dependent care benefits asks a different question. Instead of measuring whether the event affects eligibility for employer-plan coverage, the test is whether the event affects your dependent care expenses as defined under Section 129.²

If your spouse starts a new job and your child now needs daycare, the employment-status change corresponds with an increase in dependent care expenses, so starting or increasing dependent care FSA contributions is consistent. If your spouse stops working, the need for paid care usually drops, and reducing or stopping contributions corresponds.

Dependent care FSAs also have their own rule for provider changes. Switching to a new childcare provider at a different cost counts as a coverage change that can support revising your election, as long as the new provider is not a relative. When the provider is a family member, the cost-change rules don’t apply.²

Where the Consistency Rule Doesn’t Apply

A few situations sit outside the framework, and mistaking them for consistency-rule cases wastes time.

HSA Salary-Reduction Changes

Health savings account contributions through a cafeteria plan can be changed prospectively at any time, without a qualifying life event and without a correspondence analysis.³ If your plan permits it (and most do), you can increase, decrease, or stop HSA contributions during the year subject only to the annual limits. The consistency rule simply does not govern HSA elections.

HIPAA Special Enrollment

HIPAA requires group health plans to offer special enrollment when you lose other coverage or gain a new dependent through marriage, birth, adoption, or placement for adoption.⁴ These enrollments happen whether or not the cafeteria plan’s change rules would allow them, and the plan must give you at least 30 days from the event to request enrollment.⁵ Because HIPAA operates independently of Section 125, the consistency analysis takes a back seat when a HIPAA right applies.

Court-Ordered Coverage

A Qualified Medical Child Support Order overrides the normal election framework. If a court or state agency orders you to provide coverage for a child, the plan must comply regardless of open enrollment or the consistency test.⁶

Medicare and Medicaid Entitlement

Gaining Medicare Part A or Part B, or enrolling in Medicaid, is treated as its own category. The plan may let you reduce or cancel that person’s employer coverage prospectively, and losing government coverage may let you add or increase coverage.² The change still has to match the affected person, but the analysis is about duplicate or lost government coverage rather than family status.

Your Plan Document Sets the Ceiling

Even a change that satisfies the consistency rule can still be denied. Section 125 describes changes a cafeteria plan may permit; it does not require plans to allow any of them.² Your employer has discretion over which permitted events its plan actually recognizes, subject only to HIPAA’s mandatory enrollment rights and court orders like QMCSOs.

Some employers adopt every event the regulations recognize. Others limit mid-year changes to only the events HIPAA forces them to accept. Before assuming a consistent change will be approved, check your Summary Plan Description. If the plan document does not authorize a particular type of change, the administrator must deny it even when the IRS regulations would have allowed it. That gap between what the regulations permit and what individual plans adopt is the second most common reason mid-year requests fail, right behind consistency itself.

The underlying reason for both the irrevocability rule and its consistency-based exceptions is the tax break. IRS regulations require the plan’s written document to specify that elections are irrevocable for the plan year.³ Without that restriction, employees could elect benefits only when they foresee expenses and switch back to cash when they don’t. The consistency rule preserves the annual-commitment premise by ensuring every mid-year change is anchored to a real, matching event.

Documenting the Match

The plan administrator has to see the connection between the event and the change on paper. Whatever the event, the documentation needs to show what happened, when, and to whom.

Marriage or divorce: a marriage certificate or final divorce decree showing the date.
New dependent: a birth certificate, hospital documentation, or legal adoption or placement papers.
Loss of other coverage: a letter from the prior insurer showing the termination date and the individuals affected.
Employment change: a letter from the other employer confirming the start or end date, or documentation of a change in hours.
Court order: a copy of the QMCSO identifying the covered individuals and required coverage type.

Then complete your employer’s election change form. It will ask for the event type, the exact date it occurred, and the specific changes you want. Dates matter. If the date on your form doesn’t match the date on your supporting documents, expect the request to be returned for correction, eating into your deadline window. Most plans give 30 or 31 days from the event to request the change, though some allow 60. Submit everything together rather than filing the form first and promising documentation later.

Federal law does not set a universal deadline for every Section 125 change, but HIPAA special enrollment events must allow at least 30 days.⁵ Miss whatever deadline your plan imposes and the change generally waits until the next open enrollment, no matter how well it satisfied the consistency test.

In general, approved changes take effect prospectively. If you get married in March and request to add your spouse in April, coverage typically starts on the first of the month after the plan processes the request, not retroactively to the wedding date.² Birth, adoption, and placement for adoption are the exception; coverage can be effective retroactive to the date of the event, which matters because newborns and newly placed children often need care immediately.⁴

If you keep the consistency test in mind before you submit, most rejections disappear. Identify what the event actually changed about eligibility or expenses, then request the change that tracks it. That is the analysis the administrator will run, and matching your request to it is what gets it approved.

1
eCFR. 26 CFR 1.125-4(c) – Permitted Election Changes
2
eCFR. 26 CFR 1.125-4 – Permitted Election Changes
3
Federal Register. Employee Benefits – Cafeteria Plans
4
eCFR. 29 CFR 2590.701-6 – Special Enrollment Periods
5
Office of the Law Revision Counsel. 26 USC 9801 – Increased Portability Through Limitation on Preexisting Condition Exclusions
6
U.S. Department of Labor. Qualified Medical Child Support Orders