Year-to-Date Payroll Totals (UK/IRL)

When you convert data from legacy to Dayforce, you must import Year-to-Date data for your many payroll codes. Use the Year-to-Date Payroll Totals (UK/IRL) wizard to make sure that your deductions, earnings, and taxes are loaded in Dayforce correctly.

The name and description of the codes are installed per the configuration shown on the final page in the wizard. When codes are grouped, the group name and group description determine the installed code name and description. The name is derived from the description and the description is derived from the mapped to the earnings tax and compliance code.

Completing this task makes sure that the mapping is correct from legacy to Dayforce and that the data is correct. At Go Live, data is successfully imported in anticipation of Year-end data being filed correctly for taxation and government purposes.

Important notes

You can use any of the following wizards even if any of the others is currently in use by other users: Payroll Deduction Codes, Payroll Earning Codes, Year-to-Date Payroll Totals (UK/IRL).
Activate shares all of your mappings across all applicable environments so you don't have to reconfigure each time you use a different environment. If the changes you make in one environment invalidate the mappings in another environment, Activate notifies you when you access a wizard with invalid mappings that need to be updated.
Activate users with Preceda selected as the Ascender Migration Type can use this wizard to select more than one file to upload from their computer in a single step. See Preceda Centralized Data Loads.
This wizard validates the NI (National Insurance) threshold for the Earnings Up to Lower Earning Limits value to the nearest penny (two decimal places).

Before you begin

A Native Payroll pay group for the UK or IRL (or both) with pay calendars must exist. Also, the UK/IRL Payroll Deduction Codes and UK/IRL Payroll Earning Codes must have been completed or bypassed with a committed pay run.

Key concepts

Deductions

Amounts that are subtracted from employees' gross pay during the calculation of net pay in Dayforce. Deductions can be pretax or post-tax. The four types include:

Deductions that allow partial payments:Dayforce only deducts what an employee can pay if the employee doesn’t have enough pay to cover the entire deduction.
Deductions that can go into arrears:Dayforce calculates whether the employee has enough pay to cover the entire deduction and carries forward any unpaid amount, trying to deduct the amount in the next pay period.
Declining balance deductions:Dayforce calculates the deduction against an outstanding balance owed by the employee.
Payee deductions: Deductions that are paid to a third-party payee.
Salary Sacrifice: In Ireland, Salary Sacrifice amounts are processed as a deduction.

Earnings

Amounts that are added to create an employees' gross pay during the calculation of gross pay. In Dayforce, each earning code falls into one of the following categories or earning types:

Normal: Represents earnings that are paid as income and taxed.
Reimbursement: Represent expenses (such as hotel or gas costs) that employees have paid and the employer is paying back.
Taxable Benefit: Can refer to the benefits of employment outside of cash compensation. Examples include low- and interest-free loans, gifts, and holiday trips and prizes. The value of these benefits is taxed as part of the employment income.
Memo Calc: Payments or earnings that employees receive but aren’t paid as income. An employer putting money into an RRSP or pension plan is an example of a memo calc earning. For memo calc earnings, the employees aren’t receiving the money as income today (as a check or directly deposited to their bank account), but they’re earning some amount. Memo calc earning codes aren’t taxed.
Salary Sacrifice: In the UK, Salary Sacrifice earnings are earnings that are an entitlement to cash pay.

Payroll deduction codes

Also known as Deduction Definitions, Payroll Deduction Codes define the amounts deducted from an employee’s gross pay. These amounts can be pretax or post tax. Examples include insurance plans, gym memberships, and pension plans. Each deduction code is mapped to a specific taxation method or Tax & Compliance Code.

Using this wizard

You’ll do the following in the Year-to-Date Payroll Totals (UK/IRL) wizard:

Complete and upload the UK/IRL Earning YTD, UK/IRL Deduction YTD, and UK/IRL Tax YTD template

Use the Payroll YTD Data templates to upload the key information for importing UK/IRL Earning, Deduction, and Tax YTD amounts. This data loads the information equivalent of a full pay run into the system.

Note: Complete this step using present-day employee information.

Perform a final review of the YTD values

The wizard creates a summary of the unique codes from the template. It calculates the Total Amount of each payroll code based on the legacy data. On this page, you can download reports to review the totals and validate that the codes are in balance for the wizard to move to the next steps. The Country and Payroll Identifier from the legacy system, and the codes' legacy name and description are shown in the reports. The Total Amount listed is by code but listed for the entire organization.

Map the legacy codes to the codes in Dayforce

Review the summary of unique codes from the templates and map the legacy codes to codes in the Dayforce environment.

Review the validation

Before you can install the Year-to-Date Payroll Totals with the Activate wizard, the wizard validates the data being imported against the Dayforce environment. When validation is complete, Activate shows all messages that cause or could potentially cause issues with the import. On this page, you can review these messages and download an error log. You can also validate the data from this page again or upload new templates, if needed.

If you click Upload New File(s), the wizard takes you back to the beginning and you can upload the data templates again. You’ll be required to go through each step of the wizard again.

Install the Information in Dayforce

When the payroll information is complete in Activate, you must install it in Dayforce.

Messages: Error, Warning, and Information

Activate sorts each generated message by severity:

Error codes

Actively incompatible with the data in Dayforce. If you have a data error, you must resolve the error before you can complete the installation.

Warning codes

Indicate nonstandard setup that could potentially cause an error in Dayforce. For example, if an earning code is defined as Hours x Rate and the data is amount only, the system creates a warning. However, you can still import the data into the system.

Informational codes

A notable occurrence of data in the system. For example, an informational note shows if codes are dropped from the YTD import.

Tasks

To complete and upload the UK/IRL Earning YTD, UK/IRL Deduction YTD, and UK/IRL Tax YTD templates:

In Activate Central, click Build Dayforce and the Build Dayforce wizards show.
Click Year-to-Date Payroll Totals (UK/IRL).
On the YTD Balance Data page, click Download all templates.
Note: You can also download the empty templates from the Download Template Files page.
Select the location where you want to save the template documents.
Open the UKIRLEarningYTDTemplate.xlsx, UKIRLDeductionYTDTemplate.xlsx, and TaxYTDBalanceTemplate_UK_IRL.xlsx templates on your computer.

Note: The Activate release version shows in cell B3 on the Instructions tab of the template. This information helps you later determine the version of Activate you were using when you downloaded the template.

Complete all columns on the relevant data tabs with the data for all of the employees in the organization.
Note: Instructions for populating the fields are on the Instructions tab of the templates and in the sections below: , UK/IRL Earning YTD Template Fields, UK/IRL Deduction YTD Data Template Fields, UK/IRL Tax YTD Template Fields.
Click Save and close each template.
You can use any file name for the template you upload. The file must be an Excel or CSV (Comma-Separated Value) 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.
On the YTD Data page, click Upload files.
Go to the completed UK/IRL YTD template in the location where you saved it.
Click Open. The YTD wizard validates the uploaded file.
Important: If you upload YTD files on the Pay Period End date for a pay group, you must enable the Allow Future Dated field.
Note: If the file you uploaded has any errors, a Validation Failed message shows in red at the bottom of the page. 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.
Repeat these steps to upload the remaining templates.
Note: You must upload valid files for all sections (Earnings, Deductions, and Taxes) to continue. All three templates must be uploaded to continue to the next page. You can also select all three templates at the same time and upload them in a single step.
Click Next. A prompt opens stating that the uploaded files will generate new payroll mappings and all new items found must be mapped in this wizard.
Click one of the following:
- No to return to the YTD Data page.
- Yes to continue.
You can click Download to download the Candidate Information document. This document contains the Type, Payroll Identifier, Code, Description, State/Province, Country, Tax Level, and Is Employer Tax section, and save it to your computer for future reference.

To review YTD totals for deductions, earnings, and taxes:

On the Balance page, click the Download the YTD Balance Totals for Deductions link.
Select the location where you want to save the template documents.
Open the DeductionBalance.xlsx document in the location where you saved it on your computer.
Review and verify that the information in the document is correct.
Each line shows the total amount from the upload file, grouped by country, payroll identifier, code, and description. For earnings, it also shows the total hours.
Note: If any information is wrong, click Back, make the corrections in the appropriate templates, and upload them again.
Repeat these steps for the Download the YTD Balance Totals for Earnings and the Download the YTD Balance Totals for Taxes links.
After you verify that all data is correct, select the checkbox on the page to confirm that each row is in balance.
Note: You must click the checkbox to confirm that the validation is in balance to continue.
Click Next.

To map legacy codes to the codes in Dayforce:

Note: The tasks for the earnings and deductions pages are the same.

On the Let's review and update your YTD Deduction mappings page, review the line for each code. Make that sure it’s mapped to the appropriate Dayforce code.
Deductions codes with the same “code, description, and country“ are grouped into a single-line item on the page. This grouping also applies to earnings codes.
- New codes: If a code is new to this Activate project, its mapping status is New Unmapped Code Found. Select a code from the drop-down list to complete the mapping.
  - Available codes are restricted based on their country from legacy and the taxability of the Dayforce code.
  - If a Dayforce code doesn’t show, the Implementation Consultant might need to create the code in the corresponding Dayforce environment. In this case, when the code has been created in Dayforce, refresh the page so the wizard can pull the new information from the environment when loading this page.
- Previous codes: If the code has been used in this Activate project before, it shows as Previous Mapping Found, and defaults to however you previously used this legacy code. For these codes, validate the information, and if any updates need to be made, select from the drop-down list to select a new code.
- YTD Deduction Mapping: You can remove codes that are no longer in use from the import. If a code was marked as a deduction, you can also mark it as an earning and you’ll have to map it on the Earnings Mapping page.
- YTD Earning Mapping: You can remove codes that are no longer in use from the import. If a deduction code has been marked as an earning, it shows here and you must map it.
Note: To filter the codes shown, click All Codes, Mapped Codes, and Unmapped Codes.
Note: To search for a code on the page, enter text in the Search field. To clear text in the Search field and clear the filter, click the Close button ().
For any codes that are incorrectly aligned, click the drop-down list in the column on the right for that deduction and select the correct deduction.
Mapping deductions as earnings:
If you click Map as an earning for any deductions, you can view and map those codes to earnings on the next page. Activate generates the XML file with those deduction rows mapped to the corresponding earnings, and negate the amount for nonmemo codes. You can view codes that were previously mapped as an earning in the Deduction mapper with “map as earning“ selected. Select to change the mapping to a deduction or drop the earning from import. When you map a deduction as an earning, the validation message that deduction codes aren’t allowed to map as earnings no longer shows. Instead, Activate shows that the deduction amount has been converted to earning.
Note: If you select an incorrect deduction/earning/tax, the Error icon () shows next to the selected deduction. You must select a correct earning to continue.
Note: If any errors or warnings exist, they show in the right-hand column of the table. Hover over the icon to show more details. You can’t continue if there are errors. If warnings or information only messages exist, you can continue.
Note: Activate shares the UK/IRL YTD payroll mappings across all environments (Config, Stage, and Train) so you don't have to reconfigure each time you use a different environment.
When all codes are mapped, click Next.
Repeat this process for the HCM Earnings and HCM Tax, as appropriate.

