Skip to main content

Running a Parallel Test

Learn how to run a parallel payroll test before going live, including preparation, how to run the test, dual maintenance, a step-by-step checklist, and how to validate results.

Written by Kate Biel

๐Ÿ“ Overview

A parallel test runs your payroll side-by-side in both your legacy system and DaySmart Payroll to confirm that earnings, deductions, taxes, and benefits are calculating correctly before you go live. Completing this process gives you confidence that your setup is accurate and your first live payroll will run without issues.


๐Ÿ› ๏ธ Before You Begin

Before running your parallel test, confirm the following are in place. Catching setup gaps early will save time during reconciliation.

Data Integrity & Preparation

Click the arrow to learn more

  • Employee master data: Confirm worker records match between systems, including names, IDs, addresses, SSNs, hire dates, pay rates, exemptions, and any other relevant fields.

  • YTD data: Verify that all prior wages, taxes, and benefit balances have been migrated correctly and balance against your prior payroll provider's reports.

  • Tax setup: Check work and resident tax jurisdictions, SUI rates, SUI account numbers, local tax setups, and any voluntary deductions or exemptions.

  • Banking data: Confirm routing and account numbers and pay methods for all workers.

  • Earnings codes & deductions mapping: Confirm that earning and deduction codes from your legacy system map correctly to DaySmart Payroll.

  • Pending worker updates: Apply any worker data changes that occurred in your legacy system to DaySmart Payroll before the test begins.

Defining Your Test Scope

Click the arrow to learn more

Decide what you're testing and how before you start:

  • Pay periods: Will you test one full payroll cycle or multiple? Will both hourly and salaried employees be included?

  • Population coverage: Are you testing your full workforce or a representative sample, such as workers across different tax states, pay frequencies, or multiple work sites?

  • Comparison level: Will you check totals only, or go line-by-line across gross-to-net, tax per jurisdiction, and deductions per employee?

  • Success criteria: Define an acceptable variance threshold upfront, such as $0.01 per employee, so you know what constitutes a pass.

System Configuration to Verify

Click the arrow to learn more

  • Earnings calculations: Hourly, salary, multiple rates, multiple locations, overtime, shift differentials, bonuses, and PTO payouts.

  • Tax calculation: Account for rounding differences between systems and define a tolerance threshold.

  • Benefit deductions: Confirm pre-tax vs. post-tax designations and applicable limits.

  • Third-party deductions: Garnishments, child support, and other court-ordered deductions.

  • Accruals: PTO, vacation, and sick balances, including accrual rates and rules.

  • Manual adjustments: One-off or retroactive payments should be entered the same way they were handled in your prior system.


โš™๏ธ Running the Parallel Test

Follow these steps to run your parallel payroll test in DaySmart Payroll.

Step 1: Complete Onboarding & Review Payroll Setup

Click the arrow to learn more

  1. Confirm that employer onboarding is complete in DaySmart Payroll.

  2. Confirm that all worker onboarding is complete, including personal information, contracts, work location, tax information, payment methods and types, time off, and benefits.

  3. Verify your employer profile for accuracy: pay schedules, deduction codes, benefit plans, and tax tables should all match your legacy system.

Step 2: Gather Payroll Data

Click the arrow to learn more

  1. Collect all payroll inputs needed for the test period:

    • Gross earnings, hourly rates, and hours worked

    • Taxes (federal, state, and local)

    • Benefits and deductions

    • Employer contributions

  2. Collect the most recent live payroll register from your legacy system. You'll use this as your comparison baseline.

Step 3: Run the Parallel Payroll

Click the arrow to learn more

โ›”๏ธ Important Note: Do not advance past Step 2 in the Payroll Processing Cycle. Proceeding further will trigger a live payroll submission and initiate money movement.

  1. Enter all payroll inputs in DaySmart Payroll: hours worked, salaries, overtime, bonuses, and any other applicable earnings.

  2. Proceed to Step 2 in the Payroll Processing Cycle to create a draft payroll. Review the hours and earnings screen.

  3. Select the radio button to download and preview the payroll journal and cash requirements reports. Do not advance beyond Step 2.

  4. Process payroll as normal in your legacy system for the same pay period.

  5. Generate full payroll reports from both systems for comparison.

Step 4: Compare Outputs

Click the arrow to learn more

  1. Build a side-by-side comparison matrix using reports from both systems. Your matrix should include the following at both the company and individual employee level:

    • Gross pay

    • Tax withholdings

    • Deductions

    • Employer contributions

    • Net pay

  2. Reconcile totals at the company level: wages, taxes, deductions, and general ledger.

  3. Highlight any variances for investigation.

๐Ÿง  Tip: Reports to use for comparison: gross-to-net report, tax liability report, payroll journal, and cash requirements report. Pull these from both systems to ensure an apples-to-apples comparison.

Step 5: Analyze & Resolve Variances

Click the arrow to learn more

  1. Reference the variance threshold you defined before the test. Any differences within tolerance can be documented and accepted.

  2. For variances outside your threshold, investigate the root cause. Common sources include:

    • Misaligned deduction or tax codes

    • Incorrect jurisdiction setup

    • Missing benefit elections or garnishments

    • Differences in calculation methods, such as overtime or accrual rules

  3. Document all discrepancies in a test log, including the root cause and the correction made.

Step 6: Adjust & Re-Test

Click the arrow to learn more

  1. Correct any configuration issues in DaySmart Payroll: earnings codes, tax setup, benefit deductions, or other affected settings.

  2. Rerun the parallel payroll test following the same process above.

  3. Confirm that results now align with your legacy payroll within your defined tolerance.

Step 7: Validate & Sign Off

