To run a Workday Payroll parallel test or release regression audit in a Sandbox or Implementation tenant, execute Run Retro Pay Calculation followed by Run Pay Calculation (On-Cycle Payroll) for your target pay run groups, and then run Run Payroll Audit alongside Workday's delivered period-comparison and retro verification reports. This sequence lets you compare gross-to-net totals, individual earning and deduction calculation lines, and retroactive pay adjustments against either a prior completed period or your baseline production run before committing Run Retro Pay Complete and Run Pay Complete.
When to run a Sandbox payroll parallel and retro audit
A disciplined Sandbox payroll regression is essential in four scenarios:
- Workday semi-annual releases and compliance updates: Validating statutory tax table updates, FLSA/overtime calculation changes, or new pay component behaviors in Sandbox Preview before the production update window.
- Earning, deduction, or related calculation edits: Modifying eligibility rules, calculation formulas, lookup tables, or selecting/clearing Recalculate during Retro on an earning or deduction.
- Inbound integration or EIB changes: Testing bulk time-clock imports, Import Payroll Input EIBs, or benefit deduction feeds to confirm they trigger recalculation and produce expected net pay.
- Initial deployment parallel testing: Comparing Workday Payroll results in an Implementation tenant against a legacy payroll system across two or more full pay cycles.
End-to-end execution sequence in Sandbox
Workday requires retro calculations to finish before regular on-cycle payroll calculations pick up prior-period adjustments. Always execute your Sandbox parallel run in this order:
| Step | Task Name | Required Security Domain (Core Payroll) | What It Does |
|---|---|---|---|
| Step1. Pre-check retro volume | Task NameRun Retro Pay Calculation Preprocessor | Required Security Domain (Core Payroll)Process: Run Batch Calculations (Retro Calculation) | What It DoesCounts workers requiring retro in the pay group and flags high-volume workers that could slow down batch runs. |
| Step2. Calculate retro differences | Task NameRun Retro Pay Calculation | Required Security Domain (Core Payroll)Process: Run Batch Calculations (Retro Calculation) | What It DoesRecalculates prior completed periods on or after each worker's NRPPT date and marks open pay results as Waiting to pick up Retro Difference. |
| Step3. Audit retro output | Task NameRetro Calculation Processing Report & Retro Results Report | Required Security Domain (Core Payroll)Reports: Pay Calculation Results for Pay Group (Results) | What It DoesSurfaces supported, unsupported, and unprocessed retro differences before they merge into regular pay. |
| Step4. Calculate on-cycle pay | Task NameRun Pay Calculation | Required Security Domain (Core Payroll)Process: Run Batch Calculations (Pay Calculation) | What It DoesPulls forwarded retro differences into the current open period and calculates gross-to-net, taxes, and deductions. |
| Step5. Run automated variance rules | Task NameRun Payroll Audit | Required Security Domain (Core Payroll)Reports: Pay Calculation Results for Pay Group (Audits) | What It DoesEvaluates configured audit rules (such as Net/Gross > 10% variance from prior period) and generates manageable exceptions. |
| Step6. Compare line-level registers | Task NamePayroll Register / Payroll Calculation Lines Processing Report | Required Security Domain (Core Payroll)Reports: Pay Calculation Results for Pay Group (Results) | What It DoesExports pay component totals and related calculation lines for side-by-side reconciliation against baseline runs. |
Auditing Retro Pay Calculations and NRPPT dates
When you run Run Retro Pay Calculation, how you select the Employees to Calculate option determines whether Workday tests only recent staffing/input events or re-evaluates your new configuration changes across the pay group:
- Smart Retro: Processes only workers who have had a supported or unsupported retro event since
the last retro run, or whose result status is
Requires Re-calculation. - Smart Retro by Events: Filters the retro calculation to specific event types (listed on the Payroll Retro Event Categories tab of the View Payroll Event Categories report).
- Calculation Statuses or Workers: Select Calculation Statuses or specific Workers when you are testing a configuration change (such as editing a calculation or deduction formula in Sandbox) on workers who have not had a new staffing or payroll input event since the last retro run.
Why expected retro differences fail to calculate
Workday creates retro results for workers with retro events, but only generates monetary differences when two conditions are met:
- Supported vs. Unsupported events: The triggering transaction must be a supported retro event.
Check the Retro Calculation Processing Report facets to filter workers with
UnsupportedorUnprocessedretro. - No Retro Processing Prior To (NRPPT) date boundary: Workday ignores any retroactive change
whose effective date falls before the worker's NRPPT date. For example, if a worker's NRPPT
date is
2026-02-01and you enter a retroactive salary increase of200per month effective2026-01-01, Run Retro Pay Calculation recalculates February (+200) but leaves January (200) unprocessed.- Run Payroll Changes Unprocessed for a Retro Run or Payroll Retro Unprocessed Differences to catch amounts blocked by an NRPPT date or unsupported event that require a manual payroll input adjustment.
- Note that when a worker has an unsupported retro event, Workday automatically advances their NRPPT date to one day after the last period with completed on-cycle or off-cycle results.
Tax rate behavior in Retro (U.S., Canada, France): For Payroll for the U.S., Canada, and France, Workday does not recalculate taxes using the prior period's tax rate. Instead, it applies the tax rate effective in the target period where the retro differences are paid (and taxes retro bonus earnings at the regular run rate rather than a standalone supplemental rate).
Configuring and running Gross-to-Net Variance Audits
Rather than manually eye-balling thousands of payslips in Sandbox, configure automated variance rules via Maintain Payroll Audit Configurations (secured by Set Up: Payroll (Reporting)) and run them with Run Payroll Audit:
Example: Catching >10% Gross or Net variance across periods
- Open Maintain Payroll Audit Configurations, select the Prior Period Comparison tab, and click Create.
- Set the Reporting Level to
Worker. - Optional: In the Worker(s) to include grid, attach a Worker Eligibility Rule (created via Create Payroll Audit Worker Eligibility) to scope the audit by Region or exclude pay groups with naturally volatile pay (such as quarterly bonus executive pay groups).
- In the Pay result(s) to include grid, add rows for
Net(greater than,Percentage: 10) andGross(greater than,Percentage: 10) withWarningorCriticalseverity. - After running Run Pay Calculation, execute Run Payroll Audit for the pay period and click Launch Audit Report (or open Payroll Audit Exceptions and Payroll Audit Exception Summary on the Pay Cycle Command Center dashboard).
Delivered period-comparison and register reports
Use these standard reports to reconcile your Sandbox run against a prior period or a production baseline export:
- Audit - Pay Calculation Results Comparison to a Prior Period (By Pay Group / By Worker / Period Summary): Compares current calculation results directly against a prior completed period. (Note: Workday suppresses the audit alert flag on these comparison reports if an audit rule uses worker eligibility rules or is inactive.)
- Pay Calculation Results for Group of Workers: Filters results by calculation moment so you can isolate only the workers whose pay results changed after your latest Sandbox configuration edit.
- Payroll Totals by Category and Payroll Register Summary / Earning Register / Deduction Register: Aggregates earnings, deductions, and employer taxes at the company or pay group level to reconcile penny-for-penny against production.
- Payroll Calculation Lines Processing Report: Exposes individual payroll result lines and their underlying Related Calculations (such as hours, rate, and basis) when a worker's gross or deduction amount differs from baseline.
Resetting or Suspending Retro Results during Sandbox testing
While iterating on a calculation fix in Sandbox, you often need to hold or roll back a retro run before completing payroll:
- Canceling retro for a subset of workers: On the Retro Calculation Processing Report,
select specific workers and click Cancel (requires no on-cycle payroll process running).
Workday restores those workers' NRPPT dates to their pre-run values so you can adjust
configuration and rerun Run Retro Pay Calculation. To reset the retro calculation status all
the way back to
Not Yet Started, run Run Retro Pay Cancel. - Suspending retro results: If you click Suspend on an in-progress retro result (with status
Supported Retro to process) and also move the worker's NRPPT date earlier, retro and regular pay calculations can produce mismatched balances in the next run unless you offset the suspended amount with a memo earning or memo deduction (configured via Create Earning or Create Deduction to update balances/limits without affecting gross pay) and rerun both Run Retro Pay Calculation and Run Pay Calculation. - Ineligible Cancel Pay Complete on off-cycle runs: If you test Cancel Pay Complete via the
Payroll Calculation Processing Report, remember that Workday only allows canceling the most
recent completed result for a worker (
Not Last Completederror occurs if you try to cancel an off-cycle payment after a later on-cycle payroll has already been completed).
How kiweely fits
Running a payroll parallel or release audit in Sandbox requires coordinating retro preprocessors, NRPPT date checks, calculation line exports, and variance reconciliations across thousands of workers. kiweely connects to your Sandbox tenant to inspect earning and deduction calculation definitions, query retro and on-cycle calculation lines, and pinpoint the exact pay component or eligibility rule causing a gross-to-net variance between runs. Kiweely Personal is free for your Workday personal developer account and its tenant. Any other tenant needs a Personal licence, $99 a month, or a seat in your firm.
Frequently asked questions
Why didn't Run Retro Pay Calculation pick up my Sandbox earning or deduction formula change?
If you ran Run Retro Pay Calculation using the Smart Retro option, Workday only recalculates
workers who have a new retro event or a Requires Re-calculation status since the last run. To
force Workday to test a configuration change on workers without a new staffing/input event, run
Run Retro Pay Calculation using the Calculation Statuses or Workers selection option
instead.
Why is a retroactive salary change showing on Payroll Changes Unprocessed for a Retro Run?
Check the worker's No Retro Processing Prior To (NRPPT) date on the Retro Pay Calculation Results for Group of Workers report. If the effective date of the compensation change is earlier than the worker's NRPPT date—or if the change was triggered by an unsupported retro event—Workday does not automatically calculate the retro difference for periods prior to the NRPPT date, and you must enter a manual payroll input for that prior difference.
Why did my Payroll Audit Exception status not change to Resolved after I fixed the worker's pay result?
Fixing the payroll input and running Run Pay Calculation recalculates the worker's pay result,
but does not automatically refresh the audit exception table. You must rerun the Run Payroll
Audit task for that same pay period before Workday updates the exception status to Resolved.
How do I isolate only the workers whose pay changed after a Sandbox fix?
Run the Pay Calculation Results for Group of Workers report and filter by the Calculation Moment timestamp, or check the Recalculated filter to view only workers whose results were updated in your most recent calculation pass.