Recruitment to HR
Recruitee to Officient integration: hired candidates into the Belgian HR file
With an integration between Recruitee and Officient, a hired candidate from Recruitee arrives automatically as a new person in Officient, with name, email, phone, personal email, start date, role and team. HR completes contract, wage and Dimona declaration there.
What the integration does
Organisations with Belgian employees in Officient that recruit in Recruitee pass on new colleagues one by one by hand. Anyone who is forgotten is not in Officient, and HR still fills in start date, role and team afterwards.
- The recruiter moves the candidate in Recruitee to a stage with the hire category.
- The candidate_moved webhook starts the transfer without a click.
- KoppelHet creates the new person in Officient and adds start date, role and team.
- HR completes contract, wage and Dimona in Officient.
What to watch for with Recruitee and Officient
- Officient keeps the work address and the personal address apart, while Recruitee only knows the address the candidate applied with. KoppelHet sets that address as personal email and takes the work address from a profile field.
- HR can only file the Dimona declaration once the start date is in Officient. KoppelHet therefore includes the start date straight away, with role and team.
- Officient stores a name in parts, with the name particle and the partner's name separately. Recruitee has one name field, so KoppelHet splits a name such as Van den Broeck by a fixed rule and leaves doubtful cases to HR.
- Officient reports a new person with the person_added webhook, with only the ID. KoppelHet waits for that notice before role and team are added.
- According to the documentation, a new person can be created in Officient with a name and an email address. Recruitee only knows the address the candidate applied with. If the work address is not yet in the profile field at the hire, KoppelHet holds the hire and reports it to HR.
- Officient grants access per object, with read or write. Person detail requires personal.info:read. KoppelHet only requests the scopes on personal information that the hire needs, and no access to objects such as wage.
- Officient allows 30 calls every five seconds and returns an empty 429 above that, which the caller has to retry itself. KoppelHet spreads the calls after each person_added notice, so a series of hires from Recruitee does not get stuck halfway.
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 the integration also file the Dimona declaration?
No. HR files it from Officient, with the start date the integration supplies.
Does the wage come along from Recruitee?
Not in the first version. HR records Belgian pay elements in Officient; a wage line from the offer can follow later as an extension.
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 candidate_moved webhook with event_subtype stage_changed to a stage with the hire category (HMAC SHA-256 in X-Recruitee-Signature, up to nine retries) and the ATS API for profile fields.
- Officient through api.officient.io/1.0 with an OAuth 2.0 token; webhook person_added, GET /people/{id}/detail with name_parts, email, personal_email, team and current_role; the notice only contains account, event_type and related_object_id.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Officient | Notes |
|---|---|---|
name | first_name en last_name | Name particle separately in name_parts.insertion |
Zakelijk e-mailadres (profielveld) | email | |
emails[0] | personal_email | |
phones[0] | Telefoon | |
Startdatum (profielveld) | Startdatum van de functie | |
Functietitel van de vacature | current_role | |
Afdeling van de vacature | team |
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