Payroll integration
Deel to DATEV integration: employees of your own German GmbH from Deel to the tax adviser
An integration between Deel and DATEV prepares the employees of your own German company from Deel, with name, start date, pay and last working day, in DATEV for the tax adviser. Contractors and EOR employees in Deel stay out of DATEV, because Deel pays them itself.
What the integration does
Organisations that use Deel for contractors and EOR in several countries, and also have their own German GmbH paid in DATEV by a tax adviser, manage their German employees in Deel as well. Without an integration, new German colleagues and leavers go to the office by email.
- KoppelHet gets a Deel API token with read rights on people and employments, and subscribes to the contract events.
- On an event KoppelHet fetches the employment and checks hiring type and legal entity.
- Only employees of the German GmbH are converted into master and movement data for DATEV.
- The delivery goes to the data centre through the Lohnimportdatenservice or as an ASCII file to the office.
- The tax adviser completes the German tax data and takes over the data.
What to watch for with Deel and DATEV
- Deel holds contractors, EOR employees and employees of your own entities side by side. KoppelHet filters on the hiring type for your own employees and on the German legal entity, so a German EOR employee, whom Deel pays itself, never also ends up in DATEV.
- Deel has two hiring types for your own employees, hris_direct_employee and direct_employee. At the start KoppelHet establishes which type is used in your Deel environment, so no German employee slips between the filters.
- Pay sits in Deel per employment as an amount with a scale and a currency. KoppelHet checks that the currency is euro and converts a yearly amount to the monthly fixed pay DATEV expects.
- Each German company is its own client legal entity in Deel and has its own client number with the tax adviser. KoppelHet chooses the client based on that legal entity, not on country or work location.
- Deel only returns national numbers such as a social security number if that feature is enabled for the organisation and the request is not redacted. Without that data the tax adviser enters the tax ID and social insurance number in DATEV, and the integration does not overwrite them.
- If an employee moves from EOR to your own GmbH, that is a new employment in Deel. In DATEV it becomes a hire with the new start date; the EOR period has already been paid by Deel.
- Deel signs its webhooks. KoppelHet only accepts events with a valid signature and also compares the German employees in Deel daily with what has already gone to DATEV, so a missed event does not miss the run.
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
Do our German EOR employees go to DATEV as well?
No. They are paid by Deel. Only employees of your own German company go to the tax adviser.
What if we want to use Deel for German payroll as well?
Then DATEV is no longer needed and this integration falls away. This page is for organisations that keep their tax adviser.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through the REST API: GET people with hiring_types (hris_direct_employee or direct_employee) and employments (start_date, payment with rate, scale and currency, client_legal_entity, termination_last_day); additional_details with national numbers only with a feature flag. Signed webhooks on contract events.
- To DATEV through the Lohnimportdatenservice (master and movement data through the DATEV data centre, activated by the tax adviser in DATEV Arbeitsplatz, access for partner software after onboarding) or an ASCII file the office imports into LODAS.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in DATEV | Notes |
|---|---|---|
employments[].employee_number of worker_id | Personalnummer | |
first_name, last_name, birth_date | Vorname, Name, Geburtsdatum | |
addresses | Anschrift | |
employments[].start_date | Eintrittsdatum | |
employments[].payment (rate, scale, currency) | Festbezug of Stundenlohn | Scale decides month, year or hour |
client_legal_entity | Mandant | Each German company its own client |
termination_last_day | Austrittsdatum |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions