Recruitment to HR
Carerix to YouForce integration: a placed candidate starts the hire workflow in YouForce
With an integration between Carerix and Visma YouForce, a candidate placed in Carerix automatically starts the hire workflow in YouForce, with personal details, start date, hours, contract type, job and organisational unit from the vacancy. HR completes the workflow in YouForce, and a former employee gets a rehire instead of a second employee number.
What the integration does
Organisations that recruit in Carerix and administer their staff in YouForce fill in the YouForce hire form by hand after every placement. Someone who worked there before sometimes gets a new employee number, because nobody searched YouForce first.
- The recruiter moves the match in Carerix to the placement status.
- KoppelHet fetches match, candidate and vacancy.
- KoppelHet searches YouForce for whether the candidate was employed before.
- A hire request starts or, for a former employee, a rehire request.
- KoppelHet follows the workflow and notifies the recruiter if HR rejects it.
What to watch for with Carerix and Visma Raet YouForce
- YouForce searches for an existing person only by surname at birth, prefix, date of birth, place of birth and first name used. Carerix stores the birth name and place of birth as separate fields on the candidate, apart from a partner name. KoppelHet uses those, so a married former employee is still found.
- A YouForce request requires the number of hours, contract type, job and organisational unit. In Carerix these are on the vacancy, not on the candidate. KoppelHet fetches them through the match and holds a placement with a notification if the vacancy lacks them.
- YouForce first confirms a request only as received. Whether HR approved it only shows once the workflow is no longer active. KoppelHet follows that status and reports a rejected request back to the recruiter in Carerix.
- The agreed salary is free text on the match in Carerix, and YouForce works with scales and steps. KoppelHet sends no amount; HR picks the grading in the workflow.
- Jobs in Carerix are their own two-level pick list. YouForce provides its own list of jobs and organisational units through the API. KoppelHet records the translation once and checks for every placement whether the YouForce code still exists.
- If an organisation has several hire workflows in YouForce, for example for permanent and temporary staff, KoppelHet picks the right workflow per request based on the contract type 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 the integration create an employee in YouForce directly?
No. It starts the hire workflow. HR in YouForce checks and completes it.
What if HR rejects the request?
KoppelHet sees the outcome of the workflow and reports the rejection to the recruiter. After correction in Carerix the placement can go again.
What do we need to arrange in Carerix?
A client for the integration with read rights, and hours, contract type and job filled in per vacancy. At the start we check which statuses count as a placement.
What about the GDPR?
You are the controller and KoppelHet is the processor, under a data processing agreement. Only placed candidates go to YouForce, 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. crMatchPage on statusInfoModificationDate with statusInfo.isSuccessfullyFilled; CREmployee (birthName, lastNamePrefix, firstName, birthDate, birthCity) and CRVacancy (hoursPerWeek, toContractTypeNode, toFunctionLevel1, jobTitle).
- YouForce through the Recruitment API with OAuth 2.0. GET persons/search (only lastNameAtBirth, lastNameAtBirthPrefix, birthDate, birthPlace and knownAs); POST hires or POST persons/{personId}/contracts, both 202 Accepted, with mandatory candidateID and employmentDetails (payrollClientCode, payrollInstitutionCode, hireDate, employeeType, contractType, organizationUnit, jobProfile, amountOfHours); optional X-Raet-Workflow header. Poll the status until hrssWorkflowStatus.data.isActive is false, then endStatus OK, NOK or InProgress. Scopes HSS_startWorkflow and Get_Basic (jobProfiles, organizationUnits).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Carerix | Field in Visma Raet YouForce | Notes |
|---|---|---|
CRMatch _id | candidateID | Per match, so a second placement is recognisable |
CREmployee birthName en lastNamePrefix | Achternaam en voorvoegsel bij geboorte | Also used to find a former employee |
CREmployee birthDate en birthCity | Geboortedatum en geboorteplaats | |
CREmployee firstName | Roepnaam (knownAs) | |
CRMatch jobStartDate | employmentDetails.hireDate | |
CRVacancy hoursPerWeek | employmentDetails.amountOfHours | |
CRVacancy toContractTypeNode | employmentDetails.contractType | Through a lookup table |
CRVacancy toFunctionLevel1 en jobTitle | employmentDetails.jobProfile | Code from the YouForce list |
Afdeling van de vacature | employmentDetails.organizationUnit |
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