To do a final review of YTD values:

Review the Employee Summary section, which includes:
- Pay groups and pay periods that YTD data will be loaded into.
- Total active and inactive employees with gross pay.
- Total terminated employees with gross pay.
- Total active and inactive employees with NO gross pay.
- Total terminated employees with NO gross pay.
Note: The Gross Pay total includes the Salary Sacrifice earning type and Normal and Reimbursement for UK employees only. Ireland Salary Sacrifice amounts are included in the Pretax Deduction total.
Note: Any fields that don’t apply for the county loaded show a dash.

If you want to download a report containing the pay period detail, status, employee identifier/name, and the gross pay total, click Employee Summary.
Review the Company Totals Summary section.
Activate groups the totals in this section by Payroll Identifier and Company ID. For example, HMRC/PAYE Number.
This section includes:
- Payroll Identifier
- HMRC/PAYE Number/LEI
- Gross earnings total (Normal, Salary Sacrifice, and Reimbursements): Includes the Salary Sacrifice earning type and Normal and Reimbursement earnings.
- Total Taxable Benefit Earnings: Includes all earnings mapped to taxable benefits.
- Total Taxable Benefit Medical Total (IRL): Includes any taxable benefits for Ireland, which have the ‘Medical’ box checked on the Tax and Compliance code.
- Total Memo Earnings: Includes any deductions mapped as memo calc earnings.
- Total Pretax Deduction total: Includes IRL Salary Sacrifice totals.
- Total Salary Sacrifice Deduction (IRL)
- Total Post Tax Deduction total
- Total Memo Deduction
- Total PAYE tax: Shows the total tax amount mapped to PAYE Tax for IRL and UK groups.
- Total Employee NI/PRSI: Shows the total tax amount mapped to Employee National Insurance (UK) or Employee Pay Related Social Insurance (IRL).
- Total Employer NI/PRSI: Shows the total tax amount mapped to Employer National Insurance (including Class 1A NIC; UK) or Employer Pay Related Social Insurance (IRL).
- Total USC Tax (IRL): Shows the total tax amount mapped to the Universal Social Charge (IRL).
- Total LPT Tax (IRL): Shows the total tax amount mapped to Local Property Tax (IRL).
- Total net pay: UK: Gross Pay – Pre Tax Deductions – Post Tax Deductions – Employee Taxes (PAYE and EE NI) IRL: Gross Pay – Pre Tax Deductions – Post Tax Deductions – Employee Taxes (PAYE, PRSI, USC, and LPT)
Note: The deduction columns don’t include any deductions mapped to earnings.
If you want to download a report containing the information in the Company Totals section, click Company Totals Summary.
If you want to download a report containing the information in the Employee Totals section, click Employee Totals Summary. The report shows the pay period detail, status, employee identifier/name, and gross pay total by employee.
Click Next.

To validate YTD balance data:

On the Validate page, review the summary of any error or warning messages shown and the count of the affected records.
If any error messages are shown:
1. Resolve the error messages.
2. Click Re-Validate.
3. Review the updated error messages.
4. Repeat until all error messages are resolved.
Note: You must resolve all error messages before you can install the data in Dayforce.
Note: If an error exists in the Dayforce environment, you must resolve it in Dayforce.
If you want to upload new files, click Upload New File(s).
Click Download to download a spreadsheet that has a record of all populated messages from this data validation. Save this document to your computer for reference.

To install the Information in Dayforce:

On the Validate page, click Done & Install.
Activate reruns the validation.
Important: If someone is signed directly in to Dayforce and potentially applying manual configuration, Activate shows a warning at Done & Install. Don’t continue with the Activate installation if users are actively applying configuration changes. Users’ changes might be lost if a failure occurs during the Activate installation. Download the User Report and follow up with the team members before you continue with the Activate wizard.
Important: A dialog box states that at completion of this load, access to the Org Hierarchy solution will be limited to Dayforce users. If you have outstanding validation messages, by continuing, you confirm that you have reviewed all remaining validation results. You also commit to making the necessary updates to the applicable configuration and/or data in Dayforce to make sure that these issues are correct as soon as possible. You acknowledge that failure to do so could result in pay or year-end filing errors.
If any new validations are detected, you’ll be taken back to the Validate page and presented with the new validations to review.
Important: If someone is signed directly in to Dayforce and potentially applying manual configuration, Activate shows a warning at Done & Install. Don’t continue with the Activate installation if users are actively applying configuration changes. Users’ changes might be lost if a failure occurs during the Activate installation. Download the User Report and follow up with the team members before you continue with the Activate wizard.
The system notifies you that Org Hierarchy access will be limited in the system from now on.
If you haven’t already completed the Organizational Hierarchy wizard, review it now.
You might also download the mapping for the different codes that were used in this YTD load now.
If you want to view and save the mapping information that will be loaded, click Download and save the Payroll Mapping File to your computer for future reference.
Click one of the following:
- No to cancel the installation and return to the Validate page.
- Yes to acknowledge the disclaimer and continue with the installation. The Loading YTD Data page opens.
Click one of the following:
- Add Email and enter your email address to receive an email when the installation process ends, instead of waiting for it to finish.
- Next w hen the installation is complete.
Activate Central opens with the name of the Wizard now shown in green text and a green checkmark to the left of the wizard’s name. The current day, date, and time of completion are included, along with your name as the user who completed the Wizard. The environment in which the installation was applied (Stage, Config, or Train) is also shown.
Note: If you want to add more information, click I want to add more. See Executing a Rollback When Using the “Add More“ Feature in the Payroll Wizards.

Results

Dayforce now contains the UK/IRL YTD Data that was imported during installation. The pay period used in the legacy system is now considered Committed data. The Taxation and calculation parameters on each earning and deduction code that was used in this pay period are locked down. These parts of the Payroll codes are now locked into unmodifiable states.

Note: When the installation completes, you can download the Mapping Files, which are used as a basis for any future YTD load. To download the files, go to the User Menu (Person Icon), select Troubleshooting Resources, and then select the appropriate mapping under Customer Mapping Templates to download the file as an Excel spreadsheet.

Fields populated in Dayforce

The data uploaded from the UK/IRL Earning YTD template populates the fields on the following pages in Dayforce.

Fields populated in Dayforce from the UK/IRL Earning YTD template
Field in Template	Field in Dayforce	Page in Dayforce
Payroll Identifier	—	—
Pay Period End Date	Pay Period End Date	When the data is loaded for Parallel and Go Live, this information shows on the Payroll, Pay Run Management tab.
Employee Identifier	Employee Reference / Number
First Name	First Name
Last Name	Last Name
Company ID	HMRC/PAYE number
Earning Code	—
Earning Description	—
Amount	Amount
Work Location	Work Location
Canada Workers Comp Code (Canada only)	N/A
Canada Workers Comp Acct Number (Canada only)	N/A
Canada Previous RP Number (Canada only)	N/A	—
Canada Previous EI Rate (Canada only)	N/A	—

The data uploaded from the UK/IRL Deduction YTD template populates the fields on the following pages in Dayforce.

Fields populated in Dayforce from the UK/IRL Deduction YTD template
Field in Template	Field in Dayforce	Page in Dayforce
Payroll Identifier	—	—
Pay Period End Date	—	—
Employee Identifier	Employee Reference / Number	When data is loaded for Parallel and Go Live, this information ends up on the Payroll, Pay Run Management tab.
First Name	First Name
Last Name	Last Name
Company ID	HMRC/PAYE number
Deduction Code	Name
Deduction Description	Description
Amount	Amount
Work Location	Work State
Canada Workers Comp Code (Canada only)	N/A
Canada Workers Comp Acct Number (Canada only)	N/A
Canada Previous RP Number (Canada only)	N/A
Canada Previous EI Rate (Canada only)	N/A

The data uploaded from the UK/IRL Tax YTD template for Parallel or Go Live populates the fields on the Pay Run Management page in Dayforce (Payroll, Pay Run Management tab).

Fields populated in Dayforce from the UK/IRL Tax YTD template
Field in Template	Field in Dayforce	Page in Dayforce
Payroll Identifier	—	—
Pay Period End Date	—	—
Employee Identifier	Employee Reference / Number	When data is loaded for Parallel and Go Live, this information ends up on the Payroll, Pay Run Management tab.
First Name	First Name
Last Name	Last Name
Company ID	Legal Entity
Tax Code	Code
Tax Description	—
Tax Level	Tax Level
Work Location	Work Location
Employer Tax	—
Tax Amount	Amount
Wage Basis	Total Taxable Wages
National Insurance Letter	National Insurance Letter
Earnings Up To Lower Earnings Limit	Earnings Up To Lower Earnings Limit
Earnings Between Lower Earnings Limit And Primary Threshold	Earnings Between Lower Earnings Limit And Primary Threshold
Earnings Between Primary Threshold And Upper Earnings Limit	Earnings Between Primary Threshold And Upper Earnings Limit
Earnings Above Upper Earnings Limit	Earnings Above Upper Earnings Limit

Files generated by the Year-To-Date Payroll Totals (UK/IRL) wizard.

After completing the Year-to-Date Payroll Totals (UK/IRL) wizard, Activate automatically generates a single import file and places on the customer's FTP site.

FTP Subdirectory: Import/PayrollYTDBalancesImport
Filename: <Namespace> PayrollYTDBalancesImport <DateTime>.xml

Example illustrating how Activate translates the template data to XML:

Copy

