Payroll integration
Simployer to DATEV integration: German employees from Simployer One with salary code to DATEV
An integration between Simployer and DATEV prepares new employees, salary changes, bonuses and leavers of the German entity from Simployer One for DATEV LODAS or Lohn und Gehalt every pay month. Simployer has no DATEV integration of its own, so KoppelHet reads the HRM One API and uses the salary code from Simployer as the wage type.
What the integration does
Organisations that record HR in Simployer One and have a German entity with payroll at a tax adviser in DATEV send the firm a list every month without an integration. Simployer is built for Scandinavian payroll, and what is automatic there remains manual work for Germany.
- HR records a starter, salary change, bonus or leaver in Simployer One.
- Simployer sends a webhook; KoppelHet verifies the signature and fetches the employee, employment and compensation.
- KoppelHet selects employments with country Germany and converts the salary code to the firm's wage type.
- Before the cut-off master data and the month's movement data go to DATEV; the tax adviser takes them over.
- A salary code without a wage type or an amount in another currency appears on a list for HR.
What to watch for with Simployer and DATEV
- A fixed salary and a recurring allowance each have their own salaryCode in Simployer One. With it HR records in Simployer itself which wage type of the tax adviser belongs to it; KoppelHet does not send a code missing from the translation table, but flags it.
- A bonus in Simployer has a payoutDate, separate from the fixed salary. KoppelHet delivers it as movement data in the pay month of that date, not as a change to the fixed pay.
- Every employment in Simployer has its own country. KoppelHet only takes employments with country Germany, so colleagues from Norway or Sweden never end up in a delivery for the tax adviser.
- The employee.offboarded webhook only arrives on the day the leave takes effect. For DATEV that is too late, because the final payslip is calculated earlier; KoppelHet therefore reads changed employments every day and picks up an end date as soon as HR records it.
- Simployer stores a currency and an exchange rate with a salary, plus a converted base amount. DATEV calculates in euros; KoppelHet only sends amounts in euros and flags a German salary in another currency, instead of converting it.
- The social security number field in Simployer has a country with it, with the Scandinavian countries first. KoppelHet takes over a German social security number with country DE; a number from another country does not go to DATEV, and the firm fills it in itself.
- Simployer only signs webhooks if a secret of at least 32 characters was set when configuring them, and gives every change a fixed eventId. KoppelHet always sets a secret, verifies the signature and uses the eventId so a repeated delivery is not processed twice.
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
Does this also work with Simployer Classic?
This page is about Simployer One. Classic has different APIs and a different sign-in; we look at that per customer.
Do payslips go back to Simployer?
Not in the first version. That can follow later as an extension, with DATEV's Lohnauswertungsdatenservice.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Simployer One through the HRM One API (api.alexishr.com/v1) with an access token with owner rights. GET /employee (employeeNumber, ssn, ssnCountry, bankAccount, homeAddress), GET /employment with a filter on updated (country, startDate, endDate, effectiveEndDate, rate), GET /compensation (amount, currency, exchangeRate, payoutPeriod, effectiveDate, salaryCode), GET /additional-compensation and GET /bonus-compensation (payoutDate, currency). Webhooks employee.created, employee.updated and employee.offboarded with X-Simployer-Signature (HMAC-SHA256 over body and timestamp).
- To DATEV through the Lohnimportdatenservice (master and movement 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 Simployer | Field in DATEV | Notes |
|---|---|---|
employeeNumber | Personalnummer | Text in Simployer; agreed with the firm |
firstName, lastName, birthDate | Vorname, Familienname, Geburtsdatum | |
bankAccount (iban, bic) | Bankverbindung | |
employment (country DE, startDate, endDate) | Eintrittsdatum en Austrittsdatum | |
compensation (amount, payoutPeriod, effectiveDate, salaryCode) | Festbezug met Lohnart | |
additional-compensation (salaryCode, effectiveDate, endDate) | Festbezug met eigen Lohnart en einde | |
bonus-compensation (amount, payoutDate) | Bewegungsdaten in de maand van uitbetaling |
Related
Recruitee → Simployer
Recruitee to Simployer integration: hired candidates with employment and salary in Simployer One
Simployer → Active Directory
Simployer to Active Directory integration: accounts in your own domain from Simployer
Simployer → ADP iHCM
Simployer to ADP iHCM integration: salary, bonuses and end of employment from Simployer One to ADP iHCM
Simployer → AFAS Profit
Simployer to AFAS integration: Dutch employees from Simployer One in AFAS payroll