ICHRA and Section 125: how to make ICHRA contributions pre-tax.

ICHRA contributions are post-tax by default. That is the detail most employers miss when they launch an Individual Coverage HRA. The employer-funded reimbursement is already tax-free under IRC §106. But when an employee pays any premium above the ICHRA allowance, those dollars come from after-tax wages unless a Section 125 cafeteria plan wraps the election into a salary reduction. Stacking an ICHRA and Section 125 plan converts those employee contributions to pre-tax, captures FICA savings on both sides, and lifts employee take-home pay without changing the ICHRA structure.

If you already run an ICHRA and want to know exactly what the §125 layer returns on your payroll, request the 48-hour written projection→ or call 312-546-1730. Benecor delivers a written, payroll-specific number within 48 hours, at no cost.

What an ICHRA does, and where the tax gap lives

An ICHRA (Individual Coverage Health Reimbursement Arrangement) lets an employer reimburse employees for individual market insurance premiums and other IRC §213(d) qualified medical expenses. The employer sets a monthly reimbursement allowance, often differentiated by employee class. The employee selects and purchases their own individual market plan, submits documentation, and receives reimbursement up to the allowance. The employer-funded portion is excluded from the employee's taxable income under IRC §106.

The tax gap lives in the contribution layer. Most individual market plans cost more than the ICHRA allowance. The employee pays the difference, and without a §125 plan in place, that payment comes from after-tax wages. There is no built-in pre-tax mechanism in the ICHRA structure itself.

To make the numbers concrete: an employee earning $50,000 per year who contributes $200 per month toward an individual plan pays FICA (7.65%) and federal income tax (22% bracket) on every one of those $200. That is approximately $59 per month in avoidable tax, or $708 per year per employee. The employer simultaneously pays 7.65% employer FICA on that same $200, adding another $15.30 per employee per month in unnecessary employer cost. On a 50-person ICHRA group, the employer leaves roughly $9,180 per year in employer FICA alone on the table, before counting the employee tax burden. The fix is the §125 wrap. The complete mechanics of how a cafeteria plan eliminates that FICA exposure are in the §125 cafeteria plan pillar guide→.

How a Section 125 plan converts ICHRA contributions to pre-tax

A Section 125 cafeteria plan authorizes employees to reduce gross wages by the amount of their benefit elections before payroll taxes are calculated, under IRC §125. When layered over an ICHRA, the mechanism is a premium payment plan (POP). The employee signs a salary reduction agreement committing to reduce gross wages by the amount they elect to contribute toward their individual market plan. That election is made before the first payroll of the plan year and is irrevocable absent a qualifying life event under Treas. Reg. §1.125-4.

At each payroll, the system applies the salary reduction before calculating withholding. The reduction flows through three W-2 boxes simultaneously:

• W-2 Box 1 (federal taxable wages): reduced by the full election
• W-2 Box 3 (Social Security wages): reduced by the full election
• W-2 Box 5 (Medicare wages): reduced by the full election

The employee avoids FICA (7.65%) and federal income tax on every dollar of the elected salary reduction. The employer avoids its matching 7.65% employer FICA on the same amount. Both sides save from payroll one.

IRS authority for this structure sits in three places. IRC §125 authorizes the salary reduction mechanism. IRS Notice 2013-54 confirmed that individual market insurance premiums qualify for §125 treatment when paired with an HRA (including an ICHRA). Revenue Ruling 61-146 established that individually purchased insurance policy premiums are an eligible §125 benefit. Together, these three authorities make the ICHRA and Section 125 combination legally sound.

Timing is not flexible. The salary reduction agreement must be executed before the premium payment to which it applies. Retroactive pre-tax treatment does not exist under §125. An employer that runs an ICHRA without §125 for six months and then adds the cafeteria plan captures savings going forward only. The written plan document, adoption agreement, and Summary Plan Description must all be in place before the first pre-tax payroll. The full implementation sequence is in the implementation walkthrough→.

The dollar math on stacking

Three scenarios showing employer FICA recapture and employee take-home lift from adding the §125 layer over an existing ICHRA. All figures use Benecor's administration fee of $35 per enrolled employee per month and employer FICA recapture of $91 to $136 per enrolled employee per month.

