HR to ERP
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions
With an integration between Deel and 4PS Construct, every own employee of a Dutch legal entity in Deel automatically reaches the 4PS company of that entity, with job, work email, start date and department and cost centre as default dimensions. Once the termination in Deel is completed, the employee gets the last working day as end date in 4PS.
What the integration does
Organisations with a Dutch construction or installation entity in 4PS Construct and HR for the whole group in Deel create new fitters and site managers in 4PS by hand. Deel also holds EOR employees and contractors, and they do not belong in 4PS as employees.
- At the start we link every Dutch legal entity that works with 4PS to a 4PS company.
- Deel reports a new own employee; KoppelHet creates them in the 4PS company of their entity.
- Department and cost centre go along as default dimension, if the value already exists in 4PS.
- On a completed termination KoppelHet sets the end date, and after the last working day the status to terminated.
What to watch for with Deel and 4PS Construct
- Deel has own employees, EOR, PEO and contractors. Only own employees of the construction or installation entity belong in 4PS, because their hours are booked on projects and cost centres. An EOR employee in the Netherlands is on the payroll of a Deel employer and stays outside 4PS.
- In the standard API of Business Central, which 4PS runs on, an employee has no field for department or manager. Department and cost centre from Deel therefore go onto the employee as default dimensions. The manager from Deel is not passed on.
- Deel keeps cost centres per legal entity, with a number and a name. Dimension values are read-only in the Business Central API. If a cost centre number from Deel is not yet in 4PS, KoppelHet creates the employee without that dimension and finance gets a message with the missing number.
- A termination in Deel can still be cancelled while it is pending. KoppelHet only sets the end date in 4PS once the termination is completed, and the status to terminated only after the last working day. Up to that day the fitter can book hours in 4PS.
- A group in Deel often has several legal entities, and not every Dutch entity works with 4PS. A holding or an office without projects stays outside the integration. Every entity that does take part has its own company in 4PS, and KoppelHet writes each employee into the company of their entity.
- The employee in Business Central also has fields for address, date of birth and bank account. KoppelHet does not fill them from Deel. They are not needed for hours and projects in 4PS, and this way 4PS holds no more personal data than the work requires.
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 contractors from Deel go to 4PS?
Not as employees. Subcontracting and hired staff run through purchasing in 4PS. An integration for that 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. GET /rest/people with hiring_type, client_legal_entity, department, job_title, work_email, employments[] with employee_number, active_worker_termination_status (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.
- To 4PS through the Business Central API v2.0 per company - employees (POST and PATCH; number, givenName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated; no department or manager) and defaultDimensions with parentType Employee (dimensionCode, dimensionValueCode). dimensionValues is read-only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in 4PS Construct | Notes |
|---|---|---|
employments[].employee_number | number | |
first_name | givenName | |
last_name | surname | |
job_title | jobTitle | |
work_email | email | |
start_date | employmentDate | |
direct_employee_termination_last_day | terminationDate en status | |
department en cost_center_number | defaultDimensions | Existing dimension values only |
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 → Active Directory
Deel to Active Directory integration: domain accounts per type of worker