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 |
| Optional/Required | Format:
Corresponds to |
| Optional/Required | Format: |
| Required | Format:
|
| Optional | Format:
|
| Optional (Recommended) | Format:
|
| Optional/Required | Format:
|
| Optional/Required | Format: |
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
externalApplicationIDorsapiaApplicationIDWhen using application IDs,
externalCandidateIDandcandidateEmailare optional
Option 2: Candidate-based matching
Provide either
candidateEmailorexternalCandidateID(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:
