Recruitment to HR
Recruitee to Remote integration: hires abroad straight into an employment at Remote
With an integration between Recruitee and Remote, a candidate hired in Recruitee for a country without an own entity automatically becomes an employment at Remote, with name, email, job title, country and provisional start date. HR checks the data and sends the invitation, after which the new colleague completes the rest at Remote.
What the integration does
Organisations that recruit in Recruitee and hire outside the Netherlands through Remote as employer of record retype every foreign hire into Remote. Remote asks for different data per country, and until the employment exists, Remote cannot start the legal checks and the contract.
- The recruiter marks the candidate as hired in Recruitee.
- KoppelHet checks from the job whether the country runs through Remote; Dutch hires do not go to Remote.
- KoppelHet fetches from Remote which fields that country asks for and creates the employment.
- HR sees the employment at Remote, adds what Recruitee does not know and sends the invitation.
- If the candidate withdraws before signing, KoppelHet cancels the onboarding at Remote.
What to watch for with Recruitee and Remote
- Remote asks for different fields per country and adjusts them when legislation changes. KoppelHet fetches the current form for that country for every hire, instead of using a fixed field list.
- An employment at Remote can only be fully changed as long as the invitation has not been sent. That is why KoppelHet does not send the invitation itself; HR checks first, and changes after the invitation go through Remote.
- Recruitee records a country as placement location, Remote wants a three-letter country code. KoppelHet translates the location to that code and keeps Dutch placements out of Remote.
- The candidate number from Recruitee goes along as external reference. Remote does not enforce that it is unique, so KoppelHet checks itself whether a candidate already has an employment.
- If a candidate drops out, the onboarding at Remote can only be cancelled as long as the contract has not been signed. After that it is a termination, which KoppelHet leaves to HR.
- For a new customer Remote may first ask for a company check or a reserve payment. Those signals arrive as webhooks, and KoppelHet shows them with the hire, so the recruiter knows why onboarding is still waiting.
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 Dutch hires go to Remote too?
No. They go to your own HR or payroll system. KoppelHet decides per job which way it goes.
Does the integration send the invitation to the new colleague?
Not by default, because the employment can hardly be changed afterwards. Automatic invitations can follow later as an extension.
Does this work for contractors?
The integration creates employees. Contractors through Remote are agreed separately.
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 signed candidate_moved webhook to a stage with the hire category (X-Recruitee-Signature header) and the ATS API for candidate, placement location and profile fields.
- To Remote through the Remote API with a company-scoped bearer token. First show form schema (employment_basic_information) for the country, then create employment with basic_information, company_id, country_code, external_id and type employee. Status is followed through show employment (status, employment_lifecycle_stage).
- Cancellation through POST /v1/cancel-onboarding/{employment_id}, only with status created, created_awaiting_reserve, created_reserve_paid or pre_hire and a contract not yet signed. Webhooks employment.onboarding.cancelled and the eor_hiring events for company checks and reserve.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Remote | Notes |
|---|---|---|
name | basic_information.name | |
emails[0] | basic_information.email | Remote sends the invitation to this address |
Functie (profielveld) | basic_information.job_title | |
Startdatum (profielveld) | basic_information.provisional_start_date | |
placement_locations[0] (land) | country_code | Three-letter country code, for example DEU |
Kandidaat-ID | external_id | |
Vaste waarde | type employee |
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