Cezanne HR to Nmbrs integration: Dutch employments from Cezanne into payroll

What the integration does

Organisations that use Cezanne HR internationally and have Dutch payroll run in Nmbrs by a payroll bureau now email changes with the effective date attached. A missed entry, such as fewer hours from next month, is only noticed on the payslip.

1. HR creates an employment at the Dutch employer in Cezanne, with working time pattern and salary.
2. KoppelHet reads that person's tables with a filter on the Dutch employer.
3. Employee, employment, schedule, salary and IBAN are created in that employer's Nmbrs company.
4. The payroll bureau completes tax data, pension and collective agreement in Nmbrs.
5. A new entry with an effective date in Cezanne becomes a change as of that date in Nmbrs.

What to watch for with Cezanne HR and Nmbrs

• If a group has several Dutch employers in Cezanne, each belongs to its own CompanyCode. KoppelHet links each code to one Nmbrs company, so a transfer between entities becomes a leaver and a new hire in Nmbrs.
• Almost everything in Cezanne has an EffectiveFrom and EffectiveTo, including address and bank account. KoppelHet only sends a new entry to Nmbrs once the matching Nmbrs period exists, and passes the effective date along.
• A working time pattern in Cezanne is tied to the absence plan; according to the API documentation a pattern cannot overlap an enrolment in such a plan. KoppelHet therefore only reads the pattern and never changes it from Nmbrs; the schedule in Nmbrs follows Cezanne.
• Access to the Cezanne API goes through a user who logs in and grants consent, with the same visibility as on screen. An integration user who only sees the Netherlands prevents salaries from other countries ever passing through the integration.
• A compensation item in Cezanne can be calculated pro rata using the FTE. KoppelHet sends the salary Cezanne records for the employee and reports it when the FTE percentage does not match the schedule in Nmbrs.
• Cezanne also has its own UK payroll tables, such as Tax & NI. The integration leaves those alone; for Nmbrs only the HR part of the record counts.

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
• Cezanne HR integrations
• Nmbrs integrations

→

Cezanne HR → Active Directory

Cezanne HR to Active Directory integration: domain accounts per employer and location

→

Cezanne HR → ADP iHCM

Cezanne HR to ADP iHCM integration: compensation, single payments and leavers to Dutch ADP payroll

→

Cezanne HR → AFAS Profit

Cezanne HR to AFAS integration: the Dutch employer from Cezanne in AFAS Profit Payroll

→AS

Cezanne HR → Arbodienst (SIVI)

Cezanne HR to the occupational health service via SIVI: sickness absence events as absence reports