Payroll integration
Officient to Nmbrs integration: hires, wages and schedules from Officient to Nmbrs
With an integration between Exact Officient and Nmbrs, new employees, wage changes and weekly schedules start in Officient and reach Nmbrs by themselves. KoppelHet builds that integration and compares both systems before every Nmbrs period.
What the integration does
Organisations that use Exact Officient as HR system and Nmbrs for Dutch payroll want to do hires and pay rises in Officient. Without an integration, payroll retypes them in Nmbrs.
- HR records a new employee in Officient; the person_added webhook reports it to KoppelHet.
- KoppelHet creates employee, employment, schedule, wage and IBAN in Nmbrs and writes the Nmbrs number back to the person's payroll link in Officient, if the API allows it.
- New wage entries and weekly schedules in Officient go to Nmbrs with their start date.
- Before the close KoppelHet compares both systems and reports differences.
What to watch for with Officient and Nmbrs
- Officient has fields that according to its own documentation exist only for Dutch integrations, such as initials and the employee number at the linked payroll. KoppelHet uses that number as the bridge to Nmbrs, so both systems see the same employee.
- Officient records the weekly schedule in minutes per day, optionally with a pattern over several weeks. KoppelHet converts that to hours per day in Nmbrs; an alternating multi-week pattern goes to payroll as a notification.
- A new wage in Officient triggers no webhook; only person changes, days off and changes of team, manager and role do. KoppelHet therefore reads the wage history every hour.
- Officient has a list of sickness periods per year, with status open, closed or partially closed. Before a Nmbrs period closes KoppelHet shows the open periods to payroll; passing on sickness itself can be added later as an extension.
- Every wage entry in Officient has a registration country, such as BE or NL. An organisation with Belgian and Dutch colleagues in one Officient account therefore has both in the same wage history. KoppelHet only sends entries with registration country NL to Nmbrs.
- With a wage entry Officient also gives an estimated monthly cost, including holiday pay, end-of-year bonus and social contributions. That is an estimate by Officient, not the result of a payroll calculation. KoppelHet only takes over the wage type and the amount; Nmbrs calculates the rest itself.
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
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Officient through api.officient.io/1.0 with OAuth 2.0 - people/list (with linked_payroll_provider), people/{id}/detail, wage history, weekly_schedule/current and sickness periods. Webhooks person_added, person_updated, person_role_updated and days_off_*; the notification only contains the id. Limit 30 calls per 5 seconds.
- Nmbrs through the REST API with OAuth 2.0 at client level. The SOAP API stops on 1 March 2027.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Officient | Field in Nmbrs | Notes |
|---|---|---|
id (person) | Vrij veld in Nmbrs | Key |
linked_payroll_employee_number | Personeelsnummer | According to Officient only with Dutch integrations |
name_parts (initials, insertion) | Voorletters en tussenvoegsel | |
employment.first_employment_date | Startdatum dienstverband | |
Wage (type, rate, start_date) | Salaris of uurloon met ingangsdatum | |
weekly_time_engagement_minutes | Rooster (uren per dag) | |
bank_account_iban | IBAN | |
employment.last_employment_date | Datum uit dienst |
Related
Officient → Active Directory
Officient to Active Directory integration: AD accounts from Exact Officient
Officient → ADP iHCM
Officient to ADP iHCM integration: Dutch wages and leavers from Exact Officient to ADP iHCM
Officient → AFAS Profit
Officient to AFAS integration: Dutch employees from Exact Officient in AFAS Profit Payroll
ASOfficient → Arbodienst (SIVI)
Officient to the occupational health service via SIVI: absence periods from Exact Officient as absence reports