Lease and mobility
HiBob to NS Business integration: employees from Bob in NS Go automatically, with address, site and leaving date
With an integration between HiBob and NS Business (NS Go), the Dutch employees from Bob appear in NS Go automatically, with home address, the office address of their site and the right legal entity. A departure HR schedules ahead of time in Bob goes to NS Go straight away, so the NS-Business Card stops on the last working day.
What the integration does
Organisations that manage their people in HiBob and let Dutch colleagues travel with NS Go add new employees with the NS Go Excel template. Bob knows who is leaving or moving next month, but NS Go only hears about it when someone remembers to pass it on.
- HR adds an employee in Bob at a Dutch entity, with start date, site and home address.
- Bob sends a webhook; KoppelHet reads the employee with a service user that may only see the fields it needs.
- The employee is included in the daily delivery to NS Go and can then request the NS-Business Card.
- A new home address or another site goes to NS Go with the effective date from Bob.
- As soon as HR schedules a departure in Bob, NS Go receives the leaving date, even if it is weeks away.
What to watch for with HiBob and NS Business
- When HR schedules a departure in Bob with a future date, Bob sends a webhook for the new history entry straight away. The event that someone has actually left only arrives at midnight after the last day in the site's time zone. KoppelHet uses the first message, so NS Go knows about the departure weeks ahead.
- Bob can revoke access immediately on a departure; there is a separate webhook event for that once the flow is approved. If HR chooses this, for example on summary dismissal, KoppelHet sends today's end date to NS Go instead of the contractual end date.
- In Bob permissions can be set per field. KoppelHet only asks for the home address and work data to be opened, not the whole personal category or salary. If the service user lacks a permission, Bob reports that column as restricted; KoppelHet then stops with an alert instead of sending NS Go an empty address.
- In Bob an employee works at a site, but the site's address is not the field NS Go needs. KoppelHet keeps a table from every Dutch site to the office address, so a site change in Bob lands in NS Go as a new office address.
- Bob sends a separate event when someone goes on temporary leave. Whether an employee keeps their NS-Business Card during, for example, parental leave is agreed per leave type; KoppelHet only passes the leave on if that has been agreed.
- HiBob is widely used by organisations with people in several countries. NS Go is for travel in the Netherlands, so KoppelHet only passes on employees of Dutch entities and sets the Chamber of Commerce number per entity for the NS Go CO2 report.
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 KoppelHet see salary in Bob?
No. The service user only gets the fields NS Go needs: name, work email, home address, site, entity, cost centre and dates.
Do colleagues in other countries go to NS Go too?
No. Only employees of Dutch entities. For temporary exceptions HR keeps a short list.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HiBob through employee data webhooks (employee.updated, table.entry.created, employee.left, employee.temporaryLeave, employee.access.revoked.immediately) and the People API with a service user with per-field permissions. Responses with restricted fields contain restricted_columns and the X-Has-Restricted-Columns header.
- According to NS, NS Go supports a daily import of a data file or a direct API connection for joiners, leavers, role and address. NS publishes no technical specification; format and fields are agreed per customer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HiBob | Field in NS Business | Notes |
|---|---|---|
root.id of employee ID | Personeelsnummer | Which ID is agreed per customer |
firstName en surname | Voornaam en achternaam | |
work.email | E-mailadres | |
Woonadres (address) | Thuisadres | Only the address field is opened for the service user |
work.site | Kantooradres | Through a table from site to address |
Entiteit | Juridische entiteit | Through a table from entity to Chamber of Commerce number |
Kostenplaats | Kostenplaats | |
work.startDate en vertrekdatum uit de lifecycle | Start- en einddatum dienstverband |
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