Employee Data

1. On the Employee Data page, click Download.
2. Select the location where you want to save the template document.
3. Open the EmployeeDataTemplate.xlsx template on your computer.
4. On the EmployeeData tab, complete all columns with the data for all employees in the organization.

   Note: Instructions for populating the fields are in the Employee Data Template Fields section (below) and on the Instructions tab of the template.

5. Click Save and close the template.

   You can use any file name for the template you upload. The document must be an Excel or CSV document and contain the data in the required format.

   Important: Don’t change the name of the tab in the template. Activate uses the tab name to validate that the correct template is being uploaded. In addition, don’t change the column headings.

6. On the Employee Data page, click Upload.
7. Go to the completed Employee Data template in the location where you saved it.

8. Click Open.

   The Getting Started wizard validates the uploaded file.

   Note: If the file that you uploaded has errors, a Validation Failed message shows in red on the page to indicate what the errors are. You must correct the errors in the file on your computer and upload the file again.

   Note: When you upload an Excel file, Activate includes the name of the uploaded file into the name of the XML file it generates and loads to the Dayforce File Server. The format of the generated XML file name is <NamespaceName>_<Import Type>_<file name provided>_YYY-MM-DD_HHMM. This information makes it easier to audit files later.

9. Click Next.

The data uploaded from the Employee Data template populates the fields on the following pages in Dayforce.

Note: You must select an employee if you haven’t already done so.

After completing the Employee Data wizard with the Employee Data Template, Activate automatically generates a single import file and places it on the customer's FTP site. Employee Import

• FTP SubDirectory: Import/HRImport
• Filename: <Namespace>-HRImport-<DateTime>.xml

<?xml version="1.0" encoding="UTF-8"?>
<EmployeeImport>
    <Employee>
        <XRefCode>970001</XRefCode>
        <EmployeeNumber>970001</EmployeeNumber>
        <FirstName>AUS_FN1</FirstName>
        <MiddleName>M</MiddleName>
        <LastName>AUS_LN1</LastName>
        <Suffix>JR</Suffix>
        <HireDate>2013-07-01</HireDate>
        <OriginalHireDate>2013-07-01</OriginalHireDate>
        <LastPayrollNewHireExportDate>2013-07-01</LastPayrollNewHireExportDate>
        <BirthDate>1980-11-09</BirthDate>
        <StartDate>2013-07-01</StartDate>
        <SeniorityDate>2013-07-01</SeniorityDate>
        <CultureCode>en-AU</CultureCode>
        <BadgeNumber>970001</BadgeNumber>
        <LoginId>ausfn.ausln</LoginId>
        <WorkAssignment>
            <JobXrefCode>AUS_JOB</JobXrefCode>
            <DeptXrefCode>AUS_DEPT</DeptXrefCode>
            <OrgXrefCode>AUS_CORP_AUS_PWL_1_AUS_DEPT</OrgXrefCode>
            <IsPrimary>true</IsPrimary>
            <EffectiveStart>2013-07-01</EffectiveStart>
            <ReasonXrefCode>Promotion</ReasonXrefCode>
            <IsVirtualEmployee>1</IsVirtualEmployee>
        </WorkAssignment>
        <EmploymentStatus>
            <PayClassXrefCode>FT</PayClassXrefCode>
            <PayTypeXrefCode>HOURLY</PayTypeXrefCode>
            <EmploymentStatusXrefCode>ACTIVE</EmploymentStatusXrefCode>
            <EffectiveStart>2013-07-01</EffectiveStart>
            <ReasonXrefCode>Promotion</ReasonXrefCode>
            <PunchPolicyXrefCode>HOURLY</PunchPolicyXrefCode>
            <PayPolicyXrefCode>AUS_HNE</PayPolicyXrefCode>
            <PayHolidayGroupXrefCode>AUS_TAS_HOL</PayHolidayGroupXrefCode>
            <NormalWeeklyHours>40</NormalWeeklyHours>
            <AverageDailyHours>8</AverageDailyHours>
            <BaseRateSalary>11.00000</BaseRateSalary>
            <PayGroupXrefCode>AUSTRALIA_BI_WEEKLY_2016_08_01</PayGroupXrefCode>
            <TimeOffPolicyXrefCode>DEFAULT</TimeOffPolicyXrefCode>
            <PayrollPolicyXrefCode>AUS_DEFAULT</PayrollPolicyXrefCode>
        </EmploymentStatus>
        <Role>
            <RoleXrefCode>EMPLOYEE WITH WFM</RoleXrefCode>
            <IsDefault>true</IsDefault>
            <EffectiveStart>2013-07-01</EffectiveStart>
        </Role>
        <AddressInformation>
            <ContactInformationTypeXrefCode>PrimaryResidence</ContactInformationTypeXrefCode>
            <EffectiveStart>2013-07-01</EffectiveStart>
            <Address1>1218 Lees Ave.</Address1>
            <Address2/>
            <Address3/>
            <Address4/>
            <Address5/>
            <Address6/>
            <County/>
            <City>North Coopertown</City>
            <StateCode>AU-TAS</StateCode>
            <CountryCode>AUS</CountryCode>
            <PostalCode>9453</PostalCode>
        </AddressInformation>
    </Employee>
</EmployeeImport>

• Physical Work Location becomes Dayforce Site.
• Department + Physical Work Location becomes Dayforce On-Site Department.
• Job Title (Jobs) + Department (Departments) becomes Dayforce Job Assignment.
• When populating the data templates, remember the information above. It ensures that the starting point configuration for the Org Structure is as accurate as possible, with the hope of minimal rework for implementation.

• Although Job Start Date and Status Start Date are optional fields in the Employee Data template, they drive important data decisions during XML generation.
• Include both date fields only if history is in scope. Doing so ensures that Work Assignment and Employment Status records are created with the appropriate effective start dates to enable the history to load before them.
• If history isn’t in scope, omit them. Activate can then use the Original Hire Date or Termination Date to generate Work Assignment and Employment Status records.

• If the customer does have contractor or pensioner employees, the inclusion is important because it helps Activate drive contractor-specific Legal Entity creation.
• If the customer doesn’t have this employee type, this field can be left blank.