Payroll integration
Infor HCM to Nmbrs integration: Dutch employees from Infor ION in Nmbrs
An integration between Infor HCM and Visma Nmbrs passes new Dutch employees, changes and leavers from Infor ION's personnel messages to the right company in Nmbrs. Nmbrs then runs payroll; the payroll tax credit and other Dutch tax data are managed by payroll in Nmbrs itself.
What the integration does
Organisations that run HR in Infor HCM and have Dutch payroll in Nmbrs, often through a payroll bureau, maintain employees in both systems. Anyone who changes a department or job in Infor has to inform the payroll bureau separately.
- HR records a Dutch employee or change in Infor HCM.
- ION sends the personnel message to KoppelHet.
- KoppelHet determines the Nmbrs company from the entity and translates department and job.
- The employee is created in Nmbrs, or employment, job or department is updated with the effective date.
- Before the run KoppelHet compares Infor and Nmbrs and puts differences on a list for payroll.
What to watch for with Infor HCM and Nmbrs
- KoppelHet receives Infor messages through a connection point the administrator creates in ION Desk, with a Backend Service app in the ION API. The client ID of that app is in the connection point; revoking the app stops the integration straight away.
- Departments and jobs in Nmbrs are managed per company. KoppelHet translates the Infor code lists from Sync.CodeDefinitions per Nmbrs company, so the same Infor department in two Dutch entities goes to the right Nmbrs department.
- Infor describes for Expense Management that cost centre and work schedule are not part of the personnel message. For Nmbrs the organisation therefore chooses whether KoppelHet takes them from another source or payroll maintains them in Nmbrs.
- An integration still running on Infor's Legacy BODs no longer works with Infor HR Talent. Anyone who has to move both to Nmbrs and off Legacy BODs does so in one step with the standard messages.
- Nmbrs stops the SOAP API on 1 March 2027. An existing Infor integration on SOAP therefore has to be rebuilt; a new integration writes through the REST API straight away.
- Infor sends a message on every change, including a new phone number. KoppelHet compares every message with the last state in Nmbrs and only writes when a payroll-relevant field has changed.
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 this also work if a payroll bureau manages Nmbrs for us?
Yes. The payroll bureau gives the integration access to your Nmbrs company; exactly which rights is agreed together.
Does anything go back to Infor?
No. Infor remains the source. A flow back, for example payslips, can follow later as an extension.
What if Infor does not send a field Nmbrs needs?
We see that in the first test message. Payroll then completes it in Nmbrs, or we take it from another source.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Infor HCM through Infor ION - IMS connection point through the ION API (Backend Service app, client ID in the connection point), document flows for Sync.Personnel and Sync.CodeDefinitions; throttling per tenant on the ION API Gateway.
- To Nmbrs through the Nmbrs REST API with OAuth 2.0, per company; the SOAP API stops on 1 March 2027.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Infor HCM | Field in Nmbrs | Notes |
|---|---|---|
Personeelsnummer Infor | Personeelsnummer in Nmbrs | |
Entiteit | Nmbrs-bedrijf | One Nmbrs company per Dutch entity |
Naam en geboortedatum | Persoonsgegevens | |
Datum in dienst | Begin dienstverband | |
Afdelingscode | Afdeling | Through Sync.CodeDefinitions and a lookup table |
Functiecode | Functie | |
Datum uit dienst | Einde dienstverband |
Related
Infor HCM → AFAS Profit
Infor HCM to AFAS integration: personnel messages from Infor ION as employee and contract in AFAS Profit
Infor HCM → TOPdesk
Infor HCM TOPdesk integration: persons and onboarding tickets from Infor ION
Infor HCM → Visma Raet YouForce
Infor HCM to YouForce integration: personnel messages from Infor ION as requests in YouForce
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company