Recruitment to HR
Recruitee to AFAS integration: from hired candidate to new employee
With an integration between Recruitee and AFAS, a candidate the recruiter marks Hired in Recruitee automatically starts the onboarding process in AFAS, with personal details, start date, hours, salary, job and department already filled in. HR no longer retypes anything and onboarding starts on time, not only when the signed contract comes back.
What the integration does
Organisations that recruit in Recruitee and run HR in AFAS already have all of a new colleague's details with the recruiter. HR retypes them into AFAS, often only when the signed contract comes back, and onboarding starts too late. Department names in Recruitee and AFAS do not match.
- Every night the current departments and jobs from AFAS appear as picklists in Recruitee.
- With the offer, the recruiter fills in start date, hours, salary and job in Recruitee.
- The recruiter marks the candidate Hired.
- In AFAS the onboarding process starts with the details already filled in. If the candidate is a former employee, AFAS uses the existing employee.
- HR completes in AFAS what only HR knows, such as BSN and payroll tax credit, and finishes the workflow.
Back: Organisational units and jobs as picklists in Recruitee
What to watch for with Recruitee and AFAS Profit
- Recruitee has no standard fields for start date, hours and salary. We add them as extra fields or in an offer form, otherwise there is nothing to pass on.
- Department and job come from AFAS as picklists. The recruiter cannot pick a department that does not exist in AFAS, so the handover does not get stuck on it.
- A former employee who is rehired is looked up in AFAS, for example by date of birth and name. The onboarding process then uses the existing employee, so no second person is created.
- The BSN is not sent from Recruitee by default. The new hire or HR enters it in AFAS, so it does not need to live in the recruitment system.
- KoppelHet is a Recruitee partner. The connection to Recruitee is a building block we already have, so the time goes into your fields and workflow.
- If an offer is withdrawn after the candidate was already marked Hired, the employee is still in the AFAS workflow and HR can reject it 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 Recruitee have an integration with AFAS?
Yes, through KoppelHet. KoppelHet is a Recruitee partner and already has the connection to Recruitee. We build the integration around your fields and workflow.
Do we need to change our Recruitee setup?
Usually just a few extra fields for contract data and the picklists for department and job. We set them up together.
Does this also work with Teamtailor or OTYS?
Yes, the process is the same. Only the trigger and the fields on the recruitment system side differ.
What does HR see in AFAS?
An onboarding process with the Recruitee data already filled in. HR checks, completes and finishes.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Recruitee is read through the Recruitee ATS API, with the candidate_moved webhook as trigger and the fields name, emails and phones. Start date, hours and salary live in custom fields.
- AFAS is written through the HrOnboarding UpdateConnector, which starts the onboarding process; AFAS recommends it over HrCreateApplicant. For an existing employee the employee number (EmId) is passed.
- Organisational units and jobs from AFAS go to a custom field in Recruitee as a fixed picklist.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in AFAS Profit | Notes |
|---|---|---|
name | Voornaam, voorvoegsel, achternaam | Recruitee has one name field; we split it based on the offer form |
emails[0] | E-mail privé | |
phones[0] | Telefoon privé | |
Adres (custom field of formulier) | Adres | |
Startdatum (custom field) | Datum in dienst | |
Uren per week (custom field) | Rooster | |
Salaris (custom field) | Salaris | |
Functie (keuzelijst uit AFAS) | Functie | |
Afdeling (keuzelijst uit AFAS) | Organisatorische eenheid |
Related
Recruitee → ADP Workforce Now
Recruitee to ADP Workforce Now integration: hired candidates as an in-progress hire
Recruitee → AlexisHR
Recruitee to AlexisHR integration: hired candidates as employees in Simployer One
Recruitee → BambooHR
Recruitee to BambooHR integration: hired candidates in BambooHR without clicking and retyping
Recruitee → BuddeeHR
Recruitee to BuddeeHR integration: hired candidates as employees in BuddeeHR