Recruitment to HR
Carerix to Deel integration: successful placement as a person or contract in Deel
With an integration between Carerix and Deel, a candidate with a successful match in Carerix becomes a person in Deel with the right legal entity and team, or, if the contract type calls for it, an EOR contract with nationality from Carerix. KoppelHet checks changed matches every quarter of an hour and keeps track itself of which match belongs to which person or contract in Deel.
What the integration does
Organisations that recruit in Carerix and use Deel for staff in several countries enter every successful placement in Deel by hand. Per placement HR must choose between an own entity and an EOR contract, and look up the team and entity that Deel requires.
- The recruiter sets the match in Carerix to a status for a successful placement.
- Every quarter of an hour KoppelHet retrieves the changed matches and reads candidate and vacancy.
- Using the contract type from Carerix, KoppelHet chooses between a person at an own entity and an EOR contract.
- KoppelHet creates the person or the contract in Deel, without an invitation to the new employee.
- KoppelHet records which Deel ID belongs to which Carerix match and reports errors to HR.
What to watch for with Carerix and Deel
- Deel creates a different record per type of employment - a person without a contract at an own entity, an EOR contract, a contractor or a global payroll employee. Which one it becomes, KoppelHet reads from the contract type on the Carerix vacancy, with a table per value.
- For a person without a contract, Deel requires a team and a legal entity. A Carerix vacancy can belong to a legal entity; per Carerix entity we record the Deel ID, and the team follows from the department of the vacancy.
- According to Deel, recruitment systems usually do not record nationality, while an EOR contract does require it. Carerix has its own field for it on the candidate. KoppelHet carries it over as an ISO country code; if the field is empty, an EOR hire stops with a notice.
- Deel writes nothing back to the recruitment system and has no place to store a contract ID with an application. KoppelHet therefore keeps track itself of which Carerix match produced which Deel ID, and also puts the match number in the person's external ID field in Deel.
- By default Deel sends no invitation for a new person without a contract, unless the integration asks for an immediate invitation. KoppelHet leaves the invitation off, so the new employee does not get an email from Deel weeks before the start date.
- A contractor in Deel must first complete their contractor profile before a contract can be created. For a Carerix placement as a freelancer, KoppelHet therefore creates no contract in the first version, but prepares a task for HR with the data from Carerix.
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 Carerix have its own Deel integration?
We did not find one in the public documentation of Carerix or Deel. KoppelHet builds on the APIs of both.
Does Deel run Dutch payroll?
That depends on the type of employment. A person without a contract is only in Deel's HR records; payroll may then run elsewhere.
Does the salary go to Deel?
For an EOR contract yes, because Deel requires it there. For a person without a contract no; that 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.
- Carerix through the GraphQL API (https://api.carerix.io/graphql/v1/graphql), confidential client with client credentials. crMatchPage with a qualifier on statusInfoModificationDate and statusInfo.isSuccessfullyFilled; CRMatch _id and jobStartDate; CREmployee firstName, lastNamePrefix, lastName, emailAddress, toNationalityNode and toCountryNode; CRVacancy toLegalEntity, toContractTypeNode, toWorkUnitNode and toFunctionLevel1.
- Deel through POST /rest/pwac (scope people:write; data.person with first_name, last_name, email and start_date required, plus job_title, external_id, nationality and address.country as ISO 3166-1 alpha-2; data.client with team.id and legal_entity.id; invitation.action DISABLE or IMMEDIATE). EOR through POST /eor with employee, employment, client.team, seniority from GET /lookups/seniorities and compensation_details. Testing against api-staging.letsdeel.com.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Carerix | Field in Deel | Notes |
|---|---|---|
CRMatch _id | external_id | Also in KoppelHet's own link table |
CREmployee firstName, lastNamePrefix en lastName | first_name en last_name | |
CREmployee emailAddress | email | |
CRMatch jobStartDate | start_date | |
CRVacancy toLegalEntity | client.legal_entity.id | Through a lookup table |
CRVacancy toWorkUnitNode | client.team.id en department.id | Through a lookup table |
CRVacancy toFunctionLevel1 | job_title | |
CREmployee toNationalityNode en toCountryNode | nationality en address.country | As ISO country code |
Related
Carerix → ADP Workforce Now
Carerix to ADP Workforce Now integration: placement in North America as an in-progress hire
Carerix → AFAS Profit
Carerix to AFAS integration: a placed candidate starts onboarding in AFAS Profit
Carerix → BambooHR
Carerix to BambooHR integration: successful placement as an employee with employment status in BambooHR
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce