Recruitment to HR
Teamtailor to AFAS integration: hired candidates straight in as new employees
With an integration between Teamtailor and AFAS, a candidate hired in Teamtailor automatically starts the hiring workflow in AFAS, with start date, salary and department from the offer already filled in. Because the departments in Teamtailor come from AFAS, the recruiter never picks a department AFAS does not know.
What the integration does
Anyone recruiting in Teamtailor, also for other countries, with Dutch employees in AFAS checks after every hire whether the candidate is for the Netherlands and retypes the data. Only in AFAS does it turn out that the department from Teamtailor has a different name there.
- The departments and locations from AFAS are in Teamtailor and stay in line when they change in AFAS.
- The recruiter sends the offer with start date and salary, and marks the application as hired after acceptance.
- KoppelHet checks that the notice really comes from Teamtailor and whether the job is in the Netherlands.
- For a Dutch hire the hiring workflow starts in AFAS, with the data already filled in.
- HR checks the workflow in AFAS, adds BSN and payroll tax credit, and completes it.
Back: Organisational units as departments in Teamtailor · Offices as locations in Teamtailor
What to watch for with Teamtailor and AFAS Profit
- In Teamtailor a hire belongs to an application, not to the candidate. A candidate who applies for two jobs and is hired for one therefore reaches AFAS once, with the data of the right job.
- If the organisation also recruits for other countries in the same Teamtailor account, only hires for a Dutch location go to AFAS. Belgian or German hires stay outside the integration or go to their own HR system.
- KoppelHet puts the AFAS departments into Teamtailor, so a recruiter cannot pick a department AFAS does not know.
- Start date and salary are in the offer in Teamtailor. KoppelHet only uses an accepted offer, so a declined or pending offer does not end up in AFAS.
- Instant notifications are an add-on in Teamtailor that an administrator switches on. KoppelHet checks each notice to make sure it really comes from Teamtailor, before creating an employee in AFAS.
- Teamtailor already splits first and last name, but has no separate prefix. For a surname like van den Berg KoppelHet puts van den into the AFAS prefix field, so sorting and salutation are correct.
- A Dutch former employee who is rehired is found in AFAS by KoppelHet. The workflow then gets a new employment for the existing person.
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 Teamtailor have an integration with AFAS?
Through KoppelHet, yes. KoppelHet builds and manages the integration, including keeping the departments in Teamtailor in line with AFAS.
Do we have to set up departments in Teamtailor again?
No, the integration sets them from AFAS. We map existing departments to the right AFAS unit once.
What happens to hires for Belgium?
They do not go to AFAS. If your Belgian HR system can receive data, KoppelHet can send those hires there.
Does this work without Teamtailor's job offer feature?
Yes. We then capture start date, hours and salary in extra fields on the candidate.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Teamtailor is read through company webhooks (add-on, switched on by a Company Admin; job_application.update on a stage of type hired, with TT-Signature header) and the Teamtailor API (job-applications, candidates, jobs, job-offers with status accepted and start-date and salary in details).
- Departments and locations are created and updated through the Teamtailor API from the AFAS organisational units.
- AFAS is written through the employee UpdateConnector, as part of the hiring workflow.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Teamtailor | Field in AFAS Profit | Notes |
|---|---|---|
first-name | Voornaam | Teamtailor keeps first and last name apart; only the name prefix still needs splitting |
last-name | Voorvoegsel en achternaam | |
email | E-mail privé | |
phone | Telefoon privé | |
Aanbod: start-date (details) | Datum in dienst | |
Aanbod: salary (details) | Salaris | |
department (vacature) | Organisatorische eenheid | Same value, because the departments come from AFAS |
role of custom field | Functie | |
Uren per week (custom field) | Rooster | |
location (vacature) | Standplaats en filter op land |
Related
Teamtailor → ADP Workforce Now
Teamtailor to ADP Workforce Now integration: hired candidates as in-progress hires
Teamtailor → BambooHR
Teamtailor to BambooHR integration: hired candidates as employees in BambooHR
Teamtailor → BuddeeHR
Teamtailor to BuddeeHR integration: hired candidate as a new employee in BuddeeHR
Teamtailor → Cezanne HR
Teamtailor to Cezanne HR integration: hired candidates with the right start date and company in Cezanne