Cezanne HR logoLoket logo

Payroll integration

Cezanne HR to Loket integration: Dutch employments, working time and salary with effective dates to Loket

With an integration between Cezanne HR and Loket, new employments of the Dutch employer go from Cezanne HR to Loket as a concept employee, and working time pattern, salary and bank account follow with the same effective date as in Cezanne. Payroll in Loket then works with what HR decided in Cezanne, without retyping.

What the integration does

Organisations that run HR for several countries in Cezanne HR and have Dutch payroll processed in Loket often record changes in advance with an effective date. Without an integration payroll retypes them when they take effect, and a retroactive change then falls outside the payroll run.

  1. HR creates an employment in Cezanne at the CompanyCode of the Dutch employer.
  2. KoppelHet reads person, address, bank account, working time pattern and compensation and creates a concept employee in Loket.
  3. Payroll completes collective agreement, payroll tax credit and pension and converts the concept.
  4. A new record in Cezanne with a later effective date becomes a new record in the Loket date chain.
  5. A real end date of the employment ends the employment in Loket.
Cezanne HR → KoppelHet → LoketSOURCECezanne HRTARGETLoketKoppelHetmapping · logging · monitoringCezanne HR → KoppelHet → LoketSOURCECezanne HRTARGETLoketKoppelHetmapping · logging · monitoring
Out: Concept employee with address and bank account · Employment per CompanyCode · Working hours from the working time pattern · Wage from the base compensation item · Employment end date

What to watch for with Cezanne HR and Loket

  • Each Dutch company has its own CompanyCode in Cezanne and its own employer in Loket. KoppelHet records those pairs, so an employee moving from one Dutch entity to another gets a new employment at the new employer in Loket.
  • Loket rejects a wage or working hours record whose start date is not later than the previous record. Cezanne does allow records with an earlier EffectiveFrom. KoppelHet therefore does not write such a retroactive correction itself, but puts it as a task with payroll.
  • For an ongoing employment Cezanne fills in 31 December 2999 as the end date. Loket then has no end date; KoppelHet only passes a real end date on as a termination, so nobody in Loket gets a departure in the distant future.
  • The working time pattern in Cezanne consists of an FTE table and a table with hours per day. Loket can record a two-week work pattern, with separate hours for even and odd weeks; KoppelHet fills it from Cezanne, so an alternating pattern is not flattened into an average in Loket.
  • A compensation item in Cezanne can be pro rata on the FTE. For every wage Loket asks whether the amount is a full-time wage. KoppelHet sends the full-time amount from Cezanne and sets that flag, so Loket calculates the part-time wage itself from the working hours.
  • A Cezanne token only sees what the user who gave consent may see on screen. An integration user with only the Dutch employer makes sure salaries from other countries never come near Loket.

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.

Price indication · Complex

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

What if HR changes a salary in Cezanne retroactively?

Then payroll gets a task with the old and new amount and the effective date. Payroll processes the correction in Loket, so the recalculation is right.

Do we need People PLUS+?

No. Without webhooks KoppelHet reads every hour; for payroll that is well in time.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Cezanne HR through OData (v7 dataservice.svc, JSON) with OAuth 2.0 after sign-in and consent - People, Addresses, BankDetails, Employments (CompanyCode, StartDate, TerminationDate), EmployeeWorkingTimePatternFTE, EmployeeWorkingTimePatternDetails and Compensation (CompItemCode, EffectiveFrom, EffectiveTo). Webhooks only with People PLUS+.
  • Loket through the Loket REST API with OAuth - PostConceptEmployeeByEmployerId, PostWageByEmploymentId (isGrossWageFullTime, grossWageType) and PostWorkingHoursByEmploymentId (deviatingHoursPerWeek, workPattern with oddWeeks and evenWeeks), with chain validation on the start date, and PatchTerminateByEmploymentId. Loket has an acceptance environment.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in Cezanne HRField in LoketNotes
Id van de persoonVrij veld bij de werknemerFixed key
People (FirstName, FamilyName)Voornaam en achternaam
Addresses (EffectiveFrom)Adres conceptwerknemer
BankDetails (IBAN)IBAN zonder spaties
Employments.CompanyCodeWerkgever in LoketOne code per employer
Employments (StartDate)Begindatum dienstverband
EmployeeWorkingTimePatternFTE en DetailsAfwijkende uren per week en tweewekelijks werkpatroon
Compensation (CompItemCode BASE, EffectiveFrom)Loon met ingangsdatum
TerminationDate (niet 2999-12-31)Einde dienstverband

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.