---
title: HMRC RTI PayIds
description: "Follow this advanced article only in exceptional cases where you need to use a different RTI **PayId** than would be automatically submitted. ## Overview HMRC uses PayIDs for each \"employment\". If duplicate PayIDs are submitted, HMRC systems will assume an…"
url: "https://paiyroll.com/kb/hmrc-rti-payids/"
updated: "2026-11-20"
category: Advanced
---

# HMRC RTI PayIds

Follow this advanced article only in exceptional cases where you need to use a different RTI **PayId** than would be automatically submitted.

## Overview

HMRC uses PayIDs for each "employment". If duplicate PayIDs are submitted, HMRC systems will assume an employee has multiple employments - one for each PayID.

```
IMPORTANT: It is therefore critical that you understand how to change the pay ID, and it is critical that you check it before submission so that there are no duplicates created.

Before you approve the pay run and submit the FPS, check it: Pay runs > View > Reports tab > View for GB RTI FPS. Under Successes, each line such as "PayId changed from 13/2018-01-08 to 13/2019-06-01" is a PayId change that the FPS will send. The first PayId must be the PayId that HMRC holds. If you did not expect a change, correct it before you approve.

For the procedures below, compare each PayId in the FPS with the PayId that HMRC holds, which you can see on the employee's last FPS from the old system. They must be the same, character by character, including the start date after the /. If the FPS has PayIdChgd, its OldPayrollId must be the PayId that HMRC holds.
```

### PayId Format

paiyroll® automatically generates **PayIDs** in the following format:

```
104654/2017-05-01
```

| The left part is the unique employee Database ID. This is unique for every employee and cannot be changed. Furthermore, it can never be recovered if, for example, a company or its employees are deleted. | / | The right part is the employee start date |
| --- | --- | --- |

### What is the current Database ID?

If you view an employee, the Database ID will be the number in the browser address bar - this value is **123456** for the employee below:

```
https://login.paiyroll.com/paiyroll/employee/123456
```

You can also find it in the FPS.

### Starter Declarations and Existing employee

If you have sent a Starter declaration to HMRC, this will create a new employment record. In general, you probably do not want to send another starter declaration and therefore recreate the record. Therefore, for the procedures below, make sure that the Existing employee checkbox is ticked, which will suppress the starter declaration.

## Overriding the default Database ID

If you need to use a different PayId, this can be set as follows for each employee:

- Employees > Update > System
- Data > New > Create new entry
  - Key: Alternative database ID: {"integer": str} by job
  - Value: 123456 \[example\]
- Create
- **Update** the employee

---

## Scenarios

### 1. Send Zero YTD and leavers(employment end) for specific PayIds

You will import an FPS into a new Test company and submit an FPS using their original pay IDs as a correction.

1. Setup > Import > HMRC FPS > Run
   - Step 1
     - Import the original FPS, but not the employee CSV, to create a new Test Company. If you do not import the employee CSV, then fake usernames are created so as not to collide with the original usernames
   - Step 2
     - Select **Next pay run with FPS YTD**
     - Select **No pay items**
2. Rename this company appropriately, e.g. *Acme 2025 Correction*
3. Setup > Report Definitions
   - GB RTI **FPS** > Enter credentials > Update
   - Delete the GB RTI **EPS**
4. Correct each **Works id** and **Start date** (the import sets the Works id to the PayId from the FPS, so the Start date must be the date after the /)
5. All the year-to-date values will need to be zero
   - This can be conveniently achieved if you import a March FPS because the next April FPS will reset the YTDs to zero
6. Override the default Database ID as above for each employee
7. Add a leaving date to each employee to end their employment for that PayId, including leavers
8. You may need to move the **pay schedule date** to fall after your last FPS submission
9. Pay Run **redo**
10. You must carefully check that the FPS has exactly the information required:
    - Zero YTD values
    - The correct PayIDs
    - The correct leaving dates
    - There are no PayId changes: in **Pay runs > View > Reports** tab > **View** for **GB RTI FPS**, **Successes** shows no "PayId changed from" line
11. Then submit the FPS in the usual way

---

### 2. Send a prior year correction FPS for a specific Employee PayId

You will import one or more employees from a prior FPS into a new Test company and submit a correction using your original PayIDs.

