The Post-Claims Gap: Why ICHRA's Biggest Risk Isn't Enrollment — It's What Happens After

The ICHRA market has spent five years solving an enrollment problem.

Platform after platform has built better onboarding flows, slicker plan comparison tools, more intuitive reimbursement dashboards. The question of how to get an employee from "I've never heard of the ACA marketplace" to "I have a plan I understand" has received enormous engineering and product attention.

The question of what happens when that employee files a claim six months later — and it gets denied — has received almost none.

This is the post-claims gap, and it is quietly creating the most significant threat to sustained ICHRA adoption that the market faces. Not regulatory risk. Not subsidy uncertainty. The day-to-day experience of employees who switched from a group plan to an ICHRA, encountered a coverage problem they'd never faced before, and had nobody equipped to help them.

What ICHRA Administrators Actually Do

To understand the gap, it helps to be precise about what ICHRA platforms are built to do.

An ICHRA administrator — whether that's Take Command Health, Remodel Health, PeopleKeep, or any of the growing number of entrants in the space — is fundamentally a reimbursement engine with an enrollment layer on top. Their core job is to:

1. Verify that an employee is enrolled in a qualifying individual health insurance plan
2. Accept documentation of premium payments and eligible medical expenses
3. Process reimbursements up to the allowance amount set by the employer
4. Generate the compliance documentation required under IRS Notice 2019-45 and ACA affordability rules

That's the product. It's a well-defined, valuable product. But notice what it doesn't include: any engagement with the insurance contract itself, with the carrier, or with the claims process that happens between the employee and their individual plan.

When an ICHRA administrator's help center says "contact your insurance carrier for claims questions," they are not being unhelpful. They are accurately describing the limits of their product. The HRA administrator is not a party to the insurance contract. They have no relationship with the carrier. They cannot call on the employee's behalf. They cannot review an Explanation of Benefits. They cannot write an appeal.

Under a traditional group plan, this never surfaced as a problem because HR was the backstop. An employee with a denied claim called HR. HR called the broker. The broker called the carrier rep. Someone with leverage and knowledge resolved the issue. The employee rarely saw the machinery.

Under an ICHRA, the employee is the insurance policyholder. There is no group contract, no broker relationship attached to the plan, and no HR team with a carrier representative to call. The employee is, in the truest sense, on their own.

The Five Claims Problems Employees Encounter

The types of post-enrollment claims issues that surface in ICHRA implementations are predictable. They're not unusual or exotic — they're the normal friction of individual market coverage, experienced by people who've never had to navigate it before.

1. Denied Claims

Claim denials in individual market plans run at rates comparable to group coverage — roughly 17% of in-network claims were denied in the individual market in 2023, per KFF analysis. The denial reasons vary: services deemed not medically necessary, prior authorization requirements not met, coordination of benefits issues, out-of-network providers billing as in-network.

For an employee on a group plan, the broker or HR team typically had established escalation paths for denials. For an employee on an individual ACA plan, the appeal process is entirely self-service. They receive an Explanation of Benefits they may not know how to read, a denial reason that may be in clinical or billing language they don't recognize, and a notice that they have 30 to 180 days to file an internal appeal — depending on the carrier and the state.

Most employees don't appeal. CMS data consistently shows that fewer than 1 in 200 denied claims receives a consumer-initiated appeal, even though appeal success rates for internal reviews run 40–60% in many markets. The gap between the denial rate and the appeal rate is not a function of claim validity — it's a function of navigation capacity. Employees don't know how to appeal, don't believe it will work, or run out of time.

2. Surprise Bills and Balance Billing

The No Surprises Act, effective 2022, closed the most egregious balance billing scenarios — out-of-network emergency services and certain non-emergency care at in-network facilities. But it didn't eliminate the problem. It created a new compliance enforcement burden that falls primarily on the patient.

Employees who receive a balance bill in apparent violation of the No Surprises Act protections are entitled to an independent dispute resolution process — but initiating that process requires knowing it exists, understanding which services are covered, documenting the relevant facts, and filing within the required window.