Employee take-home lift from the §125 layer averages $70 to $110 per month per enrolled employee. The lift comes from eliminating FICA (7.65%) and reducing federal income tax withholding on the salary reduction. The exact number depends on the employee's bracket and election size. The full fee-versus-recapture breakdown across additional headcount scenarios is in the FICA recapture math on the cost guide→.

ICHRA rules every employer must follow

The ICHRA was created under a 2019 joint final rule from the Departments of Treasury, Labor, and HHS (84 FR 28888). The implementing regulations sit at 26 CFR §54.9802-2. Five rules govern how the ICHRA and §125 interact operationally.

1. Class-based eligibility. The ICHRA allows differentiated allowances by employee class: full-time versus part-time, salaried versus hourly, geographic rating area, employees under a collective bargaining agreement, and others. The §125 plan must mirror this class structure. An employee ineligible for the ICHRA cannot elect a pre-tax salary reduction for ICHRA-related premiums. The plan document must define eligible classes consistently with the ICHRA design or the nondiscrimination tests will fail.

2. ACA affordability for Applicable Large Employers. An ALE (50 or more full-time equivalents) must verify that the ICHRA is affordable each plan year. Affordability is measured against the lowest-cost silver plan in the employee's rating area: the net premium cost to the employee (plan premium minus ICHRA allowance) must not exceed 9.02% of household income under the 2026 rate-of-pay or W-2 safe harbor. Adding a §125 salary reduction does not change the affordability calculation because the test measures the ICHRA allowance, not the post-§125 net cost.

3. The employee opt-out right. An employee offered an affordable ICHRA cannot claim the premium tax credit on the ACA exchange. An employee offered an unaffordable or inadequate ICHRA may opt out and pursue the credit instead. Opted-out employees cannot use the §125 salary reduction for individual plan premiums. The §125 administrator must track opt-out elections separately to prevent impermissible pre-tax treatment.

4. Individual plan enrollment requirement. Only employees actively enrolled in an individual market plan (or Medicare) can receive ICHRA reimbursements. An employee who is uninsured, on COBRA, or on a spouse's group plan generally cannot participate in the ICHRA. The §125 salary reduction for individual market premiums applies only to employees with qualifying individual coverage.

5. Substantiation requirements. ICHRA reimbursements require documentation of the qualifying expense. The §125 plan's premium reduction must be tied to substantiated individual plan costs. The plan document must specify the substantiation process, and records must be retained for at least six years against potential IRS or DOL review. See our compliance posture→ for how Benecor maintains audit-ready substantiation records under this framework.

ICHRA vs QSEHRA: which one stacks with §125 best

Employers researching ICHRA vs QSEHRA are usually asking which HRA structure fits their headcount and which combines more cleanly with a §125 plan. Both stack. The distinction is eligibility and contribution limits.

A QSEHRA (Qualified Small Employer HRA) is available only to employers with fewer than 50 full-time equivalents that do not offer a group health plan. For 2026, contribution limits are $6,350 for self-only coverage and $12,800 for family coverage. An ICHRA has no employer-size restriction and no cap on the reimbursement allowance. An employer that offers a group plan to one employee class can simultaneously offer an ICHRA to another class. That level of class differentiation is not available under a QSEHRA.

For §125 stacking purposes, the ICHRA is the more flexible vehicle. It scales with employer contribution design, allows class-based differentiation, and is not restricted by headcount. The §125 layer operates identically on both HRA types: employee premium contributions above the HRA allowance run through a salary reduction agreement and become pre-tax. The plan document structure, nondiscrimination testing, and W-2 reporting mechanics are the same whether the underlying HRA is an ICHRA or a QSEHRA.

Employers choosing between the two should make that decision on eligibility rules, contribution limits, and group plan strategy. The §125 layer adds value to whichever they choose. The ICHRA and Section 125 combination is the more scalable path for employers above 50 employees or those who want class-based benefit differentiation.

Why most ICHRA administrators don't offer §125

Most ICHRA platforms are reimbursement engines. Their core product is the software infrastructure for collecting individual plan documentation, verifying enrollment, processing reimbursements, and tracking allowance utilization. That is an insurance-technology problem, and they solve it well.

