Payroll Earning Codes

Use the Payroll Earning Codes wizard to load in the necessary Earnings codes into Dayforce. 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.

Note: This wizard is the second of three wizards that you must complete in sequence for the initial load of Deductions, Earnings, and Tax setup in Dayforce. No sequence is required for later loads of payroll earning codes.

Subsequent loads

After the initial payroll earnings load, complete the next wizard, as appropriate. You can upload additional earnings codes at any time during the project to add on to the employee populations (and codes) not included in the initial load. Examples of when additional loads would be useful include:

• When several countries are implemented in more than one phase.
• When several business units in the same country are implemented in multiple phases.
• Instances where you have data coming from more than one system and it’s not all available at the same time.

Note: If you complete the wizard in the Stage environment and the Stage environment is backfilled into the Config environment, the Payroll Earnings Codes wizard shows as completed and includes the Add More option. See the Executing a Rollback When Using the “Add More” Feature in the Payroll Wizards topic.

Note: 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.

Note: 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, Payroll Tax Codes, Year-to-Date Payroll Totals (USA/CAN).

Using this wizard

You do the following in the Payroll Earning Codes wizard:

Upload the Earning YTD Data template

Use the Earning YTD Data template to upload the key information for initial setup of Earning codes. This data makes sure that Activate starts with the same codes that are currently in your legacy payroll system.

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

Upload the Earnings Election Data template

Use the Earnings Election Data template to upload the key information for the initial setup of Earning codes. This data makes sure that Dayforce marks specific codes as being elections. Elections can be added to employee profiles so they’re added to their pay on a regular interval or basis.

If you’re using the Benefits wizard, include benefit earnings here on the initial load so that the corresponding payroll codes can be added to Dayforce.

Verify the information

The Payroll Earning Codes wizard creates a summary of the unique earning codes found in the templates. The wizard creates a table that lists the following for each earning code:

• Country
• Payroll Identifier
• Earning Code
• Earning Description

Categorize earning codes

To make sure that the earnings have the right taxes and set up, walk through a series of setup steps. Several of the Earning Question pages use Drag and Drop pages. These pages are different from many of the table and question pages in the wizards. A more direct hand is needed to set the data correctly. See the Drag and Drop Pages section (see below).

Install the earning codes in Dayforce

When the earning codes are complete in Activate, install them in Dayforce.

Key concepts

Earnings

Earnings are amounts that are added to create an employee’s gross pay during the calculation of gross pay. In Dayforce, each earning code falls into one of the following categories or earning types:

• Normal: The Normal earning type represents earnings that are paid as income and taxed.
• Reimbursement: Reimbursement earnings represent expenses (such as hotel or gas costs) that employees have paid and that the employer is paying back.
• Taxable Benefit: Taxable benefits can refer to benefits of employment outside of cash compensation. Examples include low- and interest-free loans, gifts, holiday trips, and prizes. The values of these benefits are taxed as part of the employment income.
• Memo Calc: Memo calc earnings are payments or earnings that employees receive but that 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 are also not taxed.
• Salary Sacrifice: Salary Sacrifice earnings are earnings that are an entitlement to cash pay. This earning type applies to the UK.

Tasks

To open the wizard:

1. In Activate Central, click Build Dayforce.

   The Build Dayforce wizards are shown.

2. Click Payroll Earning Codes.

To review the What to Expect When Using “Add More” With This Wizard page:

Note: This page opens if payroll earnings codes have been uploaded previously and you selected I want to add more in Activate Central.

1. Read the information on the page.

   Note the following:

   • Any previously loaded codes are removed from the load process to prevent conflicts in mappings.
   • Activate tries to match new codes you provide to existing codes. You can choose not to accept these mappings and generated new codes.
   • You aren’t required to complete the wizard in the same strict order as the first time this Wizard was completed.
2. Click Next.

To complete and upload the Earning YTD template:

To complete and upload the Earning Election template:

To review the Summary table information:

1. Review the code table created by the wizard and verify that:
   • No codes are missing.
   • The data looks correct.

   Note: If no new codes are provided, you can go back and upload new files or return to Activate Central

2. If data is incorrect or missing, click Back and review the data imports.
3. Click Next.

To categorize earning codes:

To assign earnings to boxes on the Form W-2:

The earnings assigned to the Earnings that report in boxes 10, 11, 12 or 14 category must be assigned to the appropriate box on the Form W-2.

1. For each row in the table, select the appropriate radio button to assign the earning to the appropriate box on the Form W-2/T-4.

   Note: Click in the heading row to show a description of the box.

   Note: Click the tabs at the top (All Codes, Mapped Codes, Unmapped Codes) to show all codes (the default) or specific categories of codes. You can use the Search field to search for additional codes.

2. Click Next.

   Note: To continue, all earnings must be assigned to a box on the Form W-2.

To assign earnings to boxes on the T4 or RL-1:

The earnings assigned to the Display in Additional T4 or RL-1 Box category must be assigned to the appropriate box on the T4-Rl-1.

1. Select each item in the Uncategorized section on the left and drag it to the gray box under the appropriate category on the right.

   Payroll identifiers with the same country, code, and description are grouped as a single item. You can filter the Uncategorized list to search for specific earnings

   Note: Click the tabs at the top (All Codes, Mapped Codes, Unmapped Codes) to show all codes (the default) or specific categories of codes. You can use the Search field to search for additional codes.

   Note: If payroll earnings codes have been uploaded before, you can map the new earnings codes to existing earnings codes in Dayforce.

   Note: You can click Ctrl+Shift to select and move multiple items at the same time.

