Payroll integration
Yoobi to Nmbrs integration: hours, leave and mileage per pay period to Nmbrs
With an integration between Yoobi and Visma Nmbrs, hours, leave, mileage and privately paid expense claims from Yoobi go to Nmbrs as wage and hour components per pay period, and employees come from Nmbrs into Yoobi. A second delivery in the same period sends only what changed.
What the integration does
Organisations that record hours and leave in Yoobi and process pay in Nmbrs retype overtime, mileage and holiday hours taken into Nmbrs every month without an integration.
- Payroll links a Nmbrs user with the right permissions in Yoobi and chooses the primary Nmbrs company.
- Employees from Nmbrs are matched in Yoobi on employee number and surname.
- Per contract type, payroll records in Yoobi which Yoobi items go to which wage or hour code in Nmbrs.
- After timesheets and expense claims are approved, the period goes to Nmbrs; a second delivery sends only what changed.
- Payroll runs the payroll in Nmbrs; employees then open their payslip from Yoobi.
Back: Employee data, contract and work schedule from Nmbrs · Payslips and annual statements, fetched when the employee opens them
What to watch for with Yoobi and Nmbrs
- The integration works both ways. Employees, contract and work schedule come from Nmbrs into Yoobi; hours, leave, mileage and expense claims go from Yoobi to Nmbrs per pay period.
- Yoobi fetches all wage and hour components from wage model 1 in Nmbrs. A component in another wage model cannot be selected by payroll in the mapping.
- Holiday hours taken go to wage component 9981, which is tied to leave type 1 in Nmbrs. If you use more leave types in Nmbrs, decide in advance which Yoobi hours do and do not fall under it.
- Every later delivery in the same period sends only changed lines. What payroll enters in Nmbrs through quick entry on the same wage or hour code can overwrite those lines, so those codes do not belong in the quick entry template.
- Automatic delivery on timesheet approval only works for the current pay period. A timesheet approved after the period closes has to be delivered by payroll.
- A privately paid expense claim joins the next period and is then marked Paid, with the pay period recorded. The same claim therefore never reaches a second run.
- Yoobi picks the work email from Nmbrs and falls back to the personal address. Without an email address in Nmbrs, Yoobi does not create a user account for that employee.
- With several Nmbrs companies, Yoobi determines the company per employee, then per department and then for the whole organisation. Synchronisation, mapping and delivery run separately per company.
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
Which permissions does the Nmbrs user need?
A functional account at debtor level that may view company data, employee data and payroll tax settings, deliver and delete payroll mutations and download payslips. If that user is deactivated, the integration stops.
Can we still change hours after the first delivery?
Yes. A later delivery in the same period only sends the changed lines. Note that quick entry in Nmbrs on the same codes can overwrite those lines.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- To Nmbrs with OAuth on the REST API; the Nmbrs user must work at debtor level, have access to all linked companies and be allowed to deliver and delete payroll mutations. The Nmbrs SOAP API stops on 1 March 2027.
- KoppelHet reads Yoobi through the Yoobi REST API with an API user that may only request registrations over a period, and writes to Nmbrs through the REST API on the same codes as the mapping in Yoobi.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Yoobi | Field in Nmbrs | Notes |
|---|---|---|
Personeelsnummer | Personeelsnummer | Main matching attribute; must be identical in both systems |
Uren op activiteit (registratietype uren) | Urencode uit loonmodel 1 | |
Opgenomen vakantie-uren | Looncomponent 9981 Opname verlofuren | Linked to leave type 1 in Nmbrs |
Trefwoord KM zakelijk / KM woon-werk | Looncomponent voor kilometervergoeding | |
Goedgekeurde declaratie, privé betaald | Looncomponent voor onkostenvergoeding | Then set to Paid with the pay period recorded |
Trefwoord ziekte-uren | Urencode voor ziekte |
Related
Recruitee → Yoobi
Recruitee to Yoobi integration: new colleagues ready for planning in Yoobi
Teamtailor → Yoobi
Teamtailor to Yoobi integration: hired candidates as employees in Yoobi, ready for planning and hours
Yoobi → AFAS Profit
Yoobi to AFAS integration: overtime, mileage and expenses from Yoobi in the AFAS payroll run
Yoobi → Microsoft Entra ID
Yoobi to Entra ID integration: Microsoft accounts based on employees and contracts in Yoobi