Payroll integration
Dayforce to Zenegy integration: Danish hires, addresses and resignations from Dayforce in Zenegy Payroll
An integration between Dayforce and Zenegy creates a new employee of the Danish org unit in Dayforce in Zenegy Payroll, with CPR, address, start date and seniority date, and then passes on address changes and resignations. Danish payroll rules such as ATP and pension are chosen by payroll in Zenegy through a global value set; the integration does not overwrite them.
What the integration does
Organisations that use Dayforce for HR in several countries and run Danish payroll in Zenegy enter Danish starters and leavers in Zenegy by hand. A move or a resignation recorded by HR in Dayforce is therefore regularly missed by payroll in the next run.
- KoppelHet requests new employees of the Danish units in Dayforce through the hire date filter.
- KoppelHet reads CPR, address and dates on the start date and agrees the global value set per job group with payroll.
- The employee is created in Zenegy with the Dayforce employee number.
- Address changes go as JSON Patch; leavers become a resignation with last working day.
- After the run KoppelHet checks whether each resignation was processed.
What to watch for with Dayforce and Zenegy
- Dayforce can filter employees by org unit and by hire date with a start and end. KoppelHet combines the two, so Zenegy only receives new people from the Danish units and no colleagues from other countries.
- Zenegy wants a seniority date next to the start date for every new employee. KoppelHet uses the seniority date from Dayforce when it is filled, so someone moving to Denmark within the group keeps their accrual; otherwise the hire date goes across.
- Dayforce's termination date filter also returns resignations with a future date. KoppelHet registers them in Zenegy straight away with the last working day. Zenegy only processes the resignation in the run covering that day, and KoppelHet then checks whether isProcessed is true.
- KoppelHet finds an address change with the update filter limited to Addresses, with both start and end date because Dayforce otherwise ignores the limit. In Zenegy only that address goes as JSON Patch; sending more fields causes errors in the employee data according to Zenegy.
- Fields tied to a global value set in Zenegy cannot be changed with a PATCH: the profile stays the same and no error comes back. KoppelHet therefore reports a new Dayforce work assignment that needs a different set to payroll instead of patching it.
- Without an employee number Zenegy builds one from the CPR. KoppelHet sends the Dayforce employee number, so payroll sees the same number in both systems and no date of birth ends up in the number.
- An empty CPR from Dayforce is usually a rights issue: fields only come back when the API account's role has the authorisation for personal information. KoppelHet creates no Zenegy employee without a CPR and reports the account.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Does leave from Dayforce also go to Zenegy?
Not in the first version. Zenegy only counts approved absence and one registration per day; a leave flow can be added later as an extension.
Does the integration start the Danish payroll run?
No. Zenegy wants runs to follow the normal payroll rhythm. Payroll starts the run; KoppelHet only checks afterwards.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the REST API on /api/{clientName}/v1/Employees with OrgUnitXRefCode, FilterHireStartDate/EndDate, FilterTerminationStartDate/EndDate and FilterUpdatedStartDate/EndDate with filterUpdatedEntities=Addresses, and per employee expand for Addresses and EmploymentStatuses with contextDate on the start date.
- Zenegy Payroll-DK with OAuth 2.0 authorization code flow and refresh token. Create employee with global value set, change with JSON Patch (op replace), register resignation (dateOfResignation, lastWorkDay) and follow status through employee resignations.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Zenegy | Notes |
|---|---|---|
EmployeeNumber | employeeNumber | Otherwise Zenegy makes a number from the CPR |
National ID (DNK) | CPR-nummer | Required |
FirstName, LastName | naam | |
Addresses (primair) | adres, postcode, plaats | Required |
HireDate | in-diensttredingsdatum | |
Anciënniteitsdatum | anciënniteitsdatum | Otherwise the hire date |
TerminationDate | lastWorkDay en dateOfResignation |
Related
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce
Dayforce → 4PS Construct
Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date