Recruitment to HR
SmartRecruiters to Remote integration: hires in countries without an entity as EOR employment at Remote
With an integration between SmartRecruiters and Remote, a candidate who is ready to onboard in SmartRecruiters for a country without an own entity becomes an employment at Remote as employer of record, with name, job title, country and provisional start date. Hires for the own entities stay outside Remote, and the recruiter sees in the onboarding status in SmartRecruiters whether the employment exists.
What the integration does
Organisations that recruit in SmartRecruiters for several countries and hire through Remote where they have no entity enter the EOR hires into Remote by hand. Which hire must go to Remote is now decided by the recruiter per person.
- At the start we record in which countries the organisation has its own entity.
- The recruiter sets the onboarding status of the hired candidate to ready to onboard.
- If the job's country is an EOR country, KoppelHet fetches that country's form from Remote and creates the employment.
- KoppelHet sets the onboarding status in SmartRecruiters to successful or failed.
- HR checks in Remote and sends the invitation.
What to watch for with SmartRecruiters and Remote
- Through the API Remote only creates employments of type employee, so employer of record. KoppelHet looks at the country of the SmartRecruiters job and only sends hires in countries without an own entity to Remote; the others are left alone.
- Remote requires an answer to whether the new employee was employed before, next to a provisional start date. SmartRecruiters has no fixed field for it, so we add a property to the offer and send no when it is empty.
- Remote does not enforce that an external reference is unique, and a SmartRecruiters candidate can be on several jobs. KoppelHet uses candidate and job ID together as reference and checks itself whether it already has an employment.
- For a new customer Remote can first ask for a company check or deposit, and reports that through a webhook. The onboarding status in SmartRecruiters has only three values. KoppelHet sets it to successful as soon as the employment exists, and shows Remote's waiting reason in the KoppelHet platform.
- Remote asks for different fields per country, and far from everything is in a SmartRecruiters offer. KoppelHet fills what is there and leaves the rest empty for HR. The invitation only goes out after that, because an employment can only be changed to a limited extent after the invitation.
- A SmartRecruiters job gives the country as a two-letter code, such as NL or US. Remote uses a three-letter code for an employment, such as AUS in its own example. KoppelHet converts the code before that country's form is requested from Remote.
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
Do contractors also go to Remote?
Not through this integration, because Remote's API only creates EOR employments. HR sets up a contractor in Remote itself.
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 OAuth 2.0 client credentials. Status back through PUT /candidates/{id}/jobs/{jobId}/onboardingStatus (ONBOARDING_SUCCESSFUL or ONBOARDING_FAILED).
- To Remote through the Remote API with a company-scoped token - the country's form schema, then create employment with company_id, country_code, type employee, external_id and basic_information (name, email, job_title, provisional_start_date, has_seniority_date). Webhooks for the eor_hiring events about company check and deposit.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SmartRecruiters | Field in Remote | Notes |
|---|---|---|
firstName en lastName | basic_information.name | |
email | basic_information.email | |
Functie van de vacature | basic_information.job_title | |
Startdatum (offer property) | basic_information.provisional_start_date | |
Eerder in dienst (offer property) | basic_information.has_seniority_date | No when empty |
location.country (vacature) | country_code | |
Kandidaat-ID en job-ID | external_id |
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