Accounts in applications
Nmbrs to Simplicate integration: employees and schedules from payroll in Simplicate
With an integration between Nmbrs and Simplicate, every new employee from Nmbrs appears in Simplicate automatically, with manager, team and a timetable that matches the schedule in Nmbrs. On departure the Simplicate timetable gets the last working day as its end date and the administrator is prompted to block the user and free up the licence.
What the integration does
Organisations with several operating companies in Nmbrs that record hours and projects in Simplicate retype every new colleague, including the schedule. Someone who goes from four to three days already has the new schedule in Nmbrs, while the hours accounting in Simplicate is then wrong for weeks.
- HR enters the new employee in Nmbrs, at the company they join, with schedule and manager.
- KoppelHet first creates the person in Simplicate and then the employee, with manager and team.
- The employee gets a timetable in Simplicate from the start date, with the same hours per day as in Nmbrs.
- The Simplicate administrator is prompted to invite the employee as a user, with the right user group.
- On departure KoppelHet ends the timetable on the last working day, moves the reports of a departing manager to their new manager and asks the administrator to block the user.
What to watch for with Nmbrs and Simplicate
- A schedule in Nmbrs has two weeks, each with hours per day. Simplicate has exactly that as well, an even and an odd week. A rotating schedule with every other Friday off therefore carries over one to one, once we agree at the start which Nmbrs week is the even week.
- A new schedule in Nmbrs has its own start date. KoppelHet ends the current Simplicate timetable the day before and starts a new one on that date, so hours from earlier weeks are still measured against the old timetable.
- Employee numbers in Nmbrs are unique per company, and Simplicate has one environment for all operating companies. KoppelHet stores company and employee number together in a custom field on the employee, so number 12 in two companies does not clash.
- When a colleague moves to another operating company, Nmbrs gives them an employment at a different company. In Simplicate they stay the same employee, so hours history and projects stay together.
- Simplicate has its own Nmbrs integration for leave and absence. This integration covers the other side, who is in Simplicate and on which timetable, and does not touch leave or absence.
- Nmbrs holds salary and hourly wage, Simplicate a cost rate per employee. The integration reads no salary and no citizen service number in Nmbrs; the cost rate stays a choice the controller makes in Simplicate.
- The end-of-service date is often in Nmbrs weeks ahead. KoppelHet sets that date as the end of the Simplicate timetable, so the leaver disappears from the hours calendar after the last working day but keeps writing hours until then.
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 the integration also create the Simplicate user?
No. Simplicate's public API has no function for it, and the licence starts at the moment of invitation. The integration prepares the employee; the administrator sends the invitation and picks the user group.
What if someone changes the timetable in Simplicate by hand?
At the next change in Nmbrs, Nmbrs wins again. So agree that schedules are only changed in Nmbrs; the integration reports differences in the platform.
Can leave entitlement come along too?
Simplicate has its own Nmbrs integration for that. If you do not use it, leave entitlement can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the SOAP API (EmployeeService, including Schedule_GetCurrent with HoursMonday to HoursSunday and HoursMonday2 to HoursSunday2, ParttimePercentage and StartDate, plus Manager_GetCurrent and Department_GetCurrent), with a periodic comparison per company. The SOAP API stops on 1 March 2027; where the REST API returns the same data, we switch.
- Simplicate is written through REST API v2 with the Authentication-Key and Authentication-Secret headers. First POST /api/v2/crm/person (first_name, family_name_prefix, family_name, initials, email, teams), then POST /api/v2/hrm/employee with person_id, supervisor, status and custom_fields. The timetable goes through /api/v2/hrm/timetable with even_week, odd_week, has_odd_weeks, start_date and end_date.
- Teams and contracts are read-only in Simplicate API v2, and there is no endpoint for users and user groups. An API token inherits the rights of the user it was created for; Simplicate promises at least 60 requests per minute and returns HTTP 429 above that.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Simplicate | Notes |
|---|---|---|
Bedrijf + personeelsnummer | Eigen veld bij de medewerker (custom_fields) | Fixed key; employee numbers are unique per company |
Voornaam, voorletters | first_name, initials (persoon) | |
Tussenvoegsel, achternaam | family_name_prefix, family_name (persoon) | |
Zakelijk e-mailadres | email (persoon) en werkadres | Needed to invite the employee as a user later |
Manager_GetCurrent | supervisor (medewerker) | Through the manager's Simplicate employee |
Afdeling | teams (persoon) | Through a lookup to existing Simplicate teams |
HoursMonday … HoursSunday | even_week day_1 … day_7 (rooster) | |
HoursMonday2 … HoursSunday2 | odd_week day_1 … day_7 (rooster) | Only when week 2 differs; then has_odd_weeks |
StartDate rooster | start_date (rooster) | |
Datum uit dienst | end_date (rooster) |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll