Recruitment to HR
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
With an integration between Bullhorn and Dayforce, the first approved placement of a candidate who becomes an employee becomes an employee in Dayforce, with the start date of paid employment, the position code and the pay group from the placement. Dayforce first validates every hire without saving, and contractors and later placements of the same person do not create a new employee.
What the integration does
Organisations that place people through Bullhorn and pay their own employees in Dayforce retype every new placement in Dayforce. HR has to check each time whether the person is already an employee, and freelancers do not belong there. A mistake stays in Dayforce.
- The recruiter approves the Placement in Bullhorn.
- KoppelHet reads the placement from the event queue and looks at the employee type.
- If the candidate is not an employee yet, KoppelHet first has Dayforce validate the new employee.
- Without errors KoppelHet creates the employee and records the Dayforce number with the candidate.
- A next placement of the same person goes to HR as an alert.
What to watch for with Bullhorn and Dayforce
- Bullhorn has fields on a Placement meant for payroll integrations, such as a position code, a pay group and an employee type for payroll. The recruiter fills them on the placement; KoppelHet puts the position code in the work assignment and the pay group in Dayforce, so HR does not choose them again.
- Dayforce never removes an employee once added. KoppelHet therefore only reacts to an approved placement and first has Dayforce validate without saving; an error becomes an alert instead of an employee that stays.
- A temp or seconded worker gets a new Placement in Bullhorn for every assignment, while Dayforce has one employee per person. KoppelHet remembers which Dayforce number belongs to which Bullhorn candidate and reports a next placement to HR instead of creating a second employee.
- The employee type on a placement has values such as W2, 1099, Employee and Contractor. Only W2 and Employee go to Dayforce; freelancers and 1099 contractors stay out of payroll.
- Besides the start date of the work, Bullhorn has a separate date on which paid employment starts, for payroll integrations. KoppelHet uses that as the hire date in Dayforce, so an unpaid induction day does not count as the first working day.
- A candidate's country is stored in Bullhorn as a number from its own list, retrievable through the Candidate meta. Dayforce works with its own codes. KoppelHet translates the Bullhorn number and stops at validation if a country is missing from the table.
- Bullhorn also has a field on a placement that shows whether the placement has reached the payroll provider. KoppelHet fills it after a successful hire in Dayforce, so the recruiter sees in Bullhorn that the person is in payroll.
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 pay rate of the placement come along?
Not in the first version. HR records pay in Dayforce; sending it can be added later as an extension.
What happens when an approved placement changes?
HR then gets an alert. KoppelHet does not change Dayforce automatically.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Bullhorn through the REST API after OAuth 2.0 and a REST login with BhRestToken. Event subscription on Placement (INSERTED and UPDATED), read with GET event/subscription. Placement fields status, employeeType, employmentStartDate, dateBegin, positionCode, payGroup, payrollEmployeeType and payrollSyncStatus; Candidate firstName, lastName, email and address.countryID (labels through /meta/Candidate).
- Dayforce through POST https://www.dayforcehcm.com/api/{clientName}/v1/Employees with isValidateOnly=true and then without; EmployeePostRequest with XRefCode, FirstName, LastName and subordinate resources Contacts, WorkAssignments, EmploymentStatuses and Locations.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Bullhorn | Field in Dayforce | Notes |
|---|---|---|
Candidate firstName en lastName | FirstName en LastName | |
Candidate email | Contacts (e-mail) | |
Placement employmentStartDate | HireDate | Falls back to dateBegin if the field is empty |
Placement positionCode | WorkAssignments (positie) | |
Placement payGroup | Betaalgroep in EmploymentStatuses | Lookup table to the codes in Dayforce |
Placement employeeType | Filter: alleen Employee of W2 | Contractor and 1099 are excluded |
Candidate id | Koppeltabel naar XRefCode |
Related
Bullhorn → AFAS Profit
Bullhorn to AFAS integration: a consultant's first placement starts onboarding
Bullhorn → BambooHR
Bullhorn to BambooHR integration: first placement as an employee with a status row in BambooHR
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Bullhorn → HiBob
Bullhorn to HiBob integration: an approved placement as a new employee in Bob