A §125 cafeteria plan requires a different operational stack: written plan documents executed under ERISA, salary reduction agreements for each employee, integration with the specific payroll processor the employer uses, annual nondiscrimination testing (the eligibility, contributions and benefits, and concentration tests under IRC §125(b) and §125(c)), year-end W-2 reconciliation against actual payroll data, and ongoing audit defense capability. These are payroll-adjacent, plan-document-intensive, and legally distinct from the reimbursement function.

Most ICHRA administrators do not build the §125 layer because their product roadmap is focused on the reimbursement platform. Outsourcing the §125 layer to a separate vendor creates a coordination gap at exactly the wrong point: the payroll integration. A misconfigured salary reduction code produces incorrect W-2s and can trigger plan disqualification affecting every participant. For employers also considering S-corp owner eligibility→ questions alongside their ICHRA, that coordination gap matters even more because attribution rule errors compound across both structures.

Benecor builds both. The ICHRA integration and the §125 plan document sit under the same engagement, the same administrator, and the same payroll connection. There is no handoff between two vendors at the payroll boundary.

What proper ICHRA + §125 administration looks like

Eight functions must run in parallel. All eight must be operational before the first pre-tax payroll. Missing any one creates a compliance gap that the IRS can use to recharacterize pre-tax deductions as post-tax, triggering back-tax liability for every enrolled employee.

1. Written §125 plan document. Adopted before the plan year. Covers the plan year dates, eligible benefits, eligible employee classes, the salary reduction mechanism, qualifying life event definitions, and the nondiscrimination commitment.
2. Adoption agreement. Signed by the employer before the plan effective date. Without a signed adoption agreement, the plan has no legal existence regardless of what the payroll system does.
3. Summary Plan Description. Distributed to all participants within 90 days of enrollment. ERISA requires it. Missing this document is a separate ERISA violation independent of the §125 compliance issue.
4. Salary reduction agreements. Executed by each enrolling employee before the first pre-tax payroll of the election period. The agreement must be dated before the premium payment it covers.
5. Payroll integration. The salary reduction is configured in the employer's payroll processor as a pre-tax deduction reducing Box 1, Box 3, and Box 5 wages simultaneously. Any payroll code that reduces only Box 1 without reducing Box 3 and Box 5 produces incorrect FICA calculations and incorrect W-2s.
6. ICHRA opt-out tracking. Employees who opt out of the ICHRA to pursue premium tax credits must be flagged so the §125 administrator can exclude them from the pre-tax salary reduction for individual plan premiums. How this interacts with employee W-2 reporting is covered in the W-2 employee paycheck math→.
7. Annual nondiscrimination testing. The three required §125 tests (the eligibility test, the contributions and benefits test, and the concentration test) are run annually. Failure causes certain benefits to be included in highly compensated or key employee income for the year.
8. Year-end W-2 reconciliation. The §125 administrator reconciles actual payroll data against plan elections and produces the W-2 Box 14 entries, typically labeled "CAF125" or "Section 125." Reconciliation catches any mid-year enrollment changes, qualifying life event adjustments, or payroll coding errors before Forms W-2 are issued.

Common mistakes employers make stacking ICHRA and §125

The ICHRA-plus-§125 combination introduces a predictable set of errors. Six appear with enough frequency to address directly.

