How do accounting practices handle year-end payroll reporting and P60 distribution?

Payroll year-end isn’t one task, it’s a sequence of legally mandated steps that must happen in a specific order, to fixed deadlines, across every client on your books. HMRC’s payroll year-end guidance sets out the obligations clearly enough for a single employer, but for bureaus, that same sequence is for 50, 80, or 150 employer clients in parallel (each at a slightly different stage, each with their own employee count, pay frequency, and benefits).

The bureaus that come through year-end without drama are the ones with a standardised checklist applied to every client, a clear timeline communicated to clients well before the 5th of April, and software that handles the high-volume mechanics of generating P60s and FPS reconciliations without manual intervention for every employer on the book.

The year-end payroll checklist: What needs to happen and when

Every employer client requires the following steps to be completed in sequence:

Each step has a fixed penalty for late completion. If you miss the final FPS deadline without a nil EPS to cover the gap, HMRC may issue a late filing penalty. Fail to issue P60s by the 31st of May and the employer faces a penalty of up to £300 per instance. Late P11D submission attracts an automatic £100 per 50 employees penalty for each month or part month the return is outstanding. For a bureau managing employer clients at scale, these are exposures that compound quickly if your workflow isn’t tightly controlled.

The final FPS: What to check before submission

The final Full Payment Submission (FPS) for the tax year is the most consequential payroll filing of the year. It tells HMRC the definitive figures for every employee, including their total pay, income tax deducted, NI contributions, and student loan deductions, which feed directly into each employee’s tax record. Errors in the final FPS can cause problems downstream like incorrect tax codes in the new year, employee queries about P60 figures, and HMRC reconciliation discrepancies that take time to resolve.

Before the final FPS is submitted, bureaus should run through a pre-submission checklist for each employer client:

• Year-to-date pay figures reconcile to payslip history

• All starter and leaver records are correctly flagged, with P45 figures accurately reflected

• Any mid-year corrections or adjustments have been reconciled and are reflected in the cumulative figures

• The ‘final submission for year’ indicator is marked on the FPS (or the bureau is filing a nil EPS immediately after)

• Any statutory payments are correctly recorded and the recovery amounts are accurate

Bureaus running multiple employer clients through the same payroll platform should complete this reconciliation before pushing the final FPS for each employer, not afterwards. An error discovered after submission requires a correction through an additional FPS in the new tax year, which creates a mismatch between the original filing and the amended record and can confuse the employee’s tax position going into the next year.

P60s: the mechanics of issuance at bureau scale

A P60 must be issued to every employee who was in employment on the 5th of April, regardless of whether they’ve been on sick leave, maternity leave, or long-term absence, and regardless of whether they received a payslip in the final period.

The deadline is the 31st of May, and the P60 must show total pay for the year, total tax deducted, NI category and contributions, and any student loan deductions.

For a bureau managing 80 clients with an average of 15 employees each, that’s 1,200 P60s to generate, quality-check, and distribute by the 31st of May. On paper, it’s impractical, but electronically, it’s straightforward.

Well, provided that the payroll software automatically handles generation and distribution.

BrightPay by Bright automatically generates P60s at year-end and distributes them to employees. Employees can then log in and access their P60 directly. For bureaus distributing P60s across a large employer portfolio, that’s the difference between year-end P60 distribution being a two-day admin exercise versus and a 30 minute process.

P11D preparation: the data collection challenge

P11Ds are the year-end filing for benefits in kind, like company cars, private medical insurance, gym memberships, and any other non-cash benefit provided to employees that hasn’t been processed through payroll.

The filing deadline is the 6th of July, which feels comfortably distant after the P60 rush, but the data collection process needs to start well before that.

A structured data request sent to every employer with employees likely to have reportable benefits, issued in early May, with a clear response deadline of the 1st of June. The request should be specific. List the benefit types, ask for the values per employee, and ask about any changes in benefit provision during the year. Bureaus that send this request consistently every year find P11D season far less pressured than those that treat it as an ad hoc collection exercise.

For employers whose employees have regular, recurring benefits (company cars being the most common) encouraging the employer to payroll those benefits from the start of the next tax year removes the P11D filing requirement for those benefits entirely. Payrolling brings the tax charge into real time through the payslip, eliminating the annual filing step. BrightPay by Bright supports payrolling of benefits through the payroll run.

Client communication: what to send and when

A well-run payroll bureau communicates the year-end timeline to employer clients before the process begins, not during it. A short client communication sent in mid-March that sets out the final payroll run dates, the P60 distribution timeline, and what the employer needs to provide for P11D purposes, removes most of those unexpected last-minute queries.

The employers most likely to cause year-end problems are those who make late payroll changes. Setting a clear cutoff date for year-end payroll changes is one of the most effective operational controls available to a bureau.

How does BrightPay by Bright compare to alternatives for bureau-scale year-end payroll?

The main alternatives for payroll bureau management in the UK market are Sage, IRIS, Xero, and Moneysoft. Sage Payroll is widely used for larger employer clients and has solid year-end functionality, but its bureau pricing model is less competitive at the smaller end of the market. IRIS Payroll Professional has strong compliance functionality suited to mid-to-large bureaus. Moneysoft is popular with smaller practices for its clean interface and cost efficiency. Xero Payroll integrates well within the Xero ecosystem but is designed primarily for individual employers rather than bureau operations.

BrightPay by Bright is payroll software built specifically for bureaus with multiple clients that want to manage their portfolio within one platform. It comes with automated P60 distribution, employee self-service, and a bunch of batch capabilities that make your month that bit easier.

BrightPay by Bright handles the full year-end sequence from a single platform. Book a demo below to see how the year-end workflow operates across a full employer portfolio.

This content may have been developed with the assistance of AI tools. Content is reviewed by a member of the Bright team before publication. Guidance on legislation can be obtained from your industry body.