Carerix logoDayforce logo

Recruitment to HR

Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce

With an integration between Carerix and Dayforce, a candidate with a successful match in Carerix becomes a new employee in Dayforce, with hire date, address, contact details and work assignment. Because an employee in Dayforce can never be removed, KoppelHet has Dayforce validate every hire first and only then creates it for real.

What the integration does

Organisations that recruit in Carerix and use Dayforce as their HR system copy every successful placement into Dayforce by hand. A typo is awkward there, because a created employee stays in Dayforce, so HR checks every entry twice.

  1. The recruiter sets the match in Carerix to a status for a successful placement.
  2. Every quarter of an hour KoppelHet retrieves the changed matches and reads candidate and vacancy.
  3. KoppelHet first sends the new employee to Dayforce as a validation, without saving.
  4. If Dayforce approves the data, KoppelHet creates the employee for real; otherwise HR gets the error message.
  5. Address and contact details are then added under the new employee's XRefCode.
Carerix → KoppelHet → DayforceSOURCECarerixTARGETDayforceKoppelHetmapping · logging · monitoringCarerix → KoppelHet → DayforceSOURCECarerixTARGETDayforceKoppelHetmapping · logging · monitoring
Out: Match with status and start date · Candidate with name, date of birth, address and contact details · Vacancy with function, contract period and hours · Employee in Dayforce with XRefCode · Address, contact details and work assignment in Dayforce

What to watch for with Carerix and Dayforce

  • According to the Dayforce developer documentation, employees persist in the database forever. A placement that is later reversed in Carerix therefore leaves an employee behind in Dayforce. KoppelHet therefore only reacts to statuses ticked as successful in Carerix, not to a proposal or contract offer.
  • Dayforce has a parameter that only validates a new employee and does not save it. KoppelHet first sends every Carerix hire that way, and only for real when there are no errors. An unknown function code or missing field thus reaches HR before anything is in Dayforce.
  • Address, contact details and work assignment are separate parts in Dayforce under the employee's XRefCode. KoppelHet builds the XRefCode from the Carerix match number, so every part can later be linked to the same hire.
  • Carerix stores house number and addition separately, as well as postcode and city. KoppelHet puts those fields separately in the address in Dayforce, so payroll and reports do not depend on an address as free text.
  • Dayforce has work contracts as a separate part of an employee. A Carerix vacancy has a text field for the contract period. If it holds a temporary period, KoppelHet records it as a work contract; an unclear value goes to HR as a notice.
  • The salary is stored in Carerix on the match, with an amount and a unit. In the first version KoppelHet does not carry it over to Dayforce, because pay components differ per setup there; HR gets it as a task, and filling it automatically can be added later.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does Carerix have its own Dayforce integration?

We did not find one in the public documentation of Carerix or Dayforce. KoppelHet builds on the APIs of both.

What if a placement falls through after all?

The employee remains in Dayforce. HR terminates them there in the usual way; KoppelHet sends a notice when the match in Carerix changes status.

Do BSN and bank account come from Carerix?

No, not by default. HR or the employee enters them in Dayforce.

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, jobStartDate, salary (Float) and salaryUnitTag; CREmployee firstName, lastNamePrefix, lastName, birthDate, address fields, emailAddress and mobileNumber; CRVacancy toFunctionLevel1, hoursPerWeek and contractPeriod (String).
  • Dayforce through the REST API - POST on /api/{clientName}/v1/Employees, first with isValidateOnly and then for real. Parts through /V1/Employees/[XRefCode]/ with Addresses, Contacts, WorkAssignments and WorkContracts. Employees cannot be deleted after creation.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in CarerixField in DayforceNotes
CRMatch _idXRefCodeWith a fixed prefix; unique per hire
CREmployee firstName, lastNamePrefix en lastNameFirstName en LastName
CREmployee birthDateBirthDate
CRMatch jobStartDateHireDate
CREmployee street, houseNumber, houseNumberSuffix, postalCode en cityAddresses
CREmployee emailAddress en mobileNumberContacts (privé)
CRVacancy toFunctionLevel1 en hoursPerWeekWorkAssignmentsFunction through a lookup table
CRVacancy contractPeriodWorkContractsOnly for a temporary contract

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.