What Is a P32 Report and How Does It Work in UK Payroll?

Running payroll in the UK means more than calculating employee wages, it means tracking every penny owed to HMRC, month after month, with precision. The P32 report is the internal payroll document that makes this possible. It records your total PAYE liability, National Insurance contributions, statutory payment recoveries, and the net amount due to HMRC for each tax month across the payroll year. 

Whether you run payroll in-house or use an external bureau, understanding how the P32 works keeps you compliant, audit-ready, and in full control of your employer obligations.

What Is a P32 Employer Payment Report in UK Payroll?

The P32 Employer Payment Record is a payroll report that summarises the total amounts an employer owes to HMRC for each tax month throughout the payroll year. It is produced internally, either by payroll software or manually, and serves as the employer’s own running record of PAYE liabilities, deductions, statutory payment recoveries, and net payments made to HMRC.

The P32 is the employer payment record. It is a summary of the amounts paid to HMRC each month, including all PAYE, student loan deductions, and National Insurance contributions.

A critical point many employers misunderstand: the P32 is not submitted to HMRC. The P32 remains mandatory as an internal reconciliation record, it is not submitted to HMRC. Payroll software automates P32 calculations in real time, reducing manual errors and ensuring submissions match internal records.

Instead of submission, the P32 serves as the employer’s internal control document, the tool you use to verify what you owe, confirm what you have paid, and reconcile your records against HMRC’s employer account throughout the year.

P32 vs P30: What Changed Under RTI?

Before Real Time Information (RTI) was introduced in April 2013, employers used the P30 as a remittance slip to accompany monthly payments to HMRC. Under RTI, the P30 remittance form is no longer used. The P32 remains mandatory as an internal reconciliation record. Today, the P32 has taken on the full reconciliation role previously split across both documents.

The UK payroll year runs from 6 April to 5 April, divided into 12 tax months. Each tax month runs from the 6th of one calendar month to the 5th of the next. The P32 records a separate liability for each of these 12 tax months, giving a complete, month-by-month picture of the employer’s payroll tax position across the full year.

Why the P32 Report Is Important for Employers and Payroll Compliance

The P32 sits at the heart of employer PAYE compliance. Without it, or with one that is inaccurate, employers face a significant risk of underpaying or overpaying HMRC, triggering penalties, interest charges, and potential compliance investigations.

It Tells You Exactly What to Pay HMRC Each Month

The most immediate practical function of the P32 is straightforward: it tells you the precise net amount to transfer to HMRC by the payment deadline. After all liabilities are calculated and all statutory payment recoveries are applied, the resulting figure is your monthly HMRC payment.

It Reconciles Your Internal Records Against RTI Submissions

Every payroll run generates a Full Payment Submission (FPS) sent to HMRC. The cumulative data across all FPS submissions for the year should match the year-to-date totals on your P32. If they do not, there is a discrepancy that needs to be identified and corrected before it compounds into a larger problem at year end.

It Provides a Complete Audit Trail

The P32 is the employer’s internal payment record, tracking monthly PAYE and NI liability, statutory payment recoveries, and actual payments made to HMRC. RTI does not replace it. The P32 remains essential for reconciling your own records against HMRC’s employer account throughout the year.

It Is a Legal Record-Keeping Requirement

UK employers must retain payroll records, including P32 records, for a minimum of three years after the end of the tax year they relate to. Best practice is to retain payroll records, including P32 reports, for six years, particularly for businesses that may be subject to HMRC compliance reviews.

Treating the P32 as a live compliance document, not just a monthly formality, is what keeps payroll accurate and HMRC relationships clean.

What Information Is Included in a P32 Employer Payment Record?

The P32 captures every component of an employer’s monthly PAYE liability in a structured, standardised format. Here is a breakdown of what each section covers:

Gross Payroll Liabilities

The Apprenticeship Levy, which some employers need to pay, is included in the P32 report. CIS deductions can also be recorded and appear in the PAYE Liability screen, enabling employers to see their overall balance with HMRC.

Statutory Payment Recoveries

Employers who pay statutory payments to employees can recover a portion from HMRC by reducing their monthly P32 payment. Current recovery rates are:

Small employers, those whose total Class 1 NIC liability in the previous tax year was £45,000 or less, qualify for Small Employers’ Relief, recovering 103% of statutory payments. The additional 3% compensates for the employer NICs due on those payments.

