PAYE Forms and Technical Specifications

Introduction

If you run payroll for your business, you'll need to issue certain forms to employees and HMRC throughout the year. The most common are the P45 (when someone leaves), P60 (at the end of each tax year), and P11D (for employee benefits). While HMRC provides official versions of these forms, you can also create your own substitute versions if you use payroll software—but they must meet strict technical specifications.

What are PAYE forms?

PAYE (Pay As You Earn) is the system for collecting income tax and National Insurance from employees' wages. Several standard forms support this system:

P45: Given to an employee when they leave your employment. It shows how much they've been paid and how much tax has been deducted in the current tax year.

P60: An end of year certificate given to every employee still on your payroll on 5 April. It summarises their total pay and deductions for the tax year.

P11D: A form that reports benefits and expenses you've provided to employees (such as company cars, private health insurance, or interest-free loans).

Using official HMRC draft forms

HMRC publishes approved versions of PAYE forms that software developers can use when building payroll software. These draft forms serve as templates to ensure the software produces documents that meet HMRC's requirements.

If you're an employer using commercial payroll software, your software provider will have built these forms into their system. The forms your software generates should match HMRC's specifications so that employees and HMRC receive the correct information in the right format.

Creating substitute forms

You can create your own versions of PAYE forms rather than using HMRC's exact templates—these are called "substitute forms". This is particularly relevant if you're developing payroll software or if your business has specific requirements for how forms are presented.

However, substitute forms must follow HMRC's technical specifications precisely. HMRC publishes detailed specifications documents that explain exactly how substitute forms should be designed.

P60 substitute form specifications

For the P60 End of Year Certificate, HMRC's specifications cover several key areas:

Layout and content: Your substitute P60 must include all the mandatory information fields in a clear format. This includes the employee's details, pay information, and tax deductions for the complete tax year.

Adaptations for pension schemes: If you're issuing P60s for a pension fund scheme rather than a standard employment, the specifications explain how to adapt the form appropriately. Pension schemes have different reporting requirements, and the form needs to reflect this.

Electronic P60s: You can issue P60s electronically rather than on paper, but only if you follow HMRC's rules. The specifications include guidance on what you must do if you want to issue substitute P60s in electronic format. This might include ensuring employees can access and store the electronic version securely.

Why specifications matter

HMRC's technical specifications exist to ensure consistency. When every P60 or P45 follows the same basic structure, it's easier for:

Employees to understand their tax information
New employers to process P45s when someone starts work
HMRC to verify that the right information has been reported
Software systems to exchange data accurately

If your substitute forms don't meet the specifications, HMRC may reject them. This could mean re-issuing forms to employees and potentially facing penalties for late or incorrect reporting.

Who needs to use these specifications?

Software developers: If you're building payroll software, you must use HMRC's draft forms and specifications to ensure the forms your software generates are compliant.

Employers with in-house systems: If your business has developed its own payroll system rather than using commercial software, you'll need to apply these specifications to any substitute forms you create.

Most small businesses: If you use standard commercial payroll software (such as popular cloud-based systems), your software provider has already built these forms to specification. You don't need to worry about the technical details—the forms your software produces should already be compliant.

Accessing the specifications

HMRC publishes both the draft forms and the technical specifications for substitute forms on GOV.UK. These documents are regularly updated to reflect changes in tax rules or reporting requirements.

The specifications documents are technical and detailed. They're written primarily for software developers who need to understand the precise layout, field definitions, and validation rules for each form.

Other PAYE forms

While this article focuses on P60s, similar principles apply to other PAYE forms. HMRC provides specifications for substitute versions of forms like the P45, and software developers must follow the same approach: using draft forms as templates and adhering to technical specifications when creating substitute versions.

The P11D form, which reports benefits and expenses, has its own set of rules and filing requirements. For the 2025/26 tax year, P11D forms must be submitted to HMRC and provided to employees by 6 July following the end of the tax year.

Keeping forms up to date

HMRC updates PAYE forms and their specifications when tax rules change. If you're responsible for payroll software or in-house systems, you must ensure your forms reflect the current tax year's requirements.

Commercial payroll software providers handle these updates automatically, pushing new versions that comply with the latest specifications. This is one advantage of using established payroll software rather than building your own system.

Sources

This article provides general guidance based on current HMRC rules. For advice specific to your situation, speak to your accountant.