PAYE payroll records to keep

PAYE records should explain pay, deductions, benefits and the information reported to HMRC for each employee. Retain the supporting calculations and approvals so a later query can be resolved without reconstructing the payroll from net bank payments.

Keep a consistent employee identifier and preserve year-to-date figures. Record corrections and avoid overwriting the history of approved payroll changes.

Keep the calculation behind the payment

A useful payroll file connects the approved input, calculation, payslip, HMRC report and payment. For hourly staff, the input may be an authorised timesheet; for salaried staff, it may be a contract and a change instruction. Preserve those connections so someone can explain a particular period later. A bank statement shows what the employee received, but not why the gross pay or deductions were correct.

HMRC requires PAYE records supporting pay, deductions, reports, payments and relevant employee information. Its general PAYE retention period is three years from the end of the tax year concerned, while other record obligations can differ. Do not apply that period indiscriminately to every employment, pension or minimum-wage document. Create a retention schedule that distinguishes the purposes and requirements of each record category. ^[1]

Organise records around a stable identifier

Give each employment a consistent payroll identifier and use it across change forms, reports and reconciliations. Names can change, and several employees can share similar names, so a name-only folder structure is vulnerable to confusion. Record legitimate identifier changes carefully, especially during software migration. The file should make it possible to trace the same employment without accidentally combining two people or creating duplicate year-to-date totals.

Within each pay period, save the approved input and final output separately from drafts. Mark superseded calculations clearly rather than deleting the history of a correction. Include who approved the final version and when. If a manager changes a bonus after approval, retain the revised instruction and explain how payroll dealt with it. This prevents a later reviewer from assuming that the first spreadsheet received was the amount actually authorised.

Preserve notices and exceptional calculations

Keep tax code notices, starter information, leaving instructions and the dates on which they were received or applied. For statutory pay, director calculations or unusual deductions, retain the supporting facts and working. Software output can be useful, but it may not explain why a particular eligibility setting was selected. A brief factual note is valuable when the decision depends on dates or circumstances outside the payroll system.

Record the basis for any manual adjustment and the person who checked it. Avoid generic descriptions such as 'payroll fix' where a more precise explanation is possible. State the affected employee, period, field and reason, while restricting sensitive detail to the appropriate file. The general payroll journal does not need to reproduce private health information simply because an absence affected pay.

Reconcile reports and settlements

At each payroll cycle, compare the final payroll totals with the submitted report and the employee payment instruction. Separately reconcile the amount payable to HMRC, taking account of relevant adjustments or credits. Save acknowledgements and investigate rejected submissions. A folder full of generated reports does not prove that HMRC accepted the intended version, so the submission evidence should be identifiable alongside the calculation.

Maintain a list of differences that remain open after the routine reconciliation. Give each item an owner and expected resolution date. Examples include an employee payment returned by the bank, a notice received after processing or an unexplained HMRC allocation. Keep those operational items separate from the completed payroll totals, making it clear whether the underlying calculation, reporting or settlement still requires action.

Make records retrievable without broad access

Test whether an authorised colleague can retrieve one employee's historical calculation without opening the entire workforce's private information. Use role-based access and a clear file index. Back up records appropriately and ensure exports remain usable if a provider or software subscription changes. An archive that depends on a departed employee's personal login is not a dependable business record, even if the files technically still exist.

Read Payroll data protection and access controls for payroll access and data-protection controls, and contact Payroll administration to discuss a record-keeping review. Start with the systems used, missing periods and the type of query the business cannot currently answer. A focused review can then identify whether the gap lies in source instructions, calculation evidence, submissions or payment reconciliation, rather than requesting every payroll document without a clear purpose.

Where records have been lost, document what is missing and the steps taken to reconstruct it. Seek advice about any notification or reporting implications. Recreated schedules should be labelled as reconstructions, with their sources and uncertainties visible, so they are not mistaken for original contemporaneous evidence.

Illustrative scenario

A payroll administrator receives a query about an earlier bonus. The retained approval, calculation and submission record show how the payment was processed and which deductions were applied.

Preparation checklist

• Retain pay calculations
• Keep change approvals
• Preserve submission receipts
• Control access and retention