Employment Allowance

The P32 allowance generally refers to the Employment Allowance, which allows eligible UK employers to reduce their employer Class 1 National Insurance liability by up to £10,500 for the 2026/27 tax year. When claimed, it applies directly against employer Class 1 NICs each pay period until the full £10,500 limit is reached, automatically appearing on the monthly P32 Employer Payment Report, lowering the overall NIC bill without requiring manual recalculations.

The Net Payment to HMRC

After all liabilities are summed and statutory recoveries and Employment Allowance are deducted, the P32 shows the net amount due to HMRC for that tax month. This is the figure transferred to HMRC by the payment deadline.

Every figure on the P32 has a direct impact on what leaves your account each month, accuracy at this level is non-negotiable.

How the P32 Report Works in UK PAYE and Payroll Systems

The P32 does not exist in isolation, it sits within the broader PAYE and RTI reporting framework and draws data from several interconnected payroll processes.

The Monthly Payroll Cycle and the P32

1. Process the payroll run, calculate gross pay, deductions, and net pay for all employees
2. Generate and submit the FPS, sent to HMRC on or before each payday, reporting individual employee pay and deduction data
3. Generate the P32. The payroll software produces the P32 automatically, aggregating all employee-level data into employer-level monthly totals
4. Submit an EPS if required. An Employer Payment Summary is submitted when statutory payment recoveries, CIS deductions, or a nil payment need to be notified to HMRC
5. Verify the net payment figure, cross-check the P32 net liability against any EPS values submitted
6. Transfer the payment to HMRC by the relevant deadline for your payment method

Payment Deadlines (2026/27)

Once the total P32 payroll liability is calculated, payments must reach HMRC by the 22nd of the following tax month for electronic payments (BACS, CHAPS, Faster Payments). Cheque payments must reach HMRC by the 19th of the following tax month.

Quarterly payers: Small employers whose total annual PAYE liability is less than £1,500 per month may pay HMRC quarterly rather than monthly. In this case, the P32 accumulates across three tax months before a payment is made.

How RTI and the P32 Work Together

Under RTI, HMRC receives individual employee payroll data in real time through FPS submissions. The P32 is the employer’s internal verification that what has been submitted via FPS translates correctly into the net amount owed and paid.

Full Payment Submissions inform HMRC of employee payments. Employers still need internal P32 records to calculate the precise amount owed each month after applying allowances. RTI does not replace P32 requirements.

P32 vs Other Payroll Reports (P11, P60, and RTI Explained)

The P32 is one of several key payroll documents in UK PAYE administration. Understanding how it differs from related reports is essential for payroll accuracy and compliance.

P32 vs P11

The P11 operates at the individual employee level, it records each employee’s gross pay, tax deductions, and NIC contributions on a cumulative basis throughout the year. The P32 aggregates all employee P11 data into a single employer-level monthly payment record. The P11 feeds the P32, and the P32 is the summary of what the individual P11s collectively produce.

P32 vs P60

The P60 is issued to every employee on the payroll at 5 April, by 31 May each year, and confirms their total pay and tax for the year. P60s must be issued to all employees who were on the payroll on 5 April 2026 by 31 May 2026, either on paper or electronically provided the employee has agreed to electronic receipt. The year-to-date figures that feed into the P60 derive from the same payroll data that populates the P32 throughout the year.

P32 vs FPS and EPS

The FPS and EPS are HMRC submissions, data flows from employer to HMRC. The P32 is an internal employer document, it stays within the business. Together, they form a complete loop: FPS and EPS inform HMRC what is owed, the P32 confirms that the employer’s own records agree with what has been submitted and paid.

Each document plays a distinct role, understanding how they connect is what keeps your payroll records consistent from individual employee level right through to HMRC.

How to Calculate Employer Payments Using a P32 Report

Understanding the P32 calculation process helps you verify your payroll software output and catch errors before they reach HMRC.

The P32 Calculation Formula

Gross PAYE Liability = PAYE Income Tax + Employee NICs + Employer NICs + Student Loan Deductions + Apprenticeship Levy (if applicable)

Less: Statutory Payment Recoveries = SMP recovered + SPP recovered + SAP recovered + ShPP recovered + SNCP recovered (at applicable recovery rate)

Less: Employment Allowance = Applied against employer NICs each month until the £10,500 annual limit is reached

