HR to ERP
HiBob to 4PS Construct integration: fitters and site managers from Bob in 4PS
With an integration between HiBob and 4PS Construct, every new employee of a Dutch employer in HiBob automatically reaches the right 4PS company, with job, work email, start date and cost centre. When someone leaves, they get an end date in 4PS and the status terminated after the last working day, so hours can be booked up to that day.
What the integration does
Organisations that do HR in HiBob and work with 4PS Construct in their construction or installation business create new fitters in 4PS by hand. A leaver in Bob only reaches 4PS when planning notices someone is no longer there.
- HR creates the new colleague in HiBob at an employer that works with 4PS.
- HiBob reports the new employee; KoppelHet fetches name, job, work email and start date.
- The employee goes into the 4PS company of that employer, with the cost centre as default dimension if it already exists.
- A new job or cost centre with a future date goes through on that date.
- On departure KoppelHet sets the end date straight away, and the status to terminated after the last working day.
What to watch for with HiBob and 4PS Construct
- HiBob often holds every country and division of a group, 4PS only the construction or installation companies. KoppelHet only includes employees of the employers that work in 4PS, and puts each employer in a fixed 4PS company.
- HiBob has no cost centre field by default; organisations record it in a custom field or a custom table. A change in a custom table does not produce a regular change event in HiBob, only a table event. KoppelHet listens to both, so a cost centre change also reaches 4PS.
- In the standard API of Business Central, which 4PS runs on, dimension values such as cost centres are read-only. If the cost centre from Bob is not yet in 4PS, KoppelHet creates the employee without a cost centre and tells finance which code is missing.
- HiBob only reports a leaver in the night after the effective date. For 4PS, planning wants to know the end date earlier. KoppelHet reads the planned leaving date from Bob daily and sets it as the end date in 4PS straight away; the status only changes to terminated after the last working day.
- A HiBob webhook is retried for up to three days on errors and then disabled. If the integration to 4PS is down over a weekend, the daily check fetches all employees of the employers concerned again and fills the gap.
- Bob returns only active employees in a search by default, without pagination. KoppelHet first requests only the IDs and then the fields per block, and requests leavers separately, so a fitter leaving does not quietly disappear from view.
- Business Central has its own middle name field. If Bob holds a surname like de Vries in one field, KoppelHet puts the prefix in that field, if you want, so sorting in 4PS on Vries works.
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 also go into 4PS?
Only if they are in Bob and you agree on it. Per employment type we record at the start who goes to 4PS.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HiBob through webhooks v2 (employee.created, employee.updated, table.entry.created and table.entry.updated, employee.left; only IDs in the payload; HMAC-SHA512 in Bob-Signature; retries up to three days, then inactive) and the Employee data API: POST /people/search with fields and showInactive (default false), without pagination, first root.id and then fields per block. Custom tables do not send employee.updated.
- To 4PS through the Business Central API v2.0 per company: employees (POST and PATCH; number, givenName, middleName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated) and defaultDimensions with parentType Employee. dimensionValues is read-only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HiBob | Field in 4PS Construct | Notes |
|---|---|---|
work.employeeIdInCompany | number | |
root.firstName | givenName | |
root.surname | surname en middleName | Name prefix split off |
Werkhistorie: title | jobTitle | |
root.email | email | |
work.startDate | employmentDate | |
Geplande vertrekdatum | terminationDate en status | |
Kostenplaats (eigen veld of tabel in Bob) | defaultDimensions | Existing values only |
Related
Ashby → HiBob
Ashby to HiBob integration: a hire from Ashby straight in as an employee in Bob
Bullhorn → HiBob
Bullhorn to HiBob integration: an approved placement as a new employee in Bob
Carerix → HiBob
Carerix to HiBob integration: successful match becomes a new employee in Bob
Greenhouse → HiBob
Greenhouse to HiBob integration: from a hire in Greenhouse to a new employee in Bob