top of page

Changing payroll systems: what to check before the first live pay run

Writer: Karen Lewis
Karen Lewis
Oct 27
2 min read

Updated: Oct 29

A successful software demonstration does not tell an employer whether its first live payroll will be correct. The important questions sit in the handover: what has moved, what has been checked and who has authority to approve the result?


We recommend making those questions part of the implementation plan from the outset. A system change needs enough time for people to explain differences, rather than simply importing a file and hoping the figures match.


Define the change precisely


Start by recording what the project includes. Is it a change of software, a change of payroll provider, a new HR system feeding payroll, or several changes together?


This article concerns switching payroll software under an existing PAYE scheme. A TUPE transfer or change of employer may require different arrangements. We recommend assessing those separately before applying a standard migration checklist. A commercial changeover date does not settle the employment or payroll treatment.


Agree one checked starting position


Identify the final completed run in the existing system and the first intended run in the replacement. We suggest retaining a clear record of the figures approved at that boundary, including relevant year-to-date balances.


Assign responsibility for reconciling the data. Ask the receiving team to identify missing fields and uncertainties before import. An unexplained difference should have an owner and a decision date, rather than becoming a note that everyone assumes someone else will resolve.


Pay attention to payroll IDs


HMRC's guidance says that when reporting a payroll ID change, the change indicator should be set and both the old and new IDs entered. It also specifies that year-to-date financial data should continue from the previous submission. Re-employment has different reporting rules.


We recommend agreeing an ID mapping with the payroll team and software provider. Confirm how the replacement system handles it, including people with more than one employment. Do not assume that a staff number displayed on a screen is necessarily the same field used in the HMRC submission.


Make the test run useful


Compare calculations using an agreed set of inputs and record the differences. We suggest including cases that reflect the actual workforce, such as variable payments, salary changes, statutory pay and deductions.


The purpose is to understand the result. If two systems produce different net pay, establish why before approving the live run. Keep test activity separate from live payments and reporting so a rehearsal cannot accidentally become a second submission or payment instruction.


Set responsibility for reporting and approval


HMRC normally requires the Full Payment Submission on or before payday, subject to specified exceptions. Decide who will submit it and which system will do so. Include cover for absence and a clear escalation route for a failed submission.


We recommend a documented decision before going live: unresolved issues, approval authority and the contingency if the new process is not ready. Tell managers where to send late changes and employees where to raise pay queries.


At The HFactor HR Consultancy, we bring 85 years of combined HR experience to HR and payroll implementation, HR audits and organisational change. For a initial meeting about your next system project, contact us through www.the-hfactor.com.


Sources checked 27 October 2026


HMRC — Payroll information to report to HMRC, including payroll ID changes and year-to-date figures:



GOV.UK — Running payroll: reporting to HMRC:



 
 
 

Comments


bottom of page