ShLeave, absence and time
Deel to Shiftbase integration: own employees and employments from Deel as contracts in Shiftbase
With an integration between Deel and Shiftbase, own employees from Deel HR appear in Shiftbase automatically, with a contract per employment, the right department and the start date. When an employment ends in Deel, Shiftbase closes the matching contract on the last working day, while another running employment of the same person stays schedulable.
What the integration does
Organisations that record their own employees in Deel HR and schedule in Shiftbase enter every new worker in Shiftbase by hand. EOR workers and freelancers sit in the same Deel list, so it is not always clear who belongs in the schedule.
- HR creates an own employee in Deel at the Dutch entity, with department, work location and full-time or part-time.
- Deel sends a signed notification; KoppelHet checks the signature and fetches the person.
- Only employments of type direct_employee at an entity in the table go through; KoppelHet picks the Shiftbase department and team.
- In Shiftbase a contract is created from the employment start date, with hours per day.
- When the employment gets a last working day, the contract in Shiftbase ends on that day.
What to watch for with Deel and Shiftbase
- According to the current Deel documentation, a direct employee is someone employed by the own legal entity and paid through an own payroll provider. KoppelHet filters the people list on that type, so EOR workers and contractors stay out of Shiftbase, unless you deliberately want them scheduled.
- Deel records an own employee as full-time or part-time, with a part-time percentage. Hours per week are not in the people list. Shiftbase asks for hours per day. KoppelHet converts the percentage using the entity's full-time norm and the number of working days, which we record at the start.
- In Deel the last working day belongs to an employment, not to the person. In Shiftbase every employment therefore gets its own contract. When someone moves from an EOR contract to the own entity, one contract ends and the next starts, and the employee stays the same person in Shiftbase.
- When an employment changes in Deel, for example a different department or part-time percentage, KoppelHet does not edit the Shiftbase contract. An edit would also change past results in Shiftbase. A new contract starts from the change date.
- Deel stores a preferred name next to the official first name. Colleagues see each other in the Shiftbase app in the schedule and with swap requests. KoppelHet uses the preferred name there; the official name stays in Deel and in payroll.
- Deel sends separate notifications for a new and a changed direct employee, with the entity and team in the message. KoppelHet only uses the notification as a signal and then fetches the full person, because the notification contains no work location and no end date.
- If an organisation works with several entities in Deel, the employment's entity determines whether someone belongs in Shiftbase. An employee of the Belgian entity does not end up in the Dutch schedule, even if they are in the same Deel 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
Can EOR workers still be scheduled?
Yes, if you want that. We then switch on the eor type in the table, with its own contract type in Shiftbase, so the hours later go to Deel and not to own payroll.
Does time off from Deel also reach the schedule?
Not in this first step. Deel does report reviewed time off through webhooks; time off in Shiftbase 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 the REST API (version 2026-01-01) with an API token or OAuth2 app. GET /rest/people with hiring_types (direct_employee), offset and limit; per person id, preferred_first_name, last_name, department, work_location, client_legal_entity and employments[] (hiring_type, start_date, work_email, employee_number, termination_last_day, is_ended). Webhooks Employee Created Direct and Employee Updated Direct (contract.employment_type, team_information.legal_entity_id).
- Full-time or part-time follows the Create a direct employee schema (employment.type FULL_TIME or PART_TIME, part_time_percentage). To Shiftbase through the Shiftbase API with a token from App center, Public API, for employees and contracts.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Shiftbase | Notes |
|---|---|---|
id (Deel-persoon) | Externe referentie medewerker | Fixed key across employments |
preferred_first_name of first_name, last_name | Voornaam en achternaam | |
employments[].work_email | E-mailadres (uitnodiging app) | |
employments[].employee_number | Personeelsnummer | |
work_location en department | Contractafdeling en team | Through a lookup table |
job_title | Functie | |
Voltijd of deeltijd met percentage | Contracturen per dag | Percentage times the full-time norm, divided by working days |
employments[].start_date | Contract vanaf | |
employments[].termination_last_day | Contract tot |
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