<?xml version="1.0" encoding="utf-8"?>
-<PayrollYTDBalancesImport>
    -<Employee>
        <PayGroupXrefCode>IRELAND_BI_WEEKLY_2016_01_01</PayGroupXrefCode>
        <EmployeeXrefCode>123456</EmployeeXrefCode>
        <LegalEntityXrefCode>IRL_CORP</LegalEntityXrefCode>
        <TaxYear>2021</TaxYear>
        <PayPeriod>18</PayPeriod>
        <OffCyclePeriod>01</OffCyclePeriod>
        -<Earning>
            <XrefCode>IRLSalary</XrefCode>
            <AmountYTD>12000.00000</AmountYTD>
        </Earning>
        -<Deduction>
            <XrefCode>IRLMiscellaneous</XrefCode>
            <AmountYTD>155.00000</AmountYTD>
        </Deduction>
        -<Tax>
            <TaxAuthorityInstanceId>IRL-30000030-01</TaxAuthorityInstanceId>
            <AmountYTD>120.00000</AmountYTD>
            <WageBasisYTD>12000.00000</WageBasisYTD>
            -<IRL_Tax>
            <PRSISubClass>AL</PRSISubClass>
            <InsurableWeek>6</InsurableWeek>
            </IRL_Tax>
        </Tax>
        -<Tax>
            <TaxAuthorityInstanceId>IRL-30000030-02</TaxAuthorityInstanceId>
            <AmountYTD>120.00000</AmountYTD>
            <WageBasisYTD>12000.00000</WageBasisYTD>
            -<IRL_Tax>
            <PRSISubClass>AL</PRSISubClass>
            <InsurableWeek>6</InsurableWeek>
            </IRL_Tax>
        </Tax>
        -<Tax>
            <TaxAuthorityInstanceId>IRL-30000030-03</TaxAuthorityInstanceId>
            <AmountYTD>120.00000</AmountYTD>
            <WageBasisYTD>11845.00000</WageBasisYTD>
            -<IRL_Tax>
            <EmergencyTaxStartDate>2020-09-01</EmergencyTaxStartDate>
            <EmergencyTaxWeek>2</EmergencyTaxWeek>
            </IRL_Tax>
        </Tax>
        -<Tax>
            <TaxAuthorityInstanceId>IRL-30000030-04</TaxAuthorityInstanceId>
            <AmountYTD>120.00000</AmountYTD>
            <WageBasisYTD>11845.00000</WageBasisYTD>
        </Tax>
        -<Tax>
            <TaxAuthorityInstanceId>IRL-30000030-05</TaxAuthorityInstanceId>
            <AmountYTD>120.00000</AmountYTD>
            <WageBasisYTD>11845.00000</WageBasisYTD>
        </Tax>
    </Employee>
</PayrollYTDBalancesImport>

Activate also generates the following report to help with Year-to-Date validation and balancing:

FTP Subdirectory: PayrollYTDBalancesImport/ActivateValidationReports
FilesName:
- <Namespace>-ActivatePayRunValidationReports-<DateTimeStart> - <DateTimeEnd>.xlsx

Next steps

Review the pay period used for the YTD Load in Dayforce and validate against the legacy payroll for accuracy in mapping.

Complete the next wizard, as appropriate.

Commonly encountered issues

Before you upload the template, make sure that no errors exist in the data. Some common problems include:

Missing required field or data.
The UKIRLTaxYTDData tab is missing in the Excel document.
Incorrect formatting.
If the file includes a filter, it might result in an error.

If a column has an error that you can't resolve, click the letter at the top of the column. In the menu, select Data and Text to Columns, and then click Next, Next, and Finish. This action converts the data in the column back to text. If the information was formatted incorrectly, this might resolve the problem.

UK/IRL Earning YTD template fields

All templates have the same basic structure:

Instructions tab: Helps you understand the purpose of the data and complete the fields in the template.
Data tab: Contains headers for the data to be included in the template. The headers remain the same, but you can change the column order. If you add more columns, Activate ignores them.

All number ranges in the templates include the numbers at both ends of the range.

Payroll Identifier (Required)

Field information for the Payroll Identifier field
Order	Data Type	Description	Examples	Why This Is Needed
1	String¹ between 1-64 characters.	This field uniquely identifies a group of employees. In some previous payroll provider systems, it could be defined as “Company Number.” It could be defined as “Salary Employees” or “Hourly Employees” if you segregate them into separate groups for Payroll Register purposes. It’s the identifier used to define the current payroll the employee is paid through. This value is the grouping of employees paid at the same time who are reported together in the same payroll totals reports.	B1234 Monthly Executive Payroll	This data is used as part of the key to identify deduction definitions uniquely. It serves to preserve definitions that might have the same name or code but differing functionality between payrolls.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Pay Period End Date (Required)

Field information for the Pay Period End Date field
Order	Data Type	Description	Examples	Why This Is Needed
2	Date. Excel right-justified date format or Excel text format yyyy-mm-dd.	The Pay Period End Date of the period for given YTD values. The Pay Period End Date being used should be the same date for each of the three YTD import files.	Date formatted cells: 09/24/2015 24/09/2015 Text formatted cells: 2015-09-24	This required date identifies the period in your payroll calendar that represents the YTD values given on this import.

Employee Identifier (Required)

Field information for the Employee Identifier field
Order	Data Type	Description	Examples	Why This Is Needed
3	Alphanumeric. Unique value between 1-9 characters. For non-Canadian pay groups, a unique value between 1-40 characters.	It allows our system to identify employees uniquely. Use the same number assigned to the employee in the Getting Started HR data loads.	3241245 000000006 abc12349	The Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field validates that the data being loaded is assigned to the correct employee record. The values provided must match exactly to an existing employee record in Dayforce.

First Name (Required)

Field information for the First Name field
Order	Data Type	Description	Example	Why This Is Needed
4	String¹ between 1-64 characters.	Legal first name of the employee. Note: Activate‘ compares the First Name and the Last Name with the Employee Identifier in Dayforce. If they don’t match, Activate shows an error message that states that the data is being loaded incorrectly and to check the source data.	Joe	The Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field validates that the data being loaded is assigned to the correct employee record. The values provided must match exactly to an existing employee record in Dayforce.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Last Name (Required)

Field information for the Last Name field
Order	Data Type	Description	Example	Why This Is Needed
5	String¹ between 1-64 characters.	Legal last name of the employee. Note: Activate‘ compares the First Name and the Last Name with the Employee Identifier in Dayforce. If they don’t match, Activate shows an error message that states that the data is being loaded incorrectly and to check the source data.	Smith	The Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field validates that the data being loaded is assigned to the correct employee record. The values provided must match exactly to an existing employee record in Dayforce.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Company ID (Required)

Field information for the Company ID field
Order	Data Type	Description	Examples	Why This Is Needed
6	Numeric length 9-20.	The unique identifier for the legal entity that the employee was paid through. United Kingdom: HMRC/PAYE number Ireland: Legal Entity Identifier (LEI).	123456789 234/A1237634 12345678901	This data is required to assign the correct Legal Entity to the specific deduction for tax reporting purposes.

Earning Code (Required)

Field information for the Earning Code field
Order	Data Type	Description	Examples	Why This Is Needed
7	String¹ between 1-64 characters.	This is the payroll system Earning Code as defined on the previous payroll provider's system.	REG	This data is used in combination with the Payroll Identifier and Earning Description to identify individual earning definition requirements.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Earning Description (Required)

Field information for the Earning Description field
Order	Data Type	Description	Example	Why This Is Needed
8	String¹ between 1-64 characters.	The payroll system Earning Description as defined on the previous payroll provider's system.	Regular	This data is used with the Payroll Identifier and Earning Code to identify individual earning definition requirements.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Amount (Required)

Field information for the Amount field
Order	Data Type	Description	Example	Why This Is Needed
9	Numeric.	The accumulated dollar amount associated with this specific earning.	2751 59.5	This data is required for the first step of the Activate process to balance to the source data. It’s required for the YTD accumulator data load files to load the "To Date" amount for the specific earning for tax reporting purposes.

Hours

Field information for the Hours field
Order	Data Type	Description	Example	Why This Is Needed
10	Numeric.	This is the accumulated number of hours associated with this specific earning.	2751 59.5	This data identifies specific earnings that should be calculated by hours and rate for the first step of the Activate process. It can be loaded as zero (0.00) or Null (blank) when not required. When applicable to the earning type, It is required for the YTD accumulator data load files to load the “To Date” number of hours for various HR, Benefit (ACA) and Payroll reporting purposes.

Work Location (Required)

Field information for the Work Location field
Order	Data Type	Description	Example	Why This Is Needed
11	Numeric.	Work Location Accepted Values² For the US: 2-digit state identifier. For CAN: 2-digit province identifier. For the UK: record “GBR” For IRL: record “IRL“ For AUS: state identifier.	State: FL IL Province: AB ON United Kingdom: GBR For Ireland: IRL Australia: AU-VIC AU-SA	This data is required for the YTD data load files for tax reporting purposes. It is possible for the employee to have values in multiple states or provinces thus the requirement to identify the code for each line item.

