Payroll integration
Lucca to DATEV integration: German joiners, leavers and master data from Lucca to DATEV
An integration between Lucca and DATEV prepares new employees, personal data, bank account and leavers of the German entity from Lucca for DATEV LODAS or Lohn und Gehalt every pay month. Salary is not in the current Lucca API, so the integration delivers master data and joining and leaving; pay and hours are recorded by the tax adviser in DATEV.
What the integration does
Organisations that run HR in Lucca, often from France, and also have a German entity with payroll at a tax adviser in DATEV email the firm starters and leavers every month. The firm retypes names, date of birth, IBAN and social security number, and a typo only shows up on the payslip.
- HR creates the employee and employment in Lucca at a German establishment.
- Lucca sends a webhook; KoppelHet reads the employment and the personal record and checks the social security number and IBAN.
- Before the cut-off new employees, changes and leavers go to DATEV as master data; the tax adviser takes them over and adds pay and hours.
- KoppelHet writes the personnel number from DATEV back into the remoteId field of the employment in Lucca.
- What is not right, such as a social security number of the wrong length, appears on a list for HR.
What to watch for with Lucca and DATEV
- The current Lucca API has no salary resource; pay elements only sit in the older Pagga API, which is made for French payroll preparation. KoppelHet therefore sends no amounts to DATEV, and the tax adviser keeps the fixed pay in DATEV.
- The social security number in Lucca has a format frenchSSN, swissSSN or other, and only the first two are validated. A German social security number is therefore stored as other without validation; KoppelHet checks the length of twelve characters before the number goes to DATEV.
- For an employment in Lucca the legal entity cannot be set directly, but follows from the establishment of the first job position. KoppelHet selects German employees on that derived entity, so a transfer within France never reaches the firm.
- An employment in Lucca has a remoteId field for the number in another system, which can be changed through the API. KoppelHet puts the DATEV personnel number there, so HR sees in Lucca under which number someone is known at the firm.
- An empty end in Lucca means a permanent employment. KoppelHet passes a filled end date on a new employment as fixed-term, and an end date added later as the exit date.
- The personal record in the Lucca API holds no address, and the working-time arrangement only has a name and a holiday calendar, no hours. Address and weekly working time therefore stay with the tax adviser, and the integration does not overwrite them.
- Personal records in Lucca are filtered by establishment - the API only returns employees of establishments the integration has access to. KoppelHet only gets access to the German establishments, so sensitive data of French colleagues stays out of reach.
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
Why does salary not go along?
The current Lucca API has no salary resource. If the customer uses Lucca attributes for German salaries, salary can follow later as an extension.
Does leave go to DATEV too?
Not in the first version. Absence from Lucca 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.
- Lucca API (version 2024-11-01 in the Api-Version header, OAuth 2.0) with webhooks through webhook-endpoints. employments (legalEntity derived, status upcoming, active or deactivated, start.date, end.date, remoteId up to 200 characters, PATCH), employee-personal-records (scope employee-personal-records.readonly; birthDate, legalGender, insuranceNumber with format frenchSSN, swissSSN or other, bankAccount with format iban or other).
- To DATEV through the Lohnimportdatenservice (master 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 Lucca | Field in DATEV | Notes |
|---|---|---|
employment.remoteId | Personalnummer | Written back by KoppelHet |
employment.start.date | Eintrittsdatum | |
employment.end.date (leeg bij vast) | Befristung en Austrittsdatum | |
employee-personal-record.birthDate, legalGender | Geburtsdatum, Geschlecht | |
insuranceNumber (format other) | Sozialversicherungsnummer | Checked for length by KoppelHet |
bankAccount (format iban, accountIdentifier) | IBAN |
Related
Lucca → Active Directory
Lucca to Active Directory integration: accounts in your own domain based on Lucca
Lucca → ADP iHCM
Lucca to ADP iHCM integration: fixed and variable pay from Lucca Compensation to Dutch ADP payroll
Lucca → AFAS Profit
Lucca to AFAS integration: employees and pay of the Dutch entity from Lucca in AFAS
ASLucca → Arbodienst (SIVI)
Lucca to the occupational health service via SIVI: confirmed sickness per half day as absence reports