HR to ERP
HiBob to AllSolutions integration: employees from Bob in the right AllSolutions company
With an integration between HiBob and AllSolutions, every employee of a Dutch employer in HiBob automatically becomes an employee in the matching AllSolutions company, with department, job and manager. A transfer in Bob goes through on its effective date, and a leaver becomes an end date in AllSolutions, so hours and project history remain.
What the integration does
Organisations that manage people in HiBob and run projects, hours and invoicing in AllSolutions in the Netherlands enter new colleagues into AllSolutions by hand. A transfer HR enters in Bob weeks ahead only gets there when someone remembers.
- HR records a new employee, transfer or leaver in HiBob.
- HiBob reports the change; KoppelHet fetches the employee and the work history.
- Only employees of a Dutch employer continue, to the AllSolutions company that belongs to that employer.
- A change with a future date waits until that date and then goes through with only the fields that differ.
- On departure KoppelHet sets the end date, without deleting the employee.
What to watch for with HiBob and AllSolutions
- In HiBob every employee belongs to one employer, the legal unit. Every Dutch employer gets a fixed AllSolutions company. The AllSolutions integration account logs in to one default company, so KoppelHet switches company per employer before writing.
- If HR enters a transfer in Bob with a future date, HiBob reports the new work history entry straight away. KoppelHet keeps it and only passes it on on the effective date, because AllSolutions shows the current state per employee.
- HiBob only reports a leaver in the night after the effective date, in the site's time zone. That is too late for AllSolutions to set the end date in advance. KoppelHet therefore reads the planned leaving date from Bob itself every day.
- If the service user in Bob lacks permission for a field, HiBob omits that field without an error. AllSolutions could store that as an empty field. KoppelHet checks per run that department, job and dates are present, and stops rather than writing empty values.
- AllSolutions runs the same checks through the API as on screen, including fields the customer made mandatory. Bob often has no such field. KoppelHet records at the start which mandatory fields exist and where the value comes from, or which fixed value AllSolutions gets.
- A webhook from HiBob only contains the employee and the changed fields, not the new values. KoppelHet then fetches the values and sends AllSolutions only the fields that differ per record, as the AllSolutions API allows.
- An employee moving from a Dutch to a foreign employer is a leaver for AllSolutions. KoppelHet sets an end date in the AllSolutions company, while the colleague stays active in Bob.
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
Does salary information from Bob go to AllSolutions?
No. The service user in Bob gets no permissions on salary. Finance records cost rates in AllSolutions.
Can hours from AllSolutions go back to Bob?
That can be added later as an extension. We start with employees from Bob to AllSolutions.
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; HMAC-SHA512 in Bob-Signature; retries up to three days) and the Employee data API: POST /people/search with fields (up to 400) and showInactive, without pagination, and the work history per employee with effectiveDate. Missing permissions lead to omitted fields without an error.
- AllSolutions through the REST API: login with signature and refresh token, GET with filters on a view, POST per record with the same checks as the form, PUT on the record ID with only changed fields, switching company through the login-company function. Fields and labels per customer through views and settings for the REST API.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HiBob | Field in AllSolutions | Notes |
|---|---|---|
root.id | Eigen veld bij de medewerker | Fixed key between both systems |
work.employeeIdInCompany | Personeelsnummer | |
root.firstName en root.surname | Naam | |
root.email | E-mailadres | |
Werkhistorie: department, title, effectiveDate | Afdeling en functie met ingangsdatum | |
Werkhistorie: reportsTo | Leidinggevende | |
Employer | AllSolutions-bedrijf (inlogbedrijf) | Lookup per employer |
work.startDate en vertrekdatum | Datum in dienst en datum uit dienst |
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