2. Click Next

   Note: All earnings must be assigned to a box on the T4/Rl-1 to continue.

To assign the taxation method to earnings:

1. In the Taxation Method column for each row, click the drop-down list and select the appropriate taxation method for the earning.

   If the Error icon () shows next to the field, no eligible mappings are given for the data and answers. Click Back to return to the previous page and make your corrections.

   Note: To filter the codes shown, select All Codes, Mapped Codes, and Unmapped Codes.

   Use the Search field to find a code shown on the page. To clear text in the Search field and reset the filter, click the Close button ().

2. Click Next.

   Note: All groups or underlying codes must be assigned a taxation method to continue.

To combine or separate earnings into multiple codes:

1. Review the earnings groupings. Each grouping represents an earning to be created.

   Note: To filter the grouping shown, select Normal, Taxable Benefit, and Memo Calc.

2. To move an earning to a different group, select the earning and drag it to the new group.
3. To edit the information about an earning:
   1. Click Edit.
   2. Update the information as appropriate.
   3. Click Done.
4. To combine or separate an earning, select from the following buttons:
   • Merge
   • Split
   • Group

5. To combine or separate all earnings, select from the following buttons:

   • Merge All
   • Split All
   • Group All

   Note: You can’t split Canadian earnings that were mapped to the Vacation % Standard Payout – All CAN Provinces template earning in Activate into multiple separate earnings on the final consolidation page.

6. If you want to edit information about an earnings group, select the blue pencil to rename the Earning Code and assign the Debit/Credit Ledger Number. Taxable Benefit and Memo Calc. codes have a Debit and Credit Ledger Number.

   For UK earning codes, specify whether a new earning should be included in Gender Pay Gap reporting.

7. Click Done.

To install the earnings information in Dayforce:

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

1. When you click Done on the Earning Questions page, a pop-up window shows to let you know you’re about to install Earnings into Dayforce.

   The pop-up cautions about the following:

   • Confirm that all codes have been separated or consolidated as required. Also confirm that the name, display name, credit, and debit journal codes have been entered. If you don’t separate and rename the codes on the consolidator page, the resulting definition in Dayforce is the Taxation Method name, and multiple codes are merged.
   • When this installation is started, you can’t add any more Earning definitions through Activate. If you have additional Earning definitions to add or change, do so before running the installation.
2. You can click Download to download and save the EarningGenerationHistory.xlsx to your computer.

   This Excel spreadsheet lists the information that’s being uploaded by the Activate wizard. The spreadsheet notes if any codes have been moved from the Payroll wizard to the Earning wizard for further Activate configuration. If this run is a later run of the Payroll Earning Codes wizard, the report includes the current values only.

3. Click one of the following:
   • No to return to the Consolidate or Separate Earnings into Multiple Codes page.
   • Yes to continue with the installation. The Loading Your Earning Data page opens.

     Click Yes one time only. Activate prevents the duplication of earning candidates.

4. 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 Payroll Earnings Codes to the project, click I want to add more. You can run the Payroll Earning Codes wizard again, even if it’s marked as “Bypassed.” Doing this step enables you to rerun the wizard for phased implementations. See s the Executing a Rollback When Using the “Add More” Feature in the Payroll Wizards topic for additional information.

Results

Dayforce now contains a set of earning codes that mirror the wizard's installation.

Note: When installation completes, you can download the Earning Mapping File. You can use this file as a basis for the YTD wizard. Go to Payroll Icon > Troubleshooting Resources, and then click Earning Mapping under Customer Mapping Templates to download the file as an Excel spreadsheet.

Next steps

Review the new Earning Payroll Codes in Dayforce and update as required after the installation from Activate.

If payroll earning codes have been loaded before, the Payroll Tax Codes wizard is now available for completion.

Fields populated in Dayforce

Drag and Drop pages

Several of the Earnings Question pages use Drag and Drop pages. These pages are different from many of the table and question pages in the wizards, and need a more direct hand to set the data correctly.

W-2 Special Box Earning Status (US Earnings)

This page of the Earnings wizard asks you to separate US Earning Codes into Special Taxation Category or Other Earnings. The categories are:

Earnings that report in boxes 10, 11, 12, or 14

Any earnings that need special taxation in these boxes must be sorted into this category. You can also cross-reference with the information in the W2 Earning Boxes Reference Document.

All Other Earnings

Sort all standard codes into this category, and any codes that you’re unsure how to sort.

W-2 Special Box Earning Selection (US Earnings)

Any codes that have been selected as fitting Special Taxation for boxes 10, 11, 12, or 14 are shown here.

Select the radio button beneath the appropriate box in the table to select the appropriate W-2 box for each code. W-2 codes with the same “code, description, and country” are grouped into a single-line item.

If you’re unsure which box is most appropriate, select the information icon beneath the listed tax to review a short explanation.

T4 or RL-1 Special Box Earning Status (CAN Earnings)

This page of the Payroll Earning Codes wizard asks you to separate Canada Earning Codes into Special Taxation Category or Other Earnings. The categories are:

