How do I connect DATEV to Leapsome?
Your accountant prepares DATEV first. Then an admin opens the DATEV integration in Leapsome, clicks 'Start authorization', enters the Beraternummer and Mandantennummer in Kombo Connect, and signs in with the accountant's SmartCard. After that, you configure export settings, wage types, absence codes and personnel numbers.
Leapsome connects to DATEV through Kombo, our integration partner. Leapsome sends employee master data, pay and absences to DATEV, your accountant runs payroll there, and Leapsome then pulls the finished payslips back and distributes them to employees.
Table of Contents
- Before you start
- How do I authorize the DATEV connection?
- How to configure the integration
- How do I send data to DATEV?
- How do I retrieve payroll documents?
- What triggers an eAU sick note request?
- Month-to-month routine
- What Leapsome does not do
- FAQ
- Glossary
Before you start
DATEV payroll is a three-way setup: your HR admin, your accountant, and Leapsome. The accountant goes first. Authorization cannot be completed until they have prepared their side, even if your company had DATEV connected to a previous HR system.
Who does what
| Role | German term | Responsibility |
|---|---|---|
| HR admin | Mandant (your company, as your tax office sees it) | Keeps employee data correct in Leapsome, runs exports, distributes documents |
| Accountant / tax office | Steuerberater, Steuerbüro, Kanzlei | Runs payroll in DATEV, owns DATEV access and permissions |
| DATEV administrator | DATEV-Administrator | Grants DATEV service rights, often the same person as the accountant |
Which DATEV system do you use?
Every DATEV client runs one of two payroll products, and several behaviors differ between them. Ask your accountant which one applies before you configure anything.
| Lohn und Gehalt (LuG) | LODAS | |
|---|---|---|
| Where it runs | Locally at the tax office | In the DATEV data center |
| Typical client | Smaller companies | Larger companies |
| Absence code | Ausfallschlüssel (a text code) | Unterbrechungsgrund (a number) |
What your accountant must complete first
Send these five points to your accountant before booking the authorization call. They happen inside DATEV, so only your accountant can confirm them.
- Check the login device: the accountant needs a DATEV SmartCard (or equivalent) with the rights "Bestellen / Vertrags- und Personendaten verwalten" and "Beraternummern verwalten". If either is missing, their DATEV administrator grants it in RVO.
- Confirm payroll is active: the service "Lohnabrechnung" must be active in DATEV Arbeitsplatz.
- Order the data services for your client: in DATEV Arbeitsplatz, go to Unsere Kanzlei > your client > MyDATEV > Mandantenregistrierung starten. Search for the service, select the consultant number and business relationship, and order it. This includes the Lohnauswertungsdatenservice, which Leapsome uses to retrieve payroll documents.
- Switch the services on in RVO: under "Personalwirtschaft", activate the service, select the correct Beraternummer and Mandantennummer, select all personnel numbers, and assign it to the login device used for authorization.
- On direct submission (LAuDS), share the data in the DATEV data center: in LuG this happens in the Datentransfer-Cockpit. In LODAS an Änderungszeichen (change flag) must be set.
Recommended sequence: send the accountant the preparation steps from the Kombo DATEV connection guide first. Once they confirm it is done, book a joint call of about 30 minutes for authorization. Your accountant needs their SmartCard or SmartLogin on hand for that call.
How do I authorize the DATEV connection?
- In Leapsome, go to Settings > Integrations and imports > HRIS integrations > Outbound Provisioning and click 'DATEV'. This opens the DATEV settings window.
- Confirm the prerequisites above are complete.
- Click 'Start authorization'. Kombo Connect opens in a new window.
- Choose the target system (LODAS or Lohn und Gehalt) and enter the Beraternummer (consultant number) and Mandantennummer (client number) your accountant provides. These are entered in Kombo Connect, not in Leapsome.
- Click 'Mit DATEV anmelden', choose SmartCard or mIDentity, select the certificate, and enter the PIN. If the PIN step times out, click 'Neu laden' and try again.
- Accept the consent screen and finish. Kombo validates the connection.
- Back in Leapsome, check that System, Advisor ID and Tenant ID show the right values. These fields are read-only in Leapsome and come from DATEV.
Which connector do you have? Your DATEV settings show a label under the connection:
- "Direct submission (Lohnaustauschdatenservice)": LAuDS.
- "File export (DATEV HR)": the older ASCII connector.
Some behaviors in this article differ between the two and are marked where they do.
How to configure the integration
1. Review your export settings
Admins choose which attributes Leapsome sends to DATEV by switching them on or off individually. New connections start with every field switched on.
Important: on direct submission (LAuDS), a field that is switched on but empty in Leapsome is sent as empty and clears the value your accountant has in DATEV. Choices such as "keine Angabe" or "0" clear it too. Before your first submission, either fill in those fields in Leapsome or switch them off. Fields that are switched off are not sent, and DATEV keeps its value.
2. Assign wage type numbers
Every compensation type you switch on needs a Lohnartennummer (wage type number) from your accountant. Wage type numbers run from 1 to 9999 for both LODAS and LuG. Ask your accountant for the full list in writing, one number per enabled compensation type.
On direct submission, a pay item without a wage type is skipped without an error message, so check this list before your first submission.
3. Choose which documents to import
Select the document types to pull back from DATEV: employee documents (payslips) and employer documents (reports). At least one type must be enabled, otherwise retrieval fails.
eAU (electronic sick notes) has its own tab in the DATEV settings, saved separately from document import. The 'Automated eAU retrieval' toggle appears once DATEV reports the eAU service as ready. See "What triggers an eAU sick note request?" below.
4. Connect your payroll policy
Go to Payroll > Policies > select a policy > Payroll integration > DATEV. Connecting the policy adds the DATEV-specific fields to the policy's Personal Info settings. Fields are only added if their whole subsection is switched on in your export settings.
Note: missing a DATEV field on a payroll policy later? Open your DATEV export settings and click 'Save' once. This adds every switched-on DATEV field to all active DATEV payroll policies, including ones connected earlier. You do not need to reconnect the policy.
The DATEV fields are visible to Super admins and Payroll admins by default. Adjust access under Settings > Employees > Profile fields and access.
5. Map your absence policies
Every absence policy that should reach DATEV needs a DATEV absence code. Absence codes are set per legal entity in the DATEV settings, and the payroll policy decides which absence policies are in scope.
- LODAS: choose an Unterbrechungsgrund (a number) from the fixed list.
- LuG: choose an Ausfallschlüssel (a text code) from the fixed list.
- Codes: your accountant supplies them. Settings will not save while a checked absence policy is unmapped.
Note: the LODAS code list has no paid-vacation code, so check vacation mappings with your accountant rather than assuming the closest match is correct.
6. Enter personnel numbers
Personnel numbers (Personalnummer) are how Leapsome matches each person to DATEV. A wrong or missing number is the most common reason an employee never reaches payroll.
- Valid range: 1 to 99999 for all systems. On direct submission, leading zeros make no difference, so 225 and 00225 are the same number.
- Payslip retrieval: matches the number exactly as stored, so 225 and 00225 will not match when documents are imported.
- Where to enter them: per employee on the DATEV tab of the profile, or in bulk using the "DATEV ID" column. A custom profile field named "DATEV ID" is not used for this.
- Source: ask your accountant for an export of current personnel numbers and copy from that, rather than typing from memory.
- New hires: your accountant creates the employee in DATEV first. Leapsome never creates employees in DATEV and never closes a personnel number.
7. Multiple legal entities
Each secondary legal entity can either use its own DATEV configuration or inherit the primary one (read-only). Exports stay scoped to the selected entity. Switched-on DATEV fields from all connections are added to every DATEV payroll policy.
On direct submission, a user with no legal entity on a multi-entity account is skipped. Assign a legal entity to every employee in scope.
8. Set permissions
| Task | Permission needed |
|---|---|
| Open the export dialog, export, submit | Manage payroll policies |
| Connect, authorize, change DATEV settings | Manage integrations (Super admins by default) |
| See and edit DATEV fields on profiles | Super admins and Payroll admins by default |
Setup checklist
- Accountant confirmed their preparation is complete, including the service used for payroll documents
- LuG or LODAS confirmed
- Beraternummer and Mandantennummer received
- Authorization completed and System, Advisor ID and Tenant ID checked in Leapsome
- Export fields reviewed: everything switched on is actually maintained in Leapsome
- Wage type numbers received in writing for every enabled compensation type
- Payroll policy connected and DATEV fields present (if not, save your export settings once)
- Absence policies mapped to DATEV codes
- Personnel numbers entered and cross-checked against DATEV
- Payroll admins have "Manage payroll policies"
- First export reviewed with the accountant
How do I send data to DATEV?
Once the payroll cycle contains the information you want to send, go to the cycle in the relevant payroll policy and choose Actions > 'Export master data to DATEV' (file export) or 'Submit' (direct submission).
Important: Export and Submit are available on any payroll cycle that is not in the future, including open, unapproved cycles. Agree with your team that only approved cycles are submitted.
What gets sent
- Stammdaten (master data): personal information, bank details, tax details, fixed salary, fixed and recurring compensation, working hours.
- Bewegungsdaten (transaction data): absences, one-time and variable compensation, hours for hourly workers.
File export (ASCII) and direct submission (LAuDS) compared
| File export (ASCII) | Direct submission (LAuDS) | |
|---|---|---|
| How data travels | One file per cycle and legal entity, placed in your accountant's DATEV inbox or downloaded and sent manually | Separate API calls per employee, landing directly in DATEV |
| Who imports it | Your accountant, manually in DATEV | No manual import needed |
| Validation | Leapsome shows warnings. A missing personnel number refuses the transfer, though a manual download still works | Leapsome pre-checks each employee before sending. Failures are per employee and appear on the Sync tab |
| Correcting a sent amount | Re-export the cycle | One-time and variable pay: a reversal line, then the new amount. Fixed salary and hourly wage are updated in place |
| Removing a compensation | Re-export without it | Reversal to zero |
| Field switched on but empty | Written as an empty column | Clears the value in DATEV |
On a direct submission connection, the ASCII export is blocked. Mixed setups work per legal entity.
Which data is used: approved snapshot or live data?
| File export (ASCII) | Direct submission (LAuDS) | |
|---|---|---|
| Pay (monthly amounts, salary, hourly wage) | Approved cycle: the snapshot taken at approval. Open or reopened cycle: current data | The snapshot taken at approval |
| Master data and absences | Same as pay | Always the current data at the moment of sending, even on an approved cycle |
On direct submission, a profile edit made after approval reaches DATEV on the next Submit or Retry. Pay changes after approval need the cycle to be reopened.
How to check the Sync tab
On direct submission, each employee's result appears on the Sync tab of the payroll cycle. Fix the value flagged there and click 'Retry' to send that employee again from their current data.
An employee can fail on one step while others succeed, so check the whole list rather than assuming a clean run because the submission completed.
Fields DATEV maintains itself
Five fields are never written by direct submission, and there is no file export fallback for them. Your accountant maintains them directly in DATEV.
| Field | German term | Systems |
|---|---|---|
| Marital status | Familienstand | LODAS and LuG |
| Disability status | Schwerbehinderung | LODAS only (the field does not exist for LuG) |
| Notice date | Kündigungsdatum | LODAS and LuG |
| Income tax class | Steuerklasse | LODAS only (the field does not exist for LuG) |
| Church tax affiliation | Konfession | LODAS and LuG |
Note: two further fields are shown in the export settings but never sent on direct submission: payment method and the entry date of the employment period. The fax number is never exported on either connector.
What happens with unpaid leave?
The DATEV export includes the full, unreduced fixed salary for unpaid leave, and DATEV applies the reduction. This only works if the absence reaches DATEV, through your absence mapping or a manual entry. With a mix of fixed and hourly periods, a reduced amount is sent instead.
How do I retrieve payroll documents?
- Your accountant runs payroll in DATEV and the documents are produced there.
- Your accountant tells you they are ready, or you agree a fixed date, e.g. the 25th of each month.
- In the payroll cycle, go to Actions > 'Retrieve payroll documents'. Only the document types enabled in your integration settings are pulled.
- Preview them in the cycle's Imported documents tab.
- Click 'Distribute documents'. Each payslip then appears in the employee's profile under Documents.
Documents are matched only to people in that cycle, within the cycle's legal entity, whose personnel number matches DATEV.
What triggers an eAU sick note request?
eAU (elektronische Arbeitsunfähigkeitsbescheinigung) requests the electronic sick note from the employee's health insurer through DATEV, so no paper certificate is needed. It works on both connectors and uses the DATEV connection of the employee's legal entity.
All of these must be true:
- The employee has a payroll policy assigned with DATEV as the payroll provider.
- Automated eAU is switched on for the employee's legal entity.
- The employee has a DATEV personnel number.
- Health insurance type is not "private". An empty insurance type also qualifies.
- The absence is sick leave, and its absence policy requires a certificate after a set number of days.
- The absence is longer than that threshold.
Note: the threshold counts calendar days, weekends included. If a policy requires a certificate after 4 days, 3 or 4 days of sick leave trigger no request and 5 days does. A Friday-to-Monday absence counts as 3 days.
Note: the request fires as soon as the absence is entered or its dates change. Approval is not checked, so a pending sick leave request also triggers an eAU request.
If the health insurer cannot answer an eAU request before the eAU timeout, it stays pending and is then marked as outdated. Ask the employee for the certificate in that case.
Month-to-month routine
- Before your cut-off date, confirm new hires have a personnel number created in DATEV, and enter it in Leapsome.
- Review the payroll cycle: compensation changes, bonuses, absences.
- Approve the cycle, then click 'Submit' (direct submission) or 'Export' (file export).
- Check the Sync tab for failed employees, fix the values, and click 'Retry'.
- Confirm with your accountant that the data arrived.
- When documents are ready, retrieve, preview and distribute them.
Most DATEV problems come down to three things:
- Personnel numbers: a number that does not match.
- Export fields: a field switched on that nobody maintains.
- Ownership: no agreement on who maintains which field.
Settle all three at setup and the monthly run stays quiet.
What Leapsome does not do
- Create employees in DATEV: the personnel number must already exist there.
- Close or release a personnel number in DATEV: tell your accountant when someone leaves so they can handle it.
- Pull DATEV changes into Leapsome profiles: only payroll documents and eAU results come back.
Maintain in Leapsome everything Leapsome sends, and switch off anything you will not maintain. Ask your accountant not to edit the sent fields in DATEV, because the next export overwrites them.
FAQ
Why is a DATEV field missing from our payroll policy?
Open your DATEV export settings and click 'Save' once. This adds every switched-on DATEV field to all active DATEV payroll policies. If a field is still missing, check that its whole subsection is switched on in the export settings.
Why did retrieving payroll documents return 0 documents?
Check in this order: the personnel number is missing or different, the employee is not in this cycle, the document type is not switched on in the integration settings, DATEV has not finished yet, or you are looking at a different accounting month.
Why did a value we maintain in DATEV disappear?
That field is switched on in your export settings but was empty in Leapsome when you submitted, so DATEV's value was cleared. Either fill in the value in Leapsome or switch the field off. Your accountant restores the DATEV value.
Can we revoke the connection and reconnect to start fresh?
No. Revoking and then reconnecting loses all your export settings. Use 'Reconnect' instead, which keeps your export and import settings and the eAU and document toggles.
What does the "Action needed: reconnect to DATEV" banner mean?
Reconnect using the 'Reconnect to DATEV' button. The banner only appears on a legal entity's own DATEV connection, not on one inherited from the primary entity. After reconnecting, the export and import tabs stay hidden until DATEV's first sync completes.
What happens if everyone loses access to DATEV at the same time?
The authorization has dropped, often after a SmartCard change. An admin with "Manage integrations" needs to reconnect and reauthorize.
Why is an employee missing from the submission with no error?
They have no personnel number, so they were skipped. Add the number on their DATEV tab and click 'Retry'.
Why does an employee show as failed on the Sync tab?
Open the message on the Sync tab. The usual causes are an invalid or duplicate personnel number, weekly hours that do not match the day-by-day split, or a value that failed a format check such as IBAN, BIC, email, phone or country. Correct the value and click 'Retry'.
Why do we get a duplicate personnel number warning for a rehire?
Rehires and contract-type changes often reuse a number, and the duplicate check includes deactivated employees. Agree a new number with your accountant, or have them deactivate the old record correctly. The check cannot be switched off.
Can we still get an ASCII file as a fallback?
Not on a direct submission connection. The export button is disabled once every legal entity is on direct submission, and there is no fallback for the fields DATEV maintains itself.
Glossary
| Term | Meaning |
|---|---|
| Abrechnungsmonat | Accounting month: the payroll month a value is booked into |
| Ausfallschlüssel | Absence key in LuG: a text code describing the absence |
| Beraternummer | Consultant number: identifies your tax office in DATEV |
| Bewegungsdaten | Transaction data: absences, bonuses, hours for a given month |
| eAU | Electronic sick note, fetched from the health insurer through DATEV |
| LAuDS | Lohnaustauschdatenservice: DATEV's per-employee interface, shown in Leapsome as "Direct submission" |
| Lohnartennummer | Wage type number, 1 to 9999: tells DATEV what a payment is and how to tax it |
| Lohnauswertungsdatenservice | DATEV service Leapsome uses to retrieve payroll documents |
| LuG | Lohn und Gehalt: DATEV payroll run locally at the tax office |
| LODAS | DATEV payroll run in the DATEV data center |
| Mandantennummer | Client number: identifies your company within your tax office |
| Monatsabschluss | Month-end close by your accountant |
| Personalnummer | Personnel number, 1 to 99999: how Leapsome matches a person to DATEV |
| RVO | Rechteverwaltung Online: where DATEV services are switched on for a login device |
| Stammdaten | Master data: name, address, bank details, tax details, fixed salary |
| Sync tab | Payroll cycle tab showing per-employee submission results, with Retry |
| Unterbrechungsgrund | Absence reason in LODAS: a number |