Recruitment to HR
Recruitee to Loket integration: hired candidates automatically as draft employees in Loket
With an integration between Recruitee and Loket, every hired candidate from Recruitee arrives as a draft employee at the right employer in Loket, with personal data, start date, job and terms from the offer. KoppelHet does that automatically at the hired stage, also with several employers, with employment and salary included.
What the integration does
Organisations that recruit in Recruitee and run payroll in Loket often move new colleagues into Loket by hand. Payroll then retypes employment, hours and salary from the offer letter.
- The recruiter moves the candidate to the hired stage in Recruitee.
- KoppelHet retrieves the candidate and the offer, with start date, job, hours and salary.
- Based on the job or a picklist field KoppelHet determines the employer in Loket.
- KoppelHet creates the draft employee and starts the new hire checklist.
- Payroll adds the national ID and payroll tax details and completes the draft.
What to watch for with Recruitee and Loket
- KoppelHet responds to the hired stage, so no hire is left behind because someone forgot to pass it on.
- Besides the personal data, KoppelHet also takes start date, hours and salary from the offer, so payroll does not retype them.
- KoppelHet works with one integration user per payroll bureau or employer, so recruiters do not need rights in Loket.
- Recruitee has no employer or BV. With several employers in Loket we derive the employer from the job or a picklist field on the offer, so a candidate does not end up at the wrong employer.
- Loket first receives a new employee as a draft, with a checklist. Payroll adds the national ID and payroll tax details there, data that does not belong in Recruitee.
- The salary field in Recruitee holds an amount, not a period. Per job type we record whether it is a monthly salary or an hourly wage, because Loket handles them differently.
- KoppelHet writes nothing back into Recruitee; what went to Loket per candidate is in the logging of the KoppelHet platform.
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
What does payroll still add?
National ID, payroll tax, collective agreement grading and pension. They do not belong in Recruitee and are added in the draft's checklist in Loket.
What about audit logging, GDPR and our integration platform?
You are the controller and KoppelHet is the processor, under a data processing agreement. Only hired candidates go to Loket; rejected candidates stay in Recruitee, and every action is in the audit logging. An existing integration platform is left alone.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads Recruitee through the webhook candidate_moved to a stage with the hire category, and the ATS API with profile fields (date_of_birth, nationality, address, salary) and custom fields.
- Loket is written through the Loket REST API with OAuth - create a concept employee at the employer and start the new hire checklist workflow. Loket has an acceptance environment with test data.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Loket | Notes |
|---|---|---|
first_name en last_name | Voornaam en achternaam (concept) | |
date_of_birth | Geboortedatum | |
nationality | Nationaliteit | |
emails en phones | E-mail en telefoon | |
address | Adres | |
Vacature of keuzeveld bv | Werkgever in Loket | |
Startdatum (custom field) | Datum in dienst | |
Functie van de vacature | Functie | |
Uren per week (custom field) | Arbeidsvoorwaarden: uren | |
salary | Salaris | Record monthly salary or hourly wage up front |
Related
Recruitee → ADP Workforce Now
Recruitee to ADP Workforce Now integration: hired candidates as an in-progress hire
Recruitee → AFAS Profit
Recruitee to AFAS integration: from hired candidate to new employee
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