Recruitment to HR
Lever to Deel integration: hired candidate as own employee or EOR contract in Deel
With an integration between Lever and Deel, a candidate hired in Lever becomes an employee of your own entity in Deel or an EOR contract, with job title, start date, team, seniority and salary with scale from the offer. KoppelHet sends everything Deel requires in one go, so the hire is ready in Deel without completing it.
What the integration does
Organisations that recruit in Lever and use Deel for their international employees often also manage the people of their own entities there. HR then puts every hire into Deel by hand and fills in the missing details.
- KoppelHet fetches teams, legal entities and seniorities from Deel daily.
- Lever reports candidateHired; KoppelHet fetches opportunity, offer and posting and checks whether the candidate has signed.
- For an own entity KoppelHet creates the employee in Deel's HRIS, without invitation; in a country without an entity an EOR contract.
- KoppelHet puts a note with the Deel ID on the opportunity.
- HR checks in Deel and sends the invitation.
What to watch for with Lever and Deel
- KoppelHet determines the type of hire from the posting's location. In a country with your own entity it becomes an employee in Deel's HRIS, in a country without an entity an EOR contract.
- KoppelHet sends everything Deel requires in one go, so there is no half-finished contract in Deel that someone still has to complete.
- According to Deel's current guide for direct employees, Deel requires a team, a legal entity, nationality, country and seniority. A Lever posting has team and location, but no nationality or seniority. We add those two as fields to the offer form in Lever.
- By default Deel immediately sends a new direct employee an invitation. KoppelHet switches the invitation off, so the candidate does not get an email from Deel before HR has checked the data from Lever.
- For part-time Deel asks for a percentage, and a Lever posting only says Full-time or Part-time. KoppelHet converts the hours from the offer to that percentage, and converts the salary interval from Lever to Deel's scale, which defaults to annual when not given.
- Deel writes nothing back to an application. KoppelHet puts the opportunity number as external ID in Deel and the Deel ID as a note on the opportunity, so recruiter and HR find each other's record and a repeated notification does not create a second worker.
- Contractors are not in the first version, because Deel first requires a completed contractor profile. Contractors can be added later as an extension.
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 no invitation from the integration?
That way HR looks at the data first. Then HR sends the invitation in Deel.
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; five retries) and the Lever API with an API key - GET /opportunities/:opportunity/offers (fields anticipated_start_date, job_title, salary_amount, compensation_currency, salary_interval; signatures), GET /postings/:posting (categories.location, team and commitment) and POST /opportunities/:opportunity/notes.
- Direct employee according to Create a direct employee (API version 2026-01-01) - POST /rest/people, scope people:write, with client.team.id, client.legal_entity.id, employee (email, country, first_name, last_name, nationality, external_id), employment (type FULL_TIME or PART_TIME with part_time_percentage, job_title, seniority, start_date), compensation_details (salary, currency, scale) and invitation.action DISABLE. EOR through POST /eor with seniority from GET /lookups/seniorities and team from GET /teams.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Lever | Field in Deel | Notes |
|---|---|---|
name (één veld) | employee.first_name en last_name | |
emails[0] | employee.email | Deel asks for the personal address |
Nationaliteit (offer field) | employee.nationality | |
categories.location (posting) | client.legal_entity.id en employee.country | Through a table per label |
categories.team (posting) | client.team.id | |
Offer field job_title | employment.job_title | |
Offer field anticipated_start_date | employment.start_date | |
categories.commitment en uren (offer field) | employment.type en part_time_percentage | |
Senioriteit (offer field) | employment.seniority | |
Offer fields salary_amount, compensation_currency en salary_interval | compensation_details salary, currency en scale | |
opportunity id | employee.external_id |
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 → HiBob
Lever to HiBob integration: hired candidate with offer as an employee in Bob
Lever → Oracle HCM Cloud
Lever to Oracle HCM integration: hired opportunity as a pending worker in Oracle