² Accepted values for Work Location
Accepted Values	State Name	Country Name
AU-ACT	Australian Capital Territory	Australia
AU-NSW	New South Wales	Australia
AU-QLD	Queensland	Australia
AU-SA	South Australia	Australia
AU-TAS	Tasmania	Australia
AU-VIC	Victoria	Australia
AU-WA	Western Australia	Australia
ON	Ontario	Canada
QC	Quebec	Canada
NS	Nova Scotia	Canada
NB	New Brunswick	Canada
MB	Manitoba	Canada
BC	British Colombia	Canada
PE	Prince Edward Island	Canada
SK	Saskatchewan	Canada
AB	Alberta	Canada
NL	Newfoundland and Labrador	Canada
NT	Northwest Territories	Canada
YT	Yukon	Canada
NU	Nunavut	Canada
CN-11	Beijing	China
CN-12	Tianjin	China
CN-13	Hebei	China
CN-14	Shanxi	China
CN-15	NeiMonggol	China
CN-21	Liaoning	China
CN-22	Jilin	China
CN-23	Heilongjiang	China
CN-31	Shanghai	China
CN-32	Jiangsu	China
CN-33	Zhejiang	China
CN-34	Anhui	China
CN-35	Fujian	China
CN-36	Jiangxi	China
CN-37	Shandong	China
CN-41	Henan	China
CN-42	Hubei	China
CN-43	Hunan	China
CN-44	Guangdong	China
CN-45	Guangxi	China
CN-46	Hainan	China
CN-50	Chongqing	China
CN-51	Sichuan	China
CN-52	Guizhou	China
CN-53	Yunnan	China
CN-54	Xizang	China
CN-61	Shaanxi	China
CN-62	Gansu	China
CN-63	Qinghai	China
CN-64	Ningxia	China
CN-65	Xinjiang	China
CN-71	Taiwan	China
CN-91	HongKong	China
CZ-CJC	Jihoceskýkraj	Czech Republic
CZ-CJM	Jihomoravskýkraj	Czech Republic
CZ-CSC	Severoceskýkraj	Czech Republic
CZ-CSM	Severomoravskýkraj	Czech Republic
CZ-CST	Stredoceskýkraj	Czech Republic
CZ-CVC	Východoceskýkraj	Czech Republic
CZ-CZC	Západoceskýkraj	Czech Republic
CZ-PRG	Praha	Czech Republic
DE-BB	Brandenburg	Germany
DE-BE	Berlin	Germany
DE-BW	Baden-Württemberg	Germany
DE-BY	Bayern	Germany
DE-HB	Bremen	Germany
DE-HE	Hessen	Germany
DE-HH	Hamburg	Germany
DE-MV	Mecklenburg-Vorpommern	Germany
DE-NI	Niedersachsen	Germany
DE-NW	Nordrhein-Westfalen	Germany
DE-RP	Rheinland-Pfalz	Germany
DE-SH	Schleswig-Holstein	Germany
DE-SL	Saarland	Germany
DE-SN	Sachsen	Germany
DE-ST	Sachsen-Anhalt	Germany
DE-TH	Thüringen	Germany
IN-AN	AndamanandNicobarIslands	India
IN-AP	AndhraPradesh	India
IN-AR	ArunachalPradesh	India
IN-AS	Assam	India
IN-BR	Bihar	India
IN-CH	Chandigarh	India
IN-DD	DamanandDiu	India
IN-DL	Delhi	India
IN-DN	DadraandNagarHaveli	India
IN-GA	Goa	India
IN-GJ	Gujarat	India
IN-HP	HimachalPradesh	India
IN-HR	Haryana	India
IN-JK	JammuandKashmir	India
IN-KA	Karnataka	India
IN-KL	Kerala	India
IN-LD	Lakshadweep	India
IN-MH	Maharashtra	India
IN-ML	Meghalaya	India
N-MN	Manipur	India
IN-MP	MadhyaPradesh	India
IN-MZ	Mizoram	India
IN-NL	Nagaland	India
IN-OR	Orissa	India
IN-PB	Punjab	India
IN-PY	Pondicherry	India
IN-RJ	Rajasthan	India
IN-SK	Sikkim	India
IN-TN	TamilNadu	India
IN-TR	Tripura	India
IN-UP	UttarPradesh	India
IN-WB	WestBengal	India
N/A	State is not required	Ireland
IT-21	Piemonte	Italy
IT-23	ValledAosta	Italy
IT-25	Lombardia	Italy
IT-32	Trentino-AlteAdige	Italy
IT-34	Veneto	Italy
IT-36	Friuli-VeneziaGiulia	Italy
IT-42	Liguria	Italy
IT-45	Emilia-Romagna	Italy
IT-52	Toscana	Italy
IT-55	Umbria	Italy
IT-57	Marche	Italy
IT-62	Lazio	Italy
IT-65	Abruzzo	Italy
IT-67	Molise	Italy
IT-72	Campania	Italy
IT-75	Puglia	Italy
IT-77	Basilicata	Italy
IT-78	Calabria	Italy
IT-82	Sicilia	Italy
IT-88	Sardegna	Italy
IT-AG	Agrigento	Italy
IT-AL	Alessandria	Italy
IT-AN	Ancona	Italy
IT-AO	Aosta	Italy
IT-AP	AscoliPiceno	Italy
IT-AQ	LAquila	Italy
IT-AR	Arezzo	Italy
IT-AT	Asti	Italy
IT-AV	Avellino	Italy
IT-BA	Bari	Italy
IT-BG	Bergamo	Italy
IT-BI	Biella	Italy
IT-BL	Belluno	Italy
IT-BN	Benevento	Italy
IT-BO	Bologna	Italy
IT-BR	Brindisi	Italy
IT-BS	Brescia	Italy
IT-BZ	Bolzano	Italy
IT-CA	Cagliari	Italy
IT-CB	Campobasso	Italy
IT-CE	Caserta	Italy
IT-CH	Chieti	Italy
IT-CL	Caltanissetta	Italy
IT-CN	Cuneo	Italy
IT-CO	Como	Italy
IT-CR	Cremona	Italy
IT-CS	Cosenza	Italy
IT-CT	Catania	Italy
IT-CZ	Catanzaro	Italy
IT-EN	Enna	Italy
IT-FE	Ferrara	Italy
IT-FG	Foggia	Italy
IT-FI	Firenze	Italy
IT-FO	Forlì	Italy
IT-FR	Frosinone	Italy
IT-GE	Genova	Italy
IT-GO	Gorizia	Italy
IT-GR	Grosseto	Italy
IT-IM	Imperia	Italy
IT-IS	Isernia	Italy
IT-KR	Crotone	Italy
IT-LC	Lecco	Italy
IT-LE	Lecce	Italy
IT-LI	Livorno	Italy
IT-LO	Lodi	Italy
IT-LT	Latina	Italy
IT-LU	Lucca	Italy
IT-MC	Macerata	Italy
IT-ME	Mesaina	Italy
IT-MI	Milano	Italy
IT-MN	Mantova	Italy
IT-MO	Modena	Italy
IT-MS	Massa	Italy
IT-MT	Matera	Italy
IT-NA	Napoli	Italy
IT-NO	Novara	Italy
IT-NU	Nuoro	Italy
IT-OR	Oristano	Italy
IT-PA	Palermo	Italy
IT-PC	Piacenza	Italy
IT-PD	Padova	Italy
IT-PE	Pescara	Italy
IT-PG	Perugia	Italy
IT-PI	Pisa	Italy
IT-PN	Pordenone	Italy
IT-PO	Prato	Italy
IT-PR	Parma	Italy
IT-PS	Pesaro	Italy
IT-PT	Pistoia	Italy
IT-PV	Pavia	Italy
IT-PZ	Potenza	Italy
IT-RA	Ravenna	Italy
IT-RC	ReggioCalabria	Italy
IT-RE	ReggioEmilia	Italy
IT-RG	Ragusa	Italy
IT-RI	Rieti	Italy
IT-RM	Roma	Italy
IT-RN	Rimini	Italy
IT-RO	Rovigo	Italy
IT-SA	Salerno	Italy
IT-SI	Siena	Italy
IT-SO	Sondrio	Italy
IT-SP	LaSpezia	Italy
IT-SR	Siracusa	Italy
IT-SS	Sassari	Italy
IT-SV	Savona	Italy
IT-TA	Taranto	Italy
IT-TE	Teramo	Italy
IT-TN	Trento	Italy
IT-TO	Torino	Italy
IT-TP	Trapani	Italy
IT-TR	Terni	Italy
IT-TS	Trieste	Italy
IT-TV	Treviso	Italy
IT-UD	Udine	Italy
IT-VA	Varese	Italy
IT-VC	Vercelli	Italy
IT-VE	Venezia	Italy
IT-VI	Vicenza	Italy
IT-VR	Verona	Italy
IT-VT	Viterbo	Italy
IT-W	ViboValentia	Italy
JP-01	Hokkaidô	Japan
JP-02	Aomori	Japan
JP-03	Iwate	Japan
JP-04	Miyagi	Japan
JP-05	Akita	Japan
JP-06	Yamagata	Japan
JP-07	Hukusima	Japan
JP-08	Ibaraki	Japan
JP-09	Totigi	Japan
JP-10	Gunma	Japan
JP-11	Saitama	Japan
JP-12	Tiba	Japan
JP-13	Tôkyô	Japan
JP-14>	Kanagawa	Japan
JP-15	Niigata	Japan
JP-16	Toyama	Japan
JP-17	Isikawa	Japan
JP-18	Hukui	Japan
JP-19	Yamanasi	Japan
JP-20	Nagano	Japan
JP-21	Gihu	Japan
JP-22	Sizuoka	Japan
JP-23	Aiti	Japan
JP-24	Mie	Japan
JP-25	Siga	Japan
JP-26	Kyôto	Japan
JP-27	Ôsaka	Japan
JP-28	Hyôgo	Japan
JP-29	Nara	Japan
JP-30	Wakayama	Japan
JP-31	Tottori	Japan
JP-33	Okayama	Japan
JP-34	Hirosima	Japan
JP-35	Yamaguti	Japan
JP-36	Tokusima	Japan
JP-37	Kagawa	Japan
JP-38	Ehime	Japan
JP-39	Kôti	Japan
JP-40	Hukuoka	Japan
JP-41	Saga	Japan
JP-42	Nagasaki	Japan
JP-43	Kumamoto	Japan
JP-44	Ôita	Japan
JP-45	Miyazaki	Japan
JP-46	Kagosima	Japan
JP-47	Okinawa	Japan
KR-11	SeoulTeugbyeolsi	Korea
KR-26	BusanGwangyeogsi	Korea
KR-27	DaeguGwangyeogsi	Korea
KR-28	IncheonGwangyeogsi	Korea
KR-29	GwangjuGwangyeogsi	Korea
KR-30	DaejeonGwangyeogsi	Korea
KR-31	UlsanGwangyeogsi	Korea
KR-41	Gyeonggido	Korea
KR-42	Gangweondo	Korea
KR-43	Chungcheongbugdo	Korea
KR-44	Chungcheongnamdo	Korea
KR-45	Jeonrabugdo	Korea
KR-46	Jeonranamdo	Korea
KR-47	Gyeongsangbugdo	Korea
KR-48	Gyeongsangnamdo	Korea
KR-49	Jejudo	Korea
MX-AGU	Aguascalientes	Mexico
MX-BCN	BajaCalifornia	Mexico
MX-BCS	BajaCaliforniaSur	Mexico
MX-CAM	Campeche	Mexico
MX-CHH	Chihuahua	Mexico
MX-CHP	Chiapas	Mexico
MX-COA	Coahuila>	Mexico
MX-COL	Colima	Mexico
MX-DIF	DistritoFederal	Mexico
DistritoFederal	Durango	Mexico
MX-GRO	Guerrero	Mexico
MX-GUA	Guanajuato	Mexico
MX-HID	Hidalgo	Mexico
MX-JAL	Jalisco	Mexico
MX-MEX	México	Mexico
MX-MIC	Michoacán	Mexico
MX-MOR	Morelos	Mexico
MX-NAY	Nayarit	Mexico
MX-NLE	NuevoLeón	Mexico
MX-OAX	Oaxaca	Mexico
MX-PUE	Puebla	Mexico
MX-QUE	Queretaro	Mexico
MX-ROO	QuintanaRoo	Mexico
MX-SIN	Sinaloa	Mexico
MX-SLP	SanLuisPotosí	Mexico
MX-SON	Sonora	Mexico
MX-TAB	Tabasco	Mexico
MX-TAM	Tamaulipas	Mexico
MX-TLA	Tlaxcala	Mexico
MX-VER	Veracruz	Mexico
MX-YUC	Yucatán	Mexico
MX-ZAC	Zacatecas	Mexico
NL-DR	Drenthe	Netherlands
NL-FL	Flevoland	Netherlands
NL-FR	Friesland	Netherlands
NL-GE	Gelderland	Netherlands
NL-GR	Groningen	Netherlands
NL-LI	Limburg	Netherlands
NL-NB	Noord-Brabant	Netherlands
NL-NH	Noord-Holland	Netherlands
NL-OV	Overijssel	Netherlands
NL-UT	Utrecht	Netherlands
NL-ZE	Zeeland	Netherlands
NL-ZH	Zuid-Holland	Netherlands
NZ-AUK	Auckland	Netherlands
NZ-BOP	Bay of Plenty	Netherlands
NZ-CAN	Canterbury	Netherlands
NZ-CIT	Chatham Islands Territory	Netherlands
NZ-GIS	Gisborne	Netherlands
NZ-HKB	Hawke's Bay	Netherlands
NZ-MBH	Marlborough	Netherlands
NZ-MWT	Manawatu-Wanganui	Netherlands
NZ-NSN	Nelson	Netherlands
NZ-NTL	Northland	Netherlands
NZ-OTA	Otago	Netherlands
NZ-STL	Southland	Netherlands
NZ-TAS	Tasman	Netherlands
NZ-TKI	Taranaki	Netherlands
NZ-WGN	Wellington	Netherlands
NZ-WKO	Waikato	Netherlands
NZ-WTC	West Coast	Netherlands
PL-BB	Bielsko	Poland
PL-BK	Bialystok	Poland
PL-BP	BialaPodlaska	Poland
PL-BY	Bydgoszcz	Poland
PL-CH	Chelm	Poland
PL-CI	Ciechanów	Poland
PL-CZ	Czestochowa	Poland
PL-EL	Elblag	Poland
PL-GD	Gdansk	Poland
PL-GO	Gorzów	Poland
PL-JG	JeleniaGera	Poland
PL-KA	Katowice	Poland
PL-KI	Kielce	Poland
PL-KL	Kalisz	Poland
PL-KN	Konin	Poland
PL-KO	Koszalin	Poland
PL-KR	Kraków	Poland
PL-KS	Krosno	Poland
PL-LD	Lódz	Poland
PL-LE	Leszno	Poland
PL-LG	Legnica	Poland
PL-LO	Lomia	Poland
PL-LU	Lublin	Poland
PL-NS	NowySacz	Poland
PL-OL	Olsztyn	Poland
PL-OP	Opole	Poland
PL-OS	Ostroleka	Poland
PL-PI	Pila	Poland
PL-PL	Plock	Poland
PL-PO	Poznan	Poland
PL-PR	Przemysl	Poland
PL-PT	Piotrków	Poland
PL-RA	Radom	Poland
PL-RZ	Rzeszów	Poland
PL-SE	Siedlce	Poland
PL-SI	Sieradz	Poland
PL-SK	Skierniewice	Poland
PL-SL	Slupsk	Poland
PL-SU	Suwalki	Poland
PL-SZ	Szczecin	Poland
PL-TA	Tarnów	Poland
PL-TG	Tarnobrzeg	Poland
PL-TO	Torun	Poland
PL-WA	Warszawa	Poland
PL-WB	Walbrzych	Poland
PL-WL	Wloclawek	Poland
PL-WR	Wroclaw	Poland
PL-ZA	Zamosc	Poland
N/A	State is not required	United Kingdom
AL	Alabama	USA
AK	Alaska	USA
AS	AmericanSamoa	USA
AZ	Arizona	USA
AR	Arkansas	USA
CA	California	USA
CO	Colorado	USA
CT	Connecticut	USA
DE	Delaware	USA
DC	DistrictOfColumbia	USA
FL	Florida	USA
FM	FederatedStatesOfMicronesia	USA
GA	Georgia	USA
GU	Guam	USA
HI	Hawaii	USA
ID	Idaho	USA
IL	Illinois	USA
IN	Indiana	USA
IA	Iowa	USA
KS	Kansas	USA
KY	Kentucky	USA
LA	Louisiana	USA
ME	Maine	USA
MD	Maryland	USA
MA	Massachusetts	USA
MH	MarshallIslands	USA
MI	Michigan	USA
MN	Minnesota	USA
MP	NorthernMarianaIslands	USA
MS	Mississippi	USA
MO	Missouri	USA
MT	Montana	USA
NE	Nebraska	USA
NV	Nevada	USA
NH	NewHampshire	USA
NJ	NewJersey	USA
NM	NewMexico	USA
NY	NewYork	USA
NC	NorthCarolina	USA
ND	NorthDakota	USA
OH	Ohio	USA
OK	Oklahoma	USA
OR	Oregon	USA
PA	Pennsylvania	USA
PR	PuertoRico	USA
PW	Palau	USA
RI	RhodeIsland	USA
SC	SouthCarolina	USA
SD	SouthDakota	USA
TN	Tennessee	USA
TX	Texas	USA
UT	Utah	USA
VT	Vermont	USA
VA	Virginia	USA
VI	VirginIslands	USA
WA	Washington	USA
WV	WestVirginia	USA
WI	Wisconsin	USA
WY	Wyoming	USA