For an employee on an ICHRA plan who receives a $3,400 bill from an anesthesiologist they never selected and never met, figuring out whether that bill is legitimate, which protections apply, and how to dispute it is not a simple task. It requires insurance literacy that most people don't have and HR backstop that ICHRA removes.

3. Network Adequacy Problems

Individual market networks are sometimes narrower than what employees were used to under their employer's group plan. This creates a specific category of post-enrollment problem: an employee selects a plan during open enrollment, assumes their existing providers are in-network, and discovers at point of care — or worse, after receiving a bill — that the assumption was wrong.

Directory errors are common in individual market networks. Providers listed as accepting a plan may have stopped accepting new patients, may have left the network since the directory was last updated, or may have a different billing entity than the name in the directory. CMS and state regulators have strengthened network adequacy standards, but enforcement is imperfect and directory accuracy lags.

The employee in this situation has a legitimate grievance — the plan's own directory showed their provider as in-network — but the path to resolving it involves filing a carrier complaint, potentially a state insurance department complaint, and navigating a process that typically takes weeks. Without guidance, most employees simply pay the bill.

4. Coverage Gap Discovery

The most insidious category of post-claims problem is one that doesn't surface as a denial at all. It surfaces as an employee discovering, mid-treatment, that the plan they chose during open enrollment doesn't cover what they need.

This happens for predictable reasons. Decision-support tools during ICHRA enrollment are designed to optimize premium cost against deductible levels and network breadth. They are not designed to evaluate whether a specific plan's benefit structure matches an individual employee's clinical needs — ongoing specialty care, specific prescriptions, mental health coverage, or out-of-state coverage for employees who travel.

An employee who selects the lowest-premium silver plan to minimize monthly cost may discover that their rheumatologist is out-of-network, their biologic medication isn't on formulary, or their out-of-state care is excluded. These aren't enrollment errors in the traditional sense. The employee made a rational choice with the information they had. They just didn't have all the information they needed.

5. Reimbursement and EOB Confusion

ICHRA administrators process reimbursements — but they don't explain the Explanation of Benefits. When an employee submits an EOB for reimbursement and the administrator processes it, the employee still has to understand the EOB itself: what the carrier paid, what their cost-share was, whether the provider's billed charge was correct, and whether the ICHRA reimbursement is being applied to the right bucket (premium vs. eligible medical expense).

This sounds administrative and low-stakes. In practice, it generates substantial confusion and, in some cases, real financial harm — employees who don't understand their cost-share structure, who overpay providers before hitting their deductible, or who miss timely filing deadlines because they assumed the ICHRA administrator was also handling the insurance claim.

Why the Market Hasn't Solved This

The post-claims gap has existed since ICHRAs launched in 2020. The market hasn't addressed it for three structural reasons.

The incentive structure doesn't reach it. ICHRA administrators are paid per employee per month for reimbursement administration. Their sales cycle is with the employer, not the employee. Their success metric is plan sponsor retention, which is driven primarily by employer satisfaction with the setup process, compliance documentation, and employer-facing reporting. Employee satisfaction with post-claims experience is a downstream variable that affects employer renewal decisions only indirectly and with significant lag.

The problem is distributed. Unlike an enrollment failure — which surfaces immediately and affects everyone — post-claims problems surface one employee at a time, weeks or months after the ICHRA launches. There's no aggregate event to trigger a product response. The HR leader who hears about three denied claims in Q2 is unlikely to connect that to a systemic gap in their benefits structure.

The expertise required is different. ICHRA administrators have deep expertise in HRA compliance, ACA affordability rules, and reimbursement processing. Post-claims advocacy requires expertise in health insurance contracts, carrier-specific claims procedures, state insurance regulations, and appeals processes. These are different skill sets, and building them would require ICHRA platforms to expand substantially outside their core product surface.

The result is a gap that's structurally predictable, widely experienced, and essentially unaddressed by the market.

The Cost of the Gap

The post-claims gap has a direct cost to ICHRA adoption.