Less: CIS Deductions Suffered = Where the employer operates as a subcontractor in the Construction Industry Scheme

= Net Amount Payable to HMRC

Worked Example (Monthly P32 Calculation)

This net figure of £14,055 is what must be transferred to HMRC by the 22nd of the following tax month (electronic payment).

Quarterly Payment Example

For small employers paying quarterly, the net P32 liability is accumulated over three consecutive tax months before a single payment is made, covering months 1 to 3 (April to June), 4 to 6 (July to September), 7 to 9 (October to December), and 10 to 12 (January to March).

Common Payroll Errors Identified Through the P32 Report

The P32 is not just a payment calculation tool, it is one of the most effective diagnostic instruments for catching payroll errors before they escalate into HMRC disputes.

Discrepancy Between P32 Totals and FPS Submissions

• Year-to-date P32 totals and cumulative FPS data must match exactly
• Mismatches indicate a missed or duplicated FPS, a data entry error, or incorrect period allocation
• Discrepancies appear in your HMRC online employer account and must be resolved promptly

Statutory Payment Recovery Not Applied

• SMP, SPP, SAP, ShPP and SNCP paid to employees must be offset at the correct recovery rate
• Missing these recoveries results in consistent monthly overpayments to HMRC
• Small employers should also check eligibility for the 103% Small Employers’ Relief rate

Employment Allowance Not Claimed or Applied Incorrectly

• Failing to claim the Employment Allowance means leaving up to £10,500 of NIC relief unclaimed
• Applying it after the annual limit is reached creates P32 calculation errors
• Both underpayments and overpayments carry penalties or require corrective adjustments

Incorrect Period Allocation for Weekly or Irregular Pay Frequencies

• Weeks 5 ,9, 18, 22, 27, 31, 35, 40, 44 and 48 can span two tax months
• Allocation must follow the usual pay date, not the period end date
• Incorrect allocation reports P32 figures in the wrong tax month

CIS Deductions Not Recorded

• Employers operating as subcontractors can offset CIS deductions suffered against their monthly P32 liability
• Failing to record these creates unnecessary cash flow leakage
• Check monthly whether any CIS deductions apply before finalising the P32

Missing or Late FPS Submissions

• HMRC allows one late FPS per tax year without penalty
• After that – monthly penalties range from £100 to £400, depending on headcount
• Late FPS submissions create P32-to-HMRC account mismatches that complicate reconciliation

Nil Payment Not Notified via EPS

• If no employees were paid in a tax month – no standard P32 liability is generated
• An Employer Payment Summary must be submitted by the 19th of the following month
• Failing to submit leaves HMRC expecting a payment that will not arrive – triggering follow-up action

Catching these errors at the P32 stage, before payment is made, is always faster, cheaper and less disruptive than correcting them after the fact.

How to Generate and Use a P32 Report for HMRC Compliance

Generating the P32

Most UK payroll software, including Sage, Xero, BrightPay, QuickBooks, Moneysoft, and Staffology, generates the P32 automatically after each payroll run. The process typically works as follows:

1. Complete all payroll periods within the tax month before generating the P32
2. Run the P32 report from within your payroll software, usually found under Reports, HMRC Reports, or Payroll Summary
3. Review each line item, PAYE, employee NICs, employer NICs, student loans, statutory recoveries, and Employment Allowance
4. Verify the net payment figure against any EPS values submitted for the same period
5. Cross-reference against your HMRC online employer account to confirm the figures align

The P32 employer payment record shows a breakdown of total liability due to HMRC for the period, using figures from both the Full Payment Submission and the Employer Payment Summary.

Using the P32 for Ongoing Compliance

Monthly: Use the P32 net figure to confirm the correct amount to transfer to HMRC. Record the payment date and amount alongside the P32 for that month.

Quarterly: Accumulate three months of P32 data before making a single quarterly payment, ensuring all three months’ liabilities are correctly captured.

Year-end: Use the cumulative P32 year-to-date totals to reconcile against RTI submissions and confirm total payments made to HMRC match what was reported. This forms the foundation of your year-end close process.

Record Retention

The minimum retention period for payroll records, including P32 records, is three years after the end of the tax year they relate to. This covers payslips, FPS submissions, P32 records, P11D returns, and HMRC correspondence. Longer retention is appropriate where a compliance dispute is open or anticipated.

