Payroll integration
BambooHR to DATEV integration: German changes from BambooHR for the tax adviser in DATEV
An integration between BambooHR and DATEV prepares new German employees, salaries with their effective date, one-off payments and leavers from BambooHR in DATEV, where the tax adviser reviews and takes them over. KoppelHet builds the delivery on BambooHR's API and delivers through DATEV's import service or as an ASCII file.
What the integration does
Organisations that use BambooHR and have a German entity paid in DATEV by a tax adviser send the office an export of changes every month. What changes in BambooHR after that export, or takes effect retroactively, the office only sees a month later.
- KoppelHet has a separate user created in BambooHR that only sees the German employees and the fields for DATEV, with its own API key.
- Webhooks and an hourly round over changed tables report new data.
- KoppelHet converts the data into master and movement data, with the office's wage types.
- The delivery goes to the DATEV data centre through the Lohnimportdatenservice, or as an ASCII file to the office.
- The tax adviser takes over the data in LODAS or Lohn und Gehalt.
What to watch for with BambooHR and DATEV
- BambooHR stores salary as a table with an effective date per row. If HR backdates a rise by a month, it goes to DATEV with the original date, so the tax adviser calculates the back pay in the right month.
- A salary in BambooHR can be per hour, per month or per year. DATEV has a fixed monthly amount and an hourly wage as separate kinds; KoppelHet converts a yearly salary to the monthly amount and keeps an hourly wage hourly.
- BambooHR sends no webhooks for custom tables. If one-off payments or German data such as the tax ID sit in such a table, KoppelHet fetches them in the hourly round over changed table data.
- BambooHR has no standard field for an IBAN, and DATEV needs the bank details to pay. KoppelHet uses an extra field in BambooHR, or the tax adviser enters the IBAN in DATEV; we choose at the start.
- BambooHR's API key belongs to a user and gets that user's rights. With a separate user who only sees the German entity, the integration cannot send salaries of colleagues from other countries to the office.
- What the office completes in DATEV, such as tax class, health insurer and social insurance number, is not overwritten by the integration. BambooHR has no standard fields for those, so the tax adviser remains the source there.
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 the tax adviser need to do anything?
Yes. The office switches on the import service in DATEV, or agrees to import an ASCII file itself, and takes over every delivery.
Do payslips go back to BambooHR?
Not in the first version. That can follow later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- BambooHR through webhooks on changed fields and the endpoint for changed table data (jobInfo, compensation, employmentStatus and custom tables) by timestamp; salary from payRate and paidPer, end from terminationDate. Webhooks do not work for custom tables. API key of a separate user with limited rights.
- To DATEV through the Lohnimportdatenservice (master and movement data as an ASCII import through the DATEV data centre, activated by the tax adviser, only for selected partner software) 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 BambooHR | Field in DATEV | Notes |
|---|---|---|
employeeNumber | Personalnummer | |
firstName, lastName, dateOfBirth | Vorname, Name, Geburtsdatum | |
hireDate | Eintrittsdatum | |
compensation: payRate, paidPer, startDate | Festbezug of Stundenlohn | Hourly stays hourly; yearly becomes a monthly amount |
Eenmalige betaling (extra tabel) | Lohnart (Bewegungsdaten) | Through a lookup to the office's wage types |
IBAN (extra veld) | Bankverbindung | |
terminationDate | Austrittsdatum |
Related
Ashby → BambooHR
Ashby to BambooHR integration: hire, changed start date and employment status in BambooHR
BambooHR → 4PS Construct
BambooHR to 4PS Construct integration: employees from BambooHR in the 4PS company of their location
BambooHR → Active Directory
BambooHR to Active Directory integration: accounts in your own domain from HR
BambooHR → ADP iHCM
BambooHR to ADP iHCM integration: salary, bonuses and commissions to Dutch payroll