Canada Workers Comp Code (Canada only)

Field information for the Canada Workders Comp Code field
Order	Data Type	Description	Examples	Why This Is Needed
12	String¹ between 1-64 characters.	The Canadian WCB Code applies to this earning. If you leave this field blank, the earning amount won’t be included in future WCB YTD totals for this code.	4214 55264	This information is required for the Canadian WCB YTD Limit.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Canada Workers Comp Acct Number (Canada only)

Field information for the Canada Workers Comp Acct Number field
Order	Data Type	Description	Examples	Why This Is Needed
13	String¹ between 1-64 characters.	The Canadian WCB Account Number applicable to this earning. If left blank, the earning amount won’t be included in future WCB YTD totals for this code.	6274747	This information is required for a Canadian WCB YTD Limit.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Canada Previous RP Number (Canada only)

Field information for the Canada Previous RP Number field
Order	Data Type	Description	Examples	Why This Is Needed
14	String¹ 4 characters.	If a different RP Number was used earlier in the tax year or the employee has an RP Number other than the legal entity default, this field is required for YTD reporting. If there has been no change or the employee is assigned the legal entity default rate, it can be left blank.	0001	This data is required for Canadian Tax Remittance YTD when a different RP Number or EI Rate Group was used earlier in the year. If left blank, the current RP Number is used.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

If you’re using any rate groups outside of the default in your Legal Entity, the specific RP Number and EI Rate data should be populated for every record.

Canada Previous EI Rate (Canada only)

Field information for the Canada Previous EI Rate field
Order	Data Type	Description	Examples	Why This Is Needed
15	Numeric between 1.0 and 1.40.	If a different EI Rate was used earlier in the tax year or the employee has an EI Rate other than the legal entity default, this field is required for YTD reporting. If there has been no change or the employee is assigned the legal entity default rate, it can be left blank.	1.4	This value is required for Canadian Tax Remittance YTD when a different EI Rate was used earlier in the year. If left blank the current EI Rate is used.

UK/IRL Deduction YTD Data template fields

Payroll Identifier (Required)

Field information for the Payroll Identifier field
Order	Data Type	Description	Examples	Why This Is Needed
1	String¹ between 1-64 characters.	This field uniquely identifies a group of employees. In some previous payroll provider systems, it could be defined as “Company Number.” It could be defined as “Salary Employees” or “Hourly Employees” if you segregate them into separate groups for Payroll Register purposes. It’s the identifier used to define the current payroll the employee is paid through. This value is the grouping of employees paid at the same time who are reported together in the same payroll totals reports.	B1234 Monthly Executive Payroll	This data is used as part of the key to identify deduction definitions uniquely. It serves to preserve definitions that might have the same name or code but differing functionality between payrolls.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Pay Period End Date (Required)

Field information for the Pay Period End Date field
Order	Data Type	Description	Examples	Why This Is Needed
2	Date. Excel right-justified date format or Excel text format yyyy-mm-dd.	The Pay Period End Date of the period for given YTD values. The Pay Period End Date being used should be the same date for each of the three YTD import files.	Date formatted cells: 09/24/2015 24/09/2015 Text formatted cells: 2015-09-24	This required date identifies the period in your payroll calendar that represents the YTD values given on this import.

Employee Identifier (Required)

Field information for the Employee Identifier field
Order	Data Type	Description	Examples	Why This Is Needed
3	Alphanumeric. Unique value between 1-40 characters. For Canadian pay groups, a unique value between 1-9 characters.	This value enables the system to identify employees uniquely. You might want to use their employee number. It shouldn’t be your employee's Social Security number or Social Insurance Number. We’ll ask for that information later.	3241245 000000006 abc12349	In the context of this import the Employee Identifier, First Name, and Last Name are included for the purposes of helping users identify employees when completing the template. This required field validates that the data being loaded is assigned to the correct employee record. The values given must match an existing employee record in Dayforce exactly.

First Name (Required)

Field information for the First Name field
Order	Data Type	Description	Example	Why This Is Needed
4	String¹ between 1-64 characters.	The legal first name of the employee. Note: Activate‘ compares the First Name and the Last Name with the Employee Identifier in Dayforce. If they don’t match, Activate shows an error message that states that the data is being loaded incorrectly and to check the source data.	Joe	In the context of this import the Employee Identifier, First Name, and Last Name are included to help users identify employees when completing the template. This required field validates that the data being loaded is assigned to the correct employee record. The values given must match an existing employee record in Dayforce exactly.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Last Name (Required)

Field information for the Last Name field
Order	Data Type	Description	Example	Why This Is Needed
5	String¹ between 1-64 characters.	Legal last name of the employee. Note: Activate‘ compares the First Name and the Last Name with the Employee Identifier in Dayforce. If they don’t match, Activate shows an error message that states that the data is being loaded incorrectly and to check the source data.	Smith	In the context of this import the Employee Identifier, First Name, and Last Name are included to help users identify employees when completing the template. This required field validates that the data being loaded is assigned to the correct employee record. The values provided must match an existing employee record in Dayforce exactly.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Company ID (Required)

Field information for the Company ID field
Order	Data Type	Description	Examples	Why This Is Needed
6	Numeric. Length 9-20.	Provide the Federal Employer Identification Number (FEIN) if the legal entity is in the US and the Business Number (BN) if the legal entity is in Canada. For the United Kingdom enter the HMRC/PAYE number. For Ireland, enter the LEI. For Australia, enter the Australian Business Number (ABN).	123456789 234/A1237634 12345678901	This data is required to assign the correct Legal Entity to the specific deduction for tax reporting purposes.

Deduction Code (Required)

Field information for the Deduction Code field
Order	Data Type	Description	Examples	Why This Is Needed
7	String¹ between 1-64 characters.	This is the payroll system Deduction Code as defined on the previous payroll provider's system.	H1	This data is used in combination with the Payroll Identifier and Deduction Description to identify individual deduction definition requirements.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Deduction Description (Required)

Field information for the Deduction Description field
Order	Data Type	Description	Example	Why This Is Needed
8	String¹ between 1-64 characters.	This is the payroll system Deduction Description as defined on the previous payroll provider's system.	Health	This data is used in combination with the Payroll Identifier and Deduction Code to identify individual deduction definition requirements.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Amount (Required)

Field information for the Amount field
Order	Data Type	Description	Example	Why This Is Needed
9	Numeric.	YTD value for this deduction definition.	2751 59.5	This data is required for the first step of the Activate process to balance to the source data. It is required for the YTD accumulator data load files to load the 'To Date' amount for the specific deduction for tax reporting purposes.

Work Location

Field information for the Work Location field
Order	Data Type	Description	Example	Why This Is Needed
10	Numeric. Accepted Values² For US: 2-digit state identifier. For CAN: 2-digit province identifier. For UK: Record "GBR." Work Location. For IRL: Record "IRL."		State: FL IL Province: AF ON United Kingdom: UK Ireland: IRL	This data is required for the YTD data load files for tax reporting purposes. It is possible for the employee to have values in multiple states or provinces thus the requirement to identify the code for each line item.

