Payroll integration
Deel to Loket integration: employees of your own Dutch BV from Deel in Loket
With an integration between Deel and Loket, an employee of your own Dutch BV in Deel becomes a concept employee in Loket, at the employer that belongs to the legal entity in Deel. Contractors and EOR workers stay out of Loket, and the last working day from Deel ends the employment.
What the integration does
Employers that hired their first Dutch employees through EOR in Deel and now have their own entity paid in Loket pass new employees to the payroll bureau by email. People moving from EOR to the entity cause confusion every time.
- HR records a new employee in Deel, at the company's own Dutch entity.
- Deel reports the new employee; KoppelHet fetches person and employment.
- In Loket a concept employee appears at the employer of that entity, with the new hire checklist started.
- The payroll bureau adds BSN, pay, collective agreement and payroll tax credit and converts the concept.
- The last working day from Deel ends the employment in Loket.
What to watch for with Deel and Loket
- Deel holds contractors, EOR workers and employees of your own entities. KoppelHet only requests that last group, so a contractor or EOR worker never appears as a concept in Loket.
- If someone moves from EOR to your own BV, that is a new employment in Deel. For Loket it becomes a new concept with its own start date; the EOR period belongs to Deel's payroll.
- Each Dutch BV has its own legal entity in Deel and its own employer in Loket. KoppelHet picks the employer based on that entity, not on country or workplace.
- Deel reports events with a signed notification. KoppelHet only accepts notifications that demonstrably come from Deel, and also compares the employees in Deel with Loket daily.
- Loket lets a new employee arrive as a concept first, with a checklist for payroll. Because BSN and payroll tax data are rarely in Deel, the payroll bureau fills them in during the checklist.
- The last working day is recorded in Deel with the termination. KoppelHet ends the employment in Loket on that day, so the payroll bureau makes the final settlement in the right period.
- A payroll bureau managing Loket only grants the integration access to your employer. The bureau's other clients stay out of view.
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 salary and hours also come from Deel?
That depends on what Deel releases through the integration for your own employees. By default the payroll bureau completes pay and working hours in Loket during the checklist.
What happens to our EOR workers?
They stay in Deel's payroll. Only when someone is employed by your own BV does a concept arise in Loket.
Does this work if a payroll bureau manages Loket for us?
Yes. The bureau gives the integration access to your employer in Loket.
What about the GDPR?
You are the controller and KoppelHet is the processor, under a data processing agreement. Only employees of your own Dutch BV go to Loket, and every action is in the audit logging.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel is read through the Deel REST API (people list, filtered on hiring type hris_direct_employee, with employments and client_legal_entity) and through signed webhooks on contract events. Last working day from termination_last_day.
- Loket is written through the Loket REST API with OAuth - create concept employee at the employer, initiate the new hire checklist workflow and end employment.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Loket | Notes |
|---|---|---|
id van de Deel-persoon | Personeelsnummer of vrij veld | Fixed key |
Voornaam en achternaam | Voornaam, voorvoegsel en achternaam | Split the name prefix |
Geboortedatum | Geboortedatum | |
Adres | Adres | |
E-mail | E-mailadres voor selfservice | |
client_legal_entity | Werkgever | Through a lookup per entity |
Startdatum van het dienstverband | Begindatum dienstverband | |
Functie | Functie | Through a lookup table |
termination_last_day | Einde dienstverband |
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