Best practice is to retain P32 records for six years, aligning with HMRC’s standard investigation window and providing protection in the event of a later payroll compliance review.

Final Thoughts

The P32 report is one of the most practical and important tools in UK payroll administration. It consolidates every element of your monthly HMRC liability into a single, structured record, from PAYE and National Insurance to statutory recoveries and Employment Allowance. 

Reviewing it carefully each month, reconciling it against your RTI submissions, and retaining it as a permanent part of your payroll records keeps your business compliant, audit-ready, and in full command of its employer obligations throughout the tax year and beyond.

FAQs

What Is A P32 Report In UK Payroll? 

The P32, formally known as the Employer Payment Record, is an internal payroll document that summarises the total amounts an employer owes to HMRC for each tax month. It records PAYE Income Tax, employee and employer National Insurance contributions, student loan deductions, statutory payment recoveries, Employment Allowance, and the resulting net payment due to HMRC. It is not submitted to HMRC, it is an internal reconciliation and compliance record.

Is The P32 Still Required Under RTI? 

Yes. Real Time Information changed how payroll data is reported to HMRC, through FPS and EPS submissions, but it did not remove the requirement for employers to maintain internal P32 records. The P32 remains essential for calculating the precise net amount owed each month, after applying statutory payment recoveries and Employment Allowance, and for reconciling internal records against HMRC’s employer account.

How Often Is A P32 Produced? 

A P32 is produced for each tax month in the payroll year, covering 12 periods from April to March. Most payroll software generates it automatically after every payroll run. For weekly, fortnightly, or four-weekly payrolls, the P32 aggregates all pay runs falling within that tax month.

What Is The Employment Allowance And How Does It Affect The P32? 

The Employment Allowance allows eligible employers to reduce their employer Class 1 National Insurance liability by up to £10,500 in the 2026/27 tax year. It is applied against employer NICs each pay period on the P32 until the full allowance is used. Once the £10,500 limit is reached, the full NIC liability is payable for the remainder of the tax year.

When Must HMRC Be Paid The Amount Shown On The P32? 

For most employers, the net payment shown on the P32 must reach HMRC by the 22nd of the following tax month if paying electronically (BACS, CHAPS, or Faster Payments), or by the 19th if paying by cheque. Small employers paying quarterly must pay by the 22nd of the month following the end of each quarter. Missing these deadlines results in interest charges and potential late payment penalties.

How Long Should P32 Records Be Kept? 

HMRC requires employers to retain payroll records, including P32 records, for a minimum of three years after the end of the tax year they relate to. Best practice is to retain them for six years, aligning with the standard HMRC investigation window and providing protection if a compliance review arises.

What Is The Difference Between The P32 And The FPS? 

The FPS (Full Payment Submission) is a real-time RTI submission sent to HMRC on or before each payday, reporting individual employee pay and deduction data. The P32 is an internal employer document that aggregates all FPS data into monthly employer-level totals and calculates the net payment due after recoveries and allowances. The FPS informs HMRC, the P32 verifies that what has been submitted translates into the correct payment.

What Happens If The P32 Figures Do Not Match HMRC’s Records? 

Discrepancies between your P32 totals and your HMRC online employer account indicate a mismatch between your internal records and what has been reported via RTI. Common causes include missing or duplicate FPS submissions, incorrect period allocation, or statutory payment recoveries not declared via EPS. Discrepancies should be investigated and corrected promptly, either by submitting an amended FPS or an EPS, to avoid underpayment penalties or interest.

Can I Generate A P32 Without Payroll Software? 

Yes, the P32 can be produced manually using a spreadsheet, following the same calculation structure as payroll software. However, the risk of manual calculation errors is significantly higher. HMRC’s Basic PAYE Tools, available free of charge, can generate a P32 equivalent for small employers with straightforward payrolls. For any business with more than a handful of employees, dedicated payroll software is strongly recommended.

What Is A Nil P32 And When Does It Apply? 

A nil P32 occurs when an employer has an open PAYE scheme but no employee payments in a given tax month, resulting in no PAYE or NIC liability. In this situation, no standard P32 with deductions is generated. The employer must instead submit an Employer Payment Summary to HMRC by the 19th of the following month, notifying HMRC that no payment is due. Failure to submit an EPS in a nil-payment month leaves HMRC expecting a payment that will not arrive.