² Accepted values for Work Location
Accepted Values	State Name	Country Name
AU-ACT	Australian Capital Territory	Australia
AU-NSW	New South Wales	Australia
AU-QLD	Queensland	Australia
AU-SA	South Australia	Australia
AU-TAS	Tasmania	Australia
AU-VIC	Victoria	Australia
AU-WA	Western Australia	Australia
ON	Ontario	Canada
QC	Quebec	Canada
NS	Nova Scotia	Canada
NB	New Brunswick	Canada
MB	Manitoba	Canada
BC	British Colombia	Canada
PE	Prince Edward Island	Canada
SK	Saskatchewan	Canada
AB	Alberta	Canada
NL	Newfoundland and Labrador	Canada
NT	Northwest Territories	Canada
YT	Yukon	Canada
NU	Nunavut	Canada
CN-11	Beijing	China
CN-12	Tianjin	China
CN-13	Hebei	China
CN-14	Shanxi	China
CN-15	NeiMonggol	China
CN-21	Liaoning	China
CN-22	Jilin	China
CN-23	Heilongjiang	China
CN-31	Shanghai	China
CN-32	Jiangsu	China
CN-33	Zhejiang	China
CN-34	Anhui	China
CN-35	Fujian	China
CN-36	Jiangxi	China
CN-37	Shandong	China
CN-41	Henan	China
CN-42	Hubei	China
CN-43	Hunan	China
CN-44	Guangdong	China
CN-45	Guangxi	China
CN-46	Hainan	China
CN-50	Chongqing	China
CN-51	Sichuan	China
CN-52	Guizhou	China
CN-53	Yunnan	China
CN-54	Xizang	China
CN-61	Shaanxi	China
CN-62	Gansu	China
CN-63	Qinghai	China
CN-64	Ningxia	China
CN-65	Xinjiang	China
CN-71	Taiwan	China
CN-91	HongKong	China
CZ-CJC	Jihoceskýkraj	Czech Republic
CZ-CJM	Jihomoravskýkraj	Czech Republic
CZ-CSC	Severoceskýkraj	Czech Republic
CZ-CSM	Severomoravskýkraj	Czech Republic
CZ-CST	Stredoceskýkraj	Czech Republic
CZ-CVC	Východoceskýkraj	Czech Republic
CZ-CZC	Západoceskýkraj	Czech Republic
CZ-PRG	Praha	Czech Republic
DE-BB	Brandenburg	Germany
DE-BE	Berlin	Germany
DE-BW	Baden-Württemberg	Germany
DE-BY	Bayern	Germany
DE-HB	Bremen	Germany
DE-HE	Hessen	Germany
DE-HH	Hamburg	Germany
DE-MV	Mecklenburg-Vorpommern	Germany
DE-NI	Niedersachsen	Germany
DE-NW	Nordrhein-Westfalen	Germany
DE-RP	Rheinland-Pfalz	Germany
DE-SH	Schleswig-Holstein	Germany
DE-SL	Saarland	Germany
DE-SN	Sachsen	Germany
DE-ST	Sachsen-Anhalt	Germany
DE-TH	Thüringen	Germany
IN-AN	AndamanandNicobarIslands	India
IN-AP	AndhraPradesh	India
IN-AR	ArunachalPradesh	India
IN-AS	Assam	India
IN-BR	Bihar	India
IN-CH	Chandigarh	India
IN-DD	DamanandDiu	India
IN-DL	Delhi	India
IN-DN	DadraandNagarHaveli	India
IN-GA	Goa	India
IN-GJ	Gujarat	India
IN-HP	HimachalPradesh	India
IN-HR	Haryana	India
IN-JK	JammuandKashmir	India
IN-KA	Karnataka	India
IN-KL	Kerala	India
IN-LD	Lakshadweep	India
IN-MH	Maharashtra	India
IN-ML	Meghalaya	India
N-MN	Manipur	India
IN-MP	MadhyaPradesh	India
IN-MZ	Mizoram	India
IN-NL	Nagaland	India
IN-OR	Orissa	India
IN-PB	Punjab	India
IN-PY	Pondicherry	India
IN-RJ	Rajasthan	India
IN-SK	Sikkim	India
IN-TN	TamilNadu	India
IN-TR	Tripura	India
IN-UP	UttarPradesh	India
IN-WB	WestBengal	India
N/A	State is not required	Ireland
IT-21	Piemonte	Italy
IT-23	ValledAosta	Italy
IT-25	Lombardia	Italy
IT-32	Trentino-AlteAdige	Italy
IT-34	Veneto	Italy
IT-36	Friuli-VeneziaGiulia	Italy
IT-42	Liguria	Italy
IT-45	Emilia-Romagna	Italy
IT-52	Toscana	Italy
IT-55	Umbria	Italy
IT-57	Marche	Italy
IT-62	Lazio	Italy
IT-65	Abruzzo	Italy
IT-67	Molise	Italy
IT-72	Campania	Italy
IT-75	Puglia	Italy
IT-77	Basilicata	Italy
IT-78	Calabria	Italy
IT-82	Sicilia	Italy
IT-88	Sardegna	Italy
IT-AG	Agrigento	Italy
IT-AL	Alessandria	Italy
IT-AN	Ancona	Italy
IT-AO	Aosta	Italy
IT-AP	AscoliPiceno	Italy
IT-AQ	LAquila	Italy
IT-AR	Arezzo	Italy
IT-AT	Asti	Italy
IT-AV	Avellino	Italy
IT-BA	Bari	Italy
IT-BG	Bergamo	Italy
IT-BI	Biella	Italy
IT-BL	Belluno	Italy
IT-BN	Benevento	Italy
IT-BO	Bologna	Italy
IT-BR	Brindisi	Italy
IT-BS	Brescia	Italy
IT-BZ	Bolzano	Italy
IT-CA	Cagliari	Italy
IT-CB	Campobasso	Italy
IT-CE	Caserta	Italy
IT-CH	Chieti	Italy
IT-CL	Caltanissetta	Italy
IT-CN	Cuneo	Italy
IT-CO	Como	Italy
IT-CR	Cremona	Italy
IT-CS	Cosenza	Italy
IT-CT	Catania	Italy
IT-CZ	Catanzaro	Italy
IT-EN	Enna	Italy
IT-FE	Ferrara	Italy
IT-FG	Foggia	Italy
IT-FI	Firenze	Italy
IT-FO	Forlì	Italy
IT-FR	Frosinone	Italy
IT-GE	Genova	Italy
IT-GO	Gorizia	Italy
IT-GR	Grosseto	Italy
IT-IM	Imperia	Italy
IT-IS	Isernia	Italy
IT-KR	Crotone	Italy
IT-LC	Lecco	Italy
IT-LE	Lecce	Italy
IT-LI	Livorno	Italy
IT-LO	Lodi	Italy
IT-LT	Latina	Italy
IT-LU	Lucca	Italy
IT-MC	Macerata	Italy
IT-ME	Mesaina	Italy
IT-MI	Milano	Italy
IT-MN	Mantova	Italy
IT-MO	Modena	Italy
IT-MS	Massa	Italy
IT-MT	Matera	Italy
IT-NA	Napoli	Italy
IT-NO	Novara	Italy
IT-NU	Nuoro	Italy
IT-OR	Oristano	Italy
IT-PA	Palermo	Italy
IT-PC	Piacenza	Italy
IT-PD	Padova	Italy
IT-PE	Pescara	Italy
IT-PG	Perugia	Italy
IT-PI	Pisa	Italy
IT-PN	Pordenone	Italy
IT-PO	Prato	Italy
IT-PR	Parma	Italy
IT-PS	Pesaro	Italy
IT-PT	Pistoia	Italy
IT-PV	Pavia	Italy
IT-PZ	Potenza	Italy
IT-RA	Ravenna	Italy
IT-RC	ReggioCalabria	Italy
IT-RE	ReggioEmilia	Italy
IT-RG	Ragusa	Italy
IT-RI	Rieti	Italy
IT-RM	Roma	Italy
IT-RN	Rimini	Italy
IT-RO	Rovigo	Italy
IT-SA	Salerno	Italy
IT-SI	Siena	Italy
IT-SO	Sondrio	Italy
IT-SP	LaSpezia	Italy
IT-SR	Siracusa	Italy
IT-SS	Sassari	Italy
IT-SV	Savona	Italy
IT-TA	Taranto	Italy
IT-TE	Teramo	Italy
IT-TN	Trento	Italy
IT-TO	Torino	Italy
IT-TP	Trapani	Italy
IT-TR	Terni	Italy
IT-TS	Trieste	Italy
IT-TV	Treviso	Italy
IT-UD	Udine	Italy
IT-VA	Varese	Italy
IT-VC	Vercelli	Italy
IT-VE	Venezia	Italy
IT-VI	Vicenza	Italy
IT-VR	Verona	Italy
IT-VT	Viterbo	Italy
IT-W	ViboValentia	Italy
JP-01	Hokkaidô	Japan
JP-02	Aomori	Japan
JP-03	Iwate	Japan
JP-04	Miyagi	Japan
JP-05	Akita	Japan
JP-06	Yamagata	Japan
JP-07	Hukusima	Japan
JP-08	Ibaraki	Japan
JP-09	Totigi	Japan
JP-10	Gunma	Japan
JP-11	Saitama	Japan
JP-12	Tiba	Japan
JP-13	Tôkyô	Japan
JP-14>	Kanagawa	Japan
JP-15	Niigata	Japan
JP-16	Toyama	Japan
JP-17	Isikawa	Japan
JP-18	Hukui	Japan
JP-19	Yamanasi	Japan
JP-20	Nagano	Japan
JP-21	Gihu	Japan
JP-22	Sizuoka	Japan
JP-23	Aiti	Japan
JP-24	Mie	Japan
JP-25	Siga	Japan
JP-26	Kyôto	Japan
JP-27	Ôsaka	Japan
JP-28	Hyôgo	Japan
JP-29	Nara	Japan
JP-30	Wakayama	Japan
JP-31	Tottori	Japan
JP-33	Okayama	Japan
JP-34	Hirosima	Japan
JP-35	Yamaguti	Japan
JP-36	Tokusima	Japan
JP-37	Kagawa	Japan
JP-38	Ehime	Japan
JP-39	Kôti	Japan
JP-40	Hukuoka	Japan
JP-41	Saga	Japan
JP-42	Nagasaki	Japan
JP-43	Kumamoto	Japan
JP-44	Ôita	Japan
JP-45	Miyazaki	Japan
JP-46	Kagosima	Japan
JP-47	Okinawa	Japan
KR-11	SeoulTeugbyeolsi	Korea
KR-26	BusanGwangyeogsi	Korea
KR-27	DaeguGwangyeogsi	Korea
KR-28	IncheonGwangyeogsi	Korea
KR-29	GwangjuGwangyeogsi	Korea
KR-30	DaejeonGwangyeogsi	Korea
KR-31	UlsanGwangyeogsi	Korea
KR-41	Gyeonggido	Korea
KR-42	Gangweondo	Korea
KR-43	Chungcheongbugdo	Korea
KR-44	Chungcheongnamdo	Korea
KR-45	Jeonrabugdo	Korea
KR-46	Jeonranamdo	Korea
KR-47	Gyeongsangbugdo	Korea
KR-48	Gyeongsangnamdo	Korea
KR-49	Jejudo	Korea
MX-AGU	Aguascalientes	Mexico
MX-BCN	BajaCalifornia	Mexico
MX-BCS	BajaCaliforniaSur	Mexico
MX-CAM	Campeche	Mexico
MX-CHH	Chihuahua	Mexico
MX-CHP	Chiapas	Mexico
MX-COA	Coahuila>	Mexico
MX-COL	Colima	Mexico
MX-DIF	DistritoFederal	Mexico
DistritoFederal	Durango	Mexico
MX-GRO	Guerrero	Mexico
MX-GUA	Guanajuato	Mexico
MX-HID	Hidalgo	Mexico
MX-JAL	Jalisco	Mexico
MX-MEX	México	Mexico
MX-MIC	Michoacán	Mexico
MX-MOR	Morelos	Mexico
MX-NAY	Nayarit	Mexico
MX-NLE	NuevoLeón	Mexico
MX-OAX	Oaxaca	Mexico
MX-PUE	Puebla	Mexico
MX-QUE	Queretaro	Mexico
MX-ROO	QuintanaRoo	Mexico
MX-SIN	Sinaloa	Mexico
MX-SLP	SanLuisPotosí	Mexico
MX-SON	Sonora	Mexico
MX-TAB	Tabasco	Mexico
MX-TAM	Tamaulipas	Mexico
MX-TLA	Tlaxcala	Mexico
MX-VER	Veracruz	Mexico
MX-YUC	Yucatán	Mexico
MX-ZAC	Zacatecas	Mexico
NL-DR	Drenthe	Netherlands
NL-FL	Flevoland	Netherlands
NL-FR	Friesland	Netherlands
NL-GE	Gelderland	Netherlands
NL-GR	Groningen	Netherlands
NL-LI	Limburg	Netherlands
NL-NB	Noord-Brabant	Netherlands
NL-NH	Noord-Holland	Netherlands
NL-OV	Overijssel	Netherlands
NL-UT	Utrecht	Netherlands
NL-ZE	Zeeland	Netherlands
NL-ZH	Zuid-Holland	Netherlands
NZ-AUK	Auckland	Netherlands
NZ-BOP	Bay of Plenty	Netherlands
NZ-CAN	Canterbury	Netherlands
NZ-CIT	Chatham Islands Territory	Netherlands
NZ-GIS	Gisborne	Netherlands
NZ-HKB	Hawke's Bay	Netherlands
NZ-MBH	Marlborough	Netherlands
NZ-MWT	Manawatu-Wanganui	Netherlands
NZ-NSN	Nelson	Netherlands
NZ-NTL	Northland	Netherlands
NZ-OTA	Otago	Netherlands
NZ-STL	Southland	Netherlands
NZ-TAS	Tasman	Netherlands
NZ-TKI	Taranaki	Netherlands
NZ-WGN	Wellington	Netherlands
NZ-WKO	Waikato	Netherlands
NZ-WTC	West Coast	Netherlands
PL-BB	Bielsko	Poland
PL-BK	Bialystok	Poland
PL-BP	BialaPodlaska	Poland
PL-BY	Bydgoszcz	Poland
PL-CH	Chelm	Poland
PL-CI	Ciechanów	Poland
PL-CZ	Czestochowa	Poland
PL-EL	Elblag	Poland
PL-GD	Gdansk	Poland
PL-GO	Gorzów	Poland
PL-JG	JeleniaGera	Poland
PL-KA	Katowice	Poland
PL-KI	Kielce	Poland
PL-KL	Kalisz	Poland
PL-KN	Konin	Poland
PL-KO	Koszalin	Poland
PL-KR	Kraków	Poland
PL-KS	Krosno	Poland
PL-LD	Lódz	Poland
PL-LE	Leszno	Poland
PL-LG	Legnica	Poland
PL-LO	Lomia	Poland
PL-LU	Lublin	Poland
PL-NS	NowySacz	Poland
PL-OL	Olsztyn	Poland
PL-OP	Opole	Poland
PL-OS	Ostroleka	Poland
PL-PI	Pila	Poland
PL-PL	Plock	Poland
PL-PO	Poznan	Poland
PL-PR	Przemysl	Poland
PL-PT	Piotrków	Poland
PL-RA	Radom	Poland
PL-RZ	Rzeszów	Poland
PL-SE	Siedlce	Poland
PL-SI	Sieradz	Poland
PL-SK	Skierniewice	Poland
PL-SL	Slupsk	Poland
PL-SU	Suwalki	Poland
PL-SZ	Szczecin	Poland
PL-TA	Tarnów	Poland
PL-TG	Tarnobrzeg	Poland
PL-TO	Torun	Poland
PL-WA	Warszawa	Poland
PL-WB	Walbrzych	Poland
PL-WL	Wloclawek	Poland
PL-WR	Wroclaw	Poland
PL-ZA	Zamosc	Poland
N/A	State is not required	United Kingdom
AL	Alabama	USA
AK	Alaska	USA
AS	AmericanSamoa	USA
AZ	Arizona	USA
AR	Arkansas	USA
CA	California	USA
CO	Colorado	USA
CT	Connecticut	USA
DE	Delaware	USA
DC	DistrictOfColumbia	USA
FL	Florida	USA
FM	FederatedStatesOfMicronesia	USA
GA	Georgia	USA
GU	Guam	USA
HI	Hawaii	USA
ID	Idaho	USA
IL	Illinois	USA
IN	Indiana	USA
IA	Iowa	USA
KS	Kansas	USA
KY	Kentucky	USA
LA	Louisiana	USA
ME	Maine	USA
MD	Maryland	USA
MA	Massachusetts	USA
MH	MarshallIslands	USA
MI	Michigan	USA
MN	Minnesota	USA
MP	NorthernMarianaIslands	USA
MS	Mississippi	USA
MO	Missouri	USA
MT	Montana	USA
NE	Nebraska	USA
NV	Nevada	USA
NH	NewHampshire	USA
NJ	NewJersey	USA
NM	NewMexico	USA
NY	NewYork	USA
NC	NorthCarolina	USA
ND	NorthDakota	USA
OH	Ohio	USA
OK	Oklahoma	USA
OR	Oregon	USA
PA	Pennsylvania	USA
PR	PuertoRico	USA
PW	Palau	USA
RI	RhodeIsland	USA
SC	SouthCarolina	USA
SD	SouthDakota	USA
TN	Tennessee	USA
TX	Texas	USA
UT	Utah	USA
VT	Vermont	USA
VA	Virginia	USA
VI	VirginIslands	USA
WA	Washington	USA
WV	WestVirginia	USA
WI	Wisconsin	USA
WY	Wyoming	USA

Canada Workers Comp Code (Canada only)

Field information for the Canada Workers Comp Code field
Order	Data Type	Description	Examples	Why This Is Needed
11	String¹ between 1-64 characters.	The Canadian WCB Code applicable to this Deduction. If left blank, the deduction amount will not be included in future WCB YTD totals for this code.	4214 55264	Required for Canadian WCB YTD Limit.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Canada Workers Comp Acct Number (Canada only)

Field information for the Canada Workers Comp Acct Number field
Order	Data Type	Description	Examples	Why This Is Needed
12	String¹ between 1-64 characters.	The Canadian WCB Account Number applicable to this Deduction. If left blank, the deduction amount will not be included in future WCB YTD totals for this code.	6274747	Required for Canadian WCB YTD Limit.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Canada Previous RP Number (Canada only)

