Payroll implementation
A practical parallel payroll checklist when changing HRIS
By ElevenOS ··6 min read
A parallel payroll run compares your existing payroll results with calculations in a new system for the same employees and cutoff. It gives the payroll owner a practical way to investigate differences before changing the live process. Matching the grand total is only the starting point: two employee errors can cancel each other out. A useful comparison explains individual differences, checks the underlying inputs and records who accepted the result.
Published by ElevenOS. Product scope and quotes can change; confirm your requirements with each provider.
In this guide
1. Define what a successful comparison means
Choose a representative cutoff and name the payroll owner who will sign off. Include ordinary salaries and the variations your team actually processes, such as a new hire, an allowance, approved overtime or an unpaid day. If the chosen cutoff does not cover an important case, add a controlled example or plan another comparison for that scenario.
Agree on acceptance criteria before looking at results. These might require a complete employee match, no unexplained net-pay differences and documented review of contribution and tax calculations. Any rounding tolerance needs a clear basis and an approving owner. A tolerance should not hide a recurring configuration error or replace a check of individual employees.
2. Give both processes the same inputs
Record the cutoff start and end, payday, employee list and currency. Check hire and separation dates, pay frequency, salary effective dates, approved time and leave, recurring earnings, deductions and loan balances. For a migration during the year, agree which opening and year-to-date balances must be carried forward and have the responsible payroll reviewer verify them.
Keep a dated copy of the source register and a short input log. If an attendance correction arrives after the first calculation, mark the input set as changed and update both sides before comparing again. Comparing yesterday’s spreadsheet with today’s attendance figures produces a difference, but it does not isolate a problem in the new payroll calculation.
3. Match employees before matching amounts
Use a stable employee number as the matching key. Names can be spelled differently, shared by multiple people or changed after marriage. Check for duplicate identifiers and employees appearing on only one side. A person missing from the comparison is an investigation item, even when the totals happen to look reasonable.
ElevenOS provides a payroll comparison template for PHP batches. Employee number, currency, basic pay, gross pay, total deductions and net pay are required; withholding tax and employer contributions can also be supplied. Use the template’s columns and plain numeric amounts. The import checks duplicate employee numbers and whether gross pay minus total deductions equals net pay.
Optional amounts left blank are not verified matches. If employer contributions matter to the acceptance decision, include them and review them explicitly. Check the imported preview before saving a comparison so a formatting or population problem is caught before the team starts investigating calculation differences.
4. Explain differences one employee at a time
Start with missing employees, then work through differences in basic pay, gross pay, deductions and net pay. For example, a fictional employee might show the same basic salary but different gross pay because an allowance was omitted. Another might have identical gross pay but different net pay because a loan repayment appears in only one process.
Separate input differences from policy configuration, effective-date issues, calculation defects and intentional changes. Check the source record before deciding which system is correct. The old register is a useful baseline, but a historical mistake can exist there too. For statutory treatment or disputed company policy, have the qualified payroll reviewer check the applicable requirements and record the basis for the decision.
Keep an issue log with the employee, affected item, difference, cause, owner and resolution. ElevenOS comparison exports include employee and metric differences, calculation version and available review information. Use that record to explain what was checked instead of relying on a screenshot of the final total.
5. Recalculate and preserve the reviewed version
Fix the underlying input or configuration through its normal workflow, then recalculate and create a fresh comparison. Recheck affected employees and the wider batch: changing a shared salary basis or deduction rule may affect more people than the original example. Confirm that resolved issues stay resolved and that no new employee disappears from the comparison.
Save the source file label, cutoff, calculation version, reviewer and decision with the results. An approval belongs to the version that was reviewed. If someone changes attendance, compensation or a pay rule afterward, assess the change and review the new result before treating the earlier sign-off as applicable.
6. Check payslips and payment steps separately
A reconciled calculation still needs a usable output. Inspect sample payslips for the correct employee, period, earnings and deductions. Verify who can view them and how publication is controlled. Check that payroll exports contain the agreed fields and that only authorized people can obtain sensitive payroll data.
Bank processing, agency submission and contribution payment require their own acceptance checks. A payroll register CSV is not automatically a bank-accepted payment file. ElevenOS supports payroll preparation and digital payslips from Growth; required bank formats and reporting workflows should be confirmed for your proposed setup. Payroll calculations do not themselves establish filing or payment completion.
7. Turn the evidence into a go-live decision
Close the exercise with a concise decision: which cases passed, which differences were accepted and why, which items remain open, and who is responsible for them. Agree how the first live cutoff will be supported and what process the team will use if a blocking issue appears. The number of parallel runs should follow the unresolved risks and scenarios, not an arbitrary promise that one is always enough.
For an ElevenOS evaluation, bring a protected sample register, your cutoff pattern and the pay rules you need to check. Agree how sensitive information will be shared before supplying real records. A walkthrough can establish the comparison process; the customer’s own payroll reconciliation and approval establish whether that setup is ready for use.
Frequently asked questions
Is matching the total net pay enough?
No. Individual differences can offset each other. Compare employee coverage and each relevant pay component, then investigate unexplained differences before approval.
How many parallel payroll runs should we complete?
Agree this with your payroll owner based on the scenarios covered and unresolved issues. Repeat affected cases after changes, and add another cutoff when an important variation has not been tested.
Does a successful comparison verify bank payments or government filing?
No. It verifies the compared calculation results within the reviewed scope. Bank output acceptance, submission, payment and receipt checks are separate steps.
