Leave, absence and time
Dyflexis to Nmbrs integration: locked payroll periods to Nmbrs, employees back to scheduling
With an integration between Dyflexis and Nmbrs, the worked hours and allowances of a locked payroll period in Dyflexis go to the right Nmbrs company automatically as hour components, and employees and contracts from Nmbrs reach scheduling by themselves. KoppelHet keeps several Nmbrs companies, cost centres and hour codes apart along the way.
What the integration does
Organisations that plan all shifts in Dyflexis and run payroll in Nmbrs often close the period per location. Payroll then checks per location whether the allowances came through correctly and changes the cost centre of stand-ins at another location by hand.
- HR records a new employee in Nmbrs with employment and schedule.
- KoppelHet sends the employee and the contract to Dyflexis. An administrator links the employee to a Dyflexis employee the first time.
- The planner locks the payroll period per venue and contract type group and sends it on. Dyflexis puts the period in a queue.
- KoppelHet fetches the hours per day, sums them per wage component and posts them as hour components in the right Nmbrs company.
- KoppelHet writes the result back to the Dyflexis queue, so the planner sees on the payroll page whether the period was processed correctly.
Back: New employees with employer to Dyflexis · Contracts with hours and days per week to Dyflexis · End date to Dyflexis
What to watch for with Dyflexis and Nmbrs
- Dyflexis delivers hours per venue, per contract type group and per period. An employee who worked at two venues in one period therefore appears in two deliveries. KoppelHet merges them per Nmbrs employee and keeps the venue as cost centre.
- For every locked period Dyflexis indicates in which target period and year the hours are paid. KoppelHet posts to that period in Nmbrs, even when the planner only sends last month's period now.
- Nmbrs refuses hours in a period that has already passed unless this is explicitly allowed. If the Dyflexis target period falls before the current Nmbrs period, KoppelHet marks the delivery as partial and reports the reason, instead of silently posting into another period.
- Dyflexis holds an employer reference per employee, and one Nmbrs environment can hold several companies. KoppelHet sets the Nmbrs company as the employer reference in Dyflexis, so hours from a venue of entity A never land at entity B.
- Wage components in Dyflexis are columns in the hours sheet the customer configures. Nmbrs works with hour codes per company. A new allowance in Dyflexis without an hour code in Nmbrs is not posted and appears as an alert, so no hours disappear unnoticed.
- Dyflexis lets several applications process the same queue, each with its own status. If another application already processes some venues, KoppelHet can work alongside it without periods being paid twice.
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
What does the planner see if something goes wrong?
KoppelHet sets a status per locked period in Dyflexis, with a short reason on an error or partial processing. The planner sees it on the Dyflexis payroll page, the details are in the platform.
What changes when Nmbrs retires the SOAP API?
Nmbrs retires the SOAP API in 2027. KoppelHet builds new integrations on the REST API. For an existing integration on SOAP we plan the switch well before that date.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dyflexis through the Dyflexis API with a token per environment and scopes. The queue with GET /api2/payroll/queue/from/{lastQueueId} (at most 10 items per call) or the payrollPeriodReady webhook; hours with GET /api/payroll/v3/hours-per-day per venue, contract type group and period; status back with POST /api2/payroll/queue/{queueId}/status (in progress, success, failed, partial) with its own application ID.
- Employees and contracts go to Dyflexis with POST /api2/external-employees/{employeeReference} (personnelNumber, employerReferenceId, costCenter, employmentStart, employmentEnd) and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, hours, days).
- Nmbrs through the EmployeeService with HourComponentVar_Insert_Batch (EmployeeId, HourCode, Hours, CostCenterId, Period, Year; UnprotectedMode for an earlier period). Nmbrs calls the SOAP API deprecated and will retire it in 2027; new integrations are built on the REST API.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dyflexis | Field in Nmbrs | Notes |
|---|---|---|
employee.personnelNumber | Medewerker in het Nmbrs-bedrijf | The Nmbrs employee number, set in Dyflexis by the integration |
employee.employerReferenceId | Nmbrs-bedrijf | Determines which company the hours land in |
components (bijvoorbeeld work, Allowance.150) | HourCode | Through a translation table from Dyflexis wage components to Nmbrs hour codes |
Som per component over de periode | Hours | |
period.targetPeriod en targetYear | Period en Year | |
employee.costCenter | CostCenterId | Through a translation table |
Dienstverband en rooster (terug) | contractReference, hours en days | |
Bedrijf in Nmbrs (terug) | employerReferenceId |
Related
DyADP iHCM → Dyflexis
ADP iHCM to Dyflexis integration: employees and contracts in scheduling, hours back to ADP
DyADP Workforce Now → Dyflexis
ADP Workforce Now to Dyflexis integration: employees and contracts of the European sites in the schedule
DyAFAS Profit → Dyflexis
AFAS to Dyflexis integration: employees per employer to scheduling, paid hours back as payroll changes
DyBambooHR → Dyflexis
BambooHR to Dyflexis integration: Dutch employees and contract hours from BambooHR in the schedule