Lease and mobility
YouForce to NS Business integration: employees from Visma Raet YouForce in NS Go automatically
With an integration between Visma Raet YouForce and NS Business (NS Go), every employee with a current employment in YouForce appears in NS Go automatically, with home address, employer and cost centre. If someone has several employments, they remain one traveller in NS Go, and only when the last employment ends does NS Go stop too.
What the integration does
Organisations that run payroll and HR in YouForce and let employees travel with NS Go manage the workforce in YouForce and next to it an Excel list for NS Go. With people who have two employments, or with a move to another employer within the group, NS Go goes wrong most often.
- HR or payroll records a new employment in YouForce.
- Every day KoppelHet fetches the changes since the previous synchronisation, with the home address from the private contact details.
- Per person KoppelHet merges the employments into one traveller for NS Go, under the employer of the main employment.
- A move or another organisational unit takes effect in NS Go the next day.
- When the last current employment gets a discharge date, it goes to NS Go as the end date.
What to watch for with Visma Raet YouForce and NS Business
- In YouForce one person can have several employments at the same time. NS Go has one account per traveller. KoppelHet merges the employments per person and only stops the account in NS Go when the last employment ends, not already at the first.
- Visma itself names the link with a system for business mobility and travel expenses as a typical use of the Youforce Basic API. That API is read-only; the integration therefore takes data from YouForce and writes nothing back.
- The home address and work email sit in YouForce behind a separate scope for private contact details, which also returns the citizen service number and private email. KoppelHet only uses address and work email and does not store the citizen service number, because NS Go does not need it.
- YouForce still returns a deleted record for seven days, and after that no longer. A daily run therefore sees a cancelled hire in time. KoppelHet then also removes that person from the delivery to NS Go, instead of preparing a card for someone who is not coming.
- If someone changes employer within the group, they get a new employment at another company in YouForce. For NS Go that is the same traveller under another legal entity. KoppelHet moves the employee to that entity instead of deregistering and re-registering them.
- NS Go processes travel costs per pay code for payroll, and that payroll runs in YouForce itself here. Because the Basic API is read-only, that way back goes through another route in YouForce; it can be added later as an extension.
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
What happens with two employments?
The employee remains one traveller in NS Go. The account only stops when the last employment ends.
Can travel costs go back to YouForce automatically?
Not through this integration, because the Basic API only reads. A flow back to payroll 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.
- Youforce Basic API with the scopes Youforce-Basic:Get_Basic and Youforce-Basic:GetPrivateContactDetails; Persons, Employments (read-only, filter on company) and organisational units. Delta with from and to on latestSync; historical days in the Configuration API; deleted records visible for seven days; paging with take (up to 1000), skip and nextLink.
- According to NS, NS Go supports a daily import of a data file or a direct API connection for joiners, leavers, role and address. Format and fields are agreed per customer with NS.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in NS Business | Notes |
|---|---|---|
personCode | Personeelsnummer | Per person, not per employment |
Roepnaam en achternaam | Voornaam en achternaam | |
Zakelijk e-mailadres | E-mailadres | From the private contact details scope |
Woonadres | Thuisadres | |
Employment company | Juridische entiteit | Through a table from employer to Chamber of Commerce number |
Organisatie-eenheid | Kostenplaats | |
Datum in dienst en dischargeDate | Start- en einddatum dienstverband | End date of the last current employment |
Related
ADP Workforce Now → Visma Raet YouForce
ADP Workforce Now to YouForce integration: requests for new Dutch hires and contract changes
Bullhorn → Visma Raet YouForce
Bullhorn to YouForce integration: a placement becomes a hire request
Carerix → Visma Raet YouForce
Carerix to YouForce integration: a placed candidate starts the hire workflow in YouForce
Darwinbox → Visma Raet YouForce
Darwinbox to YouForce integration: hires and pay changes from Darwinbox as a request in YouForce