DyLeave, absence and time
Dayforce to Dyflexis integration: work assignments and weekly hours automatically in scheduling
With an integration between Dayforce and Dyflexis, employees of the sites that schedule in Dyflexis come from Dayforce into scheduling automatically, with a contract per work assignment, the site from the location and the normal weekly hours. Hires and terminations that HR enters ahead of time in Dayforce are in Dyflexis on time.
What the integration does
Organisations that run HR in Dayforce and have their Dutch or Belgian sites schedule in Dyflexis enter every new employee again in Dyflexis. A termination fixed in Dayforce weeks ago often only reaches scheduling after the last working day.
- HR enters a hire or change in Dayforce, also with a later effective date.
- KoppelHet requests the changed employees for the organisation units that schedule in Dyflexis.
- For each work assignment a contract arrives in Dyflexis, with site, contract type and weekly hours.
- An administrator links a new employee once to a Dyflexis employee.
- On termination the contract closes on the end date from Dayforce.
What to watch for with Dayforce and Dyflexis
- Dayforce records normal weekly hours on the employment status, not on the work assignment. An employee with two work assignments therefore has one number of hours. KoppelHet puts the hours on the contract of the primary assignment; the second contract gets its hours from an agreement per site.
- An employment status in Dayforce has a pay type, hourly or salaried, and a class such as full or part time. Dyflexis contract types determine whether someone has fixed hours or is on call. KoppelHet translates that combination, so an on-call worker does not enter scheduling with a fixed weekly roster.
- Dayforce returns data as it applies today by default. With a date range the API also returns future records. KoppelHet requests them, so a transfer from next month is already in Dyflexis as a new contract with that start date.
- Hires and terminations are often in Dayforce weeks ahead. KoppelHet searches separately on hire and termination date, not only on change date, so a termination closes the contract in Dyflexis on time and no shifts are planned after the last day.
- Dayforce only returns a field if it has a value and the API user's role has rights to it. If location or weekly hours are missing, KoppelHet sends no half contract to Dyflexis but an alert to HR.
- A work assignment in Dayforce also has an FTE. Dyflexis asks for the average number of days per week next to hours. KoppelHet derives the days from a table per site and contract type, because the FTE only gives the size and not how many days it is spread over.
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
Do the hours from Dyflexis go back to Dayforce?
Not in this integration. Hours for Dutch payroll are a separate flow that can be added later as an extension.
Does the wage go to Dyflexis?
Not by default. Labour cost in scheduling with hourly rates from Dayforce can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the RESTful Web Services (https://www.dayforcehcm.com/api/{CompanyName}/V1/Employees) with filterUpdatedStartDate and filterUpdatedEndDate, filterHireStartDate, filterTerminationStartDate and orgUnitXRefCode. Details per XRefCode with Expand=EmploymentStatuses,WorkAssignments (NormalWeeklyHours, PayType, PayClass, Location, IsPrimary, FTE, EffectiveStart, EffectiveEnd) and ContextDateRangeFrom and ContextDateRangeTo. Role feature RESTful Services > Employee required.
- To Dyflexis through POST /api2/external-employees/{employeeReference} and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, start, end, hours, days); upserts with scope external_employees.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Dyflexis | Notes |
|---|---|---|
XRefCode | employeeReference en personnelNumber | |
FirstName en LastName | firstName, lastNamePrefix, lastName | |
WorkAssignments.Position.XRefCode en EffectiveStart | contractReference | |
WorkAssignments.Location | office | Through a translation table |
EmploymentStatuses.NormalWeeklyHours | hours | |
PayType en PayClass | type | Hourly or salaried, full or part time |
Werkpatroon of tabel | days | |
Legal entity of org unit | employerReferenceId | |
HireDate en TerminationDate | employmentStart en employmentEnd |
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