Payroll ID
- What it is
- The unique payroll identifier for an employment in the PAYE scheme.
- Why it matters
- A change needs the maintained FPS fields that link old and new IDs for a continuing employment.
See how approved work reaches payroll in Workmax. Book a Workflow Demo
Payroll migration record guide · UK employees and employers
Why a payroll migration can make HMRC show you as a leaver.
Understand the difference between a real employment end and an RTI matching issue—and check the evidence before anyone assumes the record will fix itself.
UK employees and employersReviewed July 2026Based on HMRC RTI guidance
A payroll-system change does not by itself end employment. But a changed payroll ID without the right RTI linking information can create a separate employment record or misleading HMRC view.
HMRC: payroll-ID reporting issues ↗Start with the record
A leaver display is a signal to check the facts—not proof that employment ended.
If the employer, job and PAYE scheme continued, payroll should first examine the first FPS submitted after migration. Waiting may be reasonable before that first report has been processed; once it is accepted, unexplained duplication or a leaver record needs an evidence-led review.
Local-only record guide
What changed around the migration?
Use this to organise the facts for payroll. It stores nothing, does not access an HMRC account and does not submit or correct RTI.
Which statement is closest to the situation?
Identifier map
Check the record that changed, not just the label an employee can see.
| Identifier or record | What it is | Why it matters here |
|---|---|---|
| Payroll ID | The unique payroll identifier for an employment in the PAYE scheme. | A change needs the maintained FPS fields that link old and new IDs for a continuing employment. |
| Employee number | An internal workforce identifier, which may or may not be the payroll ID sent to HMRC. | Changing it does not by itself explain the RTI record; check what was reported as the payroll ID. |
| PAYE reference | The employer’s HMRC PAYE scheme reference. | A new reference can indicate a business-change route, not simply new payroll software. |
| National Insurance number | A personal identifier used in payroll reporting. | It does not make a new payroll ID automatically match an existing employment record. |
| Employment record | The HMRC-facing record of a job under a PAYE scheme. | A continuing employment, a genuine leaver and a new job must be distinguished in the report. |
Employee number
- What it is
- An internal workforce identifier, which may or may not be the payroll ID sent to HMRC.
- Why it matters
- Changing it does not by itself explain the RTI record; check what was reported as the payroll ID.
PAYE reference
- What it is
- The employer’s HMRC PAYE scheme reference.
- Why it matters
- A new reference can indicate a business-change route, not simply new payroll software.
National Insurance number
- What it is
- A personal identifier used in payroll reporting.
- Why it matters
- It does not make a new payroll ID automatically match an existing employment record.
Employment record
- What it is
- The HMRC-facing record of a job under a PAYE scheme.
- Why it matters
- A continuing employment, a genuine leaver and a new job must be distinguished in the report.
First migrated FPS
For a continuing employment, the migration report should be explainable.
| Check | Why it matters |
|---|---|
| Unique payroll ID | The employment record must not reuse an identifier from another employment. |
| Changed-ID indicator and old ID | Where the payroll ID changed, the FPS should use the maintained linkage fields. |
| No inappropriate starter detail | A continuing employment should not be represented as a new job merely because software changed. |
| No incorrect leaving date | A migration should not create a leaver record when employment continued. |
| Continuous YTD values | Current and year-to-date figures should reconcile to the prior reported employment history. |
For employees
Ask factual questions; do not try to correct the employer’s RTI record yourself.
Ask payroll
- Which FPS was the first one from the new payroll system?
- Did my payroll ID change, and was the old ID linked in the FPS?
- Was a leaving date or P45 submitted, and if so, why?
- Do my YTD pay and deductions match the prior payroll record?
Keep and compare
- Your latest and previous payslips.
- Any P45 or employer explanation.
- Dates and details shown in your HMRC account.
- Any HMRC message that affects a live tax-code, benefit or other query.
For payroll teams
Investigate three views before choosing a correction.
Old and new payroll
Employee IDs, YTD values, payment dates and the migration boundary.
RTI evidence
The first migrated FPS, response, payroll-ID fields and any starter/leaver data.
HMRC outcome
The employer account and employee-reported record, allowing for processing time.
If the evidence does not reconcile, preserve the original record and use the maintained correction route. Do not resend an identical FPS simply to make an account screen change.
Browse all migration-leaver investigation routes
This static route map remains available without the local guide. It is educational, and does not decide whether an individual’s employment ended or an RTI report is correct.
Check the first migrated FPS as a continuing-employment record
Employment continued, but the payroll ID or system record may have changed. The migration FPS needs to link the continuing employment rather than create a separate job or leaver record.
Review provider-migration controls →Check whether the record reflects a genuine leaving event
The employee may have actually left, been re-employed or received final-pay reporting. These facts require the maintained leaver route rather than a migration-only explanation.
Use the employer leaver checklist →Treat a changed PAYE reference or business change as its own route
A merger, succession or change of employer reference is more than a payroll-software migration. HMRC has separate reporting steps for the old and new employer references.
Plan a provider migration →Preserve the submitted history and investigate before another report
A migration report has already been sent and the employee account appears to show a leaver, duplicate record or mismatch. A second unverified submission can make the history harder to reconcile.
Learn about payroll corrections →Establish the employment and reporting facts before assuming a migration error
The employment status, PAYE reference or migrated record is not clear. A missing fact can make a continuing employment look like a migration issue when it needs a different route.
Read the payroll migration guide →Prevent the issue in the next migration
Plan the provider handover around one controlled first run.
Use the migration guide to preserve records, reconcile YTD values and authorise exactly one live reporting source. Workmax can demonstrate how its workforce and payroll workflow supports that control model.
