Connecting Recruitee to AFAS
For most organisations, Recruitee's official AFAS integration is the shortest route: a hired candidate moves to AFAS as a new employee with one click and onboarding starts there automatically. Alongside the licence, count on around two consultancy days of implementation (KoppelHet, 2026). If you want more fields, two-way traffic or extra links such as payroll, a custom build on the APIs costs indicatively €1,500–€15,000.
- Fixed monthly fee
- Fixed project price up front
- Microsoft and Google
- Response to your request within one business day
How do you connect Recruitee to AFAS?
There are three routes: the official AFAS integration from the Recruitee marketplace, a managed integration via an AFAS integration partner such as Salure or KoppelHet, and a custom build directly on the APIs of both systems. The core is always the same candidate-to-employee flow — a candidate marked as hired in Recruitee becomes an employee in AFAS without retyping, including contact details, CV and start date. The same pattern works for other HR and payroll packages: Recruitee also has a standard Nmbrs integration, for example (Recruitee Help Centre, 2026).
You can see what such a flow looks like in our interactive Flow-Lab; the cost breakdown of a custom integration is in What does an API integration cost?. You will find all the systems we connect on the integrations page — if you work with OTYS instead of Recruitee, take a look at connecting OTYS.
Four routes, side by side.
| Option | Type | Indicative cost | Suitable for |
|---|---|---|---|
| Recruitee's AFAS integration | Standard app | Licence on request; implementation around 2 consultancy days (KoppelHet, 2026) | Hired candidates to AFAS as an employee with one click |
| Integration partner (Salure, KoppelHet) | Managed integration | On request; maintenance included with the licence (KoppelHet, 2026) | Broader field mapping and vacancy sync without your own management |
| Make / Zapier / Power Automate | iPaaS workflow | From around $9/mo (Make, 2026) to $19.99/mo (Zapier, 2026) | Standalone flows around the standard; AFAS requires its own setup work here with GetConnectors |
| Custom build on the APIs | Custom build | Indicatively €1,500–€15,000 one-off (see What does an API integration cost?) | Two directions, custom fields and extra links such as hours or payroll |
What syncs — and what doesn't.
The official integration sends the basic details of a hired candidate in one direction: from Recruitee to AFAS. First and last name, date of birth, gender, email address, phone number, address, CV and cover letter come across by default; extra fields you add via field mapping (Recruitee Help Centre, 2026). Anything deeper — feedback from AFAS, custom contract data, history — is partner or custom-build territory.
| Data | Standard connector | Custom integration |
|---|---|---|
| Name, address, date of birth and contact details | Yes | Yes |
| CV and cover letter | Yes | Yes |
| Vacancies from AFAS to Recruitee | Yes — via the vacancy sync | Yes |
| Custom fields (contract data, cost centre) | Limited — only what the field mapping allows | Yes |
| Feedback from AFAS to Recruitee | No — the candidate data goes one direction | Optional |
| History from before the start date | No | Optional |
Three questions that decide the choice.
Does the standard integration cover your fields and your process?
Yes → use the official AFAS integration and set up the field mapping carefully. No → look first at an integration partner, then at a custom build.
Does information need to flow back from AFAS to Recruitee?
Yes → a custom build or a partner integration that supports two directions, because the standard sends candidate data one way. No → the standard will do.
Are there more links in the chain — hours, payroll, IT onboarding?
Yes → design one continuous custom flow, so the whole chain fits rather than one piece. No → keep to the standard and expand later.
The rule of thumb: start with the standard integration if it covers your fields, and choose a custom build as soon as you need two directions, custom business rules or extra links.
Where this project runs aground in practice.
The flow stops at "hired"
The integration puts the candidate into AFAS, but the account, licences and mailbox of the new colleague remain manual work. Include IT onboarding in the same flow, otherwise the retyping merely shifts from HR to IT.
GetConnectors without an owner
The AFAS side runs on imported GetConnectors and an app connector with a token (Recruitee Help Centre, 2026). If the token expires or an authorisation changes, the integration fails silently. Record who manages and monitors this.
Field mapping as an afterthought
Roles, departments and contract types must map exactly onto each other in both systems. Skip that step, and HR will end up correcting every new employee by hand — exactly what the integration was meant to prevent.
Sending sensitive data too early
A citizen service number (BSN) only belongs in the administration on joining. Set up the integration so that sensitive fields only come across at that moment, and record the agreements in your data processing agreement.
What teams ask us up front.
What does a Recruitee-AFAS integration cost?
The official AFAS integration from Recruitee has no public price list; alongside the licence, count on a short implementation by a consultant. A custom build on the APIs costs indicatively €1,500 to €15,000, depending on the number of fields, directions and extra links. We work with a fixed project price, so you know the amount up front.
How long does it take to connect Recruitee to AFAS?
The standard integration is usually live within a few days to weeks, including setting up the GetConnectors and the field mapping in AFAS. A custom integration usually takes a few weeks of lead time, mainly due to testing and aligning fields with HR and payroll administration.
What if the standard integration doesn't support a field?
Then you don't have to jump straight to a fully custom build. Often a combination is possible: the standard integration handles the basic flow and a small custom build fills in the missing fields or the feedback. Only when the standard structurally falls short is a fully custom build the logical route.
Who manages and monitors the integration?
This must be explicitly assigned, otherwise an integration fails silently — for example through an expired token or a changed authorisation in AFAS. We include monitoring and maintenance in a fixed monthly fee, so errors are flagged before HR notices them.
Do we need to switch ATS or HR package?
No. We build around your current systems; Recruitee and AFAS both have mature APIs. If you work with a different package, such as Nmbrs for payroll, the same pattern applies: the candidate is entered once and flows through to HR and payroll.
Enter once, from application to payslip.
Book an intro call — or start with the free Operations Scan and see where the retyping sits in your organisation.