Payroll integration
Rippling to AFAS integration: new Dutch colleagues through the hiring workflow in AFAS Profit
With an integration between Rippling and AFAS Profit, every new employee of the Dutch entity in Rippling automatically starts the hiring workflow in AFAS, and job, hours and salary changes reach the AFAS contract with their effective date. Payroll checks new employees in AFAS as always, but no longer copies anything from Rippling.
What the integration does
Organisations that use Rippling as the HR and IT platform for all countries and process Dutch payroll themselves in AFAS Profit enter every Dutch employee twice. Job and salary changes often only reach AFAS when payroll asks for them, and then with the wrong effective date.
- HR hires someone at the Dutch entity in Rippling.
- KoppelHet uses it to start the hiring workflow in AFAS at the right employer, with personal data, job, schedule and salary.
- Payroll adds collective agreement, payroll tax credit and pension in the workflow and completes it.
- Later changes to job, schedule or salary go to the AFAS contract with the effective date from Rippling.
- A termination sets the end date and the termination reason on the AFAS contract.
What to watch for with Rippling and AFAS Profit
- A new employee from Rippling starts the hiring workflow in AFAS and is not created directly as a full employee. Payroll therefore keeps the same checks as with manual entry.
- In Rippling full-time means at least thirty hours a week. That says nothing about the Dutch part-time factor, so KoppelHet takes the hours from the Rippling work schedule and not the full-time or part-time code.
- Rippling gives job and salary their own effective date each. KoppelHet sets both separately in AFAS, so a promotion on the first of the month and a pay rise on another date each land in the right period.
- Rippling workers at a foreign entity or of the contractor type do not go to AFAS. The entity in Rippling decides which AFAS employer someone belongs to.
- The reason for leaving is free text in Rippling that each organisation fills in itself, AFAS uses a fixed list. At the start we create a mapping per reason; an unknown reason becomes an alert.
- In AFAS the integration gets its own app connector with only the connectors it needs. AFAS retires the classic token on 31 August 2027, so new integrations use OAuth straight away.
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
Can HR still change things in AFAS?
Yes. Data that does not come from Rippling, such as payroll tax credit and pension, stays in AFAS and the integration does not overwrite it.
What if someone moves from a foreign entity to the Dutch one?
For AFAS that is a new hire at the Dutch employer, with the start date of the new employment. Payroll completes it in the workflow.
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 (workers with legal_entity, employment_type, compensation with salary_effective_date, title_effective_date, work_schedule, termination_details; filter on updated_at), with a token with only the required scopes and a pinned Rippling-Api-Version.
- To AFAS through the HrOnboarding UpdateConnector for new employees and KnEmployee for changes to contract, job, schedule and salary. A dedicated GetConnector provides the AFAS data for the comparison.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in AFAS Profit | Notes |
|---|---|---|
number (worker) | Medewerker (EmId) | |
legal_entity_id | Werkgever in AFAS | Only the Dutch entity |
start_date | Begindatum contract | |
title + title_effective_date | Functie met ingangsdatum | Through a lookup to AFAS functions |
department | Organisatorische eenheid | Through a lookup table |
work_schedule | Rooster (uren per week) | |
compensation.annual_compensation + salary_effective_date | Salaris met ingangsdatum | Annual amount converted to the monthly amount |
termination_details.reason | Reden einde dienstverband | Rippling reasons are free text; fixed mapping per reason |
end_date | Einddatum contract |
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