Dayforce to Nmbrs integration: Dutch payroll per end client

What the integration does

Payroll providers that run Nmbrs payroll for clients who manage their staff in Dayforce receive every new employee by email or spreadsheet. For each client the payroll team has to check what changed since the previous period, and with several clients side by side that quickly diverges.

1. The end client's HR records a new hire or change in Dayforce.
2. Per end client KoppelHet fetches new and changed employees, with employment, job, address and bank account.
3. A change that takes effect later only lands in Nmbrs on that date, not too early.
4. The employee appears in that end client's Nmbrs company, with contract, schedule, salary and bank account.
5. After processing in Nmbrs the agreed feedback goes back to Dayforce. The payroll team sees errors per end client in the KoppelHet platform.

What to watch for with Dayforce and Nmbrs

• Each end client has its own Dayforce environment with its own credentials. KoppelHet manages these separately per end client, so data from different brands never mixes.
• In Nmbrs each end client sits in its own company under the payroll provider. The integration uses the Dayforce environment to decide which Nmbrs company an employee goes to.
• Dayforce only passes on a field when the integration has rights to it in the end client's role. An empty field for a new end client is therefore often a permissions issue in Dayforce.
• Dayforce stores job and department with start and end dates. KoppelHet reads which job applies on the effective date, not only the current one.
• International brands often use an annual salary and head office job codes in Dayforce. KoppelHet converts per end client to the Dutch monthly salary and the jobs in Nmbrs.
• Dutch payroll tax data is not in Dayforce by default. The payroll provider records it in Nmbrs, and the integration leaves it untouched there.
• Nmbrs retires its old integration method on 1 March 2027. New end clients therefore connect to the new one straight away.

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, architecture and compliance

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

Related

• Payroll integration
• Outsourced payroll
• Dayforce integrations
• Nmbrs integrations

→

Ashby → Dayforce

Ashby to Dayforce integration: have Dayforce validate the hire first, then save it

→

Bullhorn → Dayforce

Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce

→

Carerix → Dayforce

Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce

→

Dayforce → 4PS Construct

Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date