Let payroll keep eligibility fields up to date
Pair the classifications your payroll partner already tracks — employment type, department, location — with the Employee Navigator fields that drive benefit eligibility. Once mapped, changes flow in on their own: applied automatically for new hires, and queued for your review for existing employees.
Three moves, then it runs itself
Pull in your codes
Turn the feature on and refresh vendor codes. We fetch every cost center value your payroll partner has.
Map, skip or block
For each value, choose the EN field it feeds — or skip it, or block those employees from the integration entirely.
Review what changes
Partners don't send effective dates, so changes for existing employees wait on your homepage until you confirm the date.
What are cost centers?
Payroll's way of classifying employees. HR uses them for pay and reporting, but the same classifications usually decide who's eligible for benefits in Employee Navigator.
Fields each partner sends Payroll → EN
Any field below can map to Business Unit, Class, Department, Division, Employment Type, Job Classification or Office in EN. Employment Type is the one that most often drives eligibility — map it first. If your partner isn't listed, it doesn't support this yet.
Enable, pull, map
Four short steps. Each one below is a live walkthrough — click through it the way you would in production.
Open Cost Center Mappings
Payroll tab → your subscriptionFrom the Payroll dashboard, click your subscription card, then Cost Center Mappings.
›
Turn the feature on
Off by defaultFlip the toggle from Disabled to Enabled, then click Vendor Codes.
Pull in your payroll codes
Vendor Codes → Refresh CodesRefresh Codes asks your payroll partner for every cost center value it has and makes them available to map. Run it again any time a client adds a new value in payroll.
Click the "Refresh Codes" button to get an up-to-date list from your Payroll platform.
No codes loaded yet.
Click Refresh Codes above.
Map each value
Edit → Enable → Map / Skip / Block → SaveOpen a payroll field with Edit, enable it, then decide each value: pick the EN value it maps to, skip it, or block it.
Skip vs. Block
Mapping is the default. These are the two ways to say "not this one."
Ignore the value, keep the employee
EN keeps processing everything else for these employees — demographics, deductions, new hires — and just ignores this one field value when it arrives.
Keep the employee out entirely
Anyone assigned this value in payroll is rejected by the integration: no changes processed, no new hires created, nothing received.
Reviewing ongoing changes
Changes to mapped fields keep flowing in. New hires and empty fields are filled automatically. When an existing value differs from what payroll sent, it waits on the company homepage under Approve pending profile changes until someone confirms the effective date.
| Employee | Requested On | Changes | |
|---|---|---|---|
| Johnson, Sarah | Today | 1 | Review › |
| Abrams, Alex | 12/23/2025 | 2 | Review › |
| Ace, Carl | 03/11/2026 | 1 | Review › |
NOTE: If the requested change will affect benefit eligibility, you'll be automatically prompted to walk through the necessary benefit changes for the employee.
| Field | Current Value | Requested Value | Note |
|---|---|---|---|
| Employment Type | Full-Time |
Everything is logged
Company Homepage→Company Timeline
Employee profile→Timeline
Both the request and the approval appear, with old and new values — e.g. Employee Structure Changed (Business Unit changed from [] to Headquarters, effective 4/1/2025).
Comments
0 comments
Article is closed for comments.