Implementing payroll software with reconciled migration, parallel runs and a rehearsed cutover

Implementation succeeds when the first live payroll is correct, authorised, reported and recoverable. Installing software or importing employees is only the beginning. Payroll software implementation in England turns on three checkpoints: reconciled migration, parallel runs and a rehearsed cutover. Use a named owner, documented scope and controlled cutover.

What to take away

Confirm scope and authority

Record the employer entities, PAYE schemes, employees, pay calendars, worker situations, deductions, pension arrangements and integrations moving to the system. Identify who approves data, payroll, the Full Payment Submission (FPS), the Employer Payment Summary (EPS) and payments.

HMRC's running payroll overview provides the standard sequence around payday and the following tax month. An FPS is due on or before each payday, and an EPS by the 19th of the following tax month. Map each step to the new system and a responsible person.

Prepare and protect data

Inventory source records, remove obsolete duplicates, validate mandatory fields and agree opening balances. Agree control totals before any transfer: headcount, gross taxable pay to date, tax to date, National Insurance to date, student and postgraduate loan balances, and pension contributions to date. Transfer through an approved secure route. Limit implementation access and retain an audit trail of imports and corrections.

Document personal-data roles, retention and deletion for temporary migration copies. Use synthetic records during early configuration and training. The Data Protection Act 2018 and the UK GDPR govern the lawful basis, retention and subject rights that apply to those copies. The Information Commissioner's Office publishes employment practices guidance for employers; use it to set retention and access rules for migration copies.

Reconcile migrated payroll data

Reconcile employee by employee, not in totals alone. For each person, compare name, date of birth, National Insurance number, tax code and code basis, National Insurance category letter, student loan plan, pay frequency, annual salary or hourly rate, pension scheme and contribution basis, and year-to-date figures taken from the last FPS, P45 or P60 in the old system.

Migration closes only when the same control totals agree in the new system before the first live run: record counts, gross to date, tax to date, National Insurance to date, loan balances and pension totals, each signed off by the person who owns that figure.

Correct differences at source and re-extract. Adjusting the new system with manual overrides or a balancing journal hides the error and destroys the audit trail you will need if HMRC queries a later FPS or EPS.

Configure the tax-year context

Confirm product edition, tax year, PAYE references, pay schedules, statutory settings and applicable reporting. Check the exact product on HMRC's recognised software directory. Whether the employer runs Sage 50 Payroll, Xero Payroll, BrightPay, QuickBooks Online Payroll or another accepted package, the directory entry confirms the product and edition accepted for RTI submissions.

HMRC warns in its software guidance that mishandled payroll IDs during a change can duplicate records or affect the PAYE bill. Decide whether identifiers continue and handle any change indicator correctly for the circumstances.

Test workplace pensions

Configure the named scheme, contribution basis, tax-relief method, assessment and worker events. The Pensions Regulator's payroll process guidance recommends ensuring the software or outsourced process works with automatic enrolment.

The declaration of compliance is due to the Pensions Regulator within five months of the duties start date, and a re-declaration is due every three years. Those duties come from the Pensions Act 2008, which requires every UK employer to automatically enrol eligible workers into a workplace pension scheme and contribute to it.

Generate safe test files, confirm provider acceptance and reconcile contributions. Assign failed-file investigation and employee communication.

Run parallel payrolls

Process representative ordinary, starter, leaver, variable-pay and correction cases in the old and new systems. Reconcile gross pay, deductions, employer liabilities, net pay, pension contributions and reports. Investigate every difference rather than applying a blanket tolerance. Follow the vendor's own parallel-run guidance for the product, and ask how it opens a mid-year employee record, carries forward year-to-date figures and handles a duplicate payroll ID.

Run parallel payrolls for at least two full pay cycles, and three where pay is weekly or variable.

Reconcile at employee level, not only in totals. Illustrative figures, not current rates. An employee on £30,000 a year paid monthly has gross pay of £2,500.00 in both systems, with the same tax code and NI category letter, so income tax and employee NI match. The difference is the pension basis.

The old system applies 5 per cent employee contributions (£125.00) and 3 per cent employer contributions (£75.00). The new system uses a £1,500 qualifying-earnings band and reports £75.00 and £45.00. Net pay differs by £50.00 a month and employer NI differs on £30.00 of contributions.

That is £600.00 a year for one employee, and £54,000.00 across 90 employees on the same mistake. A 1 per cent tolerance would pass it. Check current PAYE and NI rates on GOV.UK's rates and thresholds for employers page.

Keep the old process authoritative until the agreed acceptance criteria are met. Prevent the test system from sending live reports or payments without explicit authority.

Rehearse cutover and failure

Prepare a dated cutover checklist, final data extract, approvals, support contacts and rollback decision. Test user access, FPS and EPS acknowledgements, payslips, journals, pension exchange, backups and restoration.

Agree what triggers a rollback, not only that a path exists. A workable rule is any unreconciled variance above the threshold the employer sets, for example £500 in total for one pay run, or any employee whose net pay cannot be corrected before payday. Name who can call it and how the old system restarts.

During the first live cycles, increase review and record interventions. Confirm that HMRC has accepted the FPS and EPS and that pension contributions are declared, not only that files were transmitted. Keep employees informed through the employer's approved route.

Prepare people and communications

Train each role on its own tasks, permissions, evidence and escalation. Operators need realistic cases; approvers need reports and control points; administrators need access, backup and incident procedures. Confirm who answers employee questions without exposing records to unauthorised staff.

Tell affected employees about a changed payslip or self-service route through an approved employer communication. Provide accessible instructions and a way to report difficulty. Do not use the implementation notice as consent for unrelated marketing.

Stabilise after launch

For the first agreed runs, compare expected and actual headcount, gross-to-net totals, employer liabilities, pension amounts, reports and payments. Review failed logins, support requests and manual work. Preserve the evidence and name any accepted difference.

Hold the stabilisation window for two full pay cycles or the first quarter, whichever is longer.

Restrict configuration change during the stabilisation window. Urgent fixes need review, testing, approval and a rollback path. Once results are stable, transfer open issues into normal ownership and confirm that implementation-only accounts and data copies have been removed. Measure whether the promised outcome was achieved before releasing the project team.

Close implementation only after reconciliations, exceptions, access review, temporary-data disposal, documentation and handover are complete. Schedule a post-run review and tax-year readiness check. A fast go-live is not a success if unresolved differences are carried into the next payday.

Before you act

Common questions

What should be included in the scope and authority record?

Record the employer entities, PAYE schemes, employees, pay calendars, worker situations, deductions, pension arrangements and integrations moving to the system. Identify who approves data, payroll, the FPS, the EPS and payments. This ensures clear accountability and a documented scope for the implementation.

How should data be prepared and protected during migration?

Inventory source records, remove obsolete duplicates, validate mandatory fields and agree opening balances. Transfer through an approved secure route. Limit implementation access and retain an audit trail of imports and corrections. Document personal-data roles, retention and deletion for temporary migration copies. Use synthetic records during early configuration and training.

What is involved in running parallel payrolls?

Process representative ordinary, starter, leaver, variable-pay and correction cases in the old and new systems. Reconcile gross pay, deductions, employer liabilities, net pay, pension contributions and reports. Investigate every difference at employee level and hold the parallel run open until the reconciliations are clean.