Let me tell you a story. A few years back, I was sitting with a benefits director who had just rolled out a brand new ICHRA, an individual coverage HRA that reimburses individual-market premiums and other qualified medical expenses. She was proud of the plan design: smart allowances, solid compliance checks, the works. But six months in, her employees were frustrated. They had to upload receipts for every single expense. The system didn't talk to their insurance carrier. No one knew how much allowance was left until after a claim was submitted. She asked me: "Why does this feel like a part-time job for my people?"
That's the moment I realized most HRAs are failing at something that has almost nothing to do with plan documents or compliance. It's about integration. The kind of behind-the-scenes data flow that makes or breaks a consumer-driven health strategy. And frankly, most employers are ignoring it.
Three places where HRAs break down
When I look at an HRA program, I don't start with the tax rules. I start with the data connections, and I keep finding the same three fault lines.
1. Claims-first reimbursement vs. real-time eligibility
Most HRAs work in a reactive loop: member gets care, gets an EOB, uploads it, then waits for reimbursement. That's slow. More importantly, it means members are flying blind. They don't know if a service is covered under their HRA allowance until after they've already paid out of pocket.
The better approach is real-time eligibility. The HIPAA 270/271 transaction already lets a system ask a carrier whether a member is covered and what the cost share will be, in seconds. Combined with the HRA's allowance balance, that would let a member see what's left before they schedule a procedure, and even get pointed toward in-network providers. It takes an API link between the HRA platform, the carrier, and the provider's scheduling system, and most vendors aren't there yet.
2. The payroll-to-substantiation gap
A common scenario: an employer contributes $100 per month to each employee's HRA through payroll. The contribution lands in the account. Then the employee visits the dentist, pays $200, and uploads the receipt by hand. An administrator reviews it to confirm the expense qualifies. Slow, error-prone, and annoying for everyone.
The HRA platform should pull substantiated claims straight from the carrier's records through a FHIR-based API, using the CARIN Blue Button standard that exposes claims and EOB data. The member gets reimbursed automatically, with no manual uploads and no back-and-forth. Many carriers still rely on batch EDI files (HIPAA 835), so true real-time substantiation stays rare, especially for self-funded plans.
3. Wellness data that goes nowhere
Everyone talks about using HRAs to encourage healthy behaviors. But how often does your HRA platform talk to your wellness vendor? Almost never. The instinct is to tie the data to the allowance itself: finish a screening, earn a bigger contribution next quarter. For an ICHRA, that's off the table. Within a class, the contribution can vary only by age and family size, so a wellness-adjusted allowance isn't permitted under the same-terms rule. The integration that matters is quieter: feeding screening results into care navigation, flagging gaps in preventive care, and supporting a separate wellness incentive program that doesn't touch the HRA allowance. Without it, that data sits in a vendor portal, and your employees know it.
How to spot a well-integrated HRA platform
Don't get dazzled by a shiny dashboard. Ask these three questions during your next vendor evaluation:
- Can you auto-substantiate expenses using carrier claims data? If they say they use OCR on receipts, that's not integration. Push for FHIR API access.
- Do you support real-time deductible checks? The system should know the member's remaining allowance and deductible status before they incur a cost.
- Can you pull wellness activity data? An ICHRA can't vary its allowance by wellness results, so the data should feed care navigation and any separate incentive program instead. If the answer is manual CSV uploads, you're still in the dark ages.
Why self-funded plans lag on integration
HRA Council data shows ICHRA growth is concentrated among small employers, about two-thirds of whom offered no coverage before adding one, and accelerating among large employers, up 34% from 2024 to 2025. Self-funded employers who already sponsor a group plan are not the natural adopters. They still face the same integration gap, often in sharper form: a self-funded plan run through a TPA on legacy systems usually has weaker data connections than a fully insured plan at UnitedHealthcare, Aetna, or Cigna, all of which run FHIR endpoints under the CMS interoperability rules.
New CMS rules push carriers toward FHIR APIs
The biggest changes are coming from regulators. Under CMS's Interoperability and Prior Authorization final rule, Medicare Advantage, Medicaid, CHIP, and exchange plans faced new requirements starting January 1, 2026, with provider access, payer-to-payer, and prior authorization APIs due by January 1, 2027. Prior authorization decisions now must come back within 72 hours for urgent requests and seven calendar days for standard ones. TEFCA has also moved from proposal to live exchange: the first QHINs were designated in December 2023, and data has been flowing between them since.
For an employer evaluating an HRA, the consequence is concrete. The big regulated carriers are being pushed to expose real-time APIs whether or not your vendor asks for them. The legacy TPA serving a self-funded plan sits outside that mandate, and nothing is forcing it to modernize. The gap between integrated and manual reimbursement keeps growing, and regulation is pushing it wider from the top.
The test is simple. When a vendor says it integrates with carriers, ask which APIs, which standards, and which carriers, in writing. If the answer is a batch file feed and a portal, the vendor is already behind where regulated payers now have to be.
Trace one claim to find your gaps
An HRA that doesn't talk to your carrier, your payroll, and your wellness vendor is a reimbursement ledger with a compliance sticker. If you want your employees to use the HRA and feel good about it, look past the plan design and into the data plumbing.
Start by tracing one claim through your current system. Count every manual step. Those steps are your integration gaps, and they cost you time, trust, and money.