Unique Identifiers

Dayforce allows client administrators to designate XRefCode (external reference code) values in many areas of the application, making it possible for clients to create integrations between Dayforce and other applications based on a shared unique identifier.  For example, XRefCodes can be set for client-level configuration items such as org unit, employment status and even employees, making it possible for Dayforce to exchange data with another system based on matching key values.  The general expectation is that XRefCodes will be leveraged for integration purposes where they exist.

Some areas of Dayforce, such as timesheet and schedule data, are subject to batch processing to apply the client-configured business rules, and as a result, existing records are replaced by new records when the processing is complete.  This approach allows Dayforce to perform very well when processing a large volume of records, but it also makes the use of a static record identifier with integrations impossible.  For example, if a clocking employee punches in and out on a Friday morning, the initial set of records is processed according to the client’s overtime, double time, etc. policies.  When the same employee clocks in and out again, the employee’s time for the full day is reprocessed based on the business rules.

For data sets with no unique identifiers, Dayforce recommends basing the integration on a period of time, such as pay period, week, or day, and replacing that period’s data in the downstream system when changes are made in Dayforce as well as when processing errors occur for the employee in the system receiving the data.