Recruitment to HR
Lever to Oracle HCM integration: hired opportunity as a pending worker in Oracle
With an integration between Lever and Oracle HCM Cloud, an opportunity that moves to hired in Lever becomes a pending worker in Oracle HCM Cloud, with name, projected start date, employer, location and FTE from the offer. HR converts the pending worker to an employee in Oracle itself, and the recruiter sees a note in Lever that the new colleague is in Oracle.
What the integration does
Organisations that have Oracle HCM Cloud as HR system and recruit in Lever now enter a hire into Oracle by hand. HR retypes name, start date and placement.
- At the start we record the legal employer, location code and business unit in Oracle per Lever location.
- Lever reports candidateHired; KoppelHet fetches opportunity, offer and posting.
- KoppelHet checks whether the candidate has signed the offer and creates the pending worker.
- KoppelHet puts a note on the opportunity in Lever.
- HR completes onboarding and converts the pending worker to an employee in Oracle.
What to watch for with Lever and Oracle HCM Cloud
- Oracle intends a pending worker for someone who has signed but not yet started. A Lever offer already shows a signed document as soon as one party signs. KoppelHet therefore checks per signer whether the candidate has signed before the pending worker is created.
- Lever stores the name as one field, Oracle wants first name and last name separately. KoppelHet splits the name and keeps a name prefix with the last name; a name that cannot be split unambiguously is flagged for HR to check.
- The location of a Lever posting is a free label, while Oracle expects an existing legal employer and location code. KoppelHet records which employer and location belong to each label, and a new label holds the hire until HR has assigned it.
- A Lever posting has a commitment such as Full-time or Part-time, without hours. Oracle calculates in FTE. We add hours per week to the offer form in Lever and convert them against the full-time week of the legal employer in Oracle.
- One contact can have several opportunities in Lever. KoppelHet puts the number of the hired opportunity into Oracle's applicant number and searches on it first, so a second application by the same person does not create a second pending worker.
- Lever stops a webhook after five failed attempts. KoppelHet therefore compares the hired opportunities with the pending workers in Oracle by applicant number every day, so a hire during an outage still arrives.
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 a pending worker and not an employee?
That way onboarding in Oracle stays with HR, and HR decides when someone becomes an employee. If the hire falls through, there is no employment yet to terminate.
Does the salary go across?
Not in the first version; HR records the salary in Oracle. Salary from the Lever offer can be added 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.
- Lever through the candidateHired webhook (data.opportunityId and contactId; HMAC-SHA256 over token and triggeredAt with the signing token; five retries) and the Lever API with an API key through basic authentication - GET /opportunities/:opportunity, GET /opportunities/:opportunity/offers (fields with anticipated_start_date and job_title; signatures per signer), GET /postings/:posting (categories.location, department and commitment) and POST /opportunities/:opportunity/notes. Limit 10 requests per second.
- To Oracle HCM Cloud through the workers REST API as a pending worker (worker type P) with ApplicantNumber, ProjectedStartDate, LegalEmployerName, LocationCode, BusinessUnitName and workMeasures (FTE). Conversion through the ready-to-convert flag and a scheduled process in Oracle. Integration user with rights per legal employer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Lever | Field in Oracle HCM Cloud | Notes |
|---|---|---|
opportunity id | ApplicantNumber | |
name (één veld) | names (FirstName, LastName) | Split; HR checks when in doubt |
emails[0] | emails (privé) | |
phones[0] | phones | |
Offer field anticipated_start_date | ProjectedStartDate | |
categories.location (posting) | LegalEmployerName en LocationCode | Through a table per label |
categories.department (posting) | BusinessUnitName en afdeling | |
Offer field job_title | Functie op de assignment | |
Uren per week (offer field) | workMeasures (FTE) |
Related
Lever → BambooHR
Lever to BambooHR integration: hired candidate as a new employee profile in BambooHR
Lever → Dayforce
Lever to Dayforce integration: signed offer as a validated new employee in Dayforce
Lever → Deel
Lever to Deel integration: hired candidate as own employee or EOR contract in Deel
Lever → HiBob
Lever to HiBob integration: hired candidate with offer as an employee in Bob