Payroll integration
Rippling to DATEV integration: Rippling's tax adviser route, and what KoppelHet adds
For organisations that stay with their tax adviser Rippling has its own route to DATEV, where Rippling supplies master and movement data per report and the firm uploads the payslips back into Rippling every month. KoppelHet only builds between Rippling and DATEV what that route does not do, such as a delivery the tax adviser takes into LODAS or Lohn und Gehalt without a report.
What the integration does
Organisations that use Rippling for HR worldwide, but leave German payroll with a tax adviser using DATEV, send the firm an overview of new hires, salaries and leavers every month. There the same data is entered into DATEV again.
- KoppelHet gets a Rippling token with only the scopes for workers and the necessary expansions.
- Every day KoppelHet reads the changed employees and keeps only your own German entity.
- Before the cut-off date the delivery goes to DATEV, through the import service or as an ASCII file.
- The tax adviser reviews and takes over the data in the payroll program.
- Withdrawn offers and backdated changes go on a separate list for the firm.
What to watch for with Rippling and DATEV
- Rippling also pays German employees itself and then sends booking data to accounting through the DATEV Buchungsdatenservice. For those staying with their tax adviser, Rippling supplies master and movement data per report, and the firm uploads the payslips back into Rippling once a month in bulk.
- Every entity in Rippling has a management type, such as PEO, EOR or COR. KoppelHet only sends employees of your own German entity, with country code DE, and never anyone Rippling employs as EOR in Germany.
- Rippling has country fields for national numbers from the US, Canada and New Zealand, but not for Germany. Tax ID and social insurance number are therefore not in a standard field; the tax adviser fills them in DATEV, and the integration does not overwrite them.
- For salaried staff Rippling calculates an hourly wage based on forty hours a week, and for hourly workers an annual amount on the same basis. A German contract of, say, 38 hours would then give a wrong amount; KoppelHet only takes the annual salary for salaried staff and only the hourly wage for hourly workers.
- A salary change has its own effective date in Rippling. If it falls in a month DATEV has already processed, KoppelHet includes the change with that date in the delivery and on the list for the firm, so the tax adviser calculates the back pay deliberately.
- A termination in Rippling can also be a declined, rescinded or reneged offer. If such a person is already in DATEV, KoppelHet sends no ordinary termination but a notification, because the firm has to reverse the registration with the health insurer differently.
- DATEV only offers the Lohnimportdatenservice for selected systems, and the user takes over each delivery with one click. Without access to that service KoppelHet delivers an ASCII file the firm imports into LODAS; we choose that with the tax adviser at the start.
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
Why not use Rippling's own German payroll?
That is possible, and then this integration is not needed. This page is for organisations that keep their tax adviser.
What does Rippling's Buchungsdatenservice link do?
According to Rippling it sends payroll bookings to accounting in DATEV. That is bookkeeping, not a delivery for payroll processing.
Does the tax adviser need to do anything?
Yes. The firm switches on the import service in DATEV, or agrees to import an ASCII file, and takes over every delivery.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Rippling through the REST API (GET workers with expand on legal_entity, employment_type and compensation; filter on updated_at and status; termination_details.type including OFFER_DECLINED, RESCIND and RENEGE), with scope workers.read and a bearer token.
- To DATEV through the Lohnimportdatenservice (master and movement data, enabled in DATEV Arbeitsplatz, only for selected third-party systems) or an ASCII file for LODAS.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in DATEV | Notes |
|---|---|---|
legal_entity (country.code DE, management_type) | Mandant bij de Steuerberater | No EOR or PEO entities |
employment_type.type EMPLOYEE | Filter: geen contractors | |
start_date | Eintrittsdatum | |
compensation.annual_compensation (EUR) | Festbezug per maand | Annual amount divided by twelve |
compensation.hourly_wage | Stundenlohn | Hourly workers only |
compensation.salary_effective_date | Ingangsmaand van de wijziging | |
end_date, termination_details.type | Austrittsdatum, of melding bij een ingetrokken aanbod |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → 4PS Construct
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension