
Recruitment to HR
SmartRecruiters to Deel integration: the right Deel contract per hire
With an integration between SmartRecruiters and Deel, a candidate hired in SmartRecruiters gets the right contract in Deel, as an EOR employee, contractor or employee of your own entity. KoppelHet fills what SmartRecruiters knows, looks up team and seniority in Deel and reports in SmartRecruiters whether the contract is ready.
What the integration does
Organisations that recruit in SmartRecruiters for countries where they have no entity of their own put every hire into Deel by hand. Per candidate HR chooses the type of contract and looks up data SmartRecruiters does not hold, such as nationality and seniority.
- The recruiter sets the candidate to hired in SmartRecruiters.
- KoppelHet fetches candidate, job and offer and reads the type of working relationship.
- Team and seniority are looked up in Deel.
- KoppelHet creates the contract that fits the working relationship; sending and signing stay in Deel.
- The onboarding status in SmartRecruiters goes to successful, or to failed when data is missing.
What to watch for with SmartRecruiters and Deel
- Deel uses a different contract per type of working relationship, with its own required data. In SmartRecruiters we record the working relationship as an offer property, so KoppelHet chooses the right contract per hire.
- An EOR contract needs nationality, a seniority from Deel's list and a team. SmartRecruiters does not have those by default. KoppelHet looks up team and seniority in Deel; Deel asks the candidate for nationality in its own onboarding.
- If something Deel requires is missing, KoppelHet sets the onboarding status in SmartRecruiters to failed with the reason. The recruiter then knows there is work left, instead of assuming the contract is ready.
- A contractor must first complete their own profile in Deel before a contract can be created. For a contractor KoppelHet sets the onboarding status in SmartRecruiters to ready to onboard and only creates the contract once the profile is complete.
- Deel does not link a contract back to an application. KoppelHet keeps its own record of which contract belongs to which SmartRecruiters candidate and job, so a repeated notification does not create a second contract.
- If the same organisation also recruits for its own Dutch entity, those hires do not belong in Deel. KoppelHet looks at the job's country and the working relationship and only sends hires for Deel to Deel.
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 Deel have a ready-made SmartRecruiters integration?
We found none in the public documentation, although Deel has one for Workable and Lever, among others. Check with Deel to be sure.
Does the integration also send the contract?
No. KoppelHet creates the contract; HR checks and sends it in Deel.
Can the onboarding status go to successful later when the contract is active?
That can be added later as an extension. In the first version successful means the contract was created in Deel.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SmartRecruiters through a webhook subscription (ID only; HMAC-SHA256 in smartrecruiters-signature; 202 within 5 seconds; up to ten retries) and the Customer API with the Offer API and PUT /candidates/{id}/jobs/{jobId}/onboardingStatus (READY_TO_ONBOARD, ONBOARDING_SUCCESSFUL, ONBOARDING_FAILED).
- Deel per working relationship through POST /eor (employee, employment, client with team, compensation_details and seniority from GET /lookups/seniorities; team from GET /teams), POST /contracts for contractors, POST /contracts/gp for global payroll or POST /people for the own entity. Contract status CREATED, PENDING_SIGNATURE and ACTIVE.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SmartRecruiters | Field in Deel | Notes |
|---|---|---|
firstName, lastName en email | employee (naam en e-mail) | |
location.country (vacature) | Land van het contract | |
Functie van de vacature | Functietitel in het contract | |
Startdatum (offer property) | Startdatum van het contract | |
Salaris en valuta (offer property) | compensation_details | |
Werkrelatie (offer property) | Contractsoort: EOR, contractor of eigen entiteit | |
Afdeling (vacature) | client.team.id | Looked up in Deel |
Related
SmartRecruiters → ADP Workforce Now
SmartRecruiters to ADP Workforce Now integration: ready to onboard becomes a hire in ADP
SmartRecruiters → AFAS Profit
SmartRecruiters to AFAS integration: hired candidate starts onboarding, status back to SmartRecruiters
SmartRecruiters → BambooHR
SmartRecruiters to BambooHR integration: hire with Dutch fields and feedback
SmartRecruiters → Dayforce
SmartRecruiters to Dayforce integration: validate first, then create the employee