Migrate HR Import 2.0

Important: Before updating a customer’s production environment, ensure that any changes are tested in a non-production or test environment.

This page provides information for customers who want to update their HR Import templates and switch from using existing legacy gender and gender identity entities to enhanced employee gender entities.

Legacy and Enhanced HR Import Entities

Why Migrate To Enhanced Import Entities?

Customers are encouraged, but not forced, to move to the enhanced employee gender entities for HR Imports. These new entities offer more features, and are designed specifically for gender information going forward. In many cases, the legacy entities don’t work with the new features for Enhanced Employee Gender, including:

• Backward compatible columns lack functionality: The backward compatible legacy Gender and Gender Identity columns can operate only through backward compatibility mode. They continue to work as long as their employees don’t update their records to enhanced ones, or administrators don’t configure the system to allow for features that are in the Enhanced Employee Gender feature set.
• Engaging with Enhanced Employee Gender Requires Updates: If employees or administrators are using Enhanced Employee Gender features, they need to update their HR Import templates to help ensure compatibility.
• Future Features for Enhanced Employee Gender: New features will only be targeted at the new enhanced HR Import entities. Dayforce will continue to maintain the existing legacy entities for a period of time, but significant future (and currently not planned) changes to Enhanced Employee Gender might cause the legacy entities to stop working.

Which Entities Have Been Updated and How?

The HR Import entities for gender have been overhauled to allow for more information, which is necessary to import Enhanced Employee Gender records.

Updating Existing HR Imports to Use Enhanced Employee Gender

With Enhanced Employee Gender, data becomes less of a “one size fits all” solution, because it now depends on the following factors:

• Has the customer done any configuration in the Gender administration screen (HR Admin > Employee Gender Admin)?
• Does the customer operate in the United States or Canada? Or are their employees in other countries too?
• Does the customer have non-binary employees?
• Will the customer allow their employees to provide multiple different assigned sex and gender identity values for different locations where they live or work?
• Has this customer enabled the Display Enhanced Gender Last Modification Information and Effective Dating client property?

The following code sample provides an example of an HR Import file that would supply Gender and Gender Identity information to Dayforce for an employee.

<?xml version="1.0" encoding="UTF-8"?>
<EmployeeImport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Employee>
    <XRefCode>123456</XRefCode>
    <EmployeeNumber>123456</EmployeeNumber>
    <FirstName>Employee</FirstName>
    <LastName>Employee</LastName>
    <Gender>M</Gender>
    <GenderIdentityXrefCode>MALE</GenderIdentityXrefCode>
  </Employee>  

Example 1

The customer has the following configuration in Dayforce:

• No changes have been made to the gender administration screen (HR Admin > Employee Gender Admin > Gender) because their employees have indicated that they don’t need non-binary options.
• The customer doesn’t operate in the United States or Canada.
• The customer operates in only one country, and all of their employees live in the United Kingdom.

For Employee 12345:

• They need CountryCode of GBR because this is where they live.
• Gender is updated to AssignedSexXrefCode
• GenderIdentityXrefCode remains, but is now in EmployeeGender, rather than in Employee.

<?xml version="1.0" encoding="UTF-8"?>
<EmployeeImport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Employee>
    <XRefCode>12345</XRefCode>
    <EmployeeNumber>123456</EmployeeNumber>
    <FirstName>Employee</FirstName>
    <LastName>Employee</LastName>
  <EmployeeGender>
    <CountryCode>GBR</CountryCode>
    <AssignedSexXrefCode>M</AssignedSexXrefCode>
    <GenderIdentityXrefCode></GenderIdentityXrefCode>
  </EmployeeGender>
</Employee>

Example 2

Another customer has the following configuration in Dayforce:

• No changes have been made to the gender administration screen (HR Admin > Employee Gender Admin > Gender).
• The customer operates in Canada.

For Employee 654321:

• They’re male and live in British Columbia.
• Because this employee is male in British Columbia, Dayforce can automatically create their federal record for Canada. The federal record is therefore not required in the import.