Display in Additional T4 or RL-1 Box

Because most codes either show in T4 box 14, or not shown in the T4 at all, categorize any codes that require a different T4 box here. You can also cross-reference with the information in the Reference Document On T4 and RL-1 Boxes document.

Display in T4 Box 14/RL-1 Box A or Not Displayed on T4/RL-1

Any standard codes should be sorted into this category.

T4 Special Box Earning Selection (CAN Earnings)

Any codes that have been selected as fitting Special Taxation for T4 boxes are shown here.

To select the appropriate T4 box for each code here, select the radio button beneath the appropriate box in the table.

If you’re unsure which box is most appropriate, select the information icon beneath the listed tax to review a short explanation.

CAN Vacation % of Earnings Paid Every Period Status (CAN Earnings)

This page of the Earnings wizard asks you to separate Canada Earning Codes into CAN Vacation % of Earnings Paid Every Period or Other Earnings. The categories are:

CAN Vacation % of Earnings Paid Every Period

This page is specifically to identify which codes are used to Pay Out the Vacation Every Period amount. It doesn’t create the grouping that the Vacation Every Period Code is based on.

All Other Earnings

All standard codes should be sorted into this category, and any codes that you’re unsure how to sort.

CAN Vacation % of Earnings Paid Every Period Taxation Selection (CAN Earnings)

Any codes that have been selected as fitting paying out CAN Vacation % of Earnings Paid Every Period are shown here with a drop-down list to select taxation. However, the only taxation option available on this page is “Vacation % Standard Payout - All CAN Provinces.”

Earning Code Categorization Page

This page prompts you to separate codes into the following categories:

• Normal: The Normal earning type represents earnings that are paid as income and taxed.
• Reimbursement: Reimbursement earnings represent expenses (like hotel or gas costs) that employees have paid and that the employer is paying back.
• Taxable Benefit: Taxable benefits can refer to benefits of employment outside of cash compensation. Examples include low- and interest-free loans, gifts, holiday trips, and prizes, among others; the values of these benefits are taxed as part of the employment income.
• Memo Calc: Memo calc earnings are 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 are also not taxed.

Normal Earnings Time Worked and Rate Status

This page prompts you to separate all codes that are categorized as Normal, and further subcategorize them based on how the employee is paid.

• Time Worked & Calculated by Hours x Rate: For any time worked that is paid based on the amount of time worked. For example, Regular pay or Overtime.
• Time Not Worked & Calculated by Hours x Rate: For any time away from work that is still paid based on how much time is taken away from work. For example, an employee doesn’t work Vacation, but they’re still paid based on how much time is taken.
• Time Worked but Not Calculated by Hours x Rate: For flat amount payments that are still tracked based on hours and time. For example, a Night Shift Premium only occurs based on the hours marked for the Premium, but could be a flat amount in addition to those hours.
• Flat Amounts Not Calculated by Hours x Rate: For flat amount payments that aren’t attached to a specific time. For example, a Bonus payment isn’t usually based on how many hours an employee has worked in the pay period.

Normal Earnings Taxation Selection

This page prompts you to select from a drop-down list of taxes to find what tax most closely matches the earning of each row. If you’re unsure, select Miscellaneous Earning. When installed, you must change taxation later, as needed, in the Dayforce environment.

Note: Tax choices on this page are restricted to codes that are available to the code country. If a tax code is restrictive, it lists countries at the end of its name (example: CAN, US, CAN/US).

Reimbursement Earnings Taxation Selection

This page prompts you to select from a drop-down list of taxes to find what tax most closely matches the earning of each row. If you’re unsure, select Miscellaneous Earning. When installed, you must change taxation later, as needed, in the Dayforce environment.

Note: Tax choices on this page are restricted to codes that are available to the code country. If a tax code is restrictive, it lists countries at the end of its name (example: CAN, US, CAN/US).

Taxable Benefits Earnings Taxation Selection

This page prompts you to select from a drop-down list of taxes to find what tax most closely matches the earnings of each row. If you’re unsure, select Miscellaneous Earning. When installed, you must change taxation later, as needed, in the Dayforce environment.

Note: Tax choices on this page are restricted to codes that are available to the code country. If a tax code is restrictive, it lists countries at the end of its name (example: CAN, US, CAN/US).

Memo Earnings Taxation Selection

This page asks you to select from a drop-down list of taxes to find what tax most closely matches the earning of each row. If you’re unsure, select Miscellaneous Earning. After installed, you must change taxation later, as needed, in the Dayforce environment.

Note: Tax choices on this page are restricted to codes that are available to the code country. If a tax code is restrictive, it lists countries at the end of its name (example: CAN, US, CAN/US).

Eligible Termination Payments Selection

This page prompts you to indicate which earnings represent Eligible Termination Payments, and need special attention during configuration.

Consolidate or Separate Earnings into Multiple Codes

On this page, the wizard shows groupings that are representative of each of the different codes that are going to be created in the Dayforce environment. Each box on this page lists new Earning Codes in groupings that show the different legacy codes that are being mapped to that one code. If more than one code could use the same taxation, the boxes can be consolidated, but codes are placed in separate subgroups that represent unique earnings.

This page is divided into separate tabs based on the previous categories that deduction codes have been separated into: Normal, Reimbursement, Taxable Benefit, Memo Calc

