Established MMXXVRemote-first · Serving clients worldwideConversions both directions
care@ezconvertbooks.com

October 14, 2026

Switching UK payroll software mid-year vs at 6 April: RTI, payroll IDs and year-to-date figures

The short answer: if you can wait, switch UK payroll software at the start of a tax year (6 April); if you cannot, a mid-year switch is safe only when every employee’s year-to-date figures and payroll ID carry across exactly. HMRC does not see “new software”. It sees Full Payment Submissions (FPS) under your PAYE reference, and it matches each one to an existing employment. Break that match and HMRC creates a second employment record for the same person. The same rules apply whether payroll sits inside Xero, QuickBooks, Sage or a standalone product.

Mid-year vs 6 April at a glance

Switch mid-yearSwitch at 6 April
Year-to-date figuresMust be entered per employee: gross pay, tax, National Insurance, student loan, pensionStart from zero in the new tax year
Final FPS of the old yearSent later, from the new softwareSent from the old software, flagged as the final submission for the year
P60sCome from the new software, so it needs the full-year totalsCome from the old software for the year just ended
Main riskWrong YTD or a changed payroll ID creates duplicate employmentsPayroll IDs that change at cutover
Data entryEvery employee, every YTD fieldEmployee details only

Why mid-year switches go wrong

PAYE is cumulative: a wrong opening figure changes every payslip that follows. HMRC also checks that each FPS follows on from the one before. Its guidance on what payroll information to report says the year-to-date figures must carry on from the previous submission.

HMRC’s April 2026 Employer Bulletin lists the errors it still sees, and most of them happen when payroll changes systems:

  • A payroll ID changes without the payroll ID changed indicator. HMRC treats the new ID as a new job, which leads to incorrect year-to-date information and manual corrections.
  • A start date or starter declaration is sent for someone who already works for you. That also creates a second employment record. Start dates are for genuine new employees only. For continuing employees, leave the field blank.
  • Taxable pay for the period is sent as nil while the year-to-date figure is filled in. This can merge or corrupt employment records.
  • A payroll ID is reused for a different person. That data then lands on the wrong employee’s record.

Avoid the “leaver in the old system, starter in the new one” workaround. The employment has not ended, and HMRC says a start date sent for a continuing employee is exactly what creates the duplicate.

Option 1: switch mid-year and carry the year-to-date figures

  1. Pick a cutover after a completed pay run. Run the last period in the old software, send its FPS, and make sure HMRC accepted it.
  2. Export a year-to-date report for each employee. Cover gross and taxable pay, PAYE tax, employee and employer NI (with category letter), student loan, pension and statutory payments.
  3. Keep the same payroll IDs if the new software allows it. If it cannot, the first FPS from the new system must set the payroll ID changed indicator and send both the old and new IDs. HMRC says to leave out the original start date when you do this.
  4. Enter opening balances before the first pay run. In QuickBooks Online Advanced Payroll, for example, Intuit’s UK help covers year-to-date opening balances for earnings, deductions, pension and PAYE, and National Insurance. The NI section asks for the NI-able gross, employee and employer NI to date, and the earnings bands (LEL, LEL to PT, PT to UEL). Intuit notes that these balances apply to the current tax year only.
  5. Run a parallel check. Calculate the first period in both systems before you submit.

Option 2: switch at 6 April

The tax year runs from 6 April to 5 April. If you cut over on that boundary, the old software sends the final FPS of the year, with the “final submission for year” field set to Yes. It also produces the P60s, which you must give by 31 May to every employee working for you on 5 April. The new software then starts with zero year-to-date figures. You still need to keep payroll IDs consistent or use the change indicator, but nobody has to re-key months of cumulative totals.

For most small employers, a planned 6 April payroll cutover alongside a mid-year ledger migration works well. Post payroll journals into the new ledger until April.

Benefits in kind make April 2027 a natural boundary

HMRC’s policy paper (updated 23 July 2026) says that from 6 April 2027, most employers providing medical benefit, company cars, vans, or car and van fuel must report them through payroll software in real time instead of after the year ends. Most remaining benefits follow from April 2028; employer-provided loans and accommodation are excluded for now. Employers who were not registered to payroll benefits for 2026 to 2027 still file P11D and P11D(b) by 6 July 2027. If you provide benefits, check that your new payroll software supports payrolled benefits before you choose it, and consider making 6 April 2027 your cutover date.

A five-point check before the first FPS from the new software

  • Year-to-date totals in the new system match the old system’s last accepted FPS, employee by employee.
  • Payroll IDs are unchanged, or the change indicator is set with both the old and new IDs.
  • Start date and starter declaration are blank for everyone who is not a genuine new joiner.
  • Tax codes and NI category letters match HMRC’s latest notices.
  • Pension and leave balances are entered as at the cutover date.

Using QuickBooks for the books as well? Our UK QuickBooks support team can check the ledger side. For the Australian version of this problem, see changing payroll software mid-year under STP. For Canada, where CPP and EI maximums and ROE history are the sticking points, see switching payroll software mid-year in Canada.

Frequently asked questions

Can I change UK payroll software in the middle of the tax year?

Yes. Enter each employee’s year-to-date figures in the new software, keep their payroll IDs (or send the payroll ID changed indicator with the old and new IDs), and do not send a start date for continuing employees.

Should employees get a P45 when we change payroll software?

No. Their employment has not ended. Treating them as leavers and new starters is what HMRC says creates duplicate employment records.

Who issues the P60 after a mid-year switch?

The software running payroll on 5 April. The P60 covers total pay and deductions for the year, so that system needs the full year-to-date figures. P60s are due by 31 May.

Is 6 April always the better date?

It is the simpler date, because year-to-date figures restart at zero. A mid-year switch is fine if the opening balances are reconciled to the last FPS sent from the old software. If you provide benefits in kind, 6 April 2027 also lines up with mandatory payrolling of the most common benefits.

Related service: UK accounting software conversion

Thinking about a conversion?

Send us your details for a free, fixed-price quote within one business day.