Recruitment to HR
Recruitee to Oracle HCM integration: hired candidates straight into onboarding
With an integration between Recruitee and Oracle HCM Cloud, a candidate hired in Recruitee automatically appears in Oracle as a future employee, with start date, employer, department, location and hours. Onboarding in Oracle starts on time, and HR decides when the new colleague becomes a full employee.
What the integration does
Organisations with Oracle HCM Cloud as global HR system sometimes recruit locally in Recruitee instead of Oracle Recruiting. HR then creates every hired candidate in Oracle by hand, often shortly before the start date, and the onboarding tasks in Oracle start too late.
- The recruiter marks the candidate as hired in Recruitee.
- KoppelHet uses the placement location to determine the right employer and business unit in Oracle.
- In Oracle the candidate appears as a future employee, with contact details, projected start date, location and contract size.
- Onboarding in Oracle runs. When it is done, HR converts the new colleague into an employee.
- If the candidate is rejected in Recruitee afterwards, HR gets a notice to deal with it in Oracle.
What to watch for with Recruitee and Oracle HCM Cloud
- Oracle has a separate status for someone who has signed but not yet started. KoppelHet creates the candidate with that status, not directly as an employee.
- The conversion to employee happens in Oracle itself. The integration leaves that step to HR, so HR decides when onboarding is done.
- The candidate number from Recruitee goes to Oracle. If the same candidate comes in again, KoppelHet finds the existing future employee instead of creating a second one.
- Oracle works in FTE, Recruitee has no hours. We add weekly hours to the offer form and convert them against the full-time week of the Dutch entity.
- The placement location in Recruitee determines the employer. If the organisation also recruits for other countries in Recruitee, each candidate goes to the employer for their country.
- The BSN does not come from Recruitee. HR adds it in Oracle during onboarding, before the new colleague becomes an employee.
- If a hired candidate is rejected in Recruitee after all, they already exist in Oracle. KoppelHet reports it to HR instead of deleting anything itself.
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
Why not Oracle Recruiting?
That is the organisation's choice. If you recruit in Recruitee, you keep that way of working; the integration brings the hire into Oracle.
Can the integration create the candidate directly as an employee?
Technically yes, but we recommend the interim status. Onboarding in Oracle then runs as HR has set it up.
What if the start date changes?
If the recruiter changes the start date in Recruitee, KoppelHet updates the projected start date in Oracle, as long as the new colleague has not been converted yet.
Does the Recruitee side still need to be built?
Hardly. KoppelHet is a Recruitee partner and already has the connection to Recruitee. The time goes into the employers, business units and locations in Oracle.
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 candidate_moved webhook to a stage with the hire category, with candidate, vacancy and placement_locations, and the profile fields.
- Oracle HCM Cloud is written through the workers REST API as a pending worker (worker type P, add pending worker action) with ProjectedStartDate, LegalEmployerName, LocationCode, BusinessUnitName and workMeasures (FTE). The Recruitee ID goes into ApplicantNumber.
- Conversion happens through the ready-to-convert flag on the work relationship and a scheduled process in Oracle. Integration user with permission to create workers for the relevant legal employers.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Oracle HCM Cloud | Notes |
|---|---|---|
id (kandidaat) | ApplicantNumber | The Recruitee ID as a reference to the application |
name | names (voornaam, achternaam) | Using the Dutch name format for prefixes |
Profielveld date_of_birth | DateOfBirth | |
emails[0] | emails (privé) | |
phones[0] | phones | |
Profielveld address | addresses | One text line from Recruitee, split into the Dutch address style |
Startdatum (profielveld) | ProjectedStartDate | |
placement_locations[0] | LegalEmployerName en LocationCode | Through a lookup per office |
offer.department | assignments: BusinessUnitName en afdeling | Through a lookup table |
Uren per week (profielveld) | workMeasures (FTE) | Converted against the full-time week |
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