The Operational Stack Behind a Successful ICHRA Program
What the full operational stack actually requires: quoting and plan design tools, enrollment experience, reimbursement substantiation, affordability monitoring, compliance reporting (1095-C/B, PCORI), and ongoing member support. Maps capabilities to the TPA/GA decision of what to own vs. outsource.
OPERATING & SCALING ICHRA
The Operational Stack Behind a Successful ICHRA Program
ICHRA looks simple from the outside — employer sets a contribution, employee buys a plan. What makes it work in practice is considerably more involved.
The defined contribution model shifts administrative complexity from the employer to the infrastructure layer. The employer no longer selects plans or manages a carrier relationship. But someone has to handle quoting, enrollment, substantiation, affordability monitoring, compliance reporting, and member support — and that work doesn't disappear just because the benefit structure changed.
For TPAs and GAs operating ICHRA programs, understanding the operational stack is the starting point for honest program design. Every capability gap in the stack is a potential failure point: an employee who can't find a plan, a reimbursement that takes six weeks, an affordability error that creates ACA penalty exposure, or a 1095-C that gets generated incorrectly.
Layer 1: Quoting and Plan Design
Before an employer can set a contribution, they need to know what coverage actually costs in each geography where their employees live and work. ICHRA contribution strategy is meaningless without real premium data — the lowest-cost silver plan (LCS) for an employee's age and zip code is the benchmark for affordability calculations, and it varies significantly across markets.
A functional quoting capability pulls live carrier data, presents plan options by geography, and allows the TPA or GA to model contribution amounts against actual market conditions. Without this, employers are setting contributions blindly — and often setting them incorrectly.
Layer 2: Employee Enrollment Experience
The enrollment experience is where most ICHRA programs succeed or fail in the eyes of employees. An employee who receives a letter explaining their ICHRA allowance but has no guidance on how to actually find and enroll in a plan is not going to have a good outcome — regardless of how well-designed the contribution strategy is.
A complete enrollment capability includes:
- A plan shopping interface that shows real plans for the employee's specific zip code, household, and coverage needs — not a generic plan comparison.
- Decision support tools that help employees understand cost-sharing, network considerations, and how their ICHRA allowance interacts with plan premiums.
- A clear enrollment pathway — so the employee doesn't have to navigate multiple systems.
- Confirmation of qualifying coverage, which triggers the reimbursement relationship.
Layer 3: Reimbursement and Substantiation
Once an employee is enrolled in a qualifying plan, the reimbursement cycle begins. The employee submits documentation — typically a premium invoice or proof of payment — and the TPA verifies the coverage is qualifying and issues reimbursement up to the monthly allowance.
This sounds straightforward. At scale, it is a significant operational workflow. Common failure points include: employees submitting documentation for non-qualifying plans, coverage gaps mid-year that require pro-rated reimbursements, premium payment timing mismatches, and the mechanics of actually disbursing funds — which requires a payment rail, typically virtual cards or ACH.
The substantiation requirement also has compliance teeth. The IRS requires that ICHRA reimbursements be substantiated before payment — meaning the TPA cannot simply accept an employee's attestation. Actual documentation must be reviewed.
Layer 4: Affordability Monitoring
For employers subject to the ACA employer mandate (generally 50+ FTEs), ICHRA must be affordable for each employee in each coverage month. Affordability is calculated using the employee's monthly LCSP premium for their rating area, the applicable federal poverty line percentage for the year, and the employee's W-2 wages or rate of pay.
This is not a one-time calculation at plan design. It requires ongoing monitoring because the LCSP can change during the plan year if a carrier exits the market, and wages change as employees receive raises or change hours. An affordability failure — even for a single employee in a single month — creates potential penalty exposure for the employer.
Automated affordability monitoring is one of the clearest differentiators between a functional ICHRA program and a compliance risk.
Layer 5: Compliance Reporting and Plan Administration
The compliance tail on ICHRA is longer than most TPAs anticipate when they first enter the market:
- 1095-C and 1095-B reporting — ALEs must report ICHRA offers, employee enrollment status, and affordability determinations for every covered employee, every month of the year.
- PCORI fees — ICHRA sponsors are subject to the PCORI fee, calculated on a per-covered-life basis and filed annually.
- Plan document maintenance — ICHRA must have a written plan document, and that document needs to reflect the program's actual design accurately.
- COBRA interaction — ICHRA is subject to COBRA continuation requirements; employees who lose ICHRA eligibility due to a qualifying event have COBRA rights, which creates an administrative obligation.
What This Means for TPAs and GAs
The operational stack described above is the minimum viable capability set for running ICHRA programs with compliance integrity and a good employee experience. Organizations that approach ICHRA as a simple add-on to their existing group benefits administration will encounter the gaps quickly — usually in the form of employee complaints, reimbursement delays, or compliance errors at reporting time.
The practical implication is that ICHRA program quality is almost entirely determined by infrastructure quality. An employer with a well-designed contribution strategy and a well-communicated benefit can still have a failed program if the enrollment experience is poor or reimbursements take weeks. The stack has to work end-to-end.
- Every gap in the operational stack is visible to someone — usually the employee who can't get reimbursed, or the employer who receives a penalty notice. The TPAs and GAs running successful ICHRA programs at scale are the ones who mapped the full stack before they started and made deliberate decisions about which pieces to build, which to source, and how they connect.
Kyndly provides an enablement layer for TPAs and GAs operating ICHRA programs — the tools, integrations, and operational infrastructure to run defined contribution health benefits at scale.