Payroll integration
Factorial to AFAS integration: employees and contracts from Factorial in AFAS Profit Payroll
With an integration between Factorial and AFAS Profit, a new employee of the Dutch entity arrives in AFAS from Factorial through the onboarding process, and contract, schedule, salary, bank account and end date go to the right employer with their effective date. HR reviews in AFAS as always, without retyping from Factorial.
What the integration does
International employers that use Factorial for HR and run Dutch payroll in AFAS Profit enter every hire and contract change twice. Because Factorial has no days per week, the schedule in AFAS is often wrong.
- HR records the hire in Factorial. KoppelHet fetches the HR changes of the Dutch legal entity.
- KoppelHet starts the onboarding process in AFAS with the data from Factorial, so HR reviews and completes the new employee in AFAS.
- Contract and salary changes go to the contract, schedule and salary in AFAS with their effective date.
- A new bank account or a termination in Factorial arrives as a change in AFAS.
- Before the period closes KoppelHet compares Factorial and AFAS and reports differences.
What to watch for with Factorial and AFAS Profit
- AFAS has an onboarding process that an integration can start. KoppelHet uses it for a hire from Factorial, so HR in AFAS goes through the same checks as with manual entry and the employee only enters payroll after that.
- Factorial records hours per week; AFAS also asks for the number of days in the schedule. KoppelHet takes the days from an extra field in Factorial or uses a default per contract type, so leave accrual in AFAS is right.
- Factorial supplies the HR changes per kind and per legal entity. KoppelHet only requests the changes of the Dutch entity, so staff in other countries do not end up in AFAS.
- Contract types can be set up freely in Factorial. AFAS has a fixed type of employment, such as full-time, part-time or on-call. A lookup table agreed at the start links each Factorial type to the right AFAS type.
- A termination in Factorial becomes an end date in AFAS with a reason for end of employment. We agree that reason per type of termination, because AFAS uses it for the tax return.
- Factorial retries a failed notification up to twenty times in 48 hours and then disables the subscription. KoppelHet monitors this and compares Factorial with AFAS before every period close.
- Payroll tax credit, collective agreement and pension are not in Factorial. HR or payroll completes them in AFAS during onboarding, and the integration does not overwrite them afterwards.
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 through onboarding in AFAS and not directly as an employee?
That way HR keeps control and completes the Dutch data before anyone enters the payroll run. Creating directly is also possible, if you prefer.
We already have an integration platform. Does this fit alongside it?
Yes. This integration runs on the KoppelHet platform and asks nothing of your existing integration platform. Every action is in the audit logging, so operations and audit know what happened.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Factorial is read through the Factorial API (version 2026-07-01 in the path) with OAuth 2.0 - employee updates (new hires, contract changes, personal changes, terminations) filtered on legal_entities_ids, contract versions, compensations with concepts. Webhook subscriptions with up to twenty attempts in 48 hours.
- AFAS is written through the HrOnboarding UpdateConnector for new employees and KnEmployee (AfasContract, AfasTimeTable, AfasSalary, AfasBankInfo) for changes, under its own app connector.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in AFAS Profit | Notes |
|---|---|---|
Factorial employee id | Medewerkernummer of vrij veld | Fixed key |
Naam, geboortedatum en adres | KnPerson | |
Legal entity | Werkgever | |
Contract version (begin, soort) | AfasContract en dienstbetrekking | Lookup table to full-time, part-time or on-call |
Uren per week | AfasTimeTable (uren) | |
Werkdagen (extra veld of standaard) | AfasTimeTable (dagen) | |
Compensation met concept | AfasSalary of looncomponent | |
Bankrekening | AfasBankInfo | |
Termination | Datum uit dienst en reden einde dienstverband |
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 → AllSolutions
Factorial to AllSolutions integration: employees per legal entity with their main cost centre in AllSolutions