Learn how to use the Kombo DATEV integration to request and retrieve eAU certificates.
The Kombo DATEV eAU endpoints are available for the following integrations: DATEV HR
, DATEV LUG (legacy)
, and DATEV LODAS (legacy)
. Learn more about the DATEV variants here.
We only offer the DATEV integration to customers subscribed to our DATEV package.
To use the eAU endpoints, you must have the Manage eAU
permission enabled in your scope config.
You can allow your customers to opt-out of the eAU process by setting the permission to optional
. In this scenario, you must verify whether the permission is granted by using our Verify eAU Permission endpoint.
The corresponding service within DATEV is called DATEV Lohnaustauschdatenservice
.
To verify an employee’s sick leave, you must initiate an eAU request. This request triggers a process within the employee’s health insurance to confirm whether a sick leave was officially reported by a doctor.
Before requesting an eAU certificate, the following legal preconditions must be met:
The provided start_date
can be any day within the reported AU period. The health insurance will return the eAU certificate if the provided start_date
is between the AU’s start and end date.
Legally, employees must issue an eAU from their doctor by the fourth working day of their sick leave. However, employers can choose to shorten this period. If the sick leave lasts fewer than four days, an eAU certificate is not legally required.
You can request an eAU certificate up to four years retrospectively, but not before October 1, 2021. Doctors may issue eAU certificates up to three days retroactively.
To create an eAU request, call our Create eAU Request endpoint with the following details:
A successful eAU request creation returns an eau_id
, which you will use to query the request’s status.
Once created, the health insurance processes the eAU request and provides feedback within approximately 14 days.
Use the Get eAU Request Status endpoint with your received eau_id
to check the request status.
Note: DATEV APIs must be used efficiently. No webhook or notification mechanisms exist for status changes. Therefore, you must periodically poll the status. Avoid polling more than twice daily.
When you fetch the status we will return an object like this:
Initially, while the health insurance is processing the request, the feedbacks_from_health_insurance
array in the response is empty. You can consider the request as pending.
Once the health insurance has processed the request, the feedbacks_from_health_insurance
array will contain one or multiple feedbacks. If any errors occurred, they will be listed under the error_block_list
array.
Some feedback states are not final and can change over time. The response will include an automatic_feedback_until
date, indicating until when further polling may lead to updates.
A feedback from the health insurance does not automatically mean that the eAU is valid. You need to validate the eAU by examining the flag_current_work_incapacity
, which can have these values:
Flag 1: Health Insurance Not Responsible
Flag 2: Incapacity for Work
Flag 3: Hospitalization | Flag 6: Partial Inpatient Treatment
Flag 4: eAU or Hospitalization Report Not Found
Flag 5: Rehabilitation or Prevention
Flag 7: Under Verification
Flag 8: Other Evidence Available
Flag 9: Forwarding Procedure
If the employee has a sick leave that is longer than what was returned in the initial eAU request its possible that the doctor has issued a follow-up certificate. In this case you will need to create a new eAU request with the new start date (end date of the eAU plus 1 day).