Cezanne HR logoDATEV logo

Payroll integration

Cezanne HR to DATEV integration: the German company from Cezanne HR to the tax adviser

An integration between Cezanne HR and DATEV prepares new employees, salary changes, working time and leavers of the German company from Cezanne HR for DATEV LODAS or Lohn und Gehalt every pay month. Cezanne HR has no DATEV integration, so KoppelHet reads Cezanne's OData API and delivers master and movement data that the tax adviser takes over.

What the integration does

Organisations that manage HR for several countries in Cezanne HR and have a German company with payroll at a tax adviser in DATEV send the firm an export every month without an integration. The firm then has to work out itself which lines are new and which salary is already part-time.

  1. HR records a starter, compensation item, FTE change or leaver in Cezanne for the German company.
  2. With an integration user who only sees the German company, KoppelHet reads employees, employments, working time and compensation.
  3. KoppelHet compares with the previous delivery and converts what takes effect in the pay month to master and movement data.
  4. Before the cut-off the month goes to DATEV; the tax adviser takes over the data.
  5. Backdated corrections carry their original effective date, so the firm calculates the back pay.
Cezanne HR → KoppelHet → DATEVSOURCECezanne HRTARGETDATEVKoppelHetmapping · logging · monitoringCezanne HR → KoppelHet → DATEVSOURCECezanne HRTARGETDATEVKoppelHetmapping · logging · monitoring
Out: Employees of the German company · Salary as a compensation item with effective date · FTE and hours per week · Bank details and end of employment

What to watch for with Cezanne HR and DATEV

  • In Cezanne every employment belongs to a CompanyCode. KoppelHet only takes employments of the German company, and if an organisation has more than one German company, each company gets its own client number at the firm.
  • An ongoing employment gets 31 December 2999 as its end date in Cezanne. That is not a leave; KoppelHet only sends a real end date as the exit date to DATEV, so no termination in the distant future appears at the firm.
  • A compensation item in Cezanne can be calculated pro rata to the FTE. At the start we fix whether the amount in Cezanne is the full-time or the part-time amount, so the fixed pay in DATEV is the monthly amount the employee actually receives.
  • Working time sits in Cezanne in an FTE table and a table with hours per day. KoppelHet adds up the hours per week for the weekly working time in DATEV and flags a pattern that differs per week, instead of sending an average.
  • A salary line in Cezanne can get an EffectiveFrom in the past. KoppelHet delivers such a correction with the original date, so the tax adviser calculates the back pay in DATEV over the right months.
  • Through the API a Cezanne token sees exactly what the user who gave consent may see in the screen. KoppelHet works with an integration user who only sees the German company, so salaries of UK or other colleagues never end up in a delivery for DATEV.
  • Webhooks are only in the People PLUS+ package. Without that package KoppelHet reads the German company daily in the week before the cut-off through OData, with a filter on the company and on LastModifiedDate, and only the fields DATEV needs.

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

Do we need People PLUS+?

No. With webhooks it is faster, but for one German payroll run a month a daily run in the week before the cut-off is enough.

Does absence go along too?

Not in the first version. Absence to DATEV can follow later as an extension.

Technical details for IT

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

  • Cezanne HR through the OData API (v7 dataservice.svc, JSON) with OAuth 2.0 after sign-in and consent of the integration user - People, Addresses, BankDetails, Employments (CompanyCode, StartDate, TerminationDate), EmployeeWorkingTimePatternFTE, EmployeeWorkingTimePatternDetails and Compensation (CompItemCode, EffectiveFrom, EffectiveTo), with $filter and $select. Webhooks only with People PLUS+.
  • To DATEV through the Lohnimportdatenservice (master and movement data via the DATEV data centre, activation in DATEV Arbeitsplatz by the tax adviser, only for selected software) or an ASCII file the firm loads into LODAS or Lohn und Gehalt itself.

Which fields are transferred

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

Field in Cezanne HRField in DATEVNotes
Employments.CompanyCodeMandant (Beraternummer en Mandantennummer)One German company per client number
People (namen, geboortedatum) en AddressesPersönliche Daten en Anschrift
BankDetailsBankverbindung
Employments.StartDateEintrittsdatum
Employments.TerminationDateAustrittsdatumOnly a real date, not 31-12-2999
EmployeeWorkingTimePatternFTE en -DetailsWochenarbeitszeit
Compensation (CompItemCode BASE, EffectiveFrom, EffectiveTo)Festbezug met Lohnart

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.