Your actions are as follows:

• Merge: This option groups codes in the same box under one deduction code. You can also click Merge All to combine all boxes that are on one tab.
• Split: This option takes subgroups of codes and splits them so the box is separated into individual codes for each potential version of code. You can also Split All to separate all codes that are on one tab.
• Group: This option takes codes and separates them into like types of subgroups and renames them appropriately. You can also Group All to separate all codes into subgroups that are on one tab.

For each subgroup, you can also select the pen icon to make updates to the code that is generated:

• Name: The Name of the Earning in Dayforce
• Display Name: A 15-character limited version of the Earning Name. The display name is what shows on an employee's earning statements.
• Debit Journal: If you know the General Ledger code for an earning, you can enter the Debit Journal number here.
• Credit Journal: If you know the General Ledger code for an earning, you can enter the Credit Journal number here.
• Gender Pay Gap: If you want to include the earning in Gender Pay Gap reporting, select from Ordinary Pay or Bonus Pay. This option applies to the UK.

Earning codes templates

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.

Earning YTD Data template fields

Payroll Identifier (Required)

Field information for the Payroll Identifier field

Order	Data Type	Description	Examples	Why This Is Needed
1	String1 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 earning definitions uniquely. It serves to preserve definitions that might have the same name or code but differing functionality between payrolls. This field isn’t imported into Dayforce. It’s used as part of the mapping process.

¹ 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.	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.	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 abc123499	For this import, the Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field used to validate 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	String1 between 1-64 characters.	Legal first name of the employee. The value provided must match exactly to an existing employee record in Dayforce. 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	For this import, the Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field used to validate 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	String1 between 1-64 characters.	Legal last name of the employee. The value provided must match exactly to an existing employee record in Dayforce. 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	For this import, the Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field used to validate 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 for YTD)

Field information for the Company ID field

Order	Data Type	Description	Examples	Why This Is Needed
6	String1 between 1-256 characters	The unique identifier for the legal entity that the employee was paid through. USA: Federal Employer Identification Number (FEIN) Canada: Business Number (BN) If duplicate Business Numbers are enabled in Dayforce, you must provide the unique Legal Entity names. United Kingdom: HMRC/PAYE number Ireland: Legal Entity Identifier (LEI) Australia: Australian Business Number (ABN) NZL: New Zealand Business Number (NZBN)	123456789 234/A1237634 12345678901 1234567890123	This data is required to assign the correct Legal Entity to the specific earning for tax reporting purposes.

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

Earning Code (Required)

Field information for the Earning Code field

Order	Data Type	Description	Examples	Why This Is Needed
7	String1 between 1-64 characters.	The payroll system Earning Code as defined on the previous payroll provider's system.	REG	This data is used 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	String1 between 1-64 characters.	The payroll system Earning Description as defined on the previous payroll provider's system.	Regular	This data is used in combination 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.	The accumulated number of hours associated with this specific earning. The Hours value isn’t required when loading YTD history for the UK or Ireland.	2751 59.5	This data is used to identify 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’s 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	For US: 2-letter state identifier For CAN: 2-letter province identifier For UK: record 'GBR' For IRL: record 'IRL' For AUS: state identifier For NZL: region identifier Work Location Accepted Value2	The two letter state/province code of the state the employee worked in which triggered this deduction. If in the United Kingdom report as GBR for all records. If in Ireland report as IRL for all records. If in Australia or New Zealand, provide the location identifier from the Appendix below. Refer to the Appendix below for Valid Work Location accepted value.	USA State: FL IL CAN Province: AB ON United Kingdom: GBR Ireland: IRL Australia: AU-VIC New Zealand: NZ-WGN	This data is required for the YTD data load files for tax reporting purposes. It’s possible for the employee to have values in multiple states or provinces. That is the reason for 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
12	String1 between 1-64 characters.	The Canadian WCB Code applicable to this earning. If left blank, the earning amount won’t 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
13	String1 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	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
14	String14 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’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	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.

Earning Election Data Template Fields

Payroll Identifier (Required)

Field information for the Payroll Identifier field

Order	Data Type	Description	Examples	Why This Is Needed
1	String1 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 ExecutivePayroll	This data is used as part of the key to identify earning definitions uniquely. It serves to preserve definitions, which might have the same name or code but differing functionality between payrolls. This field isn’t imported into Dayforce. It’s used as part of the mapping process.

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

Employee Identifier (Required)

Field information for the Employee Identifier field

Order	Data Type	Description	Examples	Why This is Needed
2	Alphanumeric. Unique value between 1-9 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 abc123499	The Employee Identifier, First Name, and Last Name help users identify employees when completing the template. This required field used to validate 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
3	String1 between 1-64 characters.	Legal first name of the employee. The value provided must match exactly to an existing employee record in Dayforce. 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 used to validate 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
4	String1 between 1-64 characters.	Legal last name of the employee. The value provided must match exactly to an existing employee record in Dayforce. 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 used to validate 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 (), &

Earning Code (Required)

Field information for the Earning Code field

Order	Data Type	Description	Examples	Why This is Needed
5	String1 between 1-64 characters.	The payroll system Earning Code as defined on the previous payroll provider's system.		This data is used 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
6	String1 between 1-64 characters.	The payroll system Earning Description as defined on the previous payroll provider's system.		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 (), &

