ICHRA eligibility management

Last updated: October 31, 2025

ICHRA (Individual Coverage Health Reimbursement Arrangement) has unique complexity for determining eligibility vs the traditional group plan model:

  • ICHRA-specific class definitions: ICHRA allows employers to offer different allowance amounts to different employee classes (full-time, part-time, seasonal, salaried, hourly, etc.), but these classes must meet specific IRS requirements that don't always align with standard HRIS categories.

  • Minimum class size requirements: The IRS mandates minimum class sizes for certain ICHRA classes if offered alongside a group health plan, requiring real-time tracking and validation that payroll systems aren't designed to handle.

  • Dynamic eligibility changes: ICHRA eligibility can change based on factors like coverage effective dates, dependent verification, and insurance plan enrollment status—data that lives outside the payroll system.

  • Regulatory compliance burden: ICHRA providers must ensure compliance with IRS regulations, ACA affordability calculations, and state-specific insurance requirements that require specialized logic.

Because of these factors, ICHRA eligibility cannot simply be "inherited" from the HRIS—it must be actively managed within the ICHRA platform itself. This is where Finch can help support ICHRAs, by providing the necessary data on which to power the eligibility engine.

Why ICHRA Providers Must Own Eligibility Data

The ICHRA provider should maintain the source of truth for eligibility for several critical reasons:

1. Regulatory Compliance and Documentation

The ICHRA provider is ultimately responsible for IRS compliance, including generating Form 1095-C and maintaining documentation for audits. This requires complete control over eligibility determinations, class definitions, and allowance calculations.

2. Insurance Integration Requirements

ICHRA providers must verify that employees have qualifying individual health insurance before reimbursing them. This requires integrating eligibility data with insurance verification systems—a process that must happen within the ICHRA platform.

3. Complex Business Logic

ICHRA eligibility involves nuanced rules around waiting periods, opt-out provisions, dependent eligibility, and allowance proration. This logic is specific to ICHRA administration and doesn't exist in standard payroll systems.

4. Payroll Provider Discrepancies

Not all payrolls or HRIS systems have any pre-existing logic built in to calculate employee eligibility. Ones that do may not have the complexity available to support the nuances of ICHRA requirements, so the ICHRA provider must be the source of truth.

Best Practices: Reference Fields from Payroll/HRIS through Finch

While the ICHRA platform should own eligibility determinations, it should reference key data points from the payroll/HRIS system to keep information synchronized. Here are some commonly used fields:

/individual

  • first_name

  • middle_name

  • last_name

  • emails

  • phone_numbers

  • dob

  • ssn

/employment

  • employment.type

  • employment.subtype

  • start_date

  • end_date

  • latest_rehire_date

  • is_active

  • employment_status

  • income.unit

  • income.amount

Classification Fields within /employment for class assignment/definition

  • title

  • department.name

  • location.state

/pay-statement

  • total_hours

Technical Architecture Considerations

Data Synchronization Strategy

  • Real-time webhooks: For critical updates like terminations and new hires

  • Scheduled batch syncs: For less time-sensitive updates (Finch refreshes data regularly)

  • On-demand refresh: Allow manual triggering of data sync for specific employees

Error Handling - maybe delete tbd

Build robust error handling for common integration issues:

  • Missing required fields in HRIS data

  • Format mismatches (dates, names with special characters)

  • API timeout or connectivity issues

  • Duplicate employee records

Data Security

Implement appropriate security measures when handling HRIS data:

  • Encrypt data in transit and at rest

  • Use OAuth or API keys with appropriate scopes

  • Implement rate limiting and retry logic

  • Follow SOC 2 and HIPAA requirements for PHI/PII

Summary

While ICHRA platforms should reference employee data from payroll/HRIS systems for convenience and accuracy, they must maintain independent control over eligibility determinations. This approach balances operational efficiency with the regulatory and functional requirements unique to ICHRA administration. By establishing clear data flows, robust integrations, and appropriate override mechanisms, ICHRA providers can deliver compliant, user-friendly benefits administration while maintaining the flexibility needed for complex eligibility scenarios.