Employee Navigator first, since that is where most of our brokers and employers already live. The bundle is built to the standard EDI 834 shape, so it maps well beyond EN to other ben admins too. Keel captures the elections and hands off a clean file, your ben admin handles the carrier transmission and payroll from there.

No, and that is deliberate. Keel never transmits to a carrier directly. It captures the elections and produces the ben-admin-ready bundle. Your ben admin remains the system of record and feeds the carriers and payroll downstream. We make the handoff clean, we do not try to replace the rails that already work.

Through Finch, which keeps your census synced from the HRIS you already run. New hires and terminations are detected and reconciled, so Keel always works from a current roster. No one is missing at enrollment, and no one lingers on the file after they leave.

Payroll deductions run downstream of the ben admin, exactly as they do today. Keel hands the validated elections to Employee Navigator, and EN drives the carrier feeds and the payroll deductions from there. Keel does not touch payroll directly, it just makes sure the data EN works from is clean.

Census, including SSNs, the elections employees make, and the disclosures they choose to share in the quiz or with Amanda. All of it handled as encrypted sensitive consumer data. Keel never ingests claims, medications, diagnoses, or biometrics, the scope is deliberately tight.