The new payroll run is compared with the current process before finalisation, while rollback remains available.
Payroll implementation control
Validate one payroll month line by line before production go-live.
Use a controlled parallel run to compare employee inputs, statutory treatment, net pay and output files before the new system becomes the source of production payroll.
Representative operating scenario Current boundaries stated clearly
Payroll control roomIllustrative interaction
1Initiate2Compute3Review4Approve5Finalise
Readiness check
Owner and history remain visible482Employees
31Inputs pending
DraftRun status
Calculation in progress
Owner and history remain visible468Computed
14Exceptions
6m 18sIllustrative run
Variance and output review
Run remains reversible before finalisation94%Ready
11Variance flags
AvailableRollback
Authorised review
Owner and history remain visible471Approved
11Held
2Approvers
Payslips and outputs
Owner and history remain visible471Payslips
5Bank files
4Statutory outputs
Who this page is for
For HR, payroll, finance and implementation teams planning an HRMS migration.
The operating problem
What usually breaks before the software conversation begins.
Use these symptoms to determine whether the issue is data, policy, ownership, monthly closure or an unsupported product requirement.
01
The first production run becomes the first complete test.
02
Source data and policy gaps are discovered too late.
03
Teams compare only total payroll instead of employee-level variance.
04
Filing and bank outputs are not validated before go-live.
A practical operating approach
Resolve the policy first, then automate the cycle.
The exact product setup is validated during discovery and demonstration. The sequence below keeps the rule, owner and downstream result connected.
Freeze the comparison population
Confirm employees, salary structures, attendance, leave, reimbursements and cut-off inputs.
Run the same month in both systems
Compute the new run while keeping it reversible and separate from production payout.
Compare line by line
Review gross, deductions, statutory values, net pay and material variance for every employee.
Open the actual outputs
Validate supported registers, filing files, bank files and payslips before sign-off.
Connected product scope
View the full product The outcome depends on more than one isolated feature.
Review the upstream source, policy resolver, approval path and downstream output together.
Payroll
Connect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
ExploreTime & Attendance
Apply configurable rules to punches, shifts and work patterns, explain why each day resolved as it did, and close exceptions before they become payroll corrections.
ExploreCompliance & Audit Logs
Use role and data scopes, operational audit, security events, sensitive-data access records, effective dates and controlled exports to make important actions easier to reconstruct.
ExploreImplementation
Guided setup, validated data and parallel payroll.
Explore
Evaluation questions
Bring this use case into a demo Confirm the exact policy, evidence and product boundary.
The answers below reflect the supplied product source. Customer-specific commitments still require live-product and commercial validation.
Does duoHR support rollback before finalisation?
The product material describes rollback as available before finalisation.
How many parallel months are required?
The documented recommendation is one payroll month, but the implementation scope should reflect customer complexity and risk.
Is this a universal go-live guarantee?
No. Readiness depends on data quality, policy complexity, integrations, validation and customer decision speed.
Payroll implementation control
Validate this use case with one real policy or transaction.
Bring a representative employee, location, shift, payroll month or output. We will shape the walkthrough around the exact operating case.