1. Create an **Employee XLSX** with the worker(s) who need correcting
   - **Setup > Report Definitions > Add... > Group:Other > Template:Jinja (Company pre-approval)**
     - **Filename:** Employee.csv
     - **Base Template: Universal.imported_workers.csv.jinja**
     - **Add**
   - Pay Run **Redo**
   - **Documents > Jinja (Company pre-approval) > Download**
   - Edit the Employee.csv file, which will be in your Downloads folder, using Excel to
     - Delete all worker rows except the one(s) to correct
     - Edit the email to be unique so as not to clash with the original username, e.g. *john.smith1@example.com*
     - Prefix numeric works_ids with a single quote 1 -> '1
     - Save as an EXCEL XLSX format
2. You will need an **FPS XML file** to import
   - If the original was created in paiyroll®, use **Documents > Download** the **FPS XML** from the pay run that needs to be corrected
   - Otherwise, export it from the previous Payroll software that created the FPS
3. **Setup > Import > HMRC FPS > Run**
   - Step 1
     - Company must be left blank ——— to create a new **Test Company**
     - Select the FPS XML and employee XLSX > Upload Files
   - Step 2
     - Mode: **Create Test company** will be shown
     - Filter workers: **Import only the subset of FPS workers in the Worker Details file**
     - YTD and pay run:
       - **Parallel run by rewinding FPS YTD (recommended)**. If importing the FPS, you need to resend, or
       - **Next pay run with FPS YTD** if you're importing the previous FPS, or you were unable to parallel run due to the error: 'The parallel run import has failed because the imported FPS has different payment values than this software would generate.'
     - Pay Items: **No pay items**
     - Other fields as needed
4. Rename this company appropriately, e.g. *Acme 2025 Correction*
5. **Setup > Report Definitions**
   - GB RTI **FPS** > Set the Late reporting reason to **H: Correct an earlier payroll report** > Enter credentials > Update
   - Delete the GB RTI **EPS**
6. **Pay Item Editor > Add**the relevant Pay Items to correct the Pay as needed
7. Override the default Database ID as above for each employee
8. Pay Run **redo**
9. You must carefully check that the FPS has exactly the information required:
   - YTD values
   - The original PayID(s)
   - There are no PayId changes: in **Pay runs > View > Reports** tab > **View** for **GB RTI FPS**, **Successes** shows no "PayId changed from" line
   - Late reason code
10. Then submit the FPS in the usual way
11. **Setup > Report Definitions > Jinja (Company pre-approval) > Delete > Confirm deletion**

---

### 3. Update Employee state YTD values from an FPS

You will import one or more employees from a \[prior\] FPS into an existing company to update their state YTD values.

1. Confirm that the YTD values are incorrect in **Employees > Update > System > View State**
2. Create an **Employee** **XLSX** with the worker(s) who need correcting
   - **Setup > Report Definitions > Add... > Group:Other > Template:Jinja (Company pre-approval)**
     - **Filename:** Employee.csv
     - **Base Template: Universal.imported_workers.csv.jinja**
     - **Add**
   - Pay Run **Redo**
   - **Documents > Jinja (Company pre-approval) > Download**
   - Edit the Employee.csv file in your downloads folder in Excel (you can skip this step and use the CSV as-is if you do not need to delete any workers)
     - Delete all worker rows except the one(s) to correct
     - Prefix numeric works_ids with a single quote 1 -> '1
     - Save as an EXCEL XLSX format
3. **Documents** > Download the **FPS XML** from the pay run that includes the YTD values you wish to restore
4. **Setup > Import > HMRC FPS > Run**
   - Step 1
     - Select the company with the workers to update
     - Select the FPS XML and employee CSV/XLSX > Upload Files
   - Step 2
     - Mode: **Update workers in** \[your company name\] will be shown
     - Filter workers: **Import only the subset of FPS workers in the Worker Details file**
     - YTD and pay run: **Next pay run with FPS YTD**
     - Pay Items: **No pay items**
     - Other values: as applicable
     - Employment Allowance: leave as zero **0** to retain the existing company EA value; only enter a value to force a new EA value
   - Ignore any error messages for other frequency employees who are not updated
5. Verify the YTD values in **Employees > Update > System > View State**
