Teamtailor logoDayforce logo

Recruitment to HR

Teamtailor to Dayforce integration: the Marketplace partner connector, and when custom work is needed

Teamtailor has a Dayforce connector in its own Marketplace that sends a candidate to Dayforce as a new employee at a chosen stage, with employee data, employment status and work assignment. KoppelHet comes in when the values cannot come one to one from Teamtailor, when a hire must be checked before Dayforce creates it for good, or when the hire must go to other systems as well.

What the integration does

Organisations that recruit in Teamtailor and manage HR and time in Dayforce can use the partner connector from the Teamtailor Marketplace. Recruiters then choose pay grade and pay type from dropdowns that must exactly match Dayforce. If something goes wrong, a wrongly created employee stays in Dayforce, because Dayforce does not delete employees.

  1. The recruiter moves the application to the stage for hired candidates.
  2. KoppelHet fetches application, candidate, job, offer and the custom fields.
  3. Pay grade, pay type and pay class follow from the job and the offer through a table, not from a dropdown the recruiter fills in.
  4. KoppelHet has Dayforce check the new employee first without saving. Only if that succeeds does Dayforce create them.
  5. If the check fails, HR gets a notice with the missing field and nothing is in Dayforce.
Teamtailor → KoppelHet → DayforceSOURCETeamtailorTARGETDayforceKoppelHetmapping · logging · monitoringTeamtailor → KoppelHet → DayforceSOURCETeamtailorTARGETDayforceKoppelHetmapping · logging · monitoring
Out: Job application, candidate and job · Employee with name, role and hire date · Employment status with pay grade, pay type and pay class · Work assignment with average daily hours · CV as a document in Dayforce

What to watch for with Teamtailor and Dayforce

  • The partner connector requires option values in Teamtailor to exactly match the XRefCodes in Dayforce. A renamed pay grade in Dayforce then silently breaks the dropdown. KoppelHet keeps that translation in a table outside Teamtailor and reports an unknown code before anything is created.
  • Dayforce does not delete an employee once created. The partner connector sends directly at the trigger; KoppelHet first has Dayforce validate only and creates the employee only when all required modules are correct.
  • According to Teamtailor the partner connector can copy answers to candidate questions, based on keywords in the question. Two questions with the same keyword can then land in the wrong field. KoppelHet only uses custom fields with a fixed name, no question texts.
  • Dayforce asks for average daily hours on the work assignment, while a Dutch offer usually states hours per week. KoppelHet converts the hours from the offer using the number of working days, so a 32-hour contract over four days does not reach Dayforce as 6.4 hours per day.
  • The integration needs a web service user in Dayforce with its own role, with rights to create and update employee profiles. The same user could serve the partner connector and KoppelHet, but we recommend a separate user per integration, so Dayforce shows who created what.
  • Teamtailor can send identification data to Dayforce. For Dutch employees we keep the BSN out of Teamtailor; HR completes it in Dayforce during onboarding, so the recruitment system holds no BSN.

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

What if a candidate does not start after all?

Then HR gets a notice. Dayforce does not delete the employee, so HR ends the employment or adjusts the start date.

Do documents go to Dayforce?

The CV can go along as pdf, doc or docx, with a document type that exists in Dayforce. Other documents can come later as an extension.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Teamtailor through the job_application.update webhook to a stage of type hired and the Teamtailor API (job-applications, candidates, jobs, job-offers, custom fields and the onboarding add-on with start-date). Teamtailor has a rate limit per short period.
  • Dayforce through the REST API with a web service user (role with the HCM Anywhere and Web Services features). POST Employees first with isValidateOnly, then for real, with EmploymentStatuses (PayType, PayClass, PayGrade), WorkAssignments and Documents with DocumentTypeXRefCode. A created employee cannot be deleted.

Which fields are transferred

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

Field in TeamtailorField in DayforceNotes
job-application idEigen veld in DayforceRecognises a second notification for the same application
first-name en last-nameFirstName en LastName
Onboarding: start-date of aanbodHireDate
department en role (vacature)WorkAssignments (positie en locatie)Through a table with Dayforce XRefCodes
Aanbod (uur- of maandloon)EmploymentStatuses (PayType, PayClass, PayGrade)Through a table, not a dropdown
Uren per week (aanbod)WorkAssignments (gemiddelde uren per dag)Converted to hours per day
Cv (kandidaat)Document met DocumentTypeXRefCodeOnly pdf, doc and docx

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.