Payroll integration
Sympa to DATEV integration: Sympa's LODAS connector, and when KoppelHet does it differently
Sympa has its own DATEV Lodas Connector that sends employees, compensation, add-ons, one-off payments and absences every day as a delta file from Sympa to DATEV LODAS. KoppelHet only builds between Sympa and DATEV what that connector does not do, such as a delivery for DATEV Lohn und Gehalt or for several German entities.
What the integration does
Organisations that run HR in Sympa and have a German entity whose payroll runs at a tax adviser in DATEV send the firm changes every month. If the firm works with LODAS, Sympa's connector can take that over; with Lohn und Gehalt or a second German GmbH it remains manual work.
- With the tax adviser we establish whether the firm uses LODAS or Lohn und Gehalt, and how many client numbers there are.
- For one entity in LODAS the customer switches on Sympa's connector.
- For Lohn und Gehalt or a second entity KoppelHet reads the approved rows from Sympa through its own interface.
- KoppelHet delivers to DATEV before the cut-off date, through the import service or as a file the firm imports.
- The tax adviser reviews and takes over the data.
What to watch for with Sympa and DATEV
- Sympa's DATEV Lodas Connector sends a standardised LODAS delta file every day to SFTP or to the DATEV data centre. Lohn und Gehalt is not on the page; if the tax adviser works with it, a custom delivery is needed.
- The connector links one Sympa entity to one LODAS environment. If the organisation has two German GmbHs, each with its own client number, one connector only covers one of them; KoppelHet then splits the employees per entity across the client numbers.
- According to Sympa the connector fetches nothing back from DATEV. Payslips and payroll results stay with the firm, unless KoppelHet later fetches them through the Lohnauswertungsdatenservice and puts them in the file in Sympa.
- Salary rows in Sympa have an approval status, with Approved as value 5. KoppelHet requests only approved rows through its own interface, so a salary proposal still waiting for approval does not end up in the German payroll run.
- Sympa returns table rows valid in a period with since, until or at, if the table has validity settings. KoppelHet requests the valid rows per DATEV month, so a raise from the first of the month is processed in that month.
- An interface of the Sympa Integration API has no fixed field list; an administrator chooses which fields to expose. KoppelHet asks for an interface with only the German entity and the fields DATEV needs, so salaries from other countries stay out of view.
- Sympa charges a one-off € 2,106 for the connector plus a monthly fee by organisation size, invoiced a year in advance, and says the data must already be in Sympa. If German fields such as the tax ID are missing, the tax adviser fills them in DATEV.
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
Sympa already has a DATEV connector. Why KoppelHet?
For one entity in LODAS you do not need us. We come in with Lohn und Gehalt, with a second German entity or for the return route.
Does the tax adviser need to do anything?
Yes. The firm agrees how the files arrive, through the DATEV data centre or SFTP, and takes over every delivery.
Does this also work for Dutch employees in Sympa?
No, DATEV is for German payroll. For the Netherlands we connect Sympa with, for example, Nmbrs or AFAS.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Standard through Sympa's DATEV Lodas Connector (batch delta file in LODAS format to SFTP or the DATEV data centre, daily, one entity to one environment, nothing back).
- Custom work reads Sympa through the Integration API (OData, https://api.sympahr.net/api/{interface}) with X-ApiKey, $filter on modified and entity, since/until/at for valid rows and $expand with Approval eq 5; to DATEV through the Lohnimportdatenservice or a file the firm imports.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Sympa | Field in DATEV | Notes |
|---|---|---|
Sympa-entiteit | Mandant bij de Steuerberater | The connector does one entity to one LODAS environment |
Medewerkernummer in Sympa | Personalnummer | |
Dienstverband met geldigheidsperiode | Eintritt en Austritt | |
Salaristabel (Approval eq 5) | Festbezug met ingangsmaand | |
Toeslagen en eenmalige betalingen | Lohnarten | Through a lookup table approved by the firm |
Afwezigheid | Ausfallzeiten |
Related
Greenhouse → Sympa
Greenhouse to Sympa integration: hired candidate as a data card with contract row in Sympa
Recruitee → Sympa
Recruitee to Sympa integration: hired candidates as a data card in Sympa
SmartRecruiters → Sympa
SmartRecruiters to Sympa integration: ready to onboard becomes a data card in Sympa
Sympa → 4PS Construct
Sympa to 4PS Construct integration: fitters of the Dutch employer from Sympa in 4PS, with cost centre as a dimension