1. Running the ICHRA without a §125 wrap and not realizing contributions are post-tax. This is the most common error and the most expensive. Every month the §125 layer is absent, the employer pays unnecessary FICA on every employee contribution and the employee loses take-home pay to avoidable tax. For a 50-person group contributing $200 per month each, the employer loses roughly $9,180 per year in employer FICA alone. The fix is prospective. Past months cannot be corrected retroactively.
2. Treating the §125 addition as retroactive. Pre-tax treatment under §125 is prospective from the plan effective date. An employer that adds the §125 layer in month seven of an ICHRA arrangement captures savings from month seven forward, not from month one. Salary reduction elections must be signed before the payroll cycle in which the premium is paid. No exceptions.
3. Running a pre-tax deduction without a written plan document. A payroll system can be configured to reduce Box 1 wages without a §125 plan document in place. Many employers do exactly this, believing the payroll configuration is sufficient. It is not. The IRS requires a written plan document, an adoption agreement, and an SPD before the first salary reduction runs. Without those documents, the IRS can disallow every pre-tax deduction in the arrangement retroactively, with penalties and interest on each underpayment.
4. Mismatching ICHRA class definitions with §125 eligibility. If the ICHRA covers salaried employees only, the §125 plan's premium reduction component must also cover salaried employees only. Including employee classes in the §125 plan that are ineligible for the ICHRA creates a benefits mismatch that fails nondiscrimination testing and can disqualify the entire plan, affecting all participants.
5. Failing to track ICHRA opt-outs. An employee who opts out of the ICHRA to claim a premium tax credit on the ACA exchange is ineligible for the §125 salary reduction on individual plan premiums. If the administrator does not flag opted-out employees, those employees may receive impermissible pre-tax treatment. That impermissible treatment disqualifies the affected elections and can trigger broader plan review.
6. Assuming the ICHRA platform runs §125 nondiscrimination testing. ICHRA platforms do not perform §125 nondiscrimination testing. The three annual tests are the §125 plan administrator's responsibility. An employer that relies on the ICHRA platform to cover this function ends every year without required documentation, creating IRS audit exposure that increases in severity each year the tests are missed.

ICHRA pros and cons in 2026

The ICHRA is a capable employer benefits vehicle. A complete picture requires acknowledging both sides.

Pros. No cap on the employer reimbursement allowance, unlike the QSEHRA. Class-based design flexibility that a group plan cannot replicate: an employer can offer salaried employees a $600 per month allowance and part-time employees a $200 per month allowance under the same ICHRA, in compliance with §54.9802-2. Employees select individual market plans that fit their network preferences, prescription needs, and family structure rather than accepting a single group plan. Available to employers of any size. When combined with a §125 cafeteria plan, the ICHRA achieves pre-tax treatment for employee contributions that approaches the tax efficiency of a fully administered group plan.

Cons. Employee contributions are post-tax by default without the §125 layer, which is a material disadvantage that most ICHRA implementations leave unaddressed. Individual market plan selection falls entirely on the employee. Workers unfamiliar with individual market plan types (HMO, PPO, EPO, HDHP) sometimes make suboptimal choices that surface as claims disputes or network surprises. ACA affordability compliance is required annually for ALEs and requires rating-area and household-income data that can be difficult to obtain. An employee enrolled in an affordable ICHRA loses premium tax credit eligibility on the exchange for that plan year. And running both an ICHRA and a §125 plan adds administrative touchpoints compared to a simple group health plan.

In 2026, the ICHRA has clear advantages for employers who want to exit the group plan market or offer class-differentiated benefits. The §125 wrap converts the largest structural disadvantage (post-tax employee contributions) into a non-issue, which makes the ICHRA and Section 125 combination the most tax-efficient version of the individual market strategy available to employers.

How Benecor runs both layers

Benecor administers the §125 cafeteria plan and the integration layer that connects the ICHRA reimbursement structure to the salary reduction mechanism. The fee is $35 per enrolled employee per month. No setup fee. No long-term contract. Employers receive a written, payroll-specific projection within 48 hours of submitting two months of de-identified payroll data. Implementation takes six weeks from signed engagement to first pre-tax payroll.

The single-engagement model matters operationally. The §125 plan document is drafted in week two. Payroll integration is configured in weeks three and four against the employer's specific payroll processor. Employee enrollment and education run in week five. The plan goes live on the next payroll cycle in week six. The employer manages one vendor relationship across the payroll boundary, which is where multi-vendor ICHRA-plus-§125 arrangements typically break down.

Brokers placing ICHRA clients can add the §125 layer as a separate engagement and capture the override on the §125 administration. The broker partner program→ provides the engagement checklist, sample savings projections, and plan documentation for broker-initiated §125 additions to existing ICHRA placements. Three buyer types typically come through broker placements: employers evaluating an ICHRA before launch, employers already running an ICHRA who do not know contributions are post-tax, and brokers who want to upgrade existing ICHRA placements with the §125 layer.