Payroll integration
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
With an integration between AlexisHR (Simployer One) and Nmbrs, employees of the Dutch entity from AlexisHR reach that entity's Nmbrs company, with employment, schedule, salary and IBAN. Changes and terminations follow with their date, so the payroll bureau no longer waits for an export.
What the integration does
Organisations working with AlexisHR from Sweden, Norway or Denmark that have their Dutch employees paid through Nmbrs now email new people to the payroll bureau. The Dutch data, such as BSN and name prefix, is often not where Nmbrs expects it.
- HR creates the employee at the Dutch company in AlexisHR.
- Every hour KoppelHet fetches changed employees, with employment, work week and salary.
- In Nmbrs KoppelHet creates employee, employment, schedule, salary and IBAN.
- The payroll bureau completes tax data, pension and collective agreement.
- When an employment ends in AlexisHR, KoppelHet sets the end date in Nmbrs.
What to watch for with AlexisHR and Nmbrs
- AlexisHR only has first name and last name. A Dutch name prefix then sits in the last name; KoppelHet splits it off for Nmbrs and shows the split to payroll for checking.
- Every Dutch company in AlexisHR has its own companyId and organisation number. KoppelHet links the companyId to the Nmbrs company, so a group with several Dutch entities fits in one integration.
- AlexisHR gives an employment an end date and an effective end date, plus a terminated flag. KoppelHet uses the effective end date when present, so a moved last day is also right in Nmbrs.
- Salary entries in AlexisHR have a payout day and payment in advance or in arrears. Nmbrs decides that itself per period; KoppelHet only sends amount and effective date, and reports an entry in a currency other than euro.
- Bank details in AlexisHR include a Swedish clearing number besides IBAN and BIC. For Nmbrs only the IBAN counts; if it is missing, KoppelHet does not hold the employee back but reports it, so the bureau adds it before the first payment.
- Work weeks in AlexisHR can apply per office or per employee. KoppelHet takes the employee's work week if there is one, otherwise the office's, and sets it as the schedule in Nmbrs.
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 with our payroll bureau?
Yes. The bureau grants access to your Nmbrs company and sees notifications about name prefixes, IBAN or currency in the KoppelHet platform.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AlexisHR through the HRM One API (api.alexishr.com/v1, bearer access token with owner permissions, read calls only) - /employee, /employment, /work-week, /compensation and /company, with filters on updated and companyId. No webhooks in the public documentation.
- 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 AlexisHR | Field in Nmbrs | Notes |
|---|---|---|
id (employee) | Vrij veld in Nmbrs | Key |
employeeNumber | Personeelsnummer | |
companyId | Nmbrs-bedrijf | |
firstName, lastName, birthDate | Persoonsgegevens | Check name prefix separately |
ssn (ssnCountry NL) | BSN | |
Employment startDate | Startdatum dienstverband | |
Work week | Rooster | |
Compensation (amount, payoutPeriod, effectiveDate) | Salaris | |
bankAccount.iban en bic | IBAN | |
Employment endDate of effectiveEndDate | Datum uit dienst |
Related
AlexisHR → Active Directory
AlexisHR to Active Directory integration: accounts in your own domain from Simployer One
AlexisHR → AFAS Profit
AlexisHR (Simployer One) to AFAS integration: the Dutch entity in AFAS Profit Payroll
AlexisHR → Microsoft Entra ID
AlexisHR to Entra ID integration: users with employee number and groups, blocked on leaving
AlexisHR → Google Workspace
AlexisHR to Google Workspace integration: a Google account that follows the employee, from onboarding to departure