Payroll integration
Dayforce to DATEV integration: German employees from Dayforce ready in LODAS or Lohn und Gehalt
With an integration between Dayforce and DATEV, new German employees, changes in hours and salary, bank details and leavers from Dayforce go to the tax adviser's DATEV payroll program, where they are reviewed and taken over. KoppelHet builds the delivery on Dayforce's REST API.
What the integration does
Organisations that use Dayforce as their HR system and have German payroll processed in DATEV by a tax adviser email the changes every month without an integration. An hours change that takes effect next month in Dayforce then often reaches the office too late or in the wrong month.
- KoppelHet gets an API user in Dayforce with a role that may only see the fields for DATEV.
- Every day KoppelHet fetches the changed employees and reads their data on the effective date of the change.
- Only employees with a work assignment at a German location go through; KoppelHet converts them into master and movement data for DATEV.
- The delivery goes to the DATEV data centre through the Lohnimportdatenservice or as an ASCII file to the office.
- The tax adviser takes over the data; KoppelHet reports what is still open before the cut-off.
What to watch for with Dayforce and DATEV
- Dayforce stores work assignment, status and compensation with a start and end date. KoppelHet reads each change on its own effective date, so an hours increase from the first of next month also lands in that DATEV month and not earlier.
- A field only comes out of Dayforce if the API user's role has rights on it. An empty salary or IBAN for a German starter is therefore usually a missing right; KoppelHet then sends no partial record to the tax adviser.
- Dayforce holds employees from every country of the organisation. KoppelHet selects on a work assignment with a German location, and with several German companies on the right company, because each has its own client with the office.
- In DATEV master data and monthly movements are two kinds of delivery. A fixed salary from Dayforce goes as master data, a one-off payment as a movement in the month of payment on the wage type the office specifies.
- Dayforce identifies an employee by the XRefCode, which is also part of the API call per employee. If the tax adviser uses their own personnel numbers, KoppelHet keeps the office's number per XRefCode, so a rehire does not arrive in DATEV as a new person.
- German tax and social insurance data, such as tax class and health insurer, is usually not in Dayforce. The tax adviser records it in DATEV, and the integration does not overwrite it.
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
Who switches on the import service in DATEV?
The tax adviser, in DATEV Arbeitsplatz. Without that step nothing arrives.
Does this work if we use Dayforce Payroll for other countries?
Yes. The integration only reads the German employees; other countries stay in their own payroll.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the REST API with the company name in the URL - changed employees through the change-date filters of the Employees endpoint, details with expand for EmploymentStatuses, WorkAssignments, Addresses, DirectDeposits and CompensationSummary, with contextDate for the state on a date. Fields only with field-level access in the API user's role.
- To DATEV through the Lohnimportdatenservice (ASCII import of master and movement data through the DATEV data centre, takeover at the press of a button, status for source and user, activation in DATEV Arbeitsplatz) or an ASCII file for LODAS. Access for partner software after onboarding on the DATEV Developer Portal.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in DATEV | Notes |
|---|---|---|
XRefCode | Personalnummer | Or a lookup to the office's numbers |
FirstName, LastName, BirthDate | Vorname, Name, Geburtsdatum | |
Addresses (thuisadres) | Anschrift | |
EmploymentStatuses (start) | Eintrittsdatum | |
WorkAssignments (uren) | Wöchentliche Arbeitszeit | |
CompensationSummary | Festbezug | Converted to the monthly amount |
DirectDeposits | Bankverbindung (IBAN) |
Related
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