See how care plans, verified visits, and payroll connect in Workmax. Book a Care Demo

Why a Payroll Migration Can Make HMRC Show You as a Leaver

HMRC showing your employment as ended after a payroll system change? Learn how payroll IDs, P45s, FPS submissions, and RTI records can cause temporary leaver or duplicate employment confusion.

Your employer changes payroll systems. You get told employment has not actually ended, but HMRC suddenly shows you as a leaver or appears to show a new employment record.

That is unsettling, especially if your tax code, benefits, student loan, mortgage application, or personal tax account depends on HMRC holding the right employment record.

The short answer is: if you stayed with the same employer, this is usually a payroll reporting and matching issue, not proof that your job ended. A payroll migration can change the employee payroll ID, trigger a P45-style workflow, or send a starter/leaver signal that makes HMRC's records look wrong until the next RTI submission is processed and matched correctly.

There is no reliable public HMRC promise that this always clears in a set number of days. If the record still looks wrong after the first payroll from the new system, the employer's payroll team should check what was submitted on the Full Payment Submission.

This article is general payroll guidance, not personal tax or employment advice. If the issue affects your tax code, benefits, or a live HMRC query, speak to your employer's payroll team and HMRC.

Quick answer

HMRC can show a continuing employee as a leaver after a payroll migration when the data sent from the new payroll system does not clearly connect the old payroll record to the new one.

The most common reasons are:

the new payroll system uses a different employee payroll ID;
the payroll ID change indicator was not used correctly;
the old and new payroll IDs were not mapped correctly;
a leaving date or P45 process was used even though employment continued;
the new system sent a starter-style record that HMRC treated separately;
HMRC's online view has not yet caught up with the latest FPS.

For employees, the practical next step is to ask payroll which FPS included the migration and whether the payroll ID change was reported correctly.

For employers, the practical next step is to check the RTI submission, not just wait and hope the record fixes itself.

Why payroll IDs matter to HMRC

A payroll ID is the employee identifier used in payroll reporting. It is not the same as a National Insurance number, and it is not always the same as the employee number shown on a payslip.

HMRC guidance says payroll IDs must be unique. When a payroll ID changes, HMRC says employers should set the payroll ID changed indicator and include both the old and new payroll IDs.

That matters during a payroll migration because new software may generate employee numbers in a different format. For example, the old provider may use a 12-digit payroll ID and the new provider may use a 10-digit ID. If HMRC receives the new ID without enough information to link it to the old one, it may treat the submission as a separate employment record.

This is why the issue can appear even when:

the employer has not changed;
the PAYE reference is the same;
the employee has not resigned;
the employee's National Insurance number is unchanged.

The record matching still depends on the RTI data being submitted in the way HMRC expects.

Why a P45 can make the situation confusing

A P45 is normally associated with leaving a job. So if employees receive P45s during a payroll migration, it is reasonable for them to worry that HMRC will think employment ended.

Sometimes a P45 is produced because a system or provider treats the migration as closing the old payroll record. That does not necessarily mean the employment relationship ended in real life. But if the payroll submission includes a leaving date, or the new system starts the employee again without correctly linking the old payroll ID, HMRC may show an ended employment record, a new employment record, or both.

The employer should be able to explain why a P45 was issued, whether the employee was treated as a genuine leaver, and how the next FPS from the new payroll system links the continuing employment.

How long does HMRC take to update?

The honest answer is that there is no useful public rule that says this always takes a fixed number of days.

In many straightforward cases, employees only notice the issue temporarily around the first pay run on the new system. Once the new FPS is submitted and HMRC processes the payroll ID change correctly, the Personal Tax Account view may settle.

But if the first submission from the new system was missing the payroll ID change information, included an incorrect old payroll ID, used a leaving date incorrectly, or created a new starter record, waiting longer may not solve the underlying problem.

Use this rule of thumb:

If the first new-system payroll has not yet been submitted, wait until after that FPS has gone in.
If it has been submitted and the record still looks wrong, ask payroll to check the RTI submission.
If payroll confirms the FPS was correct but HMRC still shows duplicate or mismatched records, the employer may need to contact HMRC with the submission details.

What employees should ask payroll

If your HMRC account shows you as a leaver after a payroll migration, ask your payroll team clear, factual questions:

Which pay period was the first one submitted from the new payroll system?
Was my payroll ID changed as part of the migration?
Did the FPS include the payroll ID changed indicator?
Did the submission include both my old payroll ID and my new payroll ID?
Was a leaving date submitted for me, or was the P45 only part of the migration process?
Were my year-to-date pay and tax figures carried forward correctly?
Should I expect a new payslip portal, payroll number, or payslip format?

Also check your own records:

Compare your latest payslip with the previous one.
Check that year-to-date pay, tax, National Insurance, pension, and student loan figures look continuous.
Keep the P45, payslips, and any employer explanation together.
Recheck your HMRC Personal Tax Account after the first new-system pay run has been submitted.

Do not try to fix the employer's RTI submission yourself. If the employer reported payroll data incorrectly, the employer or payroll provider normally needs to correct it.

What employers should check before and after migration

Payroll migrations are safer when payroll IDs are treated as a matching control, not just an internal employee number.

Before the first FPS from the new system, check:

old payroll IDs from the previous provider;
new payroll IDs generated by the new system;
whether each employee's payroll ID is changing;
whether the payroll ID changed indicator will be set where needed;
whether both old and new payroll ID fields will be populated;
whether year-to-date pay, tax, National Insurance, pension, and statutory payment figures have migrated correctly;
whether the employee should continue as the same employment record rather than being treated as a starter;
whether any leaving dates or P45s are genuinely required.

After the first FPS, check:

submission success and HMRC acknowledgement;
a sample of employees' year-to-date figures;
any employee reports of duplicate jobs, ended employments, or unexpected tax code changes;
whether the old payroll provider submitted any final FPS or EPS that could conflict with the new system;
whether payroll has a written audit note explaining the migration.

If the employer PAYE reference has not changed, the migration should usually be a software/provider change rather than a new employment relationship. If the employer reference has changed because of a merger, succession, or business ownership change, HMRC has separate business-change guidance and the payroll treatment can be different.

Where Workmax helps

Payroll migration should not leave employees wondering whether HMRC thinks they left their job.

Workmax helps UK employers keep employee records, payroll checks, RTI submissions, payslips, P45s, P60s, and audit trails in one connected payroll workflow. That makes it easier to review the fields that matter before the first live submission from a new system.

If you are planning to switch payroll software, use the migration as a chance to clean up employee records, confirm payroll IDs, and check that HMRC-facing data is ready before payday.

Switch payroll systems without creating HMRC record confusion