Skip to main content

Setting Up Leaver Data (Churned Employees) via flat-file Integration for Dayforce

This guide explains how to configure Dayforce to send leaver (churned employee) data to Sapia.ai via flat-file (CSV) export.

E
Written by Elbert Pranoto

For Dayforce, leaver (churned employee) data collection can be collected via flat-file data transfer.
Clients can automate this through Dayforce reporting system and Integraton Studio any other export service, with files transferred to Sapia.ai on a regular schedule via sFTP.

sFTP Folder: LeaverData

For complete sFTP details and setup instructions, refer to: https://help.sapia.ai/en/articles/12394560-importing-data-via-sftp


CSV Specification

File Type/Format: CSV (Comma Separated Value)

Column Header

Required?

Description

externalApplicationID

Optional/Required

Format: String

Corresponds to candidateAssessmentGuid in Dayforce.

externalCandidateID

Optional/Required

Format: String

Corresponds to candidateNumber in Dayforce.

endDate

Required

Format: yyyy-MM-dd


The employment termination date (resignation, contract end, or employment conclusion).

hiredDate

Optional

Format: yyyy-MM-dd


The date the candidate/employee was initially hired for the position.

comment

Optional (Recommended)

Format: String


Free-text field for additional information about the employment termination or leaver circumstances.

sapiaApplicationID

Optional/Required

Format: String


Corresponds to assessmentReceiptID in Dayforce.

candidateEmail

Optional/Required

Format: String

Important Notes

Column Order and Headers

Column headers and their order do not need to match this specification exactly. Sapia.ai supports flexible field mapping during setup, so your CSV columns can be mapped to the correct fields in Sapia.ai's configuration.

Data Identifiers

Sapia.ai uses the following logic to match records in your file:

Option 1: Application-based matching (recommended)

  • Provide either externalApplicationID or sapiaApplicationID

  • When using application IDs, externalCandidateID and candidateEmail are optional

Option 2: Candidate-based matching

  • Provide either candidateEmail or externalCandidateID (without application IDs)

  • Sapia.ai will match the record to the candidate's most recent assessed job application

Note: If you provide application-level identifiers (externalApplicationID or sapiaApplicationID), they will take precedence over candidate-level identifiers for more precise matching.

Below is the sample file:

Did this answer your question?