HR to ERP
Deel to AllSolutions integration: own employees per legal entity in the right AllSolutions company
With an integration between Deel and AllSolutions, every own employee of a Dutch legal entity in Deel automatically appears in the matching AllSolutions company, with job, department, cost centre and start date. Once the termination in Deel is completed, the employee gets an end date in AllSolutions, so their hours and project history remain.
What the integration does
Organisations that use Deel for HR in several countries and AllSolutions for projects, hours and purchasing of their Dutch companies enter new colleagues in AllSolutions by hand. Deel mixes own employees, EOR employees and contractors, and not everyone belongs in the ERP.
- At the start we record per Dutch legal entity which AllSolutions company the employees belong to.
- Deel reports a new or changed employee; KoppelHet fetches only the fields AllSolutions needs.
- KoppelHet switches to the right AllSolutions company and creates the employee or updates the changed fields.
- Once the termination in Deel is completed, KoppelHet sets the last working day as end date in AllSolutions.
What to watch for with Deel and AllSolutions
- Besides own employees, Deel also has EOR, PEO and contractors, including contractors outside Deel. Only own employees of a Dutch legal entity become employees in AllSolutions. If you want contractors to book hours on projects, we record that per type at the start.
- Every employee belongs to a legal entity in Deel, and to a company in AllSolutions. The AllSolutions integration account has one login company and has to switch through a separate function. KoppelHet switches per employee to the company that belongs to their legal entity, and that function must be open in the REST API for this.
- A termination in Deel runs from pending to completed or cancelled. KoppelHet only sets the end date in AllSolutions once the termination is completed. A cancelled termination therefore changes nothing in planning and approvals in AllSolutions.
- Deel lets an integration choose which fields come back, including in nested contracts. In AllSolutions a view decides which fields the REST API sees, and only one view per browser is active for the API. KoppelHet only requests from Deel what that one view in AllSolutions fills.
- Deel keeps cost centres per legal entity, with number and name. AllSolutions checks a cost centre on saving the way the screen does. If the number from Deel does not yet exist in the AllSolutions company, KoppelHet does not create the employee halfway but reports the missing number to finance.
- AllSolutions records login attempts and the number of REST API actions. AllSolutions recommends having a consultant review the configured views before go-live. We schedule that check before the first employees from Deel arrive.
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 Deel EOR employees go into AllSolutions?
Not by default. They are employed by a Deel employer. If they book hours on projects, we can include them as externals; we record that at the start.
Does KoppelHet delete employees in AllSolutions?
No. A leaver gets an end date, so hours and projects stay linked to them.
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. GET /rest/people with hiring_type (including direct_employee, hris_direct_employee, eor, peo, contractor), client_legal_entity, department, job_title, direct_manager, employments[] with employee_number, and fields with dot notation; active_worker_termination_status from PENDING to COMPLETED or CANCELED and direct_employee_termination_last_day. Cost centres through GET /rest/legal-entities/{legal_entity_id}/cost-centers. Webhooks per type of creation and for updates.
- AllSolutions through the REST API - login with token and refresh token, new employees with POST /api/v1/{browser}, updates with PUT /api/v1/{browser}/{RecordID} with only the changed fields and the same checks as the screen, switching company through MWZBDR. One active view per browser for the REST API; logging in ILOGPG and IPERHS.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in AllSolutions | Notes |
|---|---|---|
employments[].employee_number | Personeelsnummer | The AllSolutions record ID is stored too |
first_name en last_name | Naam | |
work_email | E-mailadres | |
job_title | Functie | |
department | Afdeling | Through a lookup table |
cost_center_number | Kostenplaats | Existing values only |
direct_manager | Leidinggevende | |
client_legal_entity | Inlogbedrijf (MWZBDR) | Fixed mapping per entity |
start_date en direct_employee_termination_last_day | Datum in dienst en datum uit dienst |
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