Recruitment to HR
Workable to Dayforce integration: hire from the Hired stage, validated first
With an integration between Workable and Dayforce, a candidate with an accepted offer in the Workable Hired stage becomes an employee in Dayforce, with start date, location, work assignment and employment status. Workable only offers a Dayforce integration as custom work at extra cost; KoppelHet builds it with a validation in Dayforce first, because Dayforce does not delete an employee again.
What the integration does
Organisations that use Dayforce for HR and pay and recruit in Workable retype every hire in Dayforce. A mistake there cannot be removed with a click, and the salary interval from the Workable offer is easily misread when retyping.
- The recruiter moves the candidate to the Hired stage in Workable.
- KoppelHet fetches candidate, job and offer and checks that the offer was accepted.
- Dayforce validates the new employee without saving it.
- Without errors KoppelHet creates the employee for real.
- On an error HR gets a notice with the reason from Dayforce.
What to watch for with Workable and Dayforce
- Workable lists Dayforce as an integration with the status custom, built by Workable and for an additional fee. What it does is not on the public page. KoppelHet is an alternative if you want to follow the integration yourselves in one platform with other integrations.
- Dayforce does not delete an employee once created. KoppelHet therefore only reacts to the Hired stage with an accepted offer, not to an earlier stage in which a candidate can still drop out.
- Dayforce can validate a new employee without saving. KoppelHet does that for every Workable hire, so an unknown location or a missing required value gives a notice instead of a half employee.
- The salary in Workable has an amount, an interval such as month or hour, and a currency. Dayforce distinguishes hourly and salaried employees. In the first version KoppelHet only uses the interval to choose the type of pay; HR records the amount, and carrying it over can be added later.
- An employee in Dayforce gets a key that the integration supplies itself. KoppelHet uses the Workable candidate number with a fixed prefix, so a second notification about the same candidate finds the existing employee.
- In Workable the start date is a variable in the offer document, and its name differs per account. During setup we record which variable it is; if it is missing, KoppelHet stops instead of using the hired date as the first working day.
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
When do you choose Workable's Dayforce integration?
If you want to keep everything with Workable and the extra fee is no problem. Do ask which fields it carries and who resolves errors.
What if the candidate does not come after Hired?
Then the employee is already in Dayforce. KoppelHet reports it to HR, which ends the employment in Dayforce.
Does the new employee get access to Dayforce right away?
No. KoppelHet sends no access email on creation; HR arranges access before the start date.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Workable through a subscription on candidate_moved with stage_slug hired (HMAC-SHA256 in X-Workable-Signature) and GET /candidates/:id, /jobs/:shortcode and /candidates/:id/offer (state; document_variables with start_date; salary with amount, frequency and currency_iso). Token with r_candidates and r_jobs.
- Dayforce through POST on /api/{clientName}/v1/Employees with isValidateOnly=true and then without, with XRefCode, FirstName, LastName, HireDate and subordinate resources such as Contacts, Locations, WorkAssignments, EmploymentStatuses and WorkContracts. An added employee cannot be removed.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Workable | Field in Dayforce | Notes |
|---|---|---|
firstname en lastname | FirstName en LastName | |
Kandidaat-ID | XRefCode | With a fixed prefix |
email en phone | Contacts | |
location (vacature) | Locations en WorkAssignments | Through a lookup table |
document variable start_date | HireDate | |
Contractsoort (vacature) | EmploymentStatuses | |
Uren per week (document variable) | WorkContracts |
Related
Workable → ADP Workforce Now
Workable to ADP Workforce Now integration: from the Hired stage to an in-progress hire per ADP company
Workable → AFAS Profit
Workable to AFAS integration: a candidate in the hired stage starts onboarding in AFAS
Workable → BambooHR
Workable to BambooHR integration: hire with salary interval and later changes
Workable → Deel
Workable to Deel integration: from the Hired stage to a draft contract in Deel