Field information for the Canada Previous RP Number field
Order	Data Type	Description	Examples	Why This Is Needed
13	String¹. 4 characters.	If a different RP Number was used earlier in the tax year or the employee has an RP Number other than the legal entity default, this field is required for YTD reporting. If there has been no change or the employee is assigned the legal entity default rate, it can be left blank.	0001	Required for Canadian Tax Remittance YTD when a different RP Number or EI Rate Group was used earlier in the year. If left blank the current RP Number will be used.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

If you are using any rate groups outside of default within your Legal Entity, every record should have specific RP Number and EI Rate data populated.

Canada Previous EI Rate (Canada only)

Field information for the Canada Previous EI Rate field
Order	Data Type	Description	Examples	Why This Is Needed
14	Numeric between 1.0-1.40.	If a different EI Rate was used earlier in the tax year or the employee has an EI Rate other than the legal entity default, this field is required for YTD reporting. If there has been no change or the employee is assigned the legal entity default rate, it can be left blank.	1.4	Required for Canadian Tax Remittance YTD when a different EI Rate was used earlier in the year. If left blank the current EI Rate will be used.

UK/IRL Tax YTD template fields

Payroll Identifier (Required)

Field information for the Payroll Identifier field
Order	Data Type	Description	Examples	Why This Is Needed
1	String¹ between 1-64 characters.	This field is used to identify a group of employees uniquely. It could be defined as “Company Number“ in some previous payroll provider systems. It could be defined as “Salary Employees“ or “Hourly Employees“ if you segregate them into separate groups for Payroll Register purposes. It’s the identifier used to define the current payroll the employee is paid through. This is the grouping of employees paid at the same time who are reported together in the same payroll totals reports.	B1234 Monthly Executive Payroll	This data is used as part of the key to identify tax definitions uniquely. It serves to preserve definitions, which might have the same name or code but differing functionality between payrolls.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Pay Period End Date (Required)

Field information for the Pay Period End Date field
Order	Data Type	Description	Examples	Why This Is Needed
2	Date. Excel right-justified date format or Excel text format yyyy-mm-dd.	The Pay Period End Date of the period for provided YTD values. The Pay Period End Date being used should be the same date for each of the three YTD import files. Note: Activate validates that the Pay Period End Date is within the effective dates of the National Insurance letter.	Date formatted cells:09/24/2015 24/09/2015 Text formatted cells: 2015-09-24	This date is required to identify the period within your payroll calendar that represents the YTD values provided on this import.

Employee Identifier (Required)

Field information for the Employee Identifier field
Order	Data Type	Description	Examples	Why This Is Needed
3	Alphanumeric. Unique value between 1-9 characters.	Allows our system to identify employees uniquely. Use the same number assigned to the employee in the Getting Started HR data loads.	3241245 000000006 abc123499	Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field validates that the data being loaded against the correct employee record. The values provided must match an existing employee record in Dayforce.

First Name (Required)

Field information for the First Name field
Order	Data Type	Description	Example	Why This Is Needed
4	String¹ between 1-64 characters.	Legal first name of the employee. Note: Activate‘ compares the First Name and the Last Name with the Employee Identifier in Dayforce. If they don’t match, Activate shows an error message that states that the data is being loaded incorrectly and to check the source data.	Joe	Employee Identifier, First Name, and Last Name are included for the purposes of helping users identify employees when completing the template. This required field used to validate that the data being loaded against the correct employee record. The values provided must match an existing employee record in Dayforce.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Last Name (Required)

Field information for the Last Name field
Order	Data Type	Description	Example	Why This Is Needed
5	String¹ between 1-64 characters.	Legal last name of the employee. Note: Activate‘ compares the First Name and the Last Name with the Employee Identifier in Dayforce. If they don’t match, Activate shows an error message that states that the data is being loaded incorrectly and to check the source data.	Smith	Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field validates that the data being loaded against the correct employee record. The values provided must match an existing employee record in Dayforce.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Company ID (Required)

Field information for the Compay ID field
Order	Data Type	Description	Examples	Why This Is Needed
6	Alphanumeric length 9-20.	The unique identifier for the legal entity that the employee was paid through. United Kingdom: HMRC/PAYE number Ireland: Legal Entity Identifier (LEI).	A345S 12345678901234567890	This data is required to assign the YTD amount to the correct Legal Entity for tax reporting purposes.

Tax Code

Field information for the Tax Code field
Order	Data Type	Description	Examples	Why This Is Needed
7	String¹ between 1-64 characters.	The payroll system Tax Code as defined on the previous payroll provider's system.	PayG NI ER PRSI LPT	This data is used to create a mapping from the previous payroll provider's system to the corresponding HCM tax.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Tax Description

Field information for the Tax Description field
Order	Data Type	Description	Examples	Why This Is Needed
8	String¹ between 1-64 characters.	The payroll system Tax Description as defined on the previous payroll provider's system.	Pay As You Go National Insurance Employer Local Property Tax	This data is used to help identify the purpose of the existing legacy tax code.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Tax Level

Field information for the Tax Level field
Order	Data Type	Description	Examples	Why This Is Needed
9	String¹ between 1-64 characters. For the UK: UK_FEDERAL For IRL: Ireland FEDERAL	Indicates if the tax is a Federal or State/Provincial tax, and the tax country.	UK Federal Ireland Federal	This data helps narrow down the possible HCM tax options that this tax code could be mapped to.

¹ Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Work Location (Required)

Field information for the Work Location field
Order	Data Type	Description	Example	Why This Is Needed
10	Country identifier. For the UK: Report “GBR.“ For IRL: Report “IRL.“	If in the United Kingdom, report as GBR for all records. If in Ireland, report as IRL for all records.	GBR IRL	This data is required for the YTD data load files to report against the correct tax codes.

Employer Tax

Field information for the Employer Tax field
Order	Data Type	Description	Examples	Why This Is Needed
11	String Accepted Values: Y N	Indicate if this tax is to be paid by the employer instead of the employee.	Y N	This data is help narrow down the possible HCM tax options this tax code could be mapped to.

Tax Amount

Field information for the Tax Amount field
Order	Data Type	Description	Examples	Why This Is Needed
12	Numeric.	The accumulated amount for the entire tax year associated with this specific tax code. Employees that were terminated and rehired in the same tax year should have a separate set of YTDs for each employment period.	2751 59.5	This data is required to load the To Date amount for the tax code for reporting purposes.

Wage Basis

Field information for the Wage Basis field
Order	Data Type	Description	Examples	Why This Is Needed
13	Numeric.	The accumulated amount of the Taxable Wages pay used to calculate the tax amount for the entire tax year. Employees that were terminated and rehired within the same tax year should have a separate set of YTDs for each employment period.	123456.78	This data is required for YTD Tax reporting in addition to the correct calculation of tax on the following pay period.

National Insurance Letter

Field information for the National Insurance Letter field
Order	Data Type	Description	Examples	Why This Is Needed
14	1-letter identifier.	The National Insurance Letter code. Accepted values: (A, B, C, F, G, H, J, M, S, X, or Z). Only applicable to the UK.	A C M	Required for reporting the National Insurance tax rate for the individual wages. Only include this information with National Insurance tax records.

Earnings Up To Lower Earnings Limit

Field information for the Earnings up To Lower Earnings Limit field
Order	Data Type	Description	Examples	Why This Is Needed
15	Numeric.	The Total Amount of Taxable Wages up to the current tax year Lower Earning Limit (LEL). Only applicable to the UK.	123	Required for reporting the National Insurance tax rate for the individual wages. Only include this information with National Insurance tax records.

Earnings Between Lower Earnings Limit And Primary

Field information for the Earnings Between Lower Earnings Limit And Primary field
Order	Data Type	Description	Examples	Why This Is Needed
16	Numeric.	The Total Amount of Taxable Wages between the current tax years Lower Earning Limit (LEL) and the Primary Threshold. Only applicable to the UK.	123456.78	Required for reporting the National Insurance tax rate for the individual wages. Only include this with National Insurance tax records.

Earnings Between Primary Threshold And Upper Limit

Field information for the Earnings Between Primary Threshold And Upper Limit field
Order	Data Type	Description	Examples	Why This Is Needed
17	Numeric.	The Total Amount of Taxable Wages between the current tax years Lower Earning Limit (LEL) and the Primary Threshold. Only applicable to the UK.	123456.78	Required for reporting the National Insurance tax rate for the individual wages. Only include this information with National Insurance tax records.

Earnings Between Primary Threshold And Upper Earnings Limit

Field information for the Earnings Between Primary Threshold And Upper Earnings Limit field
Order	Data Type	Description	Examples	Why This Is Needed
18	Numeric	The Total Amount of Taxable Wages above and beyond the Upper Earnings Limit (UEL) amount. Only applicable to the UK.	123456.78	Required for reporting the National Insurance tax rate for the individual wages. Only include this information with National Insurance tax records.

PRSI Sub-Class

Field information for the PRSI Sub-Class field
Order	Data Type	Description	Examples	Why This Is Needed
19	1 or 2-letter identifier.	The PRSI Sub-Class Code. Accepted values include: AO, AX, AL, A1, A4, A6, A7, A8, A9, BO, BX, B1, CO, CX, C1, DO, DX, D1, E, HO, HX, H1, J0, J1, J9, K1, M, S0, S1. Required field for PRSI taxes. Only applicable to IRL.	A0 C1 M	Required to delineate some or all earnings to a particular PRSI Sub-Class.

Insurable Weeks

Field information for the Insurable Weeks field
Order	Data Type	Description	Examples	Why This Is Needed
20	Numeric.	The number of weeks in the current tax year that the employee has had their PRSI taxes calculated with the specified sub-class. Required field for PRSI taxes. Only applicable to IRL	12	Required for reporting the number of weeks the employee was covered under the specified PRSI sub-class code.

Emergency Tax Start Date

Field information for the Emergency Tax Start Date field
Order	Data Type	Description	Examples	Why This Is Needed
21	Date. Excel right-justified date format or Excel text format yyyy-mm-dd.	The date the employee started having their PAYE tax calculated on an emergency basis. Only applicable if the employee's IRL PAYE tax is calculated on an emergency basis.	Date formatted cells: 09/24/2015 24/09/2015 Text formatted cells: 2015-09-24	Required to track how long the employee has been eligible to have their taxes calculated on an emergency basis.

Emergency Tax Week

Field information for the Emergency Tax Week field
Order	Data Type	Description	Examples	Why This Is Needed
22	Numeric.	The number of weeks the employee has had their taxes calculated on an emergency basis. Only applicable if the employee's IRL PAYE tax is calculated on an emergency basis.	12	Required to make sure that the appropriate emergency tax rate is used in Dayforce.