<?xml version="1.0" encoding="UTF-8"?>
<EmployeeImport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Employee>
    <XRefCode>654321</XRefCode>
    <EmployeeNumber>654321</EmployeeNumber>
    <FirstName>Employee2</FirstName>
    <LastName>Employee2</LastName>
  <EmployeeGender>
    <CountryCode>CAN</CountryCode>
    <StateCode>BC</StateCode>
    <AssignedSexXrefCode>M</AssignedSexXrefCode>
    <GenderIdentityXrefCode>M<GenderIdentityXrefCode>
  </EmployeeGender>
</Employee>

Example 3

For a different customer, they have made the following changes to Dayforce:

• Several changes have been made to the gender administration screen (HR Admin > Employee Gender Admin > Gender).
  • Mexico allows for non-mandatory assigned sex values for employees.
  • California allows for a custom non-binary assigned sex option for employees.
• The customer operates in the United States.
• Some employees live in Mexico, and therefore might supply both a US value and a Mexican value.

For Employee 23456:

• They’re non-binary and work virtually from the California office.
• They live in Mexico, where assigned sex has been configured as non-mandatory. Therefore, assigned sex is reported as blank.
• Because this employee is non-binary in California, they must supply a federal record, with the isFederal token set to 1, with a binary option for the United States.

<?xml version="1.0" encoding="UTF-8"?>
<EmployeeImport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Employee>
    <XRefCode>23456</XRefCode>
    <EmployeeNumber>23456</EmployeeNumber>
    <FirstName>Employee3</FirstName>
    <LastName>Employee3</LastName>
  <EmployeeGender>
    <CountryCode>USA</CountryCode>
    <StateCode>CA</StateCode>
    <AssignedSexXrefCode>Non-Binary_CA</AssignedSexXrefCode>
    <GenderIdentityXrefCode>Non-Binary_CA<GenderIdentityXrefCode>
  </EmployeeGender>
  <EmployeeGender>
    <CountryCode>USA</CountryCode>
    <StateCode></StateCode>
    <AssignedSexXrefCode>M</AssignedSexXrefCode>
    <GenderIdentityXrefCode><GenderIdentityXrefCode>
    <isFederal>1</isFederal>
  </EmployeeGender>
  <EmployeeGender>
    <CountryCode>MEX</CountryCode>
    <AssignedSexXrefCode></AssignedSexXrefCode>
    <GenderIdentityXrefCode>Non-Binary_MEX<GenderIdentityXrefCode>
  </EmployeeGender>
</Employee>

Example 4

• No changes have been made to the gender administration screen (HR Admin > Employee Gender Admin > Gender).
• Customer operates only in France.
• Customer has enabled the Display Enhanced Gender Last Modification Information and Effective Dating client property

For Employee 741852:

• They have always lived in France.
• They were assigned male at birth. They’re currently female.
• They want to record both values (the current value and the historical value).

<?xml version="1.0" encoding="UTF-8"?>
<EmployeeImport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Employee>
    <XRefCode>741852</XRefCode>
    <EmployeeNumber>741852</EmployeeNumber>
    <FirstName>Employee4</FirstName>
    <LastName>Employee4</LastName>
  <EmployeeGender>
    <CountryCode>FRA</CountryCode>
    <AssignedSexXrefCode>M</AssignedSexXrefCode>
    <GenderIdentityXrefCode>F</GenderIdentityXrefCode>
    <EffectiveStart>1988-01-01</EffectiveStart>
    <EffectiveEnd>2021-12-31</EffectiveEnd>
  </EmployeeGender>
    <EmployeeGender>
    <CountryCode>FRA</CountryCode>
    <AssignedSexXrefCode>F</AssignedSexXrefCode>
    <GenderIdentityXrefCode>F</GenderIdentityXrefCode>
    <EffectiveStart>2022-01-01</EffectiveStart>
  </EmployeeGender>
</Employee>

For the HR Import XSD and further data examples, see HR Import 2.0 Technical Detail and Examples.