Leave, absence and time
Tamigo to Nmbrs integration: employees from Nmbrs in scheduling, worked hours back as wage components
With an integration between Tamigo and Nmbrs, employees with contract and wage come from Nmbrs into Tamigo, and worked hours go back to Nmbrs per wage component. Nmbrs remains the source for employees, and the hours go to Nmbrs after review per payroll period.
What the integration does
Organisations that plan in Tamigo and run payroll in Nmbrs often still enter employees in both systems and pass on the hours per period as a list.
- The payroll bureau or HR records the employee with contract and wage in Nmbrs.
- The integration takes the employee into Tamigo, with department or cost centre.
- Employees work their shifts; Tamigo records only the hours actually worked.
- Tamigo maps the hours to the Nmbrs wage components.
- After review the hours go to the Nmbrs environment.
Back: Worked hours per wage component
What to watch for with Tamigo and Nmbrs
- In this integration Nmbrs is the source for employees. Anyone who changes a contract in Tamigo will see it replaced at the next sync. Changes therefore belong in Nmbrs, even when the planner hears about them first.
- Next to contract type and hours, the integration also takes over the wage and the start dates of contract type and wage. A pay rise from the first of the month thus counts in scheduling's labour cost from that date, not earlier.
- The hours must be in Nmbrs before the period closes there. If they come later, they miss the payroll run. Agree a fixed day with the payroll bureau.
- Tamigo calculates premiums and overtime itself, with rules per country and collective agreement. Nmbrs can also derive premiums from the collective agreement. Decide which side calculates, and align the wage components in Tamigo with that, otherwise Nmbrs pays a premium twice.
- Nmbrs stops its SOAP API on 1 March 2027. KoppelHet therefore writes through the REST API, so the integration does not stop in March 2027.
- With the wage, salary data is also in the scheduling environment. Decide in Tamigo which roles may see wages, so a team lead sees the labour cost of the roster but not the wage per colleague, if that is your policy.
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 send employees from Tamigo to Nmbrs?
No. Nmbrs is the source. New employees are created in Nmbrs and then reach Tamigo.
What if we also plan locations outside the Netherlands in Tamigo?
They do not belong in Nmbrs. During setup we record which locations go to Nmbrs.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Tamigo publishes no public API documentation; which entry point and which rights KoppelHet uses on the Tamigo side is agreed with Tamigo at the start.
- KoppelHet writes to Nmbrs through the REST API with OAuth 2.0 and a subscription key, per company, with variable hours per hour code and period. The SOAP variant HourComponentVar_Insert requires unprotected mode for an earlier period and stops on 1 March 2027.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Tamigo | Field in Nmbrs | Notes |
|---|---|---|
Personeelsnummer (Nmbrs) | Medewerker-ID in Tamigo | Fixed key between both |
Afdeling of kostenplaats | Afdeling in Tamigo | |
Contracttype en uren, met startdatum | Contract in Tamigo | |
Loon met startdatum | Loon in Tamigo | For labour cost in scheduling |
Datum in en uit dienst | Start- en einddatum in Tamigo | |
Gewerkte uren per soort (terug) | Looncomponent in Nmbrs | Mapping set up in Tamigo |
Related
Tamigo → AFAS Profit
Tamigo to AFAS integration: worked hours from Dutch stores to AFAS, employees and pay agreements back
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