Click the arrow to learn more

  1. Confirm all employee and employer totals reconcile within your accepted threshold.

  2. Document the following for your records:

    • Variances found

    • Corrections made

    • Final sign-off confirming go-live readiness

  3. Retain copies of all test run reports as part of your implementation audit trail.

๐Ÿ”” Once your parallel test is complete and sign-off is confirmed, you're ready to process your first live payroll in DaySmart Payroll.


๐Ÿ”ง Dual Maintenance

Once worker onboarding is complete, there may be a gap between that point and your first live payroll. During this period, your team is responsible for keeping employee data up to date in both your legacy system and DaySmart Payroll. This is called dual maintenance, and it ensures your records are accurate when you go live.

What Needs to Be Maintained in Both Systems

Until your first payroll is processed in DaySmart Payroll, apply all of the following changes in both systems:

Worker Profile Information

Click the arrow to learn more

  • Name or address changes

  • Federal, state, or local tax withholding updates, such as new W-4s or state tax forms

  • Direct deposit or banking changes

  • Employment status changes: hires, terminations, leaves of absence, and rehires

Worker Pay Information

Click the arrow to learn more

  • Pay rate changes, including hourly and salary adjustments, merit increases, bonuses, and overtime rates

  • Job titles, departments, cost centers, or work location changes

  • One-time payments or adjustments needed for the first payroll

Deductions & Benefits

Click the arrow to learn more

  • Benefit enrollment or plan changes, especially if open enrollment occurs during your migration period

  • Per-pay-period deduction updates, such as medical, dental, FSA, or HSA changes

  • 401(k) or other retirement contribution changes

  • Child support orders, garnishments, or loan repayments that are added or modified

โš ๏ธ Reminder: If open enrollment or mid-year benefit changes occur during your migration, confirm whether current benefit plans will carry over or new plans are being introduced, and make sure deduction amounts match benefit elections in both systems.

โ›”๏ธ Failing to maintain both systems during this period can result in payroll errors, incorrect tax filings, and delayed direct deposits on your first live payroll run.


๐Ÿ“‹ Parallel Test Checklist

Use this checklist to track your progress and confirm all steps are complete before going live.

Preparation

Click the arrow to learn more

  • Collect the most recent live payroll register from your current provider

  • Confirm employee master data in DaySmart Payroll

  • Verify year-to-date (YTD) balances are loaded into DaySmart Payroll

  • Confirm pay schedules: frequency, period dates, and pay dates

Data Input & Setup

Click the arrow to learn more

  • Enter or import current payroll data: hours, salary, commissions, PTO, and bonuses

  • Validate recurring deductions: benefits, retirement, and garnishments

  • Confirm employer tax rates and settings: FUTA, SUTA, and local taxes

  • Add one-time adjustments: retroactive pay, manual checks, etc.

Run Payroll in Both Systems

Click the arrow to learn more

  • Process payroll in your legacy system

  • Create a draft payroll in DaySmart Payroll (do not submit)

  • Generate full payroll reports from both systems

Comparison & Reconciliation

Click the arrow to learn more

  • Compare gross pay at the company and employee level

  • Compare tax withholdings at the company and employee level

  • Compare deductions at the company and employee level

  • Compare employer contributions at the company and employee level

  • Compare net pay at the company and employee level

  • Reconcile totals at the company level: wages, taxes, deductions, and GL

Issue Resolution

Click the arrow to learn more

  • Document all discrepancies in a test log

  • Investigate root causes of mismatches

  • Correct setup errors in DaySmart Payroll

  • Re-run the test payroll if fixes were made

Final Review & Sign-Off

Click the arrow to learn more

  • Validate that all employee and employer totals reconcile

  • Ensure all differences are documented

  • Obtain payroll or finance team sign-off

  • Confirm readiness for go-live payroll cycle


โ“ Frequently Asked Questions (FAQs)

Find answers to common questions or additional details that may not be covered in the main instructions.

Click the arrow to view frequently asked questions

Do I have to run a parallel test before going live?

Click the arrow to see the answer

A parallel test is not required, but it is strongly recommended. It gives you an opportunity to catch configuration errors, verify that calculations match your legacy system, and build confidence in your setup before any real money moves. Skipping it increases the risk of payroll errors on your first live run.

How many pay periods should I test?

Click the arrow to see the answer

At minimum, test one full payroll cycle. If your workforce includes a mix of hourly and salaried employees, multiple pay frequencies, or workers in multiple tax jurisdictions, consider running the test across more than one period to capture the full range of scenarios.

What if results don't match exactly?

Click the arrow to see the answer

Small differences are common, often due to rounding rules that vary between payroll systems. That's why defining a variance threshold before you start matters. If variances fall within your threshold, document them and move on. If they exceed it, investigate the root cause, correct the configuration, and re-run the test.

Can I run a parallel test without completing full worker onboarding?

Click the arrow to see the answer

No. Worker onboarding must be complete before the parallel test. All worker profiles, tax information, payment methods, deductions, and benefits need to be in DaySmart Payroll for the test results to be meaningful. Testing with incomplete data will produce results that don't reflect your actual payroll.

What is dual maintenance and how long does it last?

Click the arrow to see the answer

Dual maintenance is the period between completing worker onboarding and processing your first live payroll in DaySmart Payroll. During this time, any changes to worker data must be entered in both your legacy system and DaySmart Payroll to keep records aligned. It ends once your first live payroll is processed.

What records should I keep from the parallel test?

Click the arrow to see the answer

Retain copies of the test run reports from both systems, your comparison matrix, the discrepancy log, and the final sign-off documentation. These serve as your implementation audit trail and may be useful if questions arise after going live.

Did this answer your question?