HR Brew's reporting on employer ICHRA implementations is consistent with what the adoption data shows: the employers who have the hardest ICHRA transitions are not the ones who chose the wrong allowance level or picked the wrong administrator. They're the ones whose employees had bad claims experiences and blamed the ICHRA model for problems that were actually carrier-level issues.

When an employee spends three months fighting a denied claim with no support, they don't think "my carrier's prior authorization process is opaque." They think "this ICHRA thing doesn't work." When that employee talks to their colleagues — and they will — the sentiment spreads. The HR leader hears that benefits have gotten worse. The CFO sees turnover that HR attributes, in part, to the benefits transition. The employer cancels the ICHRA at the next renewal.

The claim that ICHRA transitions have higher administrative burden than group plans is partially true and widely cited. What's less examined is how much of that administrative burden is post-claims support that HR teams are providing informally, without tools, without training, and without any recognition that it's a distinct function that requires dedicated capacity.

BrightView Health's HR business partner told HR Brew that she could no longer handle both payroll and benefits simultaneously after the ICHRA transition. The volume of employee questions about their plans was too high. That's not an enrollment problem. Enrollment was a one-time event. The ongoing question volume is post-claims: employees trying to understand their EOBs, navigate denials, and figure out whether a bill is correct.

What Employers Can Do Now

The post-claims gap is a known problem with improvable, if imperfect, solutions available today.

Designate a post-claims contact. Even if it's an existing HR team member, explicitly designating a person whose job includes helping employees navigate post-claims issues changes the employee experience materially. The barrier most employees face isn't the complexity of the appeal — it's not knowing who to ask or whether asking is appropriate.

Brief your ICHRA administrator on escalation. Most ICHRA administrators cannot advocate on the employee's behalf with the carrier, but they can provide documentation of the ICHRA structure that may be relevant to a coverage dispute, clarify the reimbursement implications of different resolution paths, and in some cases flag issues that affect multiple employees for HR's attention. Build that communication path explicitly.

Invest in a benefits advisor with individual market experience. The broker who placed your group plan for 15 years may not have deep experience with individual ACA plans, denial appeals, or the No Surprises Act dispute process. Finding an advisor with that specific expertise — and making them available to employees who have claims issues, not just to leadership during renewal — is the highest-leverage intervention most mid-market employers can make.

Set expectations proactively. The employers who manage ICHRA transitions best are the ones who told employees, before the first renewal, that the individual market works differently from a group plan — that there will be a learning curve, that claims questions are normal, and that support is available. The surprise is often the problem. Employees who know what to expect from the individual market handle its friction better than those who assumed it would work like their old group plan.

Track post-claims issues systematically. Most employers running ICHRAs have no aggregate data on their employees' claims experience. They know about the issues that employees escalate loudly; they don't know about the ones employees absorbed quietly or gave up on. Building even a simple tracking mechanism — a shared inbox, a Slack channel, a monthly HR check-in — creates the data needed to identify systemic problems before they drive turnover.

What's Coming

The market will eventually produce a purpose-built post-claims support layer for ICHRA-covered employees. The economics support it: the problem is widespread, the current solutions are inadequate, and the willingness of employers and employees to pay for resolution support is well-documented in adjacent markets (patient advocacy, medical billing audit, surprise bill negotiation).

What that looks like in practice will vary. Some versions will be employer-purchased services — a per-employee-per-month add-on to the ICHRA stack that provides dedicated advocacy support. Some will be consumer-direct tools that employees use independently. Some will be embedded in the ICHRA administrator's product as the platforms expand their post-enrollment surface.

The common elements will be claim dispute navigation specific to the employee's carrier and state, appeal template generation calibrated to the denial reason code, coverage gap identification based on the employee's plan and care patterns, and employer-level reporting that aggregates claims experience into actionable benefits intelligence.

The post-claims gap is a solvable problem. It requires the same clarity of purpose that the enrollment layer received — product investment, design attention, and a clear articulation of what success looks like for the employee, not just the plan sponsor.

Until that layer exists at scale, employers running ICHRAs are on their own. The guidance above helps. It's not a substitute for infrastructure that doesn't exist yet.