Payroll Reconciliation: A Practical UK Employer Guide
PAYE and National Insurance owed to HMRC must clear by the 22nd of the month when paid electronically, and any Employer Payment Summary claiming a reduction has to arrive by the 19th of the following tax month to be applied [1][2]. Those two dates sit three days apart, and the gap between them is where payroll reconciliation lives.
Reconciliation is the process of proving that three separate records agree: what the payroll system calculated, what HMRC believes is owed, and what actually left the bank account. When they agree, the month closes cleanly. When they do not, the difference compounds into the next period and eventually into the year-end return.
This article is written for accountants, payroll bureaux and finance teams responsible for closing a PAYE scheme each month. It covers the role of the P32, the reductions that legitimately lower a PAYE bill, the monthly cycle and its deadlines, and the route HMRC offers when its figures and the employer's figures refuse to meet.
Key takeaways
- Payroll reconciliation proves that the payroll calculation, HMRC's liability record and the bank payment all agree for a given tax month [3].
- The P32 employer payment record is an internal reconciliation document built from FPS and EPS figures, and is not itself submitted to HMRC [4].
- An EPS must reach HMRC by the 19th of the following tax month for any reduction, such as recovered statutory pay, to be applied to the bill [2].
- Employers whose Class 1 National Insurance liability is £45,000 or less qualify for Small Employers' Relief and recover 100% of most statutory payments plus 9% compensation [5][6].
- Payroll records must be kept for three years from the end of the tax year they relate to, and inadequate records can attract a penalty of up to £3,000 [7].
What payroll reconciliation means in a UK PAYE scheme
Reconciliation in payroll is narrower and more mechanical than reconciliation in general accounting. It is not an investigation into whether staff were paid the right amount, which is a separate control. It is the check that the liability generated by the payrun, the liability HMRC has recorded, and the cash actually paid across are the same number for the same tax month [8].
Real Time Information makes this both easier and less forgiving. HMRC's record of what an employer owes is built directly from the submissions sent on or before each payday, so there is no lag and no opportunity to tidy the figures before they land [3]. The upside is that the employer can see the liability form in real time. The downside is that an error in a submission becomes an error in HMRC's ledger immediately [9].
The three records that must agree
The first record is the payroll calculation itself: gross pay, income tax, employee and employer National Insurance, student loan deductions and pension contributions for every employee in the period. The second is HMRC's liability, derived from the FPS and adjusted by any EPS [3]. The third is the bank payment made against the Accounts Office reference [1].
A reconciliation is complete when a single figure ties all three together with a documented explanation for every difference. Most unexplained differences turn out to be timing rather than error: an EPS submitted after the 19th, a correction applied to a different month, or a payment allocated to the wrong period [4].
Why the FPS and EPS both matter
The Full Payment Submission reports what each employee was paid and what was deducted, and it is what creates the gross liability [3]. The Employer Payment Summary works in the opposite direction, reporting scheme-level reductions such as recovered statutory pay and the Employment Allowance [2].
An employer who files the FPS but forgets the EPS will be billed the gross amount with none of the reductions applied. This is the single most common cause of a PAYE bill that looks too high, and it resolves itself only once the EPS arrives [4]. Because the EPS is a separate return with a separate deadline, reconciliation has to treat it as a distinct step rather than assuming it went out with the payrun.
The P32, the employer's own reconciliation record
The P32 employer payment record is the working document that makes reconciliation possible. It sets out the total liability due to HMRC for the period, built from the figures in the FPS and the EPS. Critically, the P32 is an internal record and is not submitted to HMRC, which is precisely what makes it useful: it is the employer's independent statement of what it believed it owed, ready to be compared against HMRC's version [8].
What the P32 contains
A complete P32 breaks the period's liability into its components rather than showing a single total. The table below sets out the standard lines and what each represents.
| P32 line | What it represents | Direction |
|---|---|---|
| Income tax deducted | PAYE withheld from employees in the period | Increases liability |
| Employee National Insurance | Primary Class 1 contributions | Increases liability |
| Employer National Insurance | Secondary Class 1 at 15% above the Secondary Threshold | Increases liability |
| Student loan deductions | Plans 1, 2, 4, 5 and postgraduate loans | Increases liability |
| Statutory payments recovered | SMP, SPP, SAP, ShPP, SPBP and SNCP recovery | Reduces liability |
| Small Employers' Relief compensation | Additional 9% for qualifying employers | Reduces liability |
| Employment Allowance | Annual allowance against employer Class 1 | Reduces liability |
Sources: HMRC guidance on paying PAYE and recovering statutory payments [1][5].
The employer rate of secondary Class 1 National Insurance sits at 15% on earnings above the Secondary Threshold, which makes the employer NI line the largest single component of most P32s [10]. Any misapplied NI category letter therefore has an outsized effect on the reconciliation, which is one reason the category letter is worth checking as a standing control [10].
When to produce it
Sequence matters. The P32 should only be produced after both the FPS and any EPS for the period have been submitted, because it is built from those figures and will otherwise show a liability that HMRC does not recognise [2]. Producing it before the EPS is the most common way to manufacture a phantom discrepancy.
The practical discipline is to save or print the P32 at the end of each tax reporting period and file it with the period's submissions. Accountants running this across many client schemes usually automate the step through a multi-client payroll dashboard so that the record is generated in the right order every time, rather than depending on an administrator remembering the sequence under month-end pressure [8].
What legitimately reduces the PAYE bill
A reconciliation that treats the FPS total as the amount payable will always overstate the liability for employers entitled to reductions. Two reductions account for most of the gap.
Statutory payment recovery and Small Employers' Relief
Employers can reclaim a proportion of the family-related statutory payments they make. The standard recovery rate is 92% of Statutory Maternity Pay and the equivalent family payments [5]. Employers who qualify as small recover the full amount plus a compensation uplift, which HMRC set at 9% from 6 April 2026 [5].
Qualification turns on a single threshold. An employer is small for this purpose where total gross Class 1 National Insurance, counting both primary and secondary liability, is at or below £45,000 in the qualifying tax year [6][11]. The comparison is set out below.
| Employer status | Class 1 NICs in qualifying year | Recovery rate |
|---|---|---|
| Small employer | £45,000 or less | 100% plus 9% compensation |
| All other employers | Above £45,000 | 92% |
Sources: HMRC statutory payments manual and recovery guidance [5][6].
One exclusion catches people out during reconciliation. Statutory Sick Pay is not recoverable at all, whatever the employer's size, so an SSP cost sits in the payroll as an unrecovered expense and should never appear as a reduction on the P32 [5].
Employment Allowance
The Employment Allowance reduces an employer's secondary Class 1 National Insurance liability, and it is claimed through the EPS. It is not automatic and it does not roll forward: the claim must be made for each new tax year by submitting an EPS [12]. A scheme that claimed successfully in one year and assumes the claim persists into the next will reconcile against a bill that is higher than expected.
Ordering matters when the allowance is applied. HMRC's guidance is that the Employment Allowance comes off employer secondary Class 1 liabilities before any other amounts are deducted, including recoverable statutory pay [13]. Applying the reductions in the wrong sequence produces a P32 that is arithmetically defensible but does not match HMRC's calculation, and the reconciliation then fails for no substantive reason [12].
The monthly reconciliation cycle
The reconciliation cycle is governed by a small set of fixed dates. Building the month-end routine around them removes most timing-related discrepancies before they arise.
The dates that govern the cycle
| Obligation | Deadline |
|---|---|
| Send the FPS | On or before the day employees are paid |
| Send the EPS for reductions to apply | 19th of the following tax month |
| Electronic payment to clear at HMRC | 22nd of the month |
| Postal payment to reach HMRC | 19th of the month |
| Quarterly payment (schemes under £1,500 per month) | 22nd after the quarter ends |
Sources: HMRC guidance on paying and reporting to HMRC [1][2].
Smaller schemes have an option worth reviewing during reconciliation. Where an employer usually pays less than £1,500 per month, it may pay quarterly rather than monthly, with the deadline falling on the 22nd after the quarter ends [1]. Quarterly payment reduces the number of reconciliation events but lengthens the period over which an unnoticed error can accumulate [8].
The practical sequence
A workable month-end sequence runs in the same order every period. The payrun is calculated and approved, the FPS is submitted on or before payday, any EPS is submitted by the 19th, the P32 is produced from the resulting figures, the P32 is compared against HMRC's online liability record, and the payment is made to clear by the 22nd [1][3].
The comparison step is the one most often skipped, and it is the one that gives the process its value. Employers running higher volumes or multiple entities frequently pull the liability figures programmatically rather than checking each scheme by hand, which is where an HMRC-recognised payroll API earns its place: the expected liability, the submitted figures and the payment can be compared automatically and the variance surfaced as an exception. Larger multi-entity groups managing this at scale can review the approach set out for enterprise payroll, and developers can browse the endpoints in the API documentation.
When the records disagree
Some discrepancies survive the routine. HMRC sets a practical checkpoint for these: if the PAYE bill is still wrong by the 12th of the next tax month, the employer should ask HMRC for help rather than continuing to investigate alone [4].
HMRC's correction service
HMRC operates a dedicated route for employers who cannot reconcile a PAYE bill. On request, HMRC will make contact by email within 40 working days, providing the FPS information it holds together with a help card to work through the payroll records [14]. Because the service supplies HMRC's own view of the submissions received, it usually identifies the mismatch quickly, most often a duplicate employment record or a submission allocated to an unexpected month [4].
The 40-working-day response window is itself a reason to raise the query early rather than at year end. A discrepancy escalated in month two is resolved well before the P60 run, whereas the same discrepancy escalated in month eleven collides with year-end deadlines. Employers preparing for that stage can work through the Moonworkers P60 end-of-year checklist.
Record keeping underpins the whole process
Reconciliation is only defensible if the underlying records survive. Payroll records must be kept for three years from the end of the tax year to which they relate, and HMRC may inspect them to confirm the right amount of tax was paid [7]. Where records are incomplete, HMRC may estimate the liability and charge a penalty of up to £3,000 [7].
If records are lost and cannot be replaced, the obligation is to tell HMRC as soon as possible and to make a genuine attempt to recreate them [7]. Retaining the P32 alongside the submission receipts for each period is the simplest way to make a later reconstruction possible, because it captures the employer's contemporaneous view of the liability [9].
Automating the reconciliation
Reconciliation is a control, and controls that depend on manual repetition degrade. The components that automate well are the ones with fixed rules: producing the P32 only after the EPS, applying the Employment Allowance before statutory recovery, excluding SSP from recoverable amounts, and comparing the calculated liability against HMRC's record before the payment is released [13][5].
Payroll software carrying the HMRC Recognised badge files the FPS and EPS in the correct sequence and derives the P32 from the submitted figures rather than from a parallel calculation, which removes an entire class of discrepancy. For growing businesses running their own schemes, HMRC-recognised payroll software makes the monthly close a review rather than a rebuild. Employers whose liability is dominated by a large pay bill may also want to read the Moonworkers explanation of the apprenticeship levy, which adds a further line to the reconciliation above the levy threshold.
Conclusion
Payroll reconciliation is not a search for errors so much as a discipline of sequence. The FPS creates the liability, the EPS reduces it, the P32 records what the employer believes is owed, and the bank payment settles it, each with its own deadline. Discrepancies that look alarming almost always trace back to one of those four steps happening in the wrong order or after its cut-off, rather than to a miscalculated payslip.
The practical implication is that the strongest reconciliation control is not a more forensic month-end review but a process that cannot run out of order. As Real Time Information reporting continues to tighten and employer National Insurance remains the dominant line on most P32s, the schemes that close cleanly each month are those where the sequence is enforced by the system rather than remembered by a person.
Frequently asked questions
What is a P32 and does it have to be sent to HMRC?
The P32 employer payment record is a breakdown of the total liability due to HMRC for a tax period, assembled from the figures in the Full Payment Submission and the Employer Payment Summary. It is an internal reconciliation record and is not submitted to HMRC [8]. Its value is precisely that independence: it gives the employer its own statement of the liability to compare against HMRC's, which is what makes a discrepancy visible.
Why is my PAYE bill higher than the amount my payroll calculated?
The most frequent cause is a missing or late Employer Payment Summary. The FPS creates the gross liability, and reductions such as recovered statutory pay and the Employment Allowance are only applied when the EPS arrives by the 19th of the following tax month [2]. If the bill is still wrong by the 12th of the next tax month after checking the submissions, HMRC should be asked for help [4].
How much statutory maternity pay can an employer reclaim?
Most employers reclaim 92% of the family-related statutory payments they make [5]. Employers whose total gross Class 1 National Insurance is £45,000 or less in the qualifying tax year meet the Small Employers' Relief test and reclaim the full amount plus 9% compensation [6]. Statutory Sick Pay is the exception and cannot be reclaimed by any employer.
How long must payroll records be kept in the UK?
Payroll records must be kept for three years from the end of the tax year they relate to, and HMRC may inspect them to confirm the correct amount of tax was paid [7]. Where records are not kept, HMRC may estimate the amount owed and charge a penalty of up to £3,000. Many employers retain records for six years instead, to align with the general limitation period for contractual claims.
Image prompt for Imagen (also in frontmatter)
A wide landscape photograph of an accountant's desk in a bright UK office, two monitors showing columns of figures beside a printed reconciliation report and a mug of tea, late afternoon window light, neutral greys and warm wood tones, shallow depth of field, realistic documentary photography, no text, no logos, 16:9
