Payroll integration
Factorial to DATEV integration: changes from Factorial checked before the cut-off
With an integration between Factorial and DATEV, KoppelHet checks in the last week before the German cut-off date whether new hires, contract changes, absences and pay components from Factorial are also with the tax adviser in DATEV LODAS or Lohn und Gehalt. Anything missing goes on a list for HR and the firm.
What the integration does
Organisations with HR in Factorial and a German entity whose payroll runs at a tax adviser in DATEV sometimes find a change at the end of the month that nobody has passed on.
- In the last week before closing KoppelHet reads the employees, contract versions and changes per legal entity from Factorial every day.
- KoppelHet compares them with what the firm has in DATEV and reports what is missing.
- The tax adviser runs payroll.
What to watch for with Factorial and DATEV
- Factorial has the field Mitarbeitercode DATEV-API per employee, under personal data. That is the personnel number in DATEV. KoppelHet checks before closing who is still missing that field.
- A different job or cost centre in a contract in Factorial does not reach the tax adviser by itself. KoppelHet puts such changes on the list for the firm.
- KoppelHet sends nothing to DATEV itself and sticks to checking. The tax adviser makes any correction in DATEV.
- Factorial gives a country code for every legal entity. KoppelHet only includes entities with country code de in the check, so employees in other countries do not end up on the list for the Steuerberater.
- A contract version in Factorial has an effective date (effective_on). KoppelHet puts a change on the list for the month in which it takes effect, even if HR entered it earlier.
- Factorial stores the salary per contract version in cents, with its own frequency. KoppelHet converts it to euros and to the period on the office's overview before it compares the amounts.
- In Factorial, changes can be requested per legal entity and per type, such as hiring, termination, contract and sick. KoppelHet requests them per entity, and so per Mandantennummer, and only the types that count for the Abrechnung.
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
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet's check reads Factorial through the API (employees, contract versions and employee updates per legal entity) and compares that with an overview from the firm out of DATEV.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in DATEV | Notes |
|---|---|---|
Juridische entiteit | Beraternummer en Mandantennummer | One consultant number can connect several client numbers |
Mitarbeitercode DATEV-API | Personalnummer in DATEV | |
Medewerkergroep | Beschäftigungsbetrieb | |
Looncomponent (Compensation) | Lohnart | |
Afwezigheidstype | Ausfallschlüssel | |
Team | Abteilung |
Related
Factorial → 4PS Construct
Factorial to 4PS Construct integration: fitters and site managers with their cost centre as a dimension in 4PS
Factorial → Active Directory
Factorial to Active Directory integration: domain accounts from Factorial
Factorial → ADP iHCM
Factorial to ADP iHCM integration: contract versions and terminations of the Dutch entity to ADP
Factorial → AFAS Profit
Factorial to AFAS integration: employees and contracts from Factorial in AFAS Profit Payroll