Recruitment to HR
Recruitee to Dayforce integration: hired candidates in Dayforce without retyping
With an integration between Recruitee and Dayforce, a candidate hired in Recruitee becomes a new employee in Dayforce, with start date, location, job and the terms of the offer. Because Dayforce never deletes an employee once created, KoppelHet first checks the data with Dayforce and only then creates the employee.
What the integration does
Organisations that manage employees in Dayforce and recruit through Recruitee retype every hired candidate into Dayforce. If a candidate drops out at the last moment, they remain in Dayforce as an employee for good, with a termination on day one.
- The recruiter moves the candidate to the hire stage in Recruitee, after the contract is signed.
- KoppelHet fetches the candidate with profile, vacancy, location and the offer form fields.
- KoppelHet first has Dayforce only validate the new employee. If anything is missing, HR gets a notification and nothing is created yet.
- If everything is correct, the employee is in Dayforce with start date, location, job, hours and salary.
- HR completes the data in Dayforce that does not belong in Recruitee, such as the BSN.
What to watch for with Recruitee and Dayforce
- Dayforce never deletes an employee once created. KoppelHet therefore only creates someone at the hire stage, and not earlier in the recruitment process.
- Dayforce can validate a new employee without creating them. KoppelHet always runs that check first, so a missing location or job produces a notification and not a half-created employee.
- The integration supplies the Dayforce key of an employee itself. We agree a number range at the start, so Recruitee candidates do not clash with employees HR creates by hand.
- If the organisation recruits for several countries in Recruitee, the vacancy location determines the location in Dayforce. A Belgian location thus never ends up under the Dutch entity.
- The salary field in Recruitee has an amount but no period, and hours per week are missing. We add both to the offer form, so Dayforce receives an hourly wage or monthly salary with the right hours.
- If a hired candidate is rejected later after all, they are already in Dayforce and cannot be removed. KoppelHet notifies HR, which ends the employment in Dayforce or adjusts the start date.
- KoppelHet reacts to the type of stage in Recruitee, not its name. Recruiters can therefore rename their stages without the integration stopping.
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
What if a candidate does not start after all?
HR then gets a notification. Dayforce cannot delete the employee, so HR ends the employment or adjusts the start date.
Do we still use Dayforce's recruiting module?
No need. Recruiters keep working in Recruitee; Dayforce only receives the hired candidates.
What do recruiters need to do differently?
Fill in the offer form completely, with start date, hours and salary with period. If anything is missing, they see the notification before anything is in Dayforce.
We already have an integration platform. Does this fit alongside it?
Yes. This integration runs on the KoppelHet platform and asks nothing of your existing integration platform. Every action is in the audit logging, so operations and audit know what happened.
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 candidate_moved webhook (only stages with the hire category) and the ATS API with profile fields (date_of_birth, address, salary), placement_locations and custom fields of the offer form. API token of a separate integration user.
- Dayforce is written through the REST API with POST on Employees, first with the isValidateOnly parameter and then for real. The request holds XRefCode, FirstName, LastName, BirthDate, HireDate and subordinate resources such as Addresses, EmploymentStatuses and WorkAssignments. A created employee cannot be deleted.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Dayforce | Notes |
|---|---|---|
Kandidaat-ID | Eigen veld in Dayforce | To recognise a second notification |
Personeelsnummer (nummerreeks) | XRefCode | Issued by the integration following your number range |
Naam | FirstName en LastName | |
date_of_birth | BirthDate | |
address | Addresses | |
Startdatum (aanbiedingsformulier) | HireDate en EmploymentStatuses | |
Vestiging van de vacature (placement_locations) | WorkAssignments (locatie) | Through a lookup per location |
Functie van de vacature | WorkAssignments (functie) | Through a lookup table |
salary met periode en uren (aanbiedingsformulier) | Salaris en uren in Dayforce |
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