Recruitment to HR
Carerix to SAP SuccessFactors integration: successful placement as a new employee in Employee Central
With an integration between Carerix and SAP SuccessFactors, a candidate with a successful match in Carerix becomes a new employee in Employee Central, with person, employment and job on the start date, with the right legal entity and the vacancy's hours. Carerix does not report a placement by itself; KoppelHet checks every quarter of an hour which matches changed status.
What the integration does
Organisations that recruit in Carerix in the Netherlands and use SAP SuccessFactors Employee Central globally pass every placement to an HR service centre that retypes the new employee. Legal entity, contract type and hours must be chosen as codes in Employee Central, and that is where it often goes wrong.
- 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 takes only the successful ones.
- KoppelHet checks in Employee Central whether the person already exists; if so, HR decides.
- Person, employment and job are created in Employee Central, with a hire event on the start date.
- The agreed salary goes to HR as a task; errors are shown per step in the KoppelHet platform.
What to watch for with Carerix and SAP SuccessFactors
- Only statuses ticked as a successful placement in Carerix lead to an employee in Employee Central. The existing Carerix setup thus decides when HR gets a new colleague, without a separate list in the integration.
- Employee Central wants the person first, then the employment and then the job with a hire event. KoppelHet remembers per Carerix match which step is done, so on an error, such as an unknown job code, only the missing step runs again.
- A Carerix vacancy can belong to a legal entity, and Employee Central records the company in the job. Per Carerix entity we record the legal entity code in Employee Central, so a placement does not fall under the wrong company.
- Carerix records the contract type on the vacancy and the hours per week as a number. KoppelHet translates the contract type to the employee class in Employee Central and sets the hours as standard hours in the job, so part-time is right from the start.
- Employee Central has its own rehire and records at termination whether someone may come back. KoppelHet therefore first searches by name and date of birth from Carerix, and on a match creates nothing but passes it to HR.
- The salary is text on the match in Carerix, while compensation in Employee Central consists of pay components per country. KoppelHet puts the salary in a task for HR; carrying it over automatically can be added later.
- Carerix sends no message on a status change. KoppelHet requests the changed matches every quarter of an hour; because a start is usually weeks later, Employee Central does not notice that delay.
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 interim workers also go to Employee Central?
Only if you want them to. Per contract type in Carerix we record whether the placement is passed on.
Do BSN and bank account come from Carerix?
No. HR or the employee enters them in Employee Central, or Dutch payroll does.
We already have an integration platform. Does this fit alongside it?
Yes. The integration runs on the KoppelHet platform and every action is in the audit logging.
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 and scope urn:cx/cx5Wrapper:data/crmatch:read. crMatchPage with a qualifier on statusInfoModificationDate; statusInfo.isSuccessfullyFilled; CRMatch jobStartDate and agreedSalary (String); CREmployee firstName, lastNamePrefix, lastName, birthDate, emailAddress and mobileNumber; CRVacancy toLegalEntity, toContractTypeNode, hoursPerWeek and toFunctionLevel1.
- SAP SuccessFactors Employee Central through OData v2 upserts in the order PerPerson and PerPersonal, EmpEmployment and EmpJob with a hire event; PerEmail and PerPhone for contact details; personIdExternal as key. Legal entity and job classification are foundation objects; okToRehire sits on EmpEmploymentTermination. API user with OAuth 2.0; basic authentication is being phased out.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Carerix | Field in SAP SuccessFactors | Notes |
|---|---|---|
CRMatch _id | Referentie bij de nieuwe medewerker | Prevents a second person in a later run |
CREmployee firstName, lastNamePrefix en lastName | PerPersonal (firstName, lastName) | |
CREmployee birthDate | PerPerson.dateOfBirth | |
CREmployee emailAddress en mobileNumber | PerEmail en PerPhone (privé) | |
CRMatch jobStartDate | EmpEmployment.startDate | |
CRVacancy toLegalEntity | EmpJob.company | Through a lookup table |
CRVacancy toContractTypeNode | EmpJob.employeeClass | Through a lookup table |
CRVacancy hoursPerWeek | EmpJob.standardHours | |
CRVacancy toFunctionLevel1 | EmpJob.jobCode | Through a table to the job classification |
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