Important: For Canadian Commercial customers (customers with fewer than 300 employees) to access the Year-to-Date Payroll Totals wizard, click Year-to-Date Payroll Totals (CAN.
To convert data from legacy to Dayforce, you must import year-to-date data for your payroll codes. Use the Year-to-Date Payroll Totals (USA/CAN) wizard to make sure that your deductions, earnings, and taxes are loaded into the system correctly. The code names and descriptions 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.
Complete this task to make sure that the mapping is correct from the legacy system to Dayforce and the data is correct. At Go Live, data is successfully imported in anticipation of the year-end data being filed correctly for taxation and government purposes.
This wizard uses the most up-to-date information from the US Tax Services to make sure that the wage and tax reporting is accurate.
Important notes
- Activate generates the Year-to-Date Import file with the ContributeToNetPay field populated based on the earning code that’s specific to the employees' respective pay group country. When the USA and CAN have shared earning definitions in Dayforce (differing earning types between earning codes of countries), Activate uses the correct tax and compliance code to determine the ContributeToNetPay value.
- This wizard is available only for USA/CAN organizations.
- The Organizational Hierarchy wizard won’t be available for use after you complete the following: a Job History (with the Employee Job History & Secondary Work Assignment wizard), or a YTD Load (with the Year-to-Date Payroll Totals (USA/CAN) wizard or the Year-to-Date Payroll Totals (CAN) wizard).
- 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).
- 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.
- If the Allow Future Dated Import setting is enabled in Dayforce (Pay Group > Payroll Properties), you can import Year-to-Date data into an ongoing/future pay period in Activate. Doing this gives you more time to prep the Go Live data loads (for example, complete mappings and validations) and you won’t have to wait until the period ends to begin the Year-to-Date process.
- The Getting Started wizard installed Canadian employees with a culture code of EN-CA.
- Activate users with Preceda selected as the Ascender Migration Type can use this wizard to select more than one file to upload from your computer in a single step. See Preceda Centralized Data Loads.
- This wizard uses the most up-to-date information from the US Tax Services.
Prerequisites
The following wizards must already be completed and the codes installed in Dayforce:
- Payroll Earnings Codes wizard
- Payroll Deductions Codes wizard
- Payroll Tax Codes wizard
Key concepts
Deductions
Amounts that are subtracted from employees' gross pay during the calculation of net pay in Dayforce. Deductions can be pre-tax 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, attempting to deduct the amount in the next pay period.
- Declining balance deductions: Dayforce calculates the deduction against an outstanding balance that the employee owes.
- Payee deductions: Deductions that are paid to a third-party payee
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 benefits of employment other than cash compensation. Examples include low- and interest-free loans, gifts, and holiday trips and prizes. The values of these benefits are 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.
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 pre-tax 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) wizard:
Complete and upload the Earnings YTD, Deductions YTD, and Taxes YTD template
Use the Payroll YTD Data templates to upload the key information for importing earning, deduction, and tax YTD amounts. This data loads into the information equivalent of a full pay run into the system.
Note: If you upload a Tax YTD record with any US state as the Work Location and no tax level is associated with the US (US Federal, State, Local), Activate shows the following error: “Tax Level: {0} isn’t allowed for Tax: {1} when Work Location is in USA.“
Note: If you upload a Tax YTD record with any Canadian province as the Work Location, the tax level must be associated with Canada (Canada Federal, Provincial). If it isn’t, Activate shows the following error: “Tax Level: {0} isn’t allowed for Tax: {1} when Work Location is in Canada.“
Note: If you upload a Canadian tax at a local level, the Canadian tax must be defined at either a provincial or the Canada Federal level.
Note: Complete this step using present-day employee information.
Indicate whether Dayforce shows historical earning statements
Use the YTD Payroll Options page to indicate whether Dayforce is the system of record for historical Employee Earning Statements. This selection determines whether to autogenerate Earning Statements based on the YTD load.
Review the Information
The wizard creates a summary of the unique codes from the template. It also calculates the total amount of each payroll code, based on the legacy data. You can download reports that show the total amount for each code for the entire organization. You must validate that the codes are in balance for the wizard to move to the next steps.
Map the Legacy Codes to the Codes in Dayforce
When the balance of each code has been verified against the data import files, the next step is to map the legacy codes to codes in the Dayforce environment.
Review the employee information, if applicable
The Mass Assignment Review page opens only if your year-to-date payroll totals include Health Savings Account type deductions. Here, you assign the proper HSA Deduction code for each employee based on their correct HSA setup and Annual Federal Limit.
Identify a Consolidation Method, if applicable.
If employees have multiple tax records mapped to the same Dayforce tax type for one employee check, identify a consolidation method. The consolidation method reports the correct taxable wages.
Different legacy systems might report taxes differently. When multiple tax rows in the file are all mapped to the same Dayforce tax, you must identify the action to take. For example, if the file contains “tax 1,“ “tax 2,“ and “tax 3“ for the same employee and pay run and all are mapped to Federal Withholding tax in Dayforce, should the amounts be summed or should the system use some other logic to identify which amount to use.
Review the validation
Before you can use the wizard to install the Year-to-Date Payroll Totals, the wizard validates the data being imported against the Dayforce environment. When validation is complete, the system shows all messages that either 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 have the system revalidate from this page or upload new templates, if necessary.
If you click Upload New File(s), you return to the beginning and you can reupload the data templates. 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 Earnings YTD, Deductions YTD, and Taxes YTD templates:
- In Activate Central, click Build Dayforce and the Build Dayforce wizards show.
- Click Year-to-Date Payroll Totals (USA/CAN).
- On the YTD Data page, click one of the following:
- Download all templates
- Download to download an individual template.
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
EarningYTDTemplate.xlsx,DeductionYTDTemplate.xlsx, and/orTaxYTDTemplate.xlsxtemplate on your computer. - On the relevant data tabs, complete all columns with the data for all employees in the organization.
Note: Instructions for populating the fields are in the , YTD Data template fields,, Deduction YTD Data template fields, and Tax YTD Data template fields sections (below) and on the Instructions tab of the templates.
- Click Save and close the 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 YTD templates in the location where you saved them 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.
- Click Open. The YTD wizard validates the uploaded files.
Important: If you upload YTD files on the Pay Period End date for a pay group, enable the Allow Future Dated field.
Note: To continue, you must upload valid files for all sections (Earnings, Deductions, and Taxes).
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.
-
Click Next.
A prompt states that the uploaded files will generate new payroll mappings.
Note: All three templates must be uploaded to continue to the next page.
-
Click one of the following:
- No to cancel the process and review the content of the files you uploaded.
- Yes to continue.
You can click Download to download the Candidate Information report. This report contains the type, payroll identifier, code, description, state/province, country, tax level. and indicates whether it’s an employer tax.
To indicate if Dayforce shows historical earning statements:
- On the YTD Payroll Options page, for the How do you want to display historical earning statement to your employees?, click one of the following:
- I want to display earning statements based on this YTD load or I will import historical earning statement records: If Dayforce is the system of record for the organization. Based on contract agreements either Earning Statements are generated based on this YTD load, or the historical earning statements are imported as static records into the Dayforce environment.
- I don’t want to display historical earning statements at all: If Earning Statements for the imported periods won’t be stored in Dayforce.
- Click Next.
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.xlsxdocument 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.
- Review the line for each code and make sure it’s mapped to the appropriate Dayforce code.
Deduction codes with the same “code+description+country“ are grouped into a single-line item on the page. This logic also applies to Earning 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. If this case, when the code has been created in Dayforce, click Back to return to a previous 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: You can select All Codes, Mapped Codes, and Unmapped Codes to filter the codes shown.
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 (
). - 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.
- For any deductions or earnings that are incorrectly aligned, select the drop-down list in the HCM Deduction or Earning column for that deduction/earning and select the correct deduction/earning.
Note: If you select an incorrect deduction/earning, the Error icon (
) shows next to the selected deduction/earning. You must select a correct earning to continue. Note: If you select Drop Earning from import, Activate ignores the earning and doesn’t include it in the election file. However, the previous mapping is retained unchanged and available for use in elections, if needed. This applies to dropped deductions and taxes. A warning shows so you can correct your data, if required, and not run the risk of job errors in Dayforce. Activate doesn’t generate the <PayRunResult> record for an employee in the XML if there are no <Earning>, <Deduction>, or <Tax> sections within it. A warning validation message shows in the summary and in the report. It states that the employee was dropped from the import because all of the earning, deduction, and/or tax data was dropped. Codes categorized as dropped show in the YTD Activate Validation report with a message stating that all YTD records for “<Code> - <Code Description>“ have been dropped from the YTD Import per mappings.
Note: Activate shares the YTD payroll mappings across all environments (Config, Stage, and Train) so you don't have to reconfigure each time you use a different environment.
Note: Deductions that are mapped to earnings show with the “Map as Earning“ option selected. If you select a deduction code instead of “Map as Earning,“ the rows in the deduction file transform to the corresponding deduction code in the XML and not to an earning. If you select “Drop Deduction from Import“ instead of “Map as Earning,“ the rows in the deduction file are dropped from the XML but aren’t transformed to a deduction or an earning. If you revert the deduction mapping but load the same code in the Earning file, it’s handled the same as the previously existing earning mapping.
-
For the YTD taxes, if any new tax records have been found because your last YTD Import or you need to make changes to the previous tax mappings:
- Click Update Tax Mappings and the Taxes page opens.
- For any taxes that are incorrectly aligned, select the drop-down list in the HCM Tax column for that tax and select the correct tax.
- Click Next.
-
On the Tax Questions page, review the items on the page.
Click the Expand icon (
) to expand a category and click the Collapse icon (
) to collapse a category. 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 (
).Click the Information icon (
) next to a category section to show an explanation of the category. In the Uncategorized section, select the items to move to a category section and click the Move Right button (
) beside the appropriate category to move the selected items to that category. Note: To select more than one item, click Ctrl+Shift.
On the right side of each category, the total number of codes currently in that category shows. A warning or error icon shows next to the number of any codes in a category that have warnings or errors, a. If a code has an error and a warning, only the error code shows because it is the higher priority code.
- Click Next.
- Review the tax mappings and make any necessary changes.
- Click Done.
- On the Multiple Wages page, select the Consolidation Method.
- Click Next.
Note: If you want to download and view the content of the tax mapping file, select the Click to download the current tax mapping file link.
- When all codes are mapped, click Done.
Note: Any errors or warnings populate in the right-hand column of the table. Hover over the icon to show more details. If errors are shown, you can’t continue. If warnings or information only messages are shown, you can continue.
To manage tax mappings:
If Activate identifies any new taxes on the YTD import or you want to update existing tax mappings, you must Update Tax Mappings to continue. If there are no new taxes, or you don’t need to make any updates, you don’t have to go through the Update pages.
- If you aren’t updating the tax mappings:
- Click the to download the current tax mapping file link, and you can download the existing tax mappings.
To find tax mappings at any time in Dayforce, go to People Icon > Troubleshooting Resources. Then, select Tax Mapping under Customer Mapping Templates to download the file as an Excel spreadsheet.
- Click Next.
- Click the to download the current tax mapping file link, and you can download the existing tax mappings.
- If you’re updating the tax mappings, update the following as appropriate:
Identify the State for Duplicate Tax Codes Page
Select a state to associate with an unmapped code. You’re given the code names and a drop-down list to select the state association from. If it isn’t a state-specific code, you can associate the tax code with all states.
Note: This page opens only if you upload the same tax with different state values in the Work Location.
HCM Tax Match pages
Match existing tax codes with the most similar Dayforce HCM Tax. You’re given the Tax Code, Description and whether the tax is an Employer Tax or not. The wizard asks you to select from a drop-down list of Dayforce HCM codes. If you’re unsure what Tax Code best matches, click I couldn't find my tax.
This page indicates which category of taxes you’re working with. For example, if you’re working in the US, it might show “USA Federal Taxes,“ and only let you select from US Federal Taxes in the HCM system.
Note: You can’t change cell length. However, if the name of the Tax Code doesn’t fit in the cell, hover your mouse over the cell to get the full name.
Tax Categories pages
Use the drag and drop pages to categorize your existing tax codes into the type of tax code they are. Each cell shows the tax description in bold, and the tax name above it in gray text. It lets you know if the tax is an Employee or Employer Tax.
You can use the Search field to find taxes from a long list. For example, search for “disability“ to find and categorize all taxes that include “disability“ in the code name or description quickly.
Note: To select and move more than one item at the same time, click Ctrl+Shift.
Items that aren’t assigned to a category show in the Uncategorized category. You can filter the Uncategorized category to search for additional categories. You can click Select All to select all uncategorized codes. When selected, the button name changes to Deselect All.
To scroll the uncategorized boxes to off-page sections, hold the mouse button down to select the box and then drag to hover the mouse over the scroll up/down buttons so you can scroll the page while dragging the tax code box.
When you complete the tax category pages, you might need to update with more tax match pages.
Final Tax Mapping Review page
This page is a final review of all Tax codes that are being used in the system.
- If you selected that you couldn’t find your tax on any previous pages, it shows here as an Unknown Tax. To complete this page, you must select a tax type. However, you can change its Level, State/Province Association, Employer Tax Status, County, and HCM tax.
- If all taxes have been completed, you can click Show All Taxes to review the information and, if necessary, change the following for a tax: Level, State/Province Association, Employer Tax Status, County, and HCM tax.
-
Click Done to complete the mapping here.
You automatically go to the next step of the wizard.
To review employee information:
Note: If your Year-to-Date Payroll Totals include Health Savings Account type deductions, the Mass Assignment Review page opens.
- On the Mass Assignment Review page, review the table of employees and make sure that each is correctly set for HSA Family or HSA Self taxation.
- For any unmapped cells under the Deduction Code column, select the most correct deduction code for the employee.
- If you want to download the data to your computer to make it easier to manage many employee records:
- Click Download File and Activate downloads a .csv file that you can edit.
- Make the changes as appropriate.
- Save the updated file to your computer.
- Click Upload File.
- Click Refresh to show the updated information in the table.
- Click Next.
Note: If any deductions are still mapped to the HSA Combined code instead of to a specific family or self-plan, a message indicates the number of issues on the aggregate. Click Back to return to the Mass Assignment Review page to make the necessary changes.
To identify consolidation methods:
If employees have multiple taxes mapped to one tax record for one employee check, identify a consolidation method to report the correct taxable wages.
Because different legacy systems might report taxes differently, when multiple tax rows in the file are all mapped to the same Dayforce tax, you must identify the action to take. For example, if the file contains “tax 1,“ “tax 2,“ and “tax 3“ for the same employee and pay run and all are mapped to Federal Withholding tax in Dayforce, should the amounts be summed or should some other logic be used to identify which amount to use.
- Review the table of Taxes.
- Select the best applicable Consolidation Method from the drop-down lists of available methods:
- Use the highest reported wages: For each employee with multiple taxes, this option pulls only the highest reported amount into the system. The risk of this method would be understating the amount of taxable wages.
- Add all the wages from each tax: This option combines all of the different taxes for the employee into a single collective amount. The risk of this method could be overstating the amount of taxable wages for the code. An error could result when you try to commit payroll in Dayforce if it contradicts the system's tax calculations.
- Use the wages from : [code name]: This option lets you select the tax code used for the reporting. However, this method doesn’t specify employee by employee.
- Click Next.
To do final reviews:
Before Year-to-Dates are loaded into the system, one more validation check takes place using the employee YTD counts and the company YTD totals.
- Review the following tables:
Employee Summary
Provides a preview of the employees who have amounts in this YTD load.
- It separates the pay groups that have employees in them, the Pay Period and Pay Date.
- The next two columns show how many Active/Inactive employees in this pay group have YTD records, and how many Terminated employees in this pay group have YTD records.
- The last two columns show the number of employees associated with this pay group that have no YTD record (or a YTD record of 0.00).
Click Employee Summary in the text string below the table to download a spreadsheet that separates out each individual employee. Use this spreadsheet to double check the data and make sure that employees who have 0.00 records should. Also, make sure that employees who do have a YTD amount have the correct YTD amount.
Company Totals Summary
Provides a preview of the company amounts that are being loaded in this YTD load. It gives the company information by Payroll Identifier and summarizes the amounts by code categories. Review and validate the following spreadsheets in this category:
Company Totals Summary
This spreadsheet is a copy of the table in the page.
Employee Totals Summary
A breakdown of the categories used in the Company Totals Summary, but on an employee by employee level. The amounts stated here are employee-specific, although unlike the Employee Summary Table, this spreadsheet only shows employees who have an amount that is being loaded in by Activate.
-
If any changes are needed, backtrack through the wizard to import any changes.
Important: After the Payroll Year to Date Totals are installed, you can’t uninstall them with Activate.
- When the review of all tables is complete and all data has been validated, click Next.
The Year-to-Date Payroll Totals wizard validates against the Dayforce environment to make sure that the load of data doesn’t cause any errors. When this validation is complete, the YTD Payroll Validate page opens.
To review messages:
- Review the different Error, Warning, and Info messages that result from validation.
- If any error messages are shown, you must resolve them to install the data.
- If the errors are in the Dayforce environment, you must resolve them in Dayforce.
- After you resolve the error messages, click Re-Validate. Repeat until all error messages are gone.
- Click Download to download a spreadsheet that has a record of all populated messages from this data validation.
If any deductions are still mapped to the HSA Combined code instead of a specific family or self-plan, the missing individualized employee mappings are listed.
- Click Download the earning mappings file and Download the deduction mappings file from beneath this table to get a spreadsheet of each set of mappings.
You can download these mapping files by going to the User Menu (Person Icon), selecting Troubleshooting Resources, and selecting the appropriate mapping document under Customer Mapping Templates to download the file as an Excel spreadsheet.
- When all error messages are resolved, click Done & Install to import the data into the system.
After you select Done & Install, Activate notifies you that Org Hierarchy access in the system will be limited from now on.
If you haven’t already completed the Organizational Hierarchy wizard, review it now.
You can also download the mapping for the different codes that were used in this YTD load now.
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.
To install the information in Dayforce:
- On the Validate page, click Done & Install and Activate reruns the validation.
Important: A dialog box states that upon 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 and commit to making the necessary updates to the applicable configuration and 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 return to the Validate page and are 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.
- 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.
During the installation, the current step in the process shows in bold text so you can monitor the progress.
- 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 YTD Data that was imported using the installation. The pay period that was used in the legacy system is now considered Committed data, The Taxation, and the calculation parameters are now locked down on each earning and deduction code that was used in this pay period. These parts of the Payroll codes are now in unmodifiable states.
Note: When the installation completes, you can download the Mapping Files, which are used as a basis for any future YTD load, as follows: 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 Earning YTD template populates the fields on the following pages in Dayforce.
| Field in Template | Field in Dayforce | Page in Dayforce |
|---|---|---|
| Payroll Identifier | — |
— |
| Pay Date | — |
— |
| Pay Frequency | — |
— |
| Employee Identifier | Employee Reference/Number |
When the data is loaded for Parallel and Go Live, this information shows on the Payroll, Pay Run Management tab.
|
| First Name | First Name | |
| Last Name | Last Name | |
| FEIN/BN | Business Number | |
| Earning Code | — | |
| Earning Description | — | |
| Amount | Amount | |
| Hours | — | |
| Employee Work State/Province | Work State | |
|
Canada Workers Comp Code (Canada only) |
Workers Comp Code | |
|
Canada Workers Comp Acct Number (Canada only) |
Workers Comp Account | |
|
Canada Previous RP Number (Canada only) |
— | — |
|
Canada Previous EI Rate (Canada only) |
— | — |
The data uploaded from the Deduction YTD template populates the fields on the following pages in Dayforce.
| Field in Template | Field in Dayforce | Page in Dayforce |
|---|---|---|
| Payroll Identifier | — | — |
| Pay Date | — | — |
| Pay Frequency | — | — |
| 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 | |
| FEIN/BN | Business Number | |
| Deduction Code | Name | |
| Deduction Description | Description | |
| Amount | Amount | |
| Employee Work State/Province | Work State | |
|
Canada Workers Comp Code (Canada only) |
Workers Comp Code | |
|
Canada Workers Comp Acct Number (Canada only) |
Workers Comp Account | |
|
Canada Previous RP Number (Canada only) |
— | |
|
Canada Previous EI Rate (Canada only) |
— |
The data uploaded from the Tax YTD template for Parallel and Go Live populates the fields on the Pay Run Management page in Dayforce (Payroll, Pay Run Management tab).
| Field in Template | Field in Dayforce |
|---|---|
| Payroll Identifier | — |
| Pay Period End Date | — |
| Employee Identifier | Employee Reference / Number |
| First Name | First Name |
| Last Name | Last Name |
| Company ID | Legal Entity |
| Tax Code | Code |
| Tax Description | — |
| Tax Level | — |
| Work Location | Work Location |
|
County (US Only) |
N/A |
| Employer Tax | — |
| Tax Amount | Amount |
| Limited Taxable Wages | Limited Wages |
| Total Taxable Wages | Total Wages |
|
PA Work PSD (US Only) |
PSD Code |
|
PA Resident PSD (US Only) |
PSD Code |
|
Local Tax Resident (US Only) |
— |
|
Canada Previous RP Number (Canada only) |
— |
|
Canada Previous EI Rate (Canada only) |
— |
Files generated by the Year-To-Date Payroll Totals wizard
After completing the Year-to-Date Payroll Totals wizard, Activate automatically generates a single import file and places on the customer's FTP site.
HR Import:
- FTP Subdirectory: Import/PayRunHistoryImport
- Filename: <Namespace> PayRunHistoryImport <DateTime>.xml
Example illustrating how Activate translates the template data to XML:
<?xml version="1.0" encoding="utf-8"?>
<PayRunHistoryImport>
<PayRunHistoryImportSetting>
<AutoCreateEarningDefinition>false</AutoCreateEarningDefinition>
<AutoCreateDeductionDefinition>false</AutoCreateDeductionDefinition>
<AutoCreateTaxDefinition>true</AutoCreateTaxDefinition>
<AutoCreatePayeeDefinition>true</AutoCreatePayeeDefinition>
<AutoCreateLegalEntityDefinition>false</AutoCreateLegalEntityDefinition>
</PayRunHistoryImportSetting>
<PayRun>
<PRPayRunId>27</PRPayRunId>
<NoOverride>false</NoOverride>
<IsOffCycle>false</IsOffCycle>
<PayDate>2019-01-04</PayDate>
<PayGroupXrefCode>CANADA_BI_WEEKLY_2016_01_01</PayGroupXrefCode>
<PayPeriod>01</PayPeriod>
<PayPeriodSuffix>00</PayPeriodSuffix>
<PayPeriodStart>2018-12-14</PayPeriodStart>
<PayPeriodEnd>2018-12-28</PayPeriodEnd>
<PayrollCommittedDate>2019-01-04</PayrollCommittedDate>
<PayRunResult>
<!--95138650: Anthony, Kato - FEIN/BN:111111118SplitbyRPNumberAndEIRate, NoEIRatePRNumber, ExtractedEIRatePRNumber-->
<EmployeeXrefCode>95138650</EmployeeXrefCode>
<PayDate>2019-01-04</PayDate>
<EmployeeWorkStateCode>ON</EmployeeWorkStateCode>
<LegalEntityXrefCode>GDLLP_CAN</LegalEntityXrefCode>
<PRPayRunDefXrefCode>NORMAL</PRPayRunDefXrefCode>
<EmployeeEarningAmount>125500.00000</EmployeeEarningAmount>
<EmployeeDeductionAmount>50.00000</EmployeeDeductionAmount>
<EmployerDeductionAmount>0</EmployerDeductionAmount>
<EmployeeTaxationAmount>3891.30000</EmployeeTaxationAmount>
<EmployerTaxationAmount>3905.10000</EmployerTaxationAmount>
<NetPayAmount>121558.70000</NetPayAmount>
<EITaxRateUsed>1.4</EITaxRateUsed>
<CheckSortOrder>1</CheckSortOrder>
<PRPayRunCheckTypeXrefCode>Normal</PRPayRunCheckTypeXrefCode>
<CheckDate>2019-01-04</CheckDate>
<EmployeeNumber>95138650</EmployeeNumber>
<IncludeOnYearEnd>true</IncludeOnYearEnd>
<PayRunEarning>
<!--CAN_Normal_TimeWorked_OT 1.0/CAN_Normal_TimeWorked_OT 1.0, Amount:125500.00000EI Rate:, RP:-->
<PREarningXrefCode>OT1_0</PREarningXrefCode><Amount>125500.00000</Amount>
<Units>1350.00000</Units>
<Rate>0</Rate>
<StateCode>ON</StateCode>
<IsWCBAssessable>true</IsWCBAssessable>
<ContributeToNetPay>true</ContributeToNetPay>
</PayRunEarning>
<PayRunDeduction>
<!--CAN_Ded_Pre_RPP/CAN_Ded_Pre_RPP. Amount:50.00000EI Rate:, RP:-->
<PRDeductionXrefCode>RPP_AMT</PRDeductionXrefCode>
<Amount>50.00000</Amount>
<IsPreTax>true</IsPreTax>
<IsEmployerDeduction>false</IsEmployerDeduction>
<IsWCBDeduction>false</IsWCBDeduction>
</PayRunDeduction>
<PayRunTax>
<!--CAN_Fed_CPP_EE/CAN-10000000-01. Amount:2544.30000TTW:, LTW:EI Rate:, RP: WorkPSD:, ResPSD:, Res: CalculatedCanGrossWageAmount, CalculatedCurrentWageBasis, CalculatedCanGrossWageAmount, CalculatedCurrentWageBasis-->
<TaxAuthorityInstanceXrefCode>CAN-10000000-01</TaxAuthorityInstanceXrefCode>
<Amount>2544.30000</Amount>
<CurrentWageBasis>57400.00000</CurrentWageBasis>
<GrossWages>125500.00000</GrossWages>
</PayRunTax>
<PayRunTax>
<!--CAN_Fed_EI/CAN-10000000-02. Amount:100.00000 TTW:5000.00000, LTW:5000.00000 EI Rate:, RP: WorkPSD:, ResPSD:, Res: ConsolidatedTaxAmounts, ConsolidatedTaxUsingHighestWages, ConsolidatedTaxAmounts CAN_Fed_EI/CAN-10000000-02. Amount:200.00000 TTW:10000.00000, LTW:10000.00000
EI Rate:, RP:
WorkPSD:, ResPSD:, Res:
ConsolidatedTaxAmounts, ConsolidatedTaxUsingHighestWages, ConsolidatedTaxAmounts CAN_Fed_EI 2/CAN-10000000-02. Amount:300.00000 TTW:20000.00000, LTW:20000.00000
EI Rate:, RP:
WorkPSD:, ResPSD:, Res:
ConsolidatedTaxAmounts, ConsolidatedTaxUsingHighestWages, ConsolidatedTaxAmounts CAN_Fed_EI 2/CAN-10000000-02. Amount:600.00000 TTW:40000.00000, LTW:40000.00000
EI Rate:, RP:
WorkPSD:, ResPSD:, Res:
ConsolidatedTaxAmounts, ConsolidatedTaxUsingHighestWages, ConsolidatedTaxAmounts CAN_Fed_EI 3/CAN-10000000-02. Amount:50.00000 TTW:2000.00000, LTW:1000.00000
EI Rate:, RP:
WorkPSD:, ResPSD:, Res:
ConsolidatedTaxAmounts, ConsolidatedTaxUsingHighestWages, ConsolidatedTaxAmounts-->
<TaxAuthorityInstanceXrefCode>CAN-10000000-02</TaxAuthorityInstanceXrefCode>
<Amount>1250.00000</Amount>
<CurrentWageBasis>60000.00000</CurrentWageBasis>
<GrossWages>60000.00000</GrossWages>
<EIRate>1.4</EIRate>
</PayRunTax>
<PayRunTax>
<!--CAN_Fed_Income_ON/CAN-10000000-15. Amount:52.00000 TTW:7720.00000, LTW:7720.00000 EI Rate:, RP: WorkPSD:, ResPSD:, Res:-->
<TaxAuthorityInstanceXrefCode>CAN-10000000-15</TaxAuthorityInstanceXrefCode>
<Amount>52.00000</Amount>
<CurrentWageBasis>7720.00000</CurrentWageBasis>
<GrossWages>7720.00000</GrossWages>
</PayRunTax>
<PayRunTax>
<!--CAN_Prov_Income_ON/CAN-10070000-15. Amount:45.00000 TTW:7710.00000, LTW:7710.00000 EI Rate:, RP: WorkPSD:, ResPSD:, Res:-->
<TaxAuthorityInstanceXrefCode>CAN-10070000-15</TaxAuthorityInstanceXrefCode>
<Amount>45.00000</Amount>
<CurrentWageBasis>7710.00000</CurrentWageBasis>
<GrossWages>7710.00000</GrossWages>
</PayRunTax>
<PayRunTax>
<!---->
<TaxAuthorityInstanceXrefCode>CAN-10000000-03</TaxAuthorityInstanceXrefCode>
<Amount>2544.30000</Amount>
<CurrentWageBasis>57400.00000</CurrentWageBasis>
<GrossWages>125500.00000</GrossWages>
</PayRunTax>
<PayRunTax>
<!---->
<TaxAuthorityInstanceXrefCode>CAN-10000000-04</TaxAuthorityInstanceXrefCode>
<Amount>1360.80000</Amount>
<CurrentWageBasis>53100.00000</CurrentWageBasis>
<GrossWages>60000.00000</GrossWages>
<EIRate>1.4</EIRate>
</PayRunTax>
</PayRunResult>
</PayRun>
<PayRun>
<PRPayRunId>28</PRPayRunId>
<NoOverride>false</NoOverride>
<IsOffCycle>false</IsOffCycle>
<PayDate>2019-01-04</PayDate>
<PayGroupXrefCode>USA_BI_WEEKLY_2016_01_01</PayGroupXrefCode>
<PayPeriod>01</PayPeriod>
<PayPeriodSuffix>00</PayPeriodSuffix>
<PayPeriodStart>2018-12-14</PayPeriodStart>
<PayPeriodEnd>2018-12-28</PayPeriodEnd>
<PayrollCommittedDate>2019-01-04</PayrollCommittedDate>
<PayRunResult>
<!--951020: Mendez, Quyn - FEIN/BN:108229865-->
<EmployeeXrefCode>951020</EmployeeXrefCode>
<PayDate>2019-01-04</PayDate>
<EmployeeWorkStateCode>NM</EmployeeWorkStateCode>
<LegalEntityXrefCode>GDLLP_USA</LegalEntityXrefCode>
<PRPayRunDefXrefCode>NORMAL</PRPayRunDefXrefCode>
<EmployeeEarningAmount>125500.00000</EmployeeEarningAmount>
<EmployeeDeductionAmount>500.00000</EmployeeDeductionAmount>
<EmployerDeductionAmount>0</EmployerDeductionAmount>
<EmployeeTaxationAmount>8.50000</EmployeeTaxationAmount>
<EmployerTaxationAmount>8.40000</EmployerTaxationAmount>
<NetPayAmount>124991.50000</NetPayAmount>
<PRPayRunCheckTypeXrefCode>Normal</PRPayRunCheckTypeXrefCode>
<CheckDate>2019-01-04</CheckDate>
<EmployeeNumber>951020</EmployeeNumber>
<IncludeOnYearEnd>true</IncludeOnYearEnd>
<PayRunEarning>
<!--US_Normal_TimeWorked_OT 1.0/US_Normal_TimeWorked_OT 1.0, Amount:125500.00000 EI Rate:, RP:-->
<PREarningXrefCode>OT1_0_1</PREarningXrefCode>
<Amount>125500.00000</Amount>
<Units>1350.00000</Units>
<Rate>0</Rate>
<StateCode>NM</StateCode>
<IsWCBAssessable>false</IsWCBAssessable>
<ContributeToNetPay>true</ContributeToNetPay>
</PayRunEarning>
<PayRunDeduction>
<!--US_Ded_Pre_Vision/US_Ded_Pre_Vision. Amount:500.00000 EI Rate:, RP:-->
<PRDeductionXrefCode>VISION_PRETAX</PRDeductionXrefCode>
<Amount>500.00000</Amount>
<IsPreTax>true</IsPreTax>
<IsEmployerDeduction>false</IsEmployerDeduction>
</PayRunDeduction>
<PayRunTax>
<!--NM_Worker Comp_EE/USA-00350000-040. Amount:8.50000 TTW:2200.00000, LTW:2200.00000 EI Rate:, RP: WorkPSD:, ResPSD:, Res: WorkersCompWagesZeroed-->
<TaxAuthorityInstanceXrefCode>USA-00350000-040</TaxAuthorityInstanceXrefCode>
<Amount>8.50000</Amount>
<CurrentWageBasis>0</CurrentWageBasis>
<GrossWages>0</GrossWages>
<TotalTaxableWages>0</TotalTaxableWages>
</PayRunTax>
<PayRunTax>
<!--NM_Worker Comp_ER/USA-00350000-030. Amount:8.40000 TTW:2200.00000, LTW:2200.00000 EI Rate:, RP: WorkPSD:, ResPSD:, Res: WorkersCompWagesZeroed-->
<TaxAuthorityInstanceXrefCode>USA-00350000-030</TaxAuthorityInstanceXrefCode>
<Amount>8.40000</Amount>
<CurrentWageBasis>0</CurrentWageBasis>
<GrossWages>0</GrossWages>
<TotalTaxableWages>0</TotalTaxableWages>
</PayRunTax>
</PayRunResult>
</PayRun>
</PayRunHistoryImport>Activate also generates the following two reports, which help with Year-to-Date validation and balancing:
- FTP Subdirectory: PayRunHistoryImport/ActivateValidationReports
- FilesNames:
- <Namespace>-ActivatePayRunValidationReports-<DateTimeStart> - <DateTimeEnd>.xlsx
- <Namespace>-ActivateYTDBalanceAudit-<DateTime>.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 the data doesn’t have any errors. Some common problems include:
- Missing required fields or data.
- The Tax YTD Data 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 and do the following: in the menu, select Data and Text to Columns, and then click Next, Next, and Finish. The data in the column is converted back to text. This action might resolve the problem if the information was formatted incorrectly.
YTD Data 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)
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 1 | String1 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. This field isn’t imported into Dayforce. It’s used as part of the mapping process. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Pay Period End Date (Required)
| 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: |
This required date identifies the period in your payroll calendar that represents the YTD values given on this import. |
Employee Identifier (Required)
| 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. |
It allows our system to uniquely identify employees. You will want to use the same number assigned to the employee in the Getting Started HR data loads. | 3241245 000000006 abc12349 |
In the context of this import 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 an existing employee record in Dayforce. |
First Name (Required)
| Order | Data Type | Description | Example | Why This Is Needed |
|---|---|---|---|---|
|
4 |
String1 between 1-64 characters. |
The legal first name of the employee. This value must match the value in Dayforce exactly. 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. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Last Name (Required)
| Order | Data Type | Description | Example | Why This Is Needed |
|---|---|---|---|---|
|
5 |
String1 between 1-64 characters.
|
Legal last name of the employee. This value must match the value in Dayforce exactly. 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. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Company ID (Required)
| 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. |
Earning Code (Required)
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 7 | String1
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. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Earning Description (Required)
| 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 with the Payroll Identifier and Earning Code to identify individual earning definition requirements. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Amount (Required)
| 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
| 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)
| Order | Data Type | Description | Example | Why This Is Needed |
|---|---|---|---|---|
|
11 |
Numeric.
|
Work Location Accepted Values2 For the US: 2-digit state identifier. For CAN: For the UK: For IRL: For AUS: |
State:
FL IL Province: United Kingdom: For Ireland: Australia: |
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 | 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)
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 12 | String1 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. |
1 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)
| 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 | This information is required for a Canadian WCB YTD Limit. |
1 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)
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 14 | String1 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. |
1 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)
| 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. |
Deduction YTD Data Template Fields
Tax YTD Data Template fields
Payroll Identifier (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 1 | Yes | Yes | 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 tax 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. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Pay Period End Date (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 2 | No | Yes | 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:
Text formatted cells:
|
This date is required to identify the period within your payroll calendar that represents the YTD values provided on this import. |
Employee Identifier (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 3 | Yes | Yes | 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)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Example | Why This Is Needed |
|---|---|---|---|---|---|---|
|
4 |
Yes | Yes | 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. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Last Name (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Example | Why This Is Needed |
|---|---|---|---|---|---|---|
|
5 |
Yes | Yes | 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. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Company ID (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 6 | No | Yes | 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. | 123456789
234/A1237634 |
This data is required to assign the correct Legal Entity to the specific tax for tax reporting purposes. |
Tax Code (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 7 | Yes | Yes | String1 between 1-64 characters. |
The payroll system Tax Code as defined on the previous payroll provider's system. For Quebec taxes - include “QC” in the Code. Example: QC -EI, QC - EI ER, QPP, QPP ER, QC Prov, QC FED |
FED W/H |
This data is used to create a mapping between this particular tax and a corresponding HCM tax. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Tax Description (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 8 | Yes | Yes | String1 between 1-64 characters. |
The payroll system Tax Description as defined on the previous payroll provider's system. For Quebec taxes - include “QC” in the Code. Example: QC -EI, QC - EI ER, QPP, QPP ER, QC Prov, QC FED |
Federal Withholding | This data is used to help identify the purpose of the existing legacy tax code. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Tax Level (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 9 | Yes | Yes |
String Accepted Values: Canada Federal, US Federal, State, Provincial, Local |
This indicates if the tax is a Federal, State/Provincial or Local tax. | Canada Federal Local |
This data is help narrow down the possible HCM tax options this tax code could be mapped to. |
Work Location (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 10 | Yes | Yes | For US: 2-digit state identifier
For CAN: 2-digit province identifier For UK: record 'UK' |
The two letter state/province code of the state the employee worked in where the taxes were paid. If in the United Kingdom report as UK for all records. |
State:
|
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, thus the requirement to identify the code for each line item. |
County (US Only)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 11 | No | No | String1 between 1-64 characters. | The County associated with the Tax Code and Tax Description when a local tax. | Sussex
Erie |
The County is used for US Local taxes to help determine the HCM tax options this tax code could be mapped to. The County provided must be an exact match found in Dayforce. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Employer Tax (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This is Needed |
|---|---|---|---|---|---|---|
| 12 | Yes | Yes |
String Accepted Values: Y |
Indicate if this is a tax 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 (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 13 | No | No | Numeric. | YTD Amount of the Tax | 1234.56 | This data is required for Quarterly and YTD Tax Reporting in addition to the correct calculation of tax on the following pay period. |
Limited Taxable Wages (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 14 | No | No | Numeric. | YTD Amount of the Taxable Wages. If the taxable wages exceed the limit for the particular tax, the limit value should be entered. If no value is provided, the lesser of the Total Taxable Wages or Taxable Wages Limit will be used. | 123456.78 |
This data is required for Quarterly and YTD Tax Reporting in addition to the correct calculation of tax on the following pay period. If the value isn’t available, Activate will calculate this amount based on the Total Taxable Wages and any applicable wage limits. |
Total Taxable Wages (Required)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 15 | No | Yes | Numeric. | Total Amount of Taxable Wages for reporting. This is the amount above and beyond a Taxable Wage Limit amount. | 123456.78 |
This data is required for Quarterly and YTD Tax Reporting in addition to the correct calculation of tax on the following pay period. For the US, this value is required for all tax records being imported. For Canada if the value isn’t available, Activate will calculate and populate with the Gross YTD Wages on your behalf. |
PA Work PSD (US Only)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 16 | No | No | String. 6 characters. | For local Pennsylvanian taxes, provide the appropriate 6-digit PSD code assigned to this Tax Authority. Leave blank for any tax that isn’t a Local Pennsylvania tax. | 123456 | This data is used to map PA Act-32 taxes to the appropriate HCM tax in addition to tax reporting requirements. |
PA Resident PSD (US Only)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 17 | No | No | String. 6 characters. | (If available) For any local Pennsylvania taxes that report a Work PSD, provide the appropriate 6-digit PSD code associated to the PA Lived In location for the employee. For Pennsylvania taxes that aren’t local, or any other taxes in any other state/province, this field can be left blank. | 054766 | This data is used for PA Act-32 tax filing to report the Resident PSD associated to the employee's primary residence at the time the work tax withholding was taken. |
Local Tax Resident (US Only)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 18 | No | No |
String Accepted Values: Yes |
For local taxes, indicate if the employee was considered a Resident for that tax when taken. For taxes that aren’t local, or any other taxes in any other state/province, this field can be left blank. | Yes No |
This data is used to map local taxes to the appropriate HCM tax code in addition to tax reporting requirements. |
Canada Previous RP Number (Canada only)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 19 | No | No | String1 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. |
1 Special characters accepted within the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
Canada Previous EI Rate (Canada only)
| Order | Required for Tax Mapping | Required for YTD | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|---|---|
| 20 | No | No | 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. |