Benefits

Finch’s Benefits product reads structured benefits enrollment data from an employer’s HCM (human capital management) system: the benefit plans the company offers, each employee’s enrollment in those plans, and the dependents covered under each enrollment.

​

What you can do

• Read the plan catalog — list every benefit plan the employer offers, with plan type, carrier, plan year, and coverage tiers.
• Read enrollment state — see who is enrolled in which plan, at what coverage tier, with effective dates, waiver status, and employee and employer contribution amounts.
• Read covered dependents — read demographic details for the spouses and children covered under an enrollment.
• Read enrollment changes — enrollment records reflect new elections, qualifying life events, and terminations; compare reads to detect changes in your system.

​

Data model: Plans, Enrollments, and Dependents

The Benefits product introduces three objects: Coverage tiers (employee_only, employee_spouse, employee_child, employee_children, employee_family) apply to health plans. Life and disability plans express coverage as a dollar amount or percentage of salary instead, so coverage_tier returns the value as it is represented in the provider system.

​

Benefits endpoints

​

How Benefits differs from Deductions

Finch’s Deductions product is payroll-centric and write-oriented:a deduction is a payroll line item that withholds money from an employee’s paycheck, a contribution is the employer-paid amount that funds the same benefit. The Deductions API creates and manages both. Benefits is benefits-centric and read-only: it returns the canonical plan and enrollment records from the benefits administration side of the employer’s system. The two overlap but are not one-to-one. A fully employer-paid plan produces an enrollment with no employee deduction, and a generic pre-tax deduction code may not map to any benefit plan. Use Benefits when you need authoritative enrollment state — coverage tier, carrier, covered dependents. Use Deductions when you need to see or change what is withheld each pay period.

​

Permissions

Benefits data is scoped as its own Finch product, separate from Organization and Payroll. Plans, enrollments, and dependents each have a distinct scope, and the dependents scope is permissioned separately because dependent records contain sensitive personal information. Benefits uses the same connection you already have for Organization and Payroll data — no separate authentication flow for the employer. To add Benefits scopes to an existing connection, send the employer through re-authentication.

​

Beta providers and limitations

Benefits reads from HCM platforms where the employer manages benefits in the same system as payroll and HR. Employers who administer benefits in a separate, standalone platform are not supported during the beta.

• ADP Workforce Now is the first provider available in the beta. Workday and UKG are coming soon, with additional providers to follow.
• For field availability, check the Field Support matrix.
• Benefits does not return beneficiary designations, evidence-of-insurability status, or enrollment history, so workflows that depend on those need another data source.

​

Common use cases

• Benefits navigation and enrollment — show employees their plans, coverage tiers, and covered dependents, and identify unenrolled employees for enrollment outreach.
• Insurance carriers — confirm an employee was covered on a given date, in a given plan, at a given tier, for group life, disability, and supplemental claims.
• Dependent eligibility verification — confirm a dependent was covered under an enrollment at claim time.
• Post-enrollment reporting — report participation and premium totals per plan from employee and employer contribution amounts.

​

Next steps