Recruitment to HR
Lever to Dayforce integration: signed offer as a validated new employee in Dayforce
With an integration between Lever and Dayforce, a candidate hired in Lever becomes a new employee in Dayforce, with name, start date, location, job and salary from the offer, after a check without saving. The Lever Marketplace lists a Dayforce connector for new hires, rehires and internal transfers; KoppelHet builds the integration when that is not purchased or when the upfront check and the report back in Lever make the difference.
What the integration does
Organisations that use Dayforce for HR and payroll and recruit in Lever now often enter hires into Dayforce by hand. Because Dayforce never deletes an employee once created, HR wants to be sure that only real, complete hires get in.
- At the start we agree a number range for Dayforce and record the Dayforce location per Lever location.
- Lever reports candidateHired; KoppelHet fetches opportunity, offer and posting and checks whether the candidate has signed.
- KoppelHet first has Dayforce only validate the new employee.
- If the check passes, KoppelHet actually creates the employee; otherwise the reason goes on the opportunity as a note.
What to watch for with Lever and Dayforce
- The Lever Marketplace lists a Dayforce connector that sends hired candidates to Dayforce, with separate flows for a new hire, a rehire and an internal transfer. Who builds it and which fields go across by default is not on that page, and pulling master data back from Dayforce costs extra according to Lever.
- Dayforce can first only validate a new employee. KoppelHet runs that check with the data from Lever, and an error, such as a location Dayforce does not know, goes on the opportunity as a note. That way the recruiter sees it in Lever and nothing is half-created in Dayforce.
- An employee in Dayforce cannot be deleted, and a Lever offer already shows a signed document after the first signature. KoppelHet therefore only creates the employee once the candidate has signed.
- An opportunity in Lever can come from an internal candidate. That person is already an employee in Dayforce, so KoppelHet does not create a new employee but passes the transfer to HR. Processing internal transfers automatically can be added later as an extension.
- The Lever offer has an amount, a currency and an interval for the salary. KoppelHet gives Dayforce the amount with the matching period, so an hourly rate from Lever does not end up as a monthly salary in Dayforce payroll.
- Dayforce lets the integration choose an employee's key itself. KoppelHet uses an agreed number range and puts the opportunity number from Lever into a custom field, so the daily comparison after Lever's five failed webhook attempts finds the missed hire.
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
Lever already has a Dayforce connector. Why KoppelHet?
If it fits, use it. KoppelHet is there when the connector is not purchased, or when an upfront check and a note in Lever are needed.
What if a hired candidate does not start after all?
Dayforce cannot delete the employee. KoppelHet reports it to HR, who terminates the employment in Dayforce.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Lever through the candidateHired webhook (data.opportunityId and contactId; HMAC-SHA256 over token and triggeredAt with the signing token; five retries) and the Lever API with an API key - GET /opportunities/:opportunity (origin and contact), GET /opportunities/:opportunity/offers (fields anticipated_start_date, job_title, salary_amount, compensation_currency, salary_interval; signatures), GET /postings/:posting and POST /opportunities/:opportunity/notes.
- To Dayforce through the REST API with POST on Employees, first with isValidateOnly and then for real; XRefCode, FirstName, LastName, HireDate and subordinate resources such as 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 Lever | Field in Dayforce | Notes |
|---|---|---|
Nummerreeks van KoppelHet | XRefCode | |
name (één veld) | FirstName en LastName | |
emails[0] en phones[0] | Contactgegevens | |
Offer field anticipated_start_date | HireDate en EmploymentStatuses | |
categories.location (posting) | WorkAssignments (locatie) | Through a table per label |
Offer field job_title | WorkAssignments (functie) | |
Offer fields salary_amount, compensation_currency en salary_interval | Salaris met periode in Dayforce | |
opportunity id | Eigen veld in Dayforce |
Related
Lever → BambooHR
Lever to BambooHR integration: hired candidate as a new employee profile in BambooHR
Lever → Deel
Lever to Deel integration: hired candidate as own employee or EOR contract in Deel
Lever → HiBob
Lever to HiBob integration: hired candidate with offer as an employee in Bob
Lever → Oracle HCM Cloud
Lever to Oracle HCM integration: hired opportunity as a pending worker in Oracle