HR to ERP
Dayforce to AllSolutions integration: Dutch employees from Dayforce in AllSolutions for hours and projects
With an integration between Dayforce and AllSolutions, every employee of the Dutch units in Dayforce automatically reaches AllSolutions, with employee number, department from the primary work assignment, job and start date. A termination recorded in advance in Dayforce appears as an end date in AllSolutions straight away, so hours can be booked up to the last working day.
What the integration does
Organisations that run HR and payroll in Dayforce and Dutch projects and hours in AllSolutions enter every new colleague twice. A transfer that takes effect in Dayforce on the first of the month is only right in AllSolutions when someone remembers, and until then hours go to the wrong department.
- HR records a hire, transfer or termination in Dayforce.
- Every hour KoppelHet asks Dayforce which employees have changed since the previous round.
- Per employee KoppelHet fetches work assignments and employment status, including those that start later.
- KoppelHet creates the employee in AllSolutions or only sends the fields that differ.
What to watch for with Dayforce and AllSolutions
- Dayforce provides a list of employees changed within a period, and then the details per employee. Every hour KoppelHet only requests the changes since the start of the previous round, so AllSolutions does not receive all employees again in every round.
- The XRefCode Dayforce uses to look up an employee in the API is not the same as the employee number. AllSolutions receives the employee number; KoppelHet stores the XRefCode in a free field with its own REST API label, so a change always reaches the same employee.
- Dayforce returns today's state by default. KoppelHet also requests the employment status a month ahead. A termination HR has already recorded therefore reaches AllSolutions straight away as an end date, and the employee can book hours up to and including their last day.
- An employee can have several work assignments in Dayforce, one of which is primary, and a work assignment can be virtual. AllSolutions has one department per employee. KoppelHet takes the department of the primary work assignment and ignores virtual work assignments when choosing the AllSolutions company.
- Dayforce omits a field when it is empty or when the API role may not see it, and also when a parent element has not been enabled. AllSolutions would then not update a missing department, without anyone noticing. KoppelHet checks per round that department, job and status came through.
- AllSolutions customers first set up an integration on their acceptance environment and then move the REST API settings to production with an export and import. KoppelHet tests the translation of Dayforce fields to AllSolutions labels on acceptance, so the same labels work in production.
- AllSolutions advises against logging in again for every action, and heavy calls keep an agent of the environment busy. KoppelHet logs in once per round, first asks Dayforce for the changed employees, and then only sends those employees to AllSolutions.
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 pay data go to AllSolutions?
No. Pay stays in Dayforce. AllSolutions gets what is needed to book hours and projects.
What if a department from Dayforce does not exist in AllSolutions?
AllSolutions then refuses the employee. KoppelHet reports the missing department and tries again once it exists.
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 (https://www.dayforcehcm.com/api/{CompanyName}/V1/Employees). Changed employees through GET Employee XRefCodes with FilterUpdatedStartDate and FilterUpdatedEndDate; details per XRefCode with Expand on WorkAssignments (Position with Department and Job, Location, IsPrimary, IsVirtual, EffectiveStart, EffectiveEnd) and EmploymentStatuses (EmployeeNumber, EmploymentStatus, EffectiveStart), with ContextDateRangeFrom and ContextDateRangeTo. Web Services Field-Level Access for every element and its parent elements.
- AllSolutions through the REST API: POST /api/v1/Login with a signature and then the token, GET on the active view, POST per record with the same checks as the form, PUT with only changed fields. Switching company through login companies (MWZBDR). Free fields with a REST API label; exporting and importing REST API settings through Interfaces (MINTFA) from version 20.0.01.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in AllSolutions | Notes |
|---|---|---|
EmploymentStatuses.EmployeeNumber | Personeelsnummer | |
XRefCode | Vrij veld met REST API-label | Key for fetching in Dayforce |
FirstName, LastName | Naam | |
WorkAssignments.Position.Department (IsPrimary) | Afdeling | Through a table |
WorkAssignments.Position.Job | Functie | |
WorkAssignments.Location | AllSolutions-bedrijf (inlogbedrijf) | Dutch locations only |
HireDate | Datum in dienst | |
EmploymentStatuses (beëindigd, EffectiveStart) | Datum uit dienst |
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