DyLeave, absence and time
Deel to Dyflexis integration: everyone working in the Netherlands through Deel is automatically in scheduling
With an integration between Deel and Dyflexis, employees of the Dutch entity, and if desired EOR workers in the Netherlands, appear in Dyflexis automatically from Deel, with employer, office and start and end date per employment. A new employment or a last working day in Deel thus also reaches the schedule, without the planner retyping it.
What the integration does
Organisations that hire staff in several countries through Deel and schedule Dutch shift work in Dyflexis keep two lists. Who works through the own entity, who through employer of record and who as a contractor is not visible to the planner in Dyflexis, while it decides where the hours must go later.
- Deel reports a new or changed employment; KoppelHet checks the signature and fetches the person.
- Only the kinds of employment the organisation wants to schedule go through, at a work location linked to a Dyflexis office in the table.
- The person arrives in Dyflexis with the employer attached; every employment becomes its own contract.
- An administrator links the new employee once in Dyflexis; after that Dyflexis follows what Deel supplies.
- A last working day in Deel closes the contract in Dyflexis on that date.
What to watch for with Deel and Dyflexis
- Deel gives every employment a kind, such as employee of an own entity, EOR, PEO or contractor. Per kind we record whether someone belongs in the schedule. An EOR worker in the Netherlands can thus be scheduled, while a freelance designer in another country stays out of Dyflexis.
- Dyflexis can store an employer reference per employee. KoppelHet fills in the legal entity from Deel there, or a fixed value for EOR. When processing worked hours it is then immediately clear whether they go to the own payroll or to Deel.
- Someone can have several employments in Deel, for example first through EOR and then with the own entity. In Dyflexis it stays one employee, with a contract per employment. The planner sees the switch as one contract ends and the next begins.
- The public description of the Deel people list contains no contract hours per week, and Dyflexis asks for them with every contract. The hours therefore come from a custom field in Deel, or scheduling completes them in Dyflexis; we choose the route together at the start.
- Deel stores a preferred name next to the official first name. In the Dyflexis schedule and app KoppelHet uses the preferred name, so colleagues recognise each other; the official name stays in Deel for contract and payslip.
- Deel recommends webhooks as the main route and fetching the list as a supplement. KoppelHet only processes notifications with a valid signature, and also compares the active employments in Deel with the contracts in Dyflexis every day.
- In Deel a last working day sits on the employment, not on the person. KoppelHet therefore only closes the matching contract in Dyflexis. If another employment is still running, the employee remains schedulable.
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 we schedule contractors in Dyflexis too?
You decide that per kind of employment. The integration only passes on the kinds switched on in the table.
Do the worked hours go back to Deel?
Not in this integration. Hours of the own entity belong with Dutch payroll, hours of EOR workers with Deel. That flow 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.
- Deel through GET /rest/v2/people (filter hiring_types, including hris_direct_employee, eor, peo, contractor; paging with offset and limit) with per person id, preferred_first_name, first_name, last_name, work_location, department, job_title, client_legal_entity and employments[] (id, work_email, hiring_type, start_date, termination_last_day, is_ended). Signed webhooks for changes; API token or OAuth2 app.
- To Dyflexis through POST /api2/external-employees/{employeeReference} (lastName required; firstName, email, employerReferenceId, employmentStart, employmentEnd, jobDescription) and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, start, end, hours, days). Scope external_employees, Authorization Token header, backoff on 429.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Dyflexis | Notes |
|---|---|---|
id (Deel-persoon) | employeeReference | Fixed key, also when one employment ends and another begins |
preferred_first_name of first_name | firstName | Preferred name if present |
last_name | lastName | |
employments[].work_email | email | |
client_legal_entity.id of EOR | employerReferenceId | So scheduling sees who the employer is |
employments[].id | contractReference | |
employments[].start_date en termination_last_day | start en end (contract), employmentStart en employmentEnd | |
work_location of department | office | Through a table to Dyflexis offices |
employments[].hiring_type | type (contract) | Through a table to the Dyflexis contract type |
job_title | jobDescription |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions