This section describes how the Display Enhanced Gender Last Modification Information and Effective Dating client property works in Dayforce. This client property is optional.
Important: After this feature is enabled it can’t be turned off, due to potential data integrity issues.
Important: Support teams shouldn’t turn off this feature without deleting past and future-dated records.
The Display Enhanced Gender Last Modification Information and Effective Dating client property is optional and allows customers to:
- View last modification information in some areas of Dayforce, which shows who edited employee gender information.
- If the Display Enhanced Gender Last Modification Information and Effective Dating client property is OFF, last modification information is only available in the Audit screens.
- If the Display Enhanced Gender Last Modification Information and Effective Dating client property is ON, last modification information is available directly in some areas of Dayforce, such as the Personal > Confidential Information screen in People.
- Use effective dating, in the style of an employment status record:
- If the Display Enhanced Gender Last Modification Information and Effective Dating client property is OFF, employees can have only one gender record per country and effective dating is hidden and controlled by Dayforce.
- If the Display Enhanced Gender Last Modification Information and Effective Dating client property is ON, employees can enter multiple dated values for each country they live in, work in, or are reported in.
Effective dating and history can be enabled by selecting the Display Enhanced Gender Last Modification Information and Effective Dating client property in the Properties tab of System Admin > Client Properties.
The following screenshot shows an example of the Gender grid in the Personal > Confidential Information screen when the Display Enhanced Gender Last Modification Information and Effective Dating client property is enabled. Historical and future records can be seen by clicking All.
For more information, see Enable Enhanced Employee Gender History in the Enhanced Employee Gender Guide.
Modules Supporting the Display Enhanced Gender Last Modification Information and Effective Dating Client Property
The Display Enhanced Gender Last Modification Information and Effective Dating client property is supported in the following areas of Dayforce.
| Area of Dayforce | Description |
|---|---|
| People |
In the Gender section of the Personal > Confidential Information screen. |
| XML forms |
Custom forms are supported if the XML form has been updated to use the new Gender grid. System forms are supported. No action required. Not supported for backward-compatible Gender and Gender Identity drop-down lists. |
| HR Import |
Supported if the customer is using Enhanced Employee Gender import token and entities. Not supported in backward-compatible legacy Gender and Gender Identity endpoints and entities. |
| RESTful API |
Supported if the customer is using Enhanced Employee Gender endpoints and entities. Not supported on backward-compatible legacy Gender and Gender Identity endpoints and entities. |
| Other |
The Display Enhanced Gender Last Modification Information and Effective Dating client property shares information with other areas of the system, such as reporting, payroll, benefits, and external systems. It provides the most recent assigned sex or gender identity record for a requested country. |
Why Enable the Display Enhanced Gender Last Modification Information and Effective Dating Client Property?
The Enable the Display Enhanced Gender Last Modification Information and Effective Dating client property has the following two use cases:
- This customer operates in a country, state, or province where historical gender information must be captured or is sent as a part of legal or payroll processes.
- In some countries, such as the United Kingdom, it’s possible to send historical payroll data to make corrections to employee data with the government. As such, if an employee is male and becomes female, and were receiving paternity pay, Dayforce can’t send their current gender information of female. Instead, the historical value needs to be used.
- The customer wants to allow their employees to record their current assigned sex and their sex at birth. Effective dating allows employees who have a change of assigned sex or gender identity to show this change over time if they want to disclose it.
Gender Options When the Display Enhanced Gender Last Modification Information and Effective Dating Client Property Is Enabled
When the Display Enhanced Gender Last Modification Information and Effective Dating client property is enabled for a customer, gender records for all employees will use effecting dating and show last modification information directly in grids, where applicable. When the Display Enhanced Gender Last Modification Information and Effective Dating client property turned off, last modification information is only visible in the Audits screen for an employee, and effective dating isn’t in effect.
For example, in the following screenshot, an employee was female from January 1, 1990 to September 29, 2024, and then wanted to be recorded as male beginning on September 30, 2024:
Effective Dating Examples
Employee at Company A:
Company A requires that employees provide their current assigned sex and gender identity data and has enabled the Display Enhanced Gender Last Modification Information and Effective Dating client property.
Employee at Company B:
Company B requires that any employees who change their assigned sex must provide a sex at birth record. Company B has also has enabled the Display Enhanced Gender Last Modification Information and Effective Dating client property.
HMRC (UK government tax office) might need an employee’s legally recognized sex to be recorded if historical payroll information is sent to them from Dayforce.
| Company | Country | State/Province | Assigned Sex | Gender Identity | Effective From | Effective To | Notes |
|---|---|---|---|---|---|---|---|
| Company A | Germany | - | Male | - | January 1, 2024 | 01/01/2024 is the employee’s hire date for this example. | |
| Company B | United Kingdom | - | Male | Female | May 1, 1985 | December 31, 2022 | Employee’s sex at birth |
| Company B | United Kingdom | - | Female | Female | January 1, 2023 | Employee’s current legal assigned sex |
Active/All Flag
As with employment status records or work assignment records, if the Display Enhanced Gender Last Modification Information and Effective Dating client property is enabled, then the customer will see an Active/All switch where it can be shown.
- Active: All present and future records for the employee.
- All: All past, present, and future records for the employee.
Display Enhanced Gender Last Modification Information and Effective Dating and Federal Records
Although employees can provide historical gender information for any location they live in, work in, or want to be reported in, there is an exception to this in US and Canadian federal records.
To simplify their implementation, federal records don’t currently support effective dating the same way all other records do. Assuming a federal US or Canadian record is created, the following behavior is observed when the Display Enhanced Gender Last Modification Information and Effective Dating client property is enabled:
- Assigned Sex: Not updated by Dayforce. Changes must be made by the employee or an administrator.
- Gender Identity: Not applicable. Federal records can’t include gender identity.
- Effective From: Automatically updated by Dayforce. Matches the earliest State/Province record for the employee.
- Effective To: Can’t be edited.
For more information, see Federal Event.
Date Inconsistencies and the Enhanced Employee Gender API
To ensure consistency between records, Dayforce automatically fixes inconsistencies in date information if conflicting dates are provided to the system. This occurs no matter what route the data is brought into Dayforce because all gender information is processed by the internal API.
In the following example, an employee has provided two records that have conflicting effective start dates:
| Record 1 | Record 2 | |
|---|---|---|
| Assigned Sex | Female | Male |
| Effective From | September 25, 2024 | September 30, 2024 |
| Effective To | October 31, 2024 | NULL |
As shown in the following screenshot:
After saving the records, Dayforce will fix the conflicts in these dates, and ensure that the most recent active record without an effective to date is made the active record. The effective to date on the female record is changed to be before the male record starts:
Client Property Can’t Be Disabled Once Enabled
Because there are concerns around data integrity, after you enable the Display Enhanced Gender Last Modification Information and Effective Dating client property, it can’t be disabled. If a customer has enabled this feature, and wants to disable it, contact Dayforce Support.