Effective Start Date (Required)

Field information for the Effective Start Date field

Order	Data Type	Description	Example	Why This is Needed
7	Date. Excel right-justified date format or Excel text format yyyy-mm-dd.	The Effective Start Date for earning to be paid to the employee.	Date formatted cells:09/24/2015 24/09/2015 Text formatted cells:2015-09-24	This data is required to determine the timeframe for beginning the payment to the employee.

Effective End Date

Field information for the Effective End Date field

Order	Data Type	Description	Example	Why This is Needed
8	Date. Excel right-justified date format or Excel text format yyyy-mm-dd.	The Effective End Date for earning to be stop being paid to the employee.	Date formatted cells:09/24/2015 24/09/2015 Text formatted cells: 2015-09-24	This data isn’t required. It can be entered if there is a known end date.

Amount (Required, when Percent blank)

Field information for the Amount field

Order	Data Type	Description	Example	Why This is Needed
9	Numeric. Accepts 10 digits and 3 decimal points.	The flat amount for the earning to be assigned to the employee's payroll record. Don’t enter an Amount when there is a Percent.	1371.3 1371.38 1371.382	This data is used to set up a permanent earning amount. It’s used to update the employee's permanent record.

Percent (Required, when Amount blank)

Field information for the Percent field

Order	Data Type	Description	Example	Why This is Needed
10	Numeric. Accepts 3 digits and 3 decimal points.	The percentage value for the earning to be assigned to the employee's payroll record. Don’t enter a Percent when there is an Amount.	1 to 100; cannot exceed 100	This data is required to set the Earning Parameters for the “Is Generated” earning definitions. It’s required for the Employee Election Import file for updating the employee's permanent record.

Frequency of Earning

Field information for the Frequency of Earning field

Order	Data Type	Description	Example	Why This Is Needed
11	String1 between 1-64 characters.	The assignment of the frequency for making a payment for this earning.	Every Regular Run First Pay of Month Last Pay of Month See drop-down list in Column K on the EarningElectionData Excel sheet.	This data is required for the Payroll Earning Codes feature to assign the proper frequency to the earning code. It’s used on the Employee Payroll Elections feature to assign special frequencies to the employee's record in the case that the employee has a different frequency from the earning definition. Choose the appropriate value from the pick list.

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

Limit Value

Field information for the Limit Value field

Order	Data Type	Description	Example	Why This is Needed
12	Numeric. Accepts 10 digits and 3 decimal points.	The flat amount or percentage that represents the cap for the total earning amount.	1371.3 1371.38 1371.382	The limit can be represented as either a flat amount or a percentage depending on how the earning has been configured. If an employee's earning reaches the limit within the specified period, the application reduces any further payments to zero.

Payee

Field information for the Payee field

Order	Data Type	Description	Example	Why This is Needed
13	String1 between 1-128 characters.	The name of the Payee who will receive the payment for the earning amount.	BCBS_Med Steve Smith Tax Levi #2312	The payee only needs to be included when an earning has more than 1 payee assigned. The application will assign the default payee automatically when left blank if the definition has been configured with a payee.

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

Payee Value

Field information for the Payee Value field

Order	Data Type	Description	Example	Why This is Needed
14	String1 between 1-64 characters.	The string or numeric value that’s unique to the employee. This value is required for reporting the payment to the payee.	Account Number Certificate Number Plan Number	The payee value only needs to be included when there is a payee value that is stored at the employee level. Payee parameters that are defined for all employees (pay group level) don’t need to be provided.

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

Commonly encountered issues

Before you upload the template, make sure that the data doesn’t have any errors. Some common problems include:

• Missing required field or data.
• Trying to upload an old or previously downloaded template file.
• The Earning YTD Data tab or the Earning Election Data tab is missing in the Excel spreadsheet.
• 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, do the following. This step converts the data in the column back to text. This step might resolve information that was formatted incorrectly.
1. Click the letter at the top of the column.
2. In the menu, select Data and Text to Columns.
3. Click Next, Next, and Finish.

Payroll Earning  Data Template Fields

Name (Required)

Field information for the Name field

Order	Data Type	Description	Examples	Why This Is Needed
1	String1 between 1-64 characters.	Name to identify the earning.	AUS Salary NZL Salary SGP Basic Salary	Is used to identify the Earning.

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

Description

Field information for the Description field

Order	Data Type	Description	Examples	Why This Is Needed
2	String1 between 1-256 characters.	Brief Description of the earning.	AUS Salary NZL Salary SGP Basic Salary	Is used to identify the Earning in reports.

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

Display Name

Field information for the Display Name field

