In the UK, what many people call an employer identification number is usually the Employer PAYE reference, also called the Employer Reference Number (ERN). It's a two-part code issued by HMRC that identifies your payroll scheme for tax and National Insurance reporting.
A newly promoted HR manager usually meets this term the hard way, in an urgent email from payroll, a new starter waiting to be added, and a system that won't move until the right reference is entered. The confusion is common, because global software and cross-border teams often borrow US language even when the UK uses different official terms.
Table of Contents
- Understanding the Employer Identification Number in the UK
- How the Employer PAYE Reference Is Structured
- PAYE Reference vs UTR vs Accounts Office Reference
- Where the Employer Reference Number Is Used in Payroll and HR
- How to Register and Obtain Your Employer PAYE Reference
- Governing Employer Identifiers Across Connected HR Systems
- Key Takeaways and Next Steps for HR Leaders
Understanding the Employer Identification Number in the UK
A payroll team can be waiting on one number while HR is searching for another, and that's where the trouble starts. In the UK, the phrase employer identification number usually points to the Employer PAYE reference, not a US-style EIN. HMRC says employers must register before their first payday to get it, and registration is not allowed more than 2 months before staff are paid, so timing matters from day one. HMRC employer registration guidance
Why the wording trips people up
The label itself causes confusion because US-based vendors, templates, and global HR platforms often default to American terminology. In UK payroll, the operational identifier is the PAYE reference, also called the ERN, and it links wage payments, Income Tax, and National Insurance to the correct employer record. That makes it foundational, not decorative. HMRC's RTI guidance requires the reference on every FPS and EPS submission, so payroll teams need it at the point they file, not just when they register. HMRC UTR guidance
If payroll asks for the employer identification number, stop and check whether they mean the PAYE reference, not the UTR or the Accounts Office Reference.
Why HR teams should care early
The practical risk isn't academic. If the wrong identifier is used in onboarding or payroll setup, submissions can be delayed, records can be split, and finance and HR teams end up chasing the same detail in different systems. HMRC guidance shows the reference is embedded in RTI data flows and in employer documents, so if you treat it as a one-off registration code, you'll probably lose track of it later.
For HR managers working across Microsoft tools, this is the point where a small naming issue becomes a process issue. The reference needs to be available to payroll, HR, onboarding, and finance in one controlled place, because it will keep reappearing as people move through the employee lifecycle.
How the Employer PAYE Reference Is Structured
Once you know the format, the code becomes much easier to recognise. HMRC guidance shows the Employer PAYE reference is built in two parts, a three-digit office number and a second employer-specific code after the slash, such as 123/A246 or 123/AB45678. The first part identifies the HMRC office, while the second part identifies the employer within that office. HMRC RTI data item guide
What each part tells you
The office number matters because it gives HMRC routing and traceability. The employer-specific part matters because it makes the payroll scheme unique. Together, they create the identifier that sits behind RTI reporting and PAYE notices.
You'll also see the reference on HMRC letters, payslips, P45s, P60s, and in payroll software such as Basic PAYE Tools. That consistency is helpful, because the structure hasn't suddenly changed from one year to the next, so once your team knows the pattern, it stands out quickly in a document search. HMRC's own guidance has kept repeating the same format across years, which is a good sign that this is a stable control field rather than a moving target.
Practical rule: store the PAYE reference in one secure, central place as soon as it arrives, because teams that rely on inboxes and paper files usually spend more time finding it than using it.
PAYE Reference vs UTR vs Accounts Office Reference
Many HR and payroll teams find this process complex. The PAYE reference identifies the payroll scheme for RTI reporting and employee tax records, the UTR identifies the taxpayer for Self Assessment and other tax filings, and the Accounts Office Reference is the code used to pay PAYE and National Insurance liabilities to HMRC. HMRC Accounts Office reference guidance
The distinction matters because the wrong number fits the wrong task just often enough to create avoidable work. A company can hold all three identifiers at once, and that's normal. It doesn't mean they're interchangeable.
| UK Employer Identifiers Compared | |||
|---|---|---|---|
| Identifier | Format | Primary Use | Issued By |
| Employer PAYE Reference | Two-part code, such as 123/AB45678 | Payroll reporting and RTI submissions | HMRC |
| UTR | 10-digit number | Self Assessment and other tax filings | HMRC |
| Accounts Office Reference | Code used for PAYE and National Insurance payments | Paying tax and National Insurance to HMRC | HMRC |
The safest way to think about them
Use the PAYE reference when payroll is filing FPS or EPS submissions. Use the UTR when the business is dealing with entity-level tax filings. Use the Accounts Office Reference when money is being paid to HMRC. That simple division reduces the chance of a submission error or a payment being misallocated.
For a newly promoted HR manager, the key lesson is to stop looking for one universal tax number. UK payroll has several official identifiers, each with a different purpose, and the fastest way to avoid confusion is to map them by workflow rather than by memory.
Where the Employer Reference Number Is Used in Payroll and HR
The PAYE reference shows up every time payroll needs to tell HMRC which employer record is being updated. It anchors Full Payment Submissions (FPS) and Employer Payment Summaries (EPS), and HMRC requires it in RTI data flows, so the number is part of the live reporting process rather than a background admin detail. If it's missing or wrong, the submission can't be routed cleanly.
The employee lifecycle touchpoints
The same reference follows the employee through leavers' paperwork, tax reporting, and payroll corrections. It appears in P45 and P60 workflows, and it also matters when payroll handles deductions or claims tied to the employer scheme. In practice, that means HR can't treat it as “a payroll-only field” and walk away.
- Payroll submission: FPS and EPS filings depend on the correct PAYE reference, so a mistyped code can slow or block reporting.
- Leavers and year-end documents: P45 and P60 outputs should align with the same employer record, or employees may receive inconsistent paperwork.
- Payroll recovery processes: statutory pay claims and similar payroll adjustments need the right scheme attached, or HMRC records won't match the employer's figures.
- Connected HR records: when employee documents are scattered, searchability matters, which is why structured document storage helps. staff administration and digital personnel files
One lost identifier can ripple across payroll, finance, and employee support, especially when more than one team keeps a copy.
The operational risk is usually delay rather than drama. A wrong reference can trigger rework, stall onboarding, and force payroll to check whether the problem sits in HR data, finance records, or HMRC correspondence. That's why the safest process is to treat the employer reference as a governed master record, not a note in an inbox.
How to Register and Obtain Your Employer PAYE Reference
A newly promoted HR manager may have a start date agreed, a payroll provider ready, and still lack the identifier needed for the first run. HMRC requires an employer to register before the first payday once the business has its first employee or director on payroll. Registration cannot take place more than 2 months before payments begin. HMRC employer registration guidance
The registration path in practice
The online application uses Government Gateway. HMRC asks for the business name, address, entity type, expected employee numbers, and first payroll date. The PAYE reference then arrives by post, so it may not appear immediately in an email or payroll application.
Registration details should be checked against the legal entity and the payroll scheme before they are copied into connected Microsoft HR and finance systems. A duplicate application, an incorrect entity selection, or a mismatch between Companies House and HMRC records can delay setup. After an acquisition or TUPE transfer, confirm whether the existing PAYE reference still matches the employer responsible for current reporting.
What to do if it goes missing
Search HMRC letters, payslips, P45s, P60s, and payroll records first. If the reference remains unavailable, contact the Employer Helpline to resolve the issue. Store the confirmed value with its related UTR and Accounts Office Reference, clearly labelled, so a finance or HR colleague does not mistake one identifier for another.
A controlled registration record also gives payroll, finance, and HR one version to verify. Teams responsible for finance and operations processes can align the application, payroll configuration, and retained correspondence instead of passing incomplete details between systems.
Governing Employer Identifiers Across Connected HR Systems
A PAYE reference becomes difficult to control when it appears in separate spreadsheets, inboxes, and payroll records. Use one governed record as the source of truth, then provide controlled access to payroll, HR, and finance systems. In a Microsoft environment, SharePoint lists, Dataverse tables, and connected workflows can store the identifier without allowing unrestricted edits.
What good governance looks like
Limit editing permission to the people responsible for payroll master data. Record every change, including who made it, when it happened, and which value was replaced. Validation rules should check the reference before it reaches payroll software or an RTI submission.
Make the record searchable by employer, payroll scheme, and HMRC correspondence date. Store the employer name, scheme status, related UTR, Accounts Office Reference, and a link to the supporting correspondence beside the PAYE reference. An HR document centre provides structured document storage for that evidence, so colleagues can verify the value without searching individual mailboxes.
A controlled record should include:
- Field-level permissions: restrict editing to approved payroll data owners.
- Audit logging: retain the user, date, previous value, and replacement value.
- Validation rules: flag incorrectly formatted entries before submission.
- Structured metadata: connect the identifier to the employer, scheme, status, and supporting document.
The UTR and Accounts Office Reference need the same control, while remaining clearly labelled as different identifiers. Keeping all three in one record helps teams select the correct value for each HMRC or payroll task. It also reduces confusion during onboarding, payroll changeovers, and audits, when several systems may need updating at once.
Operational insight: a reference that cannot be found quickly is not being governed effectively.
The identifier should appear in the Microsoft HR or finance workflow where staff use it, with access based on their role. Payroll can then read the approved value, HR can verify the employing entity, and finance can match the record to HMRC correspondence. This turns a stored number into a dependable control across connected systems.
Key Takeaways and Next Steps for HR Leaders
In the UK, employer identification number usually means the Employer PAYE reference, also called the ERN. It is not the same as the UTR, and it is not the same as the Accounts Office Reference. Each one serves a different HMRC task, and payroll depends on using the right one in the right place.
The risk of mixing them up is operational, not theoretical. Payroll submissions can be delayed, onboarding can stall, and finance teams can misroute payments if the identifiers aren't governed properly. HMRC's rules make the PAYE reference part of everyday payroll control, so it deserves a proper home in your HR and finance setup.
What to do next
- Check your records: verify the PAYE reference against your latest HMRC correspondence.
- Separate the identifiers: make sure HR, payroll, and finance staff know which number is used for each task.
- Centralise storage: keep the reference in one controlled, searchable place rather than across scattered files.
- Review access: restrict editing rights and keep an audit trail for every change.
If your team is still relying on shared inboxes and spreadsheets, now is the time to tighten it up. Review your employer reference records today, verify them against your latest HMRC correspondence, and make sure they're mapped correctly across payroll and finance systems so compliance gaps don't creep in.
HR Management 365 helps UK teams keep employer identifiers, personnel records, and payroll-related data organised inside a connected Microsoft environment. If you're ready to reduce spreadsheet drift and build a more auditable HR process, visit HR Management 365 or phone +441522508096 today, and send us a message at https://www.hrmanagement365.com/contact/.
