Every feature exists because running the sync in production surfaced the need for it. Here's the short list.
Every client, on a schedule you control. Sync runs land before your team logs in for the day.
Per-client column maps, per-client benefits-platform and payroll credentials, per-client audit trails, fully isolated.
Map payroll columns to benefits-platform fields once per client. Defaults seed from the payroll vendor; you override what's unique.
Snapshot diff per client. Only changed records get imported. Every skipped row carries a reason code.
Your benefits platform's standard import tools driven end-to-end, in the right order, with the right files.
Match benefits enrollments against payroll deductions. Spot missing, mismatched, or stale codes before carriers do.
Anything the bot can't auto-resolve lands in a per-client queue, categorized by severity, acknowledgeable in-app.
Demographic syncs respect protected-class flags. Salary, terminations, and census still flow through normally.
Compare any client's benefits-platform data against payroll on demand. Catch drift before it becomes a coverage problem.
SSNs masked to last 4 in operational data. Full identifiers only land in encrypted attachments behind explicit access gates.
Brand the portal, the emails, and the invoices for your firm. The product can look like yours.
Multiple payroll vendors supported today. New ones slot in behind a clean abstraction — usually a few days of work.
Honesty matters when you're picking a platform you'll run a client book on. EN-Payroll Sync doesn't currently offer:
If any of those are blockers, we'd rather you know now than three months in.
Tell us which payroll vendors your clients use and how many groups you manage. We'll set it up.