Order	Data Type	Description	Examples	Why This Is Needed
3	String1 between 1-15 characters.	Shown on Earning Statements. Some special characters are acceptable, for example, dollar signs ($) and single quotation marks (').	Salary Basic Salary	Is used to identify the Earning in employee Earning Statements.

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

Reference Code (Required)

Field information for the Reference Code field

Order	Data Type	Description	Example	Why This Is Needed
4	String1 between 1-128 characters.	Cross-reference codes are used to export data from Dayforce to other applications.	AUS_SALARY NZL_SALARY SGP_BASIC_SALARY	Is used for Imports and Exports.

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

Tax Compliance Rule (Required)

Field information for the Tax Compliance Rule field

Order	Data Type	Description	Example	Why This Is Needed
5	String1 between 1-128 characters.	Cross-reference code of the Tax and Compliance Rule associated with the earning.	AUS Salary NZL Salary SGP Gross Salary	This information is used to identify the Tax and Compliance Rule associated with the Earning. For nonnative payroll countries, a custom Tax and Compliance Rule must be created for the required country before using this template.

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

Entry Type (Required)

Field information for the Entry Type field

Order	Data Type	Description	Examples	Why This Is Needed
6	Accepted Values: Pay Entry Amount Only Pay Entry Rates Generated	Select one of the following options: Pay Entry Amount Only: Select so that you can only enter a currency amount (for example, dollars) for payroll entries, such as quick entries Pay Entry Rates: Select this option so that you can enter hours or amounts for this Earning on payroll entries and enable pay entry rates to load on the setup screen. If you don’t select this option, you can only enter a currency amount (for example, dollars). Generated: Select this option for generated earnings only. Selecting this option makes the Allow Payee checkbox available and makes the Parameters, Limits, and Pay Groups sub-tabs available. Selecting this option also clears any Separate Check option you previously selected.	Pay Entry Rates Pay Entry Amount Only Generated	Is used to identify if the Earning allows for the entry of pay rates or amount, or if the Earning is automatically generated based on configuration.

Pay Entry Rate Type (Conditional)

Field information for the Pay Entry Rate Type field

Order	Data Type	Description	Examples	Why This Is Needed
7	Accepted Values: Multiplier Amount	Select one of the below options: Multiplier Amount This option is required when the Entry Type is set to “Pay Entry Rates.”	Multiplier Amount	Defines whether quick entry payments are calculated with a multiplier rate, or by a defined amount.

Pay Entry Rate Amount

Field information for the Pay Entry Rate Amount field

Order	Data Type	Description	Example	Why This Is Needed
8	Decimal Digits: 15 Fraction: 5	Enter a default rate or a rate multiplier amount. You can only enter this value when the Entry Type is set to “Pay Entry Rates.”	1	The multiplier or defined amount used by the above option.

Pay Groups

Field information for the Pay Groups field

Order	Data Type	Description	Example	Why This Is Needed
9	Semi-colon separated list String1 between 1-256 characters.	When you enter a value for this option, Pay Groups are added to the Earning with default options: every regular run, effective 1/1/1975. This value can only be provided when Entry Type is set to “Generated.”	WKLY;FTNT;MNTH	Defines the eligible pay groups for Generated Earnings.

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

Allow Payee

Field information for the Allow Payee field

Order	Data Type	Description	Example	Why This Is Needed
10	Boolean.	Available only when Entry Type is set to “Generated” and the earning type is Memo Calculation, Salary Sacrifice, or Taxable Benefit.	YES NO	Allows Generated Earnings to be paid to a third-party Payee. When you select this option, the Payees sub-tab is made available, so you can configure a third-party payee after data load.

Payee Category (Conditional)

Field information for the Payee Category field

Order	Data Type	Description	Example	Why This Is Needed
11	String1 between 1-256 characters.	Cross-reference code of the Payee category. This option is required when Allow Payee is set to “YES.”	Custom Earning Payee Category	Defines the Payee Category for filtering the list of Payees available on the Payees sub-tab.

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

Is Hours Worked (Canada only)

Field information for the Is Hours Worked field

Order	Data Type	Description	Examples	Why This Is Needed
12	Boolean.	This field indicates that the earning contributes to the total hours worked.	YES NO	Is used for reporting purposes. The default value is “NO.”

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

Is Overtime Hours

Field information for the Is Overtime Hours field

Order	Data Type	Description	Examples	Why This Is Needed
13	Boolean.	This field indicates that the earning contributes to overtime hours.	YES NO	Is used for reporting purposes. The default value is “NO.”

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

Is Overtime Earnings

Field information for the Is OVertime Earnings field

Order	Data Type	Description	Examples	Why This Is Needed
14	Boolean.	This field indicates whether the earning should be accumulated as part of overtime earnings, which in turn can be used for reporting or other payroll calculations.	YES NO	Is used for reporting purposes. The default value is “NO.”

Custom Earning Groupings

Field information for the Custom Earning Groupings field

Order	Data Type	Description	Examples	Why This Is Needed
15	Semicolon separated list. String1 between 1-256 characters.	This field identifies the cross-reference code of the custom earning groupings that this earning belongs to.	AU_ORD;AU_OT;NZ_OWP;SG_OW	Is used for reporting purposes.

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

Display Hourly Rates

Field information for the Display Hourly Rates field

Order	Data Type	Description	Examples	Why This Is Needed
16	Accepted Values: Display Do Not Display Apply Report Output Setting	Include or exclude hourly employees' rates from employee earning statements. The default setting ensures that the earning respects the report output default setting.	Display Do Not Display Apply Report Output Setting	Will show hourly employee rates in the employee Earning Statements. The default value is “Apply Report Output Setting.”

Display Hourly Hours/Units

Field information for the Display Hourly Hours/Units field

Order	Data Type	Description	Examples	Why This Is Needed
17	Accepted Values: Display Do Not Display Apply Report Output Setting	Include or exclude hourly employees' hours/units from employee earning statements. The default setting ensures that the earning respects the report output default setting.	Display Do Not Display Apply Report Output Setting	Shows hourly employee hours/units in the employee Earning Statements. The default value is “Apply Report Output Setting.”

Display Salary Rates

Field information for the Display Hourly Rates field

Order	Data Type	Description	Examples	Why This Is Needed
18	Accepted Values: Display Do Not Display Apply Report Output Setting	Include or exclude salaried employees' rates from employee earning statements. The default setting ensures that the earning respects the report output default setting.	Display Do Not Display Apply Report Output Setting	Will show salaried employee rates in the employee Earning Statements. The default value is “Apply Report Output Setting.”

Display Salary Hours/Units

Field information for the Display Salary Hours/Units field

Order	Data Type	Description	Examples	Why This Is Needed
19	Accepted Values: Display Do Not Display Apply Report Output Setting	Include or exclude salaried employees' hours/units from employee earning statements. The default setting ensures that the earning respects the report output default setting.	Display Do Not Display Apply Report Output Setting	Will show salaried employee hours/units in the employee Earning Statements. The default value is “Apply Report Output Setting.”

Display Earnings

Field information for the Display Earnings field

Order	Data Type	Description	Examples	Why This Is Needed
20	Boolean.	Display the earning in the Compensation tab when an employee opens the Earnings feature.	YES NO	Will show the Earning in the Compensation Tab of the Employee Earnings feature. The default value is “YES.”

Premium

Field information for the Premium field

Order	Data Type	Description	Examples	Why This Is Needed
21	Boolean.	Display all or part of the earning as a separate premium line item in the General Ledger. If you select the Premium checkbox, any hours or units entered for this earning definition aren’t included in the total Hours/Units in the Earnings section of online or printed earning statements. They’re itemized if so configured. If this checkbox is cleared, the hours are included in the Hours/Units total in earning statements.	YES NO	Will show all or part of the earning as a separate premium line item in the General Ledger. The default value is “NO.”

Allow Hours without Amount

Field information for the Allow Hours without Amount field

Order	Data Type	Description	Examples	Why This Is Needed
22	Boolean.	Include hours without an amount associated with them in employee earning statements. This field can only be set to true if the earning type is Memo Calculation AND EntryType is NOT “Generated.” The default value is “No.”	YES NO	Allows hours without an amount associated with them in employee Earning Statements.

Unpaid Time Reduces Autopay

Field information for the Unpaid Time Reduces Autopay field

Order	Data Type	Description	Examples	Why This Is Needed
23	Boolean.	Include unpaid time to reduce an amount associated with autopay in employee earning statements. This field can only be set to true if the earning type is Memo Calculation AND EntryType is NOT “Generated.” The default value is “No.”	YES NO	Allows unpaid time to reduce an amount associated with Autopay in employee earning statements.

PAYEVNT Category

Field information for the PAYEVNT Category field

Order	Data Type	Description	Examples	Why This Is Needed
24	Accepted Values:2 Lump Sum Payments Allowances Bonuses and commission items Overtime amount Directors Fees Paid Leave CDEP Amount Income Fringe Benefits Reportable	For Australian Earnings Only Define the PAYEVNT Category for STP reporting.	Lump Sum Payments Allowances Paid Leave	Required in Australia for STP2 reporting.

²Australian STP PAYEVNT Code descriptions and which PAYEVNT Category values they can be used with

PAYEVNT Category STP Code	PAYEVNT Category	PAYEVNT Codes & Descriptions
PAYEVNTEMP226	Allowances	AD: Award Transport Payments
		CD: Cents Per Kilometer
		KN: Task Allowances
		LD: Laundry Allowance
		MD: Overtime Meal Allowances
		OD: Other Allowances
		QN: Qualifications/Certificates
		RD: Domestic or Overseas Travel
		TD: Tool Allowances
PAYEVNTEMP268	Paid Leave	A: Ancillary and defence leave
		C: Cash out leave in service
		O: Other paid leave
		P: Paid parental leave
		U: Unused leave on termination
		W: Workers' compensation
PAYEVNTEMP224	Lump Sum Payments	W: Return to Work Payment
PAYEVNTEMP281	Income Fringe Benefits Reportable	T: Taxable
		X: Exempt
PAYEVNTEMP264	Directors Fees	Leave Blank
PAYEVNTEMP279	CDEP Amount
PAYEVNTEMP263	Overtime amount
PAYEVNTEMP262	Bonuses and commission items

PAYEVNT Code (Conditional

Field information for the PAYEVNT Code field

Order	Data Type	Description	Examples	Why This Is Needed
25	Accepted Values:2 A AD C CD KN LD MD O OD P QN RD T TD U W X	For Australian Earnings Only Define the PAYEVNT code to accompany the PAYEVNT category for STP reporting. This option is required option when the PAYEVNT Category is one of the following: Lump Sum Payments Allowances Paid Leave Income Fringe Benefits Reportable	AD C CD KN L	Required in Australia for STP2 Reporting. The entered value is only valid if the PAYEVNT Category in brackets is also present:2 A (Paid Leave) C (Paid Leave) O (Paid Leave) P (Paid Leave) U (Paid Leave) W (Paid Leave) AD (Allowances) CD (Allowances) KN (Allowances) LD (Allowances) MD (Allowances) OD (Allowances) QN (Allowances) RD (Allowances) TD (Allowances) W (Lump Sum Payments) T (Income Fringe Benefits Reportable) X (Income Fringe Benefits Reportable) Blank/null value (Directors Fees | CDEP Amount | Overtime amount | Bonuses and commission items)

²Australian STP PAYEVNT Code descriptions and which PAYEVNT Category values they can be used with

PAYEVNT Category STP Code	PAYEVNT Category	PAYEVNT Codes & Descriptions
PAYEVNTEMP226	Allowances	AD: Award Transport Payments
		CD: Cents Per Kilometer
		KN: Task Allowances
		LD: Laundry Allowance
		MD: Overtime Meal Allowances
		OD: Other Allowances
		QN: Qualifications/Certificates
		RD: Domestic or Overseas Travel
		TD: Tool Allowances
PAYEVNTEMP268	Paid Leave	A: Ancillary and defence leave
		C: Cash out leave in service
		O: Other paid leave
		P: Paid parental leave
		U: Unused leave on termination
		W: Workers' compensation
PAYEVNTEMP224	Lump Sum Payments	W: Return to Work Payment
PAYEVNTEMP281	Income Fringe Benefits Reportable	T: Taxable
		X: Exempt
PAYEVNTEMP264	Directors Fees	Leave Blank
PAYEVNTEMP279	CDEP Amount
PAYEVNTEMP263	Overtime amount
PAYEVNTEMP262	Bonuses and commission items

Other Allowance Type

Field information for the Other Allowance Type field

Order	Data Type	Description	Examples	Why This Is Needed
26	Accepted Values:3V1 U1 T1 ND H1 G1	For Australian Earnings Only Used to define Other Allowance Type for STP reporting.	V1 T1	Required in Australia for STP2 reporting. The entered value is only valid if the PAYEVNT Category is “Allowances” and the PAYEVNT Code is “OD.”

³Australian Other Allowance Type descriptions

Other Allowance Types & Descriptions
V1 - Private Vehicle
U1 - Uniform
T1 - Transport/Fares
ND - Non Deductible
H1 - Home Office
G1 - General

OTE Earning

Field information for the OTE Earning field

Order	Data Type	Description	Examples	Why This Is Needed
27	Boolean	For Australian Earnings Only Include the earning as part of Ordinary Time Earnings.	YES NO	Required in Australia for STP2 reporting. The default value is “No.”

IR8A Reporting Section (Conditional)

Field information for the IR8A Reporting Section field

Order	Data Type	Description	Examples	Why This Is Needed
28	See Accepted Values: 4	For Singapore Earnings Only Used to define how the earning is to be reported on the IR8A form. This option is required for all Singapore earnings.	Gross Salary Contractual Bonus	This information is required in Singapore for Year End Reconciliation.

⁴ Singapore IR8A Reporting Section options

IR8A Reporting Section
Compensation For Loss Of Office
Contractual Bonus
Designated Pension
Director Fees
Donation
Employee Fixed Income Tax
Employer PF Cont. Overseas
Entertainment
Exempt Income
Ex-Gratia
Gratuity
Gross Commission
Gross Salary
Insurance
Lump Sum
Mosque Building Fund
Non Contractual Bonus
Notice Pay
Other Allowance
Pension
PILON
Provident Fund
RetrenchmentBenefits93
RetrenchmentBenefitsUpto92
ShareOptionGainsS101b
ShareOptionGainsS101g
Transport

Payout Balance

Field information for the Payout Balance field

Order	Data Type	Description	Examples	Why This Is Needed
29	String1 between 1-64 characters.	This field defines the balance associated with the earning.	AU_ANNUAL	This informationlinks a balance to the earning.

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

Pay On Termination

Field information for the Pay On Termination field

Order	Data Type	Description	Examples	Why This Is Needed
30	Boolean.	This field indicates whether the associated balance is paid out on termination.	YES NO	This field enables the linked balance to be automatically paid on termination. The default value is “NO.”

Pay Based on Grant

Field information for the Pay Based on Grant field

Order	Data Type	Description	Examples	Why This Is Needed
31	Boolean.	This field indicates whether only the associated Balance's grant amounts are paid on termination.	YES NO	This information prevents balances that aren’t defined as a Grant from being paid on termination. The default value is “NO.”

Payout Conversion from Balance to Currency

Field information for the Payout Conversion from Balance to Currency field

Order	Data Type	Description	Examples	Why This Is Needed
32	String1 between 1-64 characters.	The formula to apply when converting a payout balance to the earning amount to be paid. The following elements and variables can be used: {b} - Represents the balance amount. This value represents 1 unit of whatever balance being paid out. Standard mathematical symbols for multiplication (*), division (/), addition (+) and subtraction (-). {EMP_BASE_RATE} - Returns the employee’s base rate. {EMP_VAC_RATE} - Returns the employee’s vacation rate. {EMP_DAILY_HR} - Returns the employee’s average daily hours. {EMP_WEEKLY_HR} - Returns the employee’s normal weekly hours.	{b}*{EMP_WEEKLY_HRS}*{EMP_BASE_RATE}	Defines the conversion rate for the balance payout.

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

Important considerations

This wizard doesn’t load YTD information into Dayforce. When the YTD information is loaded, payroll codes are locked down and certain parameters (taxation, generated parameters) are no longer editable in Dayforce.