Payroll integration
Simployer to Nmbrs integration: from manual export to automatic HR changes in Nmbrs
With an integration between Simployer One and Nmbrs, new employees, salaries, fixed allowances, working weeks and departures of the Dutch branch go from Simployer to Nmbrs automatically, with the effective date from Simployer. Simployer One has its own Nmbrs export that HR starts by hand per employee; KoppelHet comes in when departures, allowances, future-dated changes or several Nmbrs companies must go along without manual work.
What the integration does
Anyone using Simployer One for HR and paying the Dutch branch in Nmbrs exports new employees from Simployer by hand and matches existing employees one by one. A departure or a fixed allowance is then still entered in Nmbrs by payroll.
- HR records the change in Simployer One.
- KoppelHet fetches updated employees and employments and reads salary, allowances and working week of the Dutch employees.
- New employees reach the right Nmbrs company; existing ones are matched once on employee number at the initial load.
- Salary, allowances and working week land in the Nmbrs period of their effective date.
- An end date on the employment becomes the termination date in Nmbrs.
What to watch for with Simployer and Nmbrs
- Simployer One's Nmbrs export is started by HR per employee on screen, and an existing Nmbrs employee is matched by hand. KoppelHet matches all employees at once on employee number at the start and then passes on every change without a click.
- An employment in Simployer has an end date, an effective end date and a terminated flag. KoppelHet uses the effective end date as the termination date in Nmbrs, and only when the employment is marked as terminated.
- Besides salary, Simployer holds additional compensation with a validity period and a salary code, for example a fixed travel allowance. Through a lookup table on that code it becomes a fixed pay component in Nmbrs with the same start and end date.
- When requesting an employee, Simployer returns the employment and salary valid today. KoppelHet therefore only sees a rise from next month by requesting the salary separately, and puts it ahead in the right Nmbrs period.
- Simployer records per employee a working week with hours per day and a start date. KoppelHet sets it as the schedule in Nmbrs, so an employee who moves from five to four days also works four days in the payroll calculation.
- According to Simployer the standard export signs in with an API token and the email address of a Nmbrs user. KoppelHet builds on the Nmbrs REST API, because Nmbrs stops the SOAP API on 1 March 2027.
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
Why not just use Simployer's Nmbrs export?
It is often enough when HR exports new employees themselves and payroll keeps track of departures and allowances in Nmbrs. Choose custom work when that manual work must go or there are several Nmbrs companies.
What does the payroll bureau need to arrange?
An integration in Nmbrs with access to your companies only, and agreeing the lookup table from Simployer salary codes to pay components.
We use Simployer Classic. Does this work too?
The Nmbrs export belongs to Simployer One. For Classic we read through the HRConnect API, with other fields and sign-in.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Simployer One through the HRM One API (api.alexishr.com/v1, bearer access token with owner rights). employee and employment with filters on updated; employment (endDate, effectiveEndDate, terminated); compensation and additional-compensation (salaryCode, effectiveDate, endDate); work-week (effectiveFrom, duration per day). Relations on employee point to the object that is active now.
- Nmbrs through the REST API with OAuth 2.0 at employer 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 Simployer | Field in Nmbrs | Notes |
|---|---|---|
employeeNumber | Personeelsnummer | |
firstName, lastName, birthDate | Persoonsgegevens | |
homeAddress | Adres | |
bankAccount.iban en bic | IBAN en BIC | |
hireDate en employment.startDate | Datum in dienst | |
employment.effectiveEndDate | Datum uit dienst | |
compensation.amount en effectiveDate | Salaris met ingangsperiode | |
additional-compensation: salaryCode, amount, effectiveDate, endDate | Vaste looncomponent met looptijd | Through a lookup table on salaryCode |
work-week: duration per dag, effectiveFrom | Rooster | Hours per day |
Related
Recruitee → Simployer
Recruitee to Simployer integration: hired candidates with employment and salary in Simployer One
Simployer → Active Directory
Simployer to Active Directory integration: accounts in your own domain from Simployer
Simployer → ADP iHCM
Simployer to ADP iHCM integration: salary, bonuses and end of employment from Simployer One to ADP iHCM
Simployer → AFAS Profit
Simployer to AFAS integration: Dutch employees from Simployer One in AFAS payroll