Use the Payroll Comparison wizard to upload legacy payroll data into Activate and compare it against Dayforce pay run data for Parallel testing automatically.
This wizard provides a guided process that standardizes and speeds up the Parallel testing process:
- Simple data templates you can use to upload legacy payroll data at the Company and Employee level.
- Activate automatically outputs variances between legacy and Dayforce values at the Company and Employee level.
- You can save the status, owner, root cause, and make notes that are associated with each variance record at the Company or Employee level.
- The ability to extract data from Dayforce to generate comparison reports with variances automatically.
- The ability to track the review status and progress for each pay period being tested.
Before you begin
Note the following:
-
For Dayforce Native country payroll, you must load data and calculate the payroll in Dayforce.
- For Connected/Unified country payroll, you must load the Global Pay Run Import (GPRI) data in Dayforce. This data must contain the calculated payroll results from the Connected/Unified Pay application.
- You can’t use the Payroll Comparison wizard to import data or make changes directly in Dayforce. The Testing Team executes payroll recalculations directly in Dayforce or the Connected/Unified Pay application and uses Activate to track the comparison progress.
- Tax comparison is currently supported for all countries except Mexico. For Mexico, tax records must be excluded from the Legacy Company Totals template, and the Legacy Employee Tax template can’t be used.
- Payroll Comparison doesn’t currently support a garnishment comparison.
- See the Important Information section (below) for additional information.
- 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 informs you when you access a wizard with invalid mappings that need to be updated.
Tasks
- In Activate Central, click Prepare Environment for Parallel or Go Live. The Prepare Environment for Parallel or Go Live wizards show.
- Click Payroll Comparison.
- On the Payroll Comparison page, click Add Test.
- On the Test Parameters page, complete the questions.
For information on each field see the Questions section (below).
- Click Done. The Payroll Comparison page opens with the new test included in the list of tests in the wizard.
- In Activate Central, click Prepare Environment for Parallel or Go Live. The Prepare Environment for Parallel or Go Live wizards show.
- Click Payroll Comparison.
- On the Payroll Comparison page, select the test to run.
The Payroll Comparison page shows all of the tests that were created. Each test corresponds to a pay run in Dayforce.
Note: If the organization has more than one pay group, you must add a separate test for each pay group.
The Pay Run Test Steps page opens, The Parallel Comparison workflow indicates the completion status for each step on the list. The steps include:
- Edit test parameters: Change the test name and whether the legacy data will be imported. If the test was created in error, you can delete it.
- Review employee data in Dayforce: Run a standardized set of employee data audit reports provided in Activate directly in the Dayforce instance at any time to audit employee data. The audit reports show in the Report folder in Dayforce.
- Generate Company Totals from Dayforce: You can create several payroll comparison tests. When you download the results file, Activate uses a naming convention that shows the actual test name that you populated. This naming convention enables you to differentiate between the files that you downloaded based on which organization you used. The naming convention for the results file is <File Type><Test Name><Date and Time file was downloaded>. The results file provides the Company ID, Type, Tax & Compliance Code, Source, Earning Name, Earning Description, Employee Count, Amount, and Hours.
- Generate Employee Totals Report from Dayforce.
- Upload data from legacy system: Use a guided process to upload payroll data for the entire pay period from the legacy system to Activate. This data is for comparison against the Dayforce selected pay run. If your legacy system doesn’t use two separate deductions for HSA, based on Self and Family limits, you can upload the HSA deductions as a single combined code with the HSA System Code - Federal Limit Unknown code. If you have more than one type of HSA code, a warning shows. You can click Next to continue.
Note: Uploading the legacy data into Activate doesn’t import any data directly into Dayforce.
The first step is to upload a Company Totals file that contains the total amount for each code for the entire payroll period. This information gives Activate the ability to run a comparison across organization totals between the legacy data and the payroll data in Dayforce.
Compare company totals: The Compare Company Totals step, which becomes available after you complete the Company Upload of legacy data, shows an at-a-glance summary of the high-level variance between payroll and the legacy system.When discrepancies exist, you can make corrections that will result in a recalculated pay run in Dayforce. Refresh the values on this page to pull the updated payroll data from Dayforce into Activate and recalculate the variances. You can generate a Detailed Comparison report to review the line-by-line differences.
- Track company review progress.
- Compare employee totals: The Compare Employee Totals step becomes available after you complete at least one Employee Upload file for legacy data. It shows an at-a-glance summary of the employee-level variance between Dayforce payroll and the legacy system.
Similar to the Company Totals page, when discrepancies exist, you can make corrections that result in a recalculated pay run in Dayforce. Refresh the values on this page to pull the updated payroll data from Dayforce into Activate and recalculate the variances. You can also generate a Detailed Comparison report to review the line-by-line differences. The format of the Employee report is similar to the Company report, with one significant difference: on the far left are several columns with details of the Employee record in Dayforce that can help with filtering and troubleshooting discrepancies.
- Track employee review progress: The detailed comparison reports for Company Totals and Employee Totals include review tracking columns at the far right of the data set (Review Status, Review Owner, Root Cause, and Comments). After filling them out, you can import them back into Activate for tracking. Each time the comparison report is generated, it includes the latest review status on each row. You can iteratively update and upload the review columns to track the root cause and status of the variances.
- Complete this test: You can mark the overall status of the test as Passed when you believe your review is complete. You can also save overall testing notes on this page.
- Select the step that you want to do from the list.
Important: Because the employee data drives the payroll calculations in Dayforce, complete this step first.
This step makes sure that the payroll calculated in Dayforce is accurate and the employee records are complete.
- On the Pay Run Test Steps page, select the radio button by the Review employee data in Dayforce field. The Review Employee Data page opens with a checklist of audit reports that are relevant for Parallel testing. This checklist is a way to track whether each audit report has been reviewed or not.
Note: If you want to suggest a change to the checklist for all customers, log the suggestion in the Aha! Portal.
- Log in to Dayforce.
- Go to Reporting > Reports > Employee Data Audits.
- Run the reports listed on the page to verify the data.
Note: You can run similar reports, if you prefer.
For System Integrators:
Note: The Dayforce Super User role and all customer Admin roles have access to the reports. The Dayforce System Administrator role also has access to all features and reports, updated nightly. The full list is: Dayforce Super User, Admin with Powerpay, Customer Admin, Client Administrator, HR Admin, PR Admin, WFM Admin, MS Client Admin, MS Benefits Admin, MS HR Admin, MS PR Admin.
Add role access to the Report folder and the desired reports in Dayforce. You can also edit the report configuration in Dayforce. If you delete reports, any missing reports are automatically reinstalled each time you add a new test in Payroll Comparison. Activate can’t tell whether a report was deleted accidentally or intentionally.
Note: If you want to request changes to the existing reports or suggest new reports, log the suggestion in the Aha! Portal.
- Review the audit reports on the Reports tab in Dayforce and verify that the payroll calculated in Dayforce is accurate.
Note: If you didn't complete the Getting Started wizard in Activate, any missing reports will be installed automatically when you add a new test.
- As you verify the data in each report, select the appropriate checkbox on the Review Employee Data page to record your progress.
- On the Pay Run Test Steps page, select the radio button by the Upload data from legacy system field.
Breadcrumbs at the top of the page indicate where you are in the process.
- On the Load Company Totals page, click Download.
-
Select the location on your computer where you want to save the template files.
You can also download any of the following files:
- Current Earning Mappings
Note: If you load “negative deductions” from the legacy system that are mapped as earnings, Activate converts the amounts to positive earnings, Then, you can view them in the earning comparison without having to tweak the numbers or reload the data as an earning record. This applies to the amount in the Company Earnings from the legacy system section of the Upload Summary table. It also applies to the amount in the Legacy column of the Earnings section in the Compare Company Totals summary. Deductions mapped to a memo earning code retain the original deduction amount.
- Current Deduction Mappings
- Current Tax Mappings
- Current Earning Mappings
- Open the template files on your computer.
-
Complete all required fields in the template documents.
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.
Note the following:
- Earnings that are newly mapped in parallel to a memo code show in the Memo Codes row. Earnings that are newly mapped in parallel to a taxable benefit show in the Taxable Benefits row. Deductions that are newly mapped in parallel to a memo code show in the Memo Codes row on the Compare Company Totals Summary page.
- If you’re working with a long list of earnings or deduction codes and need to stop, click Save in the bottom-left section of the page. You can later return to complete the mapping of the remaining codes.
- If you don’t want to include an earning or deduction in the Total Amount, Total Hours, or count of Unique Legacy Codes in the Company Deductions and/or Deductions and Employee Deductions and/or Employee Earnings section of the upload summary, click Drop Deduction from Importand/orDrop Earning from Import as appropriate. Dropped deductions and earnings aren’t included in the Summary page amounts for the Compare Company Totals, Company Totals comparison report, summary page amounts for Compare Employee Totals, or the Employee Totals comparison report.
- Dropped taxes aren’t included in the following: the summary page amounts for Compare Company Totals, the Company Totals comparison report, the summary page amounts for Compare Employee Totals, or the Employee Totals comparison report.
- When uploading legacy company totals, you can upload Company ID values that are 1–20 characters in length. Doing this enables you to upload legacy files for all supported countries for any pay group.
- The upload of company totals from the legacy system is required. You can provide at least some totals data from your Payroll Register, even if you can't provide line items for every single code or tax. If you can’t upload this information, edit the Test Parameters page and click No for the Will you upload data from the legacy system question.
- When the test Pay Group is in the USA or CAN, the Work Location field is required for rows with Code Type = Tax. This field is ignored for Pay Groups in other countries, and for the Deduction or Earning rows across all countries.
- If you upload a Legacy Company Totals file that contains records for the same tax code or description with both Y and N values for the Employer Tax, a message shows in Activate that states that the Tax code {code name} is listed as both employer and employee tax.
-
Click Save and close the files.
What happens next If you... This page opens... Can click Upload data from legacy on the Test steps page Upload Employee Totals. Haven’t mapped all codes from the Company Totals Mappings. Uploaded bad employee data Employee Upload.
- On the Upload Employee Totals page, click Upload.
You upload the individual Employee Totals files for Earnings, Deductions, Taxes, and Net Pay. See the Legacy Data Files section (below) for information about the Legacy Company Totals template and the Legacy Employee Tax Template fields.
- On the Load Legacy Employee Totals page, click Download All Templates or click the download links for the individual templates you want to download.
- Select the location on your computer where you want to save the files. If you load “negative deductions” from the legacy system that are mapped as earnings, Activate converts the amounts to positive earnings. This conversion enables you to view them in the earning comparison without having to tweak the numbers or reload the data as an earning record.
- Open the files on your computer.
- Complete all of the fields in the documents.
Note: If you upload a Legacy Employee Tax file that contains records for the same tax code/description with both Y and N values for Employer Tax, a message states that the Tax code {code name} is listed as both employer and employee tax. This applies to the amount in the Employee Earnings from Legacy system section of the Upload summary table. It also applies to the amount in the Legacy column of the Earnings section in the Compare Employee Totals summary. Deductions mapped to a memo earning code keep the original deduction amount.
- Click Save and close the files.
You can use any file name for the files you upload. The document must be an Excel or CSV (comma-separated value) document and contain the data in the required format.
Note: If you find any issues while loading Employee Totals or mapping, you can click Back to return to the Company Totals upload page so you can reload the file.
- On the Load Legacy Employee Totals page, click Upload to upload the files containing the legacy employee information.
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.
Note: You aren’t required to upload all four files to continue. If you’re unable to provide some or all of the employee-level data, upload what you can or skip this step.
Note: Tax comparison is currently supported for all countries except Mexico. Don’t upload Legacy Employee Tax templates in tests for Pay Groups in Mexico.
Note: If a mapping page shows instead of the summary page, go to the Profile Menu and select Troubleshooting Resources to see if any background errors exist. Any errors must be resolved to continue with the upload.
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.
- On the Pay Run Test Steps page, select the radio button by the Compare Company Totals field. The Compare Company Totals page opens with a summary of the high-level variance between Dayforce payroll and the legacy system. This variance is for the entire pay period.
- Click Generate detailed comparison report.
The Detailed Comparison report enables you to review the line-by-line differences.
Note: Activate shows the deduction type based on the pay group country if the deduction is used in more than one country on both the Company and Employee Comparison reports.
A prompt opens to help you filter the comparison results by a variance threshold to focus on large discrepancies. The report file name includes the test name to enable you to differentiate between files when working with multiple pay groups or pay periods.
Each time you generate the Detailed Comparison report, it includes the latest review status on each row.
Note: If you load “negative deductions” from the legacy system that are mapped as earnings, Activate converts the amounts to positive earnings. Then, you can view them in the earning comparison without having to tweak the numbers or reload the data as an earning record. This applies to the Legacy Amount column on the Earning tab of the Company Totals Comparison report.
Note: Activate doesn’t automatically update the review status based on the variance amount. The Testing team determines and updates the status of specific line items.
- Enter the variance amount threshold for filtering comparison results.
The default is $0.50. You can change the default in Edit Test Parameters.
-
If you want to exclude codes that are only present in legacy or codes that are only present in Dayforce, select the appropriate checkboxes.
For example, you can exclude legacy codes that weren’t configured in Dayforce to work with smaller data sets.
- Compare the legacy and Dayforce totals.
- If any discrepancies exist, click Download Report.
- Click the location on your computer where you want to save the Comparison report.
The Comparison report is an Excel file with separate tabs for Earnings, Deductions, and Taxes. The report also has an Instructions tab that contains information for tracking the review status of the lime item variances in Activate.
Each tab shows the Dayforce payroll amounts next to the legacy payroll amounts, and calculates the variant amount for review.
- On the Pay Run Test Steps page, select the radio button next to one of the following fields:
- Track company review progress
- Track employee review progress
The Load Company Comparison Review Status page opens.
- Complete the fields on the Comparison report you saved on your computer.
Several columns on the far left provide details about the Dayforce payroll calculation (for example, the Source, Tax & Compliance Code) might help you filter and troubleshoot discrepancies.
Several columns on the far right of the data set (Review Status, Review Owner, Root Cause, and Comments) provide information for tracking the review progress on each row. Completing these fields helps you to track your progress.
- Click Save and close the file.
You can use any file name for the file you upload. The document must be an Excel or CSV (comma-separated value) document and contain the data in the required format.
- Click Upload and upload the updated Comparison report.
- On the Compare Company Totals page, comp hn are the totals.
- If you find any discrepancies, log in to Dayforce and make the corrections.
- On the Compare Company Totals page, click Refresh values from Dayforce.
- Repeat these steps until no discrepancies exist.
Note: The Compare Employee Totals page becomes available after you complete at least one employee upload file containing legacy data.
- On the Pay Run Test Steps page, select the radio button by the Compare employee totals field.
The Compare Employee Totals page opens with an at-a-glance summary of the employee-level variance between Dayforce payroll and the legacy system.
-
If you’re testing a sample subset of the entire organization population, select the Display only the employees uploaded from Legacy checkbox.
Note: The Employee Count row in the summary also includes a Variance report of employees that are present in one system but not the other. This information helps you to identify employees who might have been missed in the legacy data load or aren’t set up correctly in Dayforce.
- Click Generate detailed comparison report.
Note: Activate shows the deduction type based on the pay group country if the deduction is used in more than one country on both the Company and Employee Comparison reports.
The Detailed Comparison report enables you to review the line-by-line differences.
A prompt opens so you can filter the comparison results by a variance threshold to focus on large discrepancies.
Each time you generate the Detailed Comparison report, it includes the latest review status on each row.
Note: If you load “negative deductions” from the legacy system that are mapped as earnings, Activate converts the amounts to positive earnings. Now, you can view them in the earning comparison without having to tweak the numbers or reload the data as an earning record. This applies to the Legacy Amount column on the Earning tab of the Employee Totals Comparison report.
Note: Activate doesn’t automatically update the review status based on the variance amount. The Testing team determines and updates the status of specific line items.
- Enter the variance amount threshold for filtering comparison results.
The default is $0.50. You can change the default in Edit Test Parameters.
-
If you want to exclude codes that are only present in legacy and/or codes that are only present in Dayforce, select the appropriate checkboxes.
For example, you can exclude legacy codes that weren’t configured in Dayforce to work with smaller data sets.
- Compare the legacy and Dayforce totals.
- If any discrepancies exist, click Download Report.
- Select the location on your computer where you want to save the Comparison report.
The Comparison report is an Excel file with separate tabs for Earnings, Deductions, and Taxes. The report also has an Instructions tab with information to help you track the review status of the lime item variances in Activate.
Each tab shows the Dayforce payroll amounts next to the legacy payroll amounts, and calculates the variant amount for review.
- On the Pay Run Test Steps page, select the radio button by the Complete this text field. The Complete Test opens.
- Complete the fields on the page.
For information on each field see the Questions section (below).
- Click Done.
- In Activate Central, click Prepare Environment for Parallel or Go Live. The Prepare Environment for Parallel or Go Live wizards show.
- Click Payroll Comparison.
- On the Payroll Comparison page, click Edit Test next to the test you want to update.
- On the Test Parameters page, make the necessary changes.
For information on each field see the Questions section (below).
- Click Done. The Payroll Comparison page opens.
-
In Activate Central, click Prepare Environment for Parallel or Go Live.
The Prepare Environment for Parallel or Go Live wizards are shown.
- Click Payroll Comparison.
- On the Payroll Comparison page, click the name of the Test that you want to delete and the Pay Run Test Steps page opens.
- Click Edit test parameters and the Edit Parameters page opens.
- Click Delete.
Next steps
Review the comparison results with the customer. You might also need to test exports and Year-end reports in Dayforce.
Questions
Enter a unique name for the test to help you to differentiate it from other tests.
Select the pay groups to include in the test.
Select the pay period to use for the test.
| If you upload a... | Then... |
|---|---|
| File containing a new USA deduction code | You can map it to “HSA Combined” in the Deduction mapper grid. |
| Legacy Company Totals file that contains a code that’s mapped to HSA_COMBINED (whether directly in Payroll Comparison or previously in the Payroll Deduction Codes wizard | The Summary page at the end of the Upload wizard loads successfully and the HSA_COMBINED code doesn’t count towards the number of unique Dayforce deductions. |
| Legacy Employee Deduction file that contains a code that’s mapped to HSA_COMBINED | The Summary page at the end of the Upload wizard loads successfully and the HSA_COMBINED code doesn’t count towards the number of unique Dayforce deductions. |
| Legacy Company Totals file that contains a deduction that’s mapped to HSA_COMBINED | Activate shows it in the Comparison report against an aggregated row for all HSA deductions in the Dayforce pay run. |
| Legacy Employee Deduction file that contains a deduction mapped to HSA_COMBINED in the Payroll Deduction Codes wizard | Activate shows the information in the comparison report against an aggregated row for all HSA deductions for that employee in the Dayforce pay run. For other employees or rows in the file who might have a different HSA legacy code that is mapped to an actual Dayforce deduction, it’s compared against the corresponding Dayforce deduction. |
- Yes: Click this option to show the options to Upload Legacy Data and Compare Company and Employee Totals in the test steps.
- No: Click this option to generate reports of the current Dayforce payroll totals for the pay period in question using the same format as the Detailed Comparison report. You can use the reports to track legacy amounts or review the status outside of Activate as needed. The reports include the test name in the file name. For example, “DayforceCompany Totals_test_name_timestamp.xlsx.”
If your legacy system doesn’t use two separate deductions for HSA, based on Self and Family limits, you can map to “HSA Combined” as one of the options for new deduction codes on the Deduction mapper page. Activate aggregates all HSA Self and Family codes from Dayforce and compares them against the HSA combined codes in the legacy system. When the HSA combined code is loaded, Activate doesn’t count it towards the number of “unique mapped Dayforce codes” in the Company Deductions and Employee Deductions sections.
If you upload a legacy Employee Deduction file that contains a deduction that’s mapped to HSA_COMBINED in the Payroll Deduction Codes wizard, Activate shows the code in the Payroll Comparison report against an aggregated row for all HSA deductions for that employee in the Dayforce pay run.
This question shows if you selected Yes to the Will you import data from your legacy system for comparison? question.
Enter the maximum amount of variance for filtering comparison results between the legacy system and Dayforce. This field defaults to $.50.
- Needs Review:
- Pass: Select this option after you complete the review. The test step remains accessible after being marked Pass in case the team needs to review their work or revert the test status.
Enter any testing notes.
Important information
Payroll Comparison is available to both Dayforce and customer roles, for any project that has access to Activate Central.
The payroll configuration, payroll election, and year-to-date wizards aren’t required to use this wizard. Payroll Comparison uses any existing Legacy-to-Dayforce mappings created by those wizards. Using Activate for other payroll loads simplifies the process of loading legacy payroll data.
If you don't have data from your legacy system, you can use the data audit checklist in Payroll Comparison and generate reports for the Dayforce totals and compare them outside of Activate.
All Activate reporting is based on the pay group and pay period in Dayforce. Provide data for the same time frame as closely as possible if you don't have the same pay groups or pay period dates as Dayforce. (This information is also required for Year-To-Date loads.) If you can’t provide the data, you can still generate the reports for the Dayforce totals and compare them outside of Activate.
The Company ID is required to make sure that calculated payroll values in Dayforce are aligned with the legacy system. The Company ID must exist against a Legal Entity in Dayforce, in the field for Federal/Business ID Number. This Legal Entity must have the same country as the Parallel Test’s pay group. If you can’t provide the data, you can still generate reports for the Dayforce totals and compare them with the legacy system information outside of Activate.
The uploading of legacy earnings and deductions and mapping to the relevant Dayforce earning and deduction codes is supported for all countries. You can compare legacy system data against pay run results in Dayforce for earnings, deductions, and net pay in any country. Where native Dayforce payroll isn’t available, the Global Pay Run Import (GPRI) data sent from the customer’s Connected/Unified payroll application is used to compare with the legacy system data.
Activate currently supports tax uploads and mapping to the relevant Dayforce taxes for all countries except Mexico. When the test’s pay group is Mexico, you can use the wizard to compare earnings, deductions, and net pay, and the reports will still include the tax amounts in Dayforce.
If you have several pay groups, add a separate test for each pay group.
The Payroll Comparison wizard has been used successfully with large pay groups (over 6,000 employees). Using Activate might be faster than loading pages and reports in Dayforce.
No. If you have an idea to change the checklist for all customers, log the suggestion in the Aha! Portal.
The Report folder and all reports in it are installed during Getting Started automatically. If the folder or any reports in it are missing, they’re also automatically installed when you add a new test in Payroll Comparison.
Generally, the Dayforce System Administrator role and all customer Admin roles have access to the reports.
The full list is: Dayforce System Administrator, Dayforce Administrator, Admin with Powerpay, Customer Admin, Client Administrator, HR Admin, PR Admin, WFM Admin, MS Client Admin, MS Benefits Admin, MS HR Admin, MS PR Admin.
Yes! Update the role access to the Report folder and the reports directly in Dayforce.
Yes! Edit the report configuration directly in Dayforce.
Yes! Add them directly in Dayforce.
Yes. Any missing reports are reinstalled automatically each time you add a new test in Payroll Comparison. This happens because Activate can’t tell whether a report was deleted accidentally or intentionally.
Log the suggestion in the Aha! Portal. We’ll review and update the template reports as needed.
The upload of Company Totals from the legacy system is required. Most customers can provide at least some totals data from their Payroll Register, even if they can’t provide line items for every single code or tax. If you can’t provide this data, edit the Test parameters and click No for the Will you upload data from the legacy system? question.
You can skip the upload and focus on working with the high-level Company Totals comparison. You can also work with a partial employee data load. The report has 100% variance from Dayforce on the tabs where no legacy data was uploaded.
You can’t edit codes that were mapped from a Year-To-Date or Payroll Election load in Payroll Comparison. To avoid potential issues with loading fresh data files, you must edit them in those wizards. Work with your Data Conversion Consultant (DCC) if you aren’t sure how to edit those mappings.
As an alternative, you can change the code name or description used in the Payroll Comparison load to map it as a "fresh" code.
Verify the following: the code is configured in Dayforce, you selected the correct Tax and Compliance Code in Dayforce, and it matches the country of the pay group that you’re testing.
| If the... | Then... |
|---|---|
| Deduction is configured as an earning in Dayforce | Select “Map as earning” and select the correct earning code on the next page. |
| Earning is configured as a deduction in Dayforce | Correct the data upload file to indicate that it’s a deduction and upload the file again. |
Note: Deductions mapped to earnings are shown in the Deduction mapper with the “Map as Earning” option selected. If you select a deduction code instead of Map as Earning, the rows in the deduction file are mapped to the corresponding deduction. They show under the Deduction sections in the Summary and Report Totals, and not as the earning. If a deduction was previously “map as earning” and you revert it to an actual deduction but load the same code in the Earning file, it’s handled per the previously existing earning mapping.
Verify that you provided the correct value for “Is Employer Tax?” in the upload file. You can upload the data file again if the value is incorrect. Also, verify that you selected the correct Tax Level and State/Province values.
No valid legacy data was previously uploaded for that file. The corresponding section in the Upload Summary is also blank.
These options are available only if you selected Yes for the Will you upload data from the legacy system? question in the Test set up. You can select Edit Test Parameters to change the answer, if needed.
You can access the page only after you upload a valid legacy data file and complete all missing mappings for the corresponding page. Upload a valid legacy data file in the previous step and make sure that all mappings are complete for all codes in the file.
The Last Refreshed time stamp shows at the top, above the Earnings section. The Dayforce values are refreshed each time you load the page, or click Refresh values from Dayforce. The comparison report is also generated using the current payroll data from Dayforce.
Note: If you click Refresh values from Dayforce on this page, it doesn’t start a Calculate Payroll job in Dayforce. Instead, it retrieves the latest payroll totals to show in Activate.
If you can’t provide legacy data for the entire employee population, click the following to focus on just that subset of employees in the comparison: the Display only the employees uploaded from Legacy checkbox and the Include only the employees uploaded from Legacy report filter.
Selecting the Display only the employees uploaded from Legacy checkbox includes employees that weren’t in the legacy data file. This includes the combined employee list from all of the Legacy Employee data files. For example, if you uploaded earnings but not deductions from an employee, that employee is still included in the totals for the Deductions section. Activate can’t tell whether the employee was intentionally left off the deduction file, or whether they were left off because the deduction wasn’t calculated in the legacy system and therefore is a true variance.
The checkbox includes the combined employee list from all of the Legacy Employee data files. For example, if you uploaded earnings but not deductions from an employee, that employee is still included in the totals for the Deductions section. Activate can’t tell whether the employee was left off the deduction file intentionally or they were left off because the deduction wasn’t calculated in the legacy system and is a true variance.
Yes, you can change the default filter from Edit Test Parameters in the test workflow. The default acceptable variance of 0.50 was selected to encourage testers to focus on significant differences and not waste time on variance amounts that might be rounding differences between Dayforce and the legacy system. You can change this default to the acceptable tolerance for your customer's project. You can also change the value when running individual reports, if you need a higher or lower tolerance to troubleshoot individual payroll codes or taxes.
Yes. You can also upload the review tracking file with extra columns. However, any extra columns won’t be saved to Activate, and won’t persist the next time you generate the report.
Note: If you want to suggest additional columns for all customers or reports, log the suggestion in the Aha! Portal.
All rows are marked as Needs Review by default. Activate never automatically changes the Review Status. You’re responsible for updating the Review Status for each row. If you change it to Correct and upload the values for tracking, any fresh downloads show the values that you last uploaded.
Yes. You can upload any subset of rows for review tracking. Each upload replaces the values for all rows that are included in the upload. If different people are working in different tabs or with different codes, delete those lines from your report to make that you don’t accidentally overwrite each other's work.
Uploading the Review status replaces the values for all rows that are included in the report. If different people are working in different tabs or with different codes, delete those lines from your report to make sure that you don’t accidentally overwrite each other's work. Activate has no way to tell what you intentionally edited or didn’t edit.
Each report can only have one unique line for the Company ID, Employee Identifier, and payroll XRefCode. You can’t upload duplicate lines with the same unique identifiers. Activate must be able to match the uploaded review status to a single line in the report.
Make sure that you didn’t edit the column value on the Comparison report. You might also have updated the earning or deduction XRefCodes in Dayforce since the last time you downloaded the report. Generate a fresh report and upload the Review columns again.
The option to delete the test run is at the bottom of the Edit Test Parameters page.
If you change these parameters, there’s a risk that test data will be out of alignment. You can delete the old test and add a new test for the correct pay group and pay period.
The Net Pay percentage accuracy is only available to users after they:
- Specify the acceptable variance amount in the Test Parameters and
- Upload a legacy data file for Employee Net Pay.
The next time the Compare Employee Totals page is loaded or refreshed, Activate updates the percentage accuracy. This feature allows users to gauge immediately how much progress they have made in Parallel and how many employees are still inaccurate and need to be reviewed.
The Net Pay percentage accuracy is calculated based on the list of employees that were included in the legacy data load for Employee Net Pay. Each employee's legacy net pay is compared to the Dayforce net pay when the user loads or refreshes the Compare Employee Totals page. All employees whose net pay variance is within the maximum acceptable variance (as specified in the Test Parameters) are considered to be “correct.” The test summary shows the percentage of “correct” employees, based on all employees listed in the data load.
No, as of R17. The feature will be enhanced to include garnishment comparison in an upcoming release of Activate.
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.
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 1 | String
Accepted values:
Earning Deduction Tax. |
Indicate whether this data is an earning, deduction, or tax. |
Earning Deduction Tax |
This field is used to identify the corresponding code in Dayforce payroll. |
1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 2 | 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 Dayforce definitions uniquely. It serves to preserve definitions that might have the same name or code but differing functionality between payrolls. |
1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 3 | Numeric length 9–20. |
The Federal/Business ID Number for the legal entity that the employee was paid through. Unites States of America: Federal Employer Identification Number (FEIN). Canada: Business Number (BN) United Kingdom: HMRC/PAYE number. Ireland: Legal Entity Identifier (LEI). Australia: Australian Business Number (ABN). New Zealand: Inland Revenue Number (IRD) or New Zealand Business Number (NZBN). Singapore: Singapore Unique Entity Number (UEN). |
123456789
234/A1237634 |
This data is used to compare and report on totals broken down by Legal Entity in Dayforce payroll. The Company ID must be associated with a Legal Entity in Dayforce and added to the Federal/Business ID Number field. The Legal Entity must be associated with the same country as the Parallel Test’s pay group. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 4 | String1 between 1–64 characters. | The payroll system Earning, Deduction, or Tax Code as defined on the previous payroll provider's system. |
H1
REG
Fed W/H |
This data is used with the Payroll Identifier and Legacy Description to identify individual earning, deduction, and tax definitions in Dayforce. |
1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 5 | String1 between 1–64 characters. | The payroll system Earning, Deduction, or Tax Description as defined on the previous payroll provider's system. |
Employee Health
Regular Federal Withholding |
This data is used with the Payroll Identifier and Legacy Code to identify individual earning, deduction, and tax definitions in Dayforce. |
1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 6 | Numeric. | Total value for the entire payroll period for this legacy code |
2751 37659.5 |
This data is required for the payroll comparison to balance to the Dayforce payroll data. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 7 | Numeric. | The accumulated number of hours associated with this specific earning. |
2751 59.5 |
This data is used by the payroll comparison to verify that Dayforce payroll calculates the same hours for applicable earnings as the legacy system. The earning hours might be required to balance for various HR, Benefit (ACA), and Payroll reporting purposes. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 8 | String
Accepted Values: Y N |
Indicate whether this tax is to be paid by the employer instead of the employee. |
Y |
This data is used to narrow down the possible HCM tax options this tax code could be mapped to. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 9 | Numeric. | Amount of the Taxable Wages for this tax. If the taxable wages exceed the limit for the particular tax, enter the limit value. | 123456.78 | This data is used by the payroll comparison to verify that Dayforce payroll calculates taxes on the same wage basis as the legacy system. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 10 | Numeric. | Total Amount of Taxable Wages for this tax. This amount is above and beyond a Taxable Wage Limit amount. | 123456.78 | This data is used by the payroll comparison to verify that Dayforce payroll calculates taxes on the same wage basis as the legacy system. |
| Data Type | Description | Examples | Why This Is Needed | |
|---|---|---|---|---|
| 8 |
For the USA:
For CAN:
Work Location Accepted Values.2 |
The State/Province code of the location the employee worked in that triggered this tax. Only applicable for Tax code type, and only for Pay Groups in the USA or CAN. |
USA State:
CAN Province:
|
This data is used to narrow down the possible HCM tax options this tax code could be mapped to. |
| Accepted Values | State / Province | Country Name |
|---|---|---|
| AB | Alberta | Canada |
| BC | British Columbia | Canada |
| MB | Manitoba | Canada |
| NB | New Brunswick | Canada |
| NL | Newfoundland and Labrador | Canada |
| NT | Northwest Territories | Canada |
| NS | Nova Scotia | Canada |
| NU | Nunavut | Canada |
| ON | Ontario | Canada |
| PE | Prince Edward Island | Canada |
| QC | Quebec | Canada |
| SK | Saskatchewan | Canada |
| YT | Yukon | Canada |
| AL | Alabama | USA |
| AK | Alaska | USA |
| AS | American Samoa | USA |
| AZ | Arizona | USA |
| AR | Arkansas | USA |
| CA | California | USA |
| CO | Colorado | USA |
| CT | Connecticut | USA |
| DE | Delaware | USA |
| DC | DistrictOfColumbia | USA |
| FM | FederatedStates Of Micronesia | USA |
| FL | Florida | 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 |
| MH | Marshall Islands | USA |
| MD | Maryland | USA |
| MA | Massachusetts | USA |
| MI | Michigan | USA |
| MN | Minnesota | USA |
| MS | Mississippi | USA |
| MO | Missouri | USA |
| MT | Montana | USA |
| NE | Nebraska | USA |
| NV | Nevada | USA |
| NH | New Hampshire | USA |
| NJ | New Jersey | USA |
| NM | New Mexico | USA |
| NY | New York | USA |
| NC | North Carolina | USA |
| ND | North Dakota | USA |
| MP | Northern Mariana Islands | USA |
| OH | Ohio | USA |
| OK | Oklahoma | USA |
| OR | Oregon | USA |
| PW | Palau | USA |
| PA | Pennsylvania | USA |
| PR | Puerto Rico | USA |
| RI | Rhode Island | USA |
| SC | South Carolina | USA |
| SD | South Dakota | USA |
| TN | Tennessee | USA |
| TX | Texas | USA |
| UT | Utah | USA |
| VT | Vermont | USA |
| VA | Virginia | USA |
| WA | Washington | USA |
| WV | West Virginia | USA |
| WI | Wisconsin | USA |
| WY | Wyoming | USA |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 1 | Alphanumeric. Unique value between 1–9 characters |
It enables the system to identify employees uniquely. Use the same number assigned to the employee in the Getting Started HR data loads. Note: Upon upload of the template data, Activate converts any lowercase alpha characters found in the Employee Identifier field to uppercase. |
3241245
000000006 abc123499 |
This required field used to validate that the data being loaded is assigned to the correct employee record. The value provided must match exactly to an existing employee record in Dayforce. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 2 | 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 Dayforce definitions uniquely. It serves to preserve definitions, which might have the same name or code but differing functionality between payrolls. |
1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 3 | Numeric length 9–20. |
The Federal/Business ID Number for the legal entity that the employee was paid through. United States of America: Federal Employer Identification Number (FEIN) Canada: Business Number (BN) United Kingdom: HMRC/PAYE number Ireland: Legal Entity Identifier (LEI) Australia: Australian Business Number (ABN) New Zealand: Inland Revenue Number (IRD) Singapore: Singapore Unique Entity Number (UEN) |
123456789
234/A1237634 |
This data is used to compare and report on totals broken down by Legal Entity in Dayforce payroll. The Company ID must be associated with a Legal Entity in Dayforce and added to the Federal/Business ID Number field. The Legal Entity must be associated with the same country as the Parallel Test's pay group. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 4 | String1 between 1–64 characters | The payroll system Tax Code as defined on the previous payroll provider's system. | FED W/H | This data is used with the Payroll Identifier and Tax Description to identify individual tax definitions in Dayforce. |
1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 5 | String1 between 1–64 characters | The payroll system Tax Description as defined on the previous payroll provider's system. | Federal Withholding | This data is used with the Payroll Identifier and Tax Code to identify individual tax definitions in Dayforce. |
1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &
|
Order |
Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 6 |
For the USA:
For CAN:
Work Location accepted value2. |
The State/Province code of the location the employee worked in that triggered this tax. Only applicable for pay groups in the USA or CAN. |
USA State:
CAN Province:
|
This data is required to relate the tax with the correct location for reporting purposes. It’s possible in the USA and CAN for the employee to have values in multiple states or provinces, so the requirement to identify the code for each line item. |
| Accepted Values | State / Province | Country Name |
|---|---|---|
| AB | Alberta | Canada |
| BC | British Columbia | Canada |
| MB | Manitoba | Canada |
| NB | New Brunswick | Canada |
| NL | Newfoundland and Labrador | Canada |
| NT | Northwest Territories | Canada |
| NS | Nova Scotia | Canada |
| NU | Nunavut | Canada |
| ON | Ontario | Canada |
| PE | Prince Edward Island | Canada |
| QC | Quebec | Canada |
| SK | Saskatchewan | Canada |
| YT | Yukon | Canada |
| AL | Alabama | USA |
| AK | Alaska | USA |
| AS | American Samoa | USA |
| AZ | Arizona | USA |
| AR | Arkansas | USA |
| CA | California | USA |
| CO | Colorado | USA |
| CT | Connecticut | USA |
| DE | Delaware | USA |
| DC | DistrictOfColumbia | USA |
| FM | FederatedStates Of Micronesia | USA |
| FL | Florida | 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 |
| MH | Marshall Islands | USA |
| MD | Maryland | USA |
| MA | Massachusetts | USA |
| MI | Michigan | USA |
| MN | Minnesota | USA |
| MS | Mississippi | USA |
| MO | Missouri | USA |
| MT | Montana | USA |
| NE | Nebraska | USA |
| NV | Nevada | USA |
| NH | New Hampshire | USA |
| NJ | New Jersey | USA |
| NM | New Mexico | USA |
| NY | New York | USA |
| NC | North Carolina | USA |
| ND | North Dakota | USA |
| MP | Northern Mariana Islands | USA |
| OH | Ohio | USA |
| OK | Oklahoma | USA |
| OR | Oregon | USA |
| PW | Palau | USA |
| PA | Pennsylvania | USA |
| PR | Puerto Rico | USA |
| RI | Rhode Island | USA |
| SC | South Carolina | USA |
| SD | South Dakota | USA |
| TN | Tennessee | USA |
| TX | Texas | USA |
| UT | Utah | USA |
| VT | Vermont | USA |
| VA | Virginia | USA |
| WA | Washington | USA |
| WV | West Virginia | USA |
| WI | Wisconsin | USA |
| WY | Wyoming | USA |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 7 | String
Accepted Values: Y N |
Indicate if this tax is to be paid by the employer instead of the employee. | Y
N |
This data is used to narrow down the possible HCM tax options this tax code could be mapped to. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 8 | Numeric | Total value for the employee in the given payroll period for this legacy code | 27.30
659.5 |
The payroll comparison uses this data to balance to the Dayforce payroll data. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 9 | Numeric | The amount of the Taxable Wages for this tax. If the taxable wages exceed the limit for the particular tax, enter the limit value. | 1234.56 | The payroll comparison uses this data to verify that Dayforce payroll calculates taxes on the same wage basis as the legacy system. |
| Order | Data Type | Description | Examples | Why This Is Needed |
|---|---|---|---|---|
| 10 | Numeric | Total Amount of Taxable Wages for this tax. This amount is above and beyond a Taxable Wage Limit amount. | 1234.56 | The payroll comparison uses this data to verify that Dayforce payroll calculates taxes on the same wage basis as the legacy system. |