Carerix logoAFAS Profit logo

Recruitment to HR

Carerix to AFAS integration: a placed candidate starts onboarding in AFAS Profit

With an integration between Carerix and AFAS Profit, a candidate who reaches a placement status in Carerix automatically starts the onboarding process in AFAS, with name, name prefix, date of birth, contact details and start date. HR in AFAS completes the onboarding, and nobody copies the candidate from Carerix any more.

What the integration does

Organisations that run their own recruitment in Carerix and keep their HR administration in AFAS Profit send HR an email with candidate details after a placement. HR retypes name, address and start date in AFAS, and a name prefix or date of birth easily goes wrong on the way.

  1. The recruiter moves the match between candidate and vacancy in Carerix to the placement status.
  2. KoppelHet sees the status change and fetches match, candidate and vacancy.
  3. KoppelHet looks up the job and organisational unit in AFAS for the vacancy.
  4. In AFAS the onboarding process starts with the personal details and the start date.
  5. HR adds BSN, contract and salary and completes the onboarding.
Carerix → KoppelHet → AFAS ProfitSOURCECarerixTARGETAFAS ProfitKoppelHetmapping · logging · monitoringCarerix → KoppelHet → AFAS ProfitSOURCECarerixTARGETAFAS ProfitKoppelHetmapping · logging · monitoring
Out: New employee with name, name prefix and date of birth · Private email and mobile number · Start date from the match · Job and organisational unit through the vacancy · Onboarding process in AFAS

What to watch for with Carerix and AFAS Profit

  • In Carerix the configuration of the match status decides whether a candidate is placed. A status has a flag for a successful placement; KoppelHet only reacts to statuses with that flag, so an interview or proposal never ends up in AFAS.
  • Carerix stores the name prefix as a separate field on the candidate, just like AFAS. Names such as "van der Berg" therefore arrive correctly, without the integration having to guess the surname.
  • The agreed salary is stored in Carerix on the match as free text, not as an amount. KoppelHet therefore does not put it in an AFAS salary field, but as a note on the onboarding; HR enters the salary itself.
  • In its public documentation Carerix sends no notification on a status change. KoppelHet therefore requests every fifteen minutes the matches whose status changed since the last time, using the date Carerix keeps for that separately.
  • A candidate in Carerix can have matches on several vacancies at once. KoppelHet records in AFAS which match started the onboarding; if the same person is placed again later through another vacancy, the AFAS employee number is passed on as a rehire.
  • AFAS has its own entry for candidates from an external recruitment system that starts the onboarding workflow. HR in AFAS therefore still decides on every placement, and can reject a placement that was reversed in Carerix in the workflow.
  • Carerix gives an integration its own client with a service account and rights per area. KoppelHet only gets read rights on matches, candidates and vacancies, and cannot change anything in Carerix.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Which status in Carerix counts as a placement?

Every match status you configured in Carerix as a successful placement. At the start we go through that list together.

Does the salary go to AFAS?

As a note, not as an amount. Carerix stores the agreed salary as free text, and HR records the salary in AFAS.

Does this also work for temporary workers we place through Carerix?

This integration covers your own employees who join in AFAS. Placements of temporary workers at clients belong in the agency's payroll and need a different setup.

What about the GDPR?

You are the controller and KoppelHet is the processor, under a data processing agreement. Only placed candidates go to AFAS, and every action is in the audit logging.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Carerix is read through the GraphQL API (https://api.carerix.io/graphql/v1/graphql) with a confidential client and client credentials from Identity Access, scope urn:cx/cx5Wrapper:data/crmatch:read. crMatchPage with a qualifier on statusInfoModificationDate and pageable (20 per page by default); statusInfo.isSuccessfullyFilled decides the placement. Fields from CRMatch (jobStartDate, agreedSalary as String, toVacancy, toEmployee) and CREmployee (firstName, initials, lastNamePrefix, lastName, birthDate, emailAddress, mobileNumber). The Carerix help marks the old REST API as outdated.
  • AFAS is written through the HrOnboarding UpdateConnector, which starts the Onboarding workflow for new employees, rehires and candidates from an external recruitment system. For a rehire the employee code is passed along.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in CarerixField in AFAS ProfitNotes
CRMatch _idKenmerk in het onboardingprocesTo recognise a second placement of the same match
CREmployee firstName en initialsVoornaam en voorletters
CREmployee lastNamePrefixVoorvoegselSeparate field in both systems, no splitting needed
CREmployee lastNameAchternaam
CREmployee birthDateGeboortedatum
CREmployee emailAddress en mobileNumberPrivé e-mail en mobiel
CRMatch jobStartDateDatum in dienst
CRVacancy (functie en afdeling)Functie en organisatorische eenheidThrough a lookup table

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.