Payroll Processing UK – Efficient & Accurate

Reviewed: 17 June 2026

Payroll processing is the recurring workflow used to calculate employee pay, apply deductions, produce payslips, report to HM Revenue & Customs (HMRC) and arrange payments. The employer remains legally responsible for accurate payroll even when software or an external provider carries out the work.

The payroll cycle

Collect authorised starter, leaver, hours, salary, overtime, bonus, leave and benefit information.
Validate employee records, tax codes, National Insurance categories and pension status.
Calculate gross pay, statutory deductions and employer costs.
Review exception reports and unusual changes.
Approve the payroll before releasing payments.
Issue itemised payslips on or before payday.
Send the Full Payment Submission to HMRC on or before payday.
Pay employees, pension providers and HMRC by the applicable deadlines.
Store reports, approvals and submission confirmations securely.

2026/27 checks

For 2026/27, employers should confirm the current tax codes, National Insurance thresholds, statutory-payment rates and minimum-wage rates before the first payroll of the tax year. The main employer National Insurance rate is 15% above the relevant threshold, and the employer secondary threshold is £5,000 a year.

Use HMRC employer rates and thresholds for 2026/27 and the National Minimum Wage rates.

Payroll inputs that need approval

New starters and leaving dates.
Changes to salary, hourly rates, working hours or bank details.
Overtime, commissions, bonuses and expense payments.
Sickness, family leave and other statutory absences.
Pension enrolment, opt-outs and contribution changes.
Benefits, deductions, attachments of earnings and student loans.

A clear cut-off date and named approver reduce late changes and incorrect payments.

RTI and HMRC payments

The Full Payment Submission is normally due on or before payday. An Employer Payment Summary may also be required for certain adjustments, recoveries or periods with no employee payments.

PAYE and National Insurance are usually due by the 22nd of the following tax month when paid electronically, or by the 19th when paid by post. Confirm the current process using HMRC payroll reporting guidance and PAYE payment guidance.

Review controls

Compare total gross pay and net pay with the previous period.
Investigate large or unexpected variances.
Confirm starters and leavers have been processed correctly.
Review negative pay, duplicate payments and manual overrides.
Reconcile payroll liabilities to the amounts paid.
Restrict who can amend employee and bank details.
Keep evidence of review and approval.

Common payroll mistakes

Processing unapproved changes.
Using outdated thresholds or tax codes.
Submitting RTI after payday.
Missing pension or statutory-payment changes.
Paying HMRC late.
Failing to reconcile payroll reports to bank payments and the accounts.

Software and outsourcing

Payroll software can automate calculations and submissions, but it depends on accurate setup and review. See Payroll Software Explained for UK Employers. Businesses considering an external provider should also read Outsourced Payroll Services UK.

This page provides general educational information, not personalised payroll, tax, employment or legal advice.

How a controlled payroll process works

Payroll processing is a sequence of data collection, calculation, review, reporting and payment. The software performs calculations, but the reliability of the result depends on the inputs, configuration and approval process. A payroll can be arithmetically correct and still be wrong because an employee, pay rate, absence, deduction or benefit was recorded incorrectly.

Step 1: establish the payroll timetable

Set a recurring timetable that identifies the employee payday, manager-input cut-off, calculation date, approval date, bank-payment date, pension submission date and HMRC payment date. The cut-off should leave enough time to investigate queries. Late changes should follow a documented exception process rather than being inserted informally.

Step 2: maintain employee master data

Master data includes names, addresses, National Insurance numbers, tax codes, pay basis, normal hours, National Insurance category, pension status, bank details and relevant statutory-leave information. Changes to sensitive fields should be independently checked. A request to change bank details should be verified through a trusted route rather than by replying to the same email that requested the change.

Step 3: collect and approve variable inputs

Hours, overtime and shift payments
Bonuses, commission and allowances
Unpaid leave and salary adjustments
Sickness and statutory family-leave information
Expenses, benefits and taxable reimbursements
Pension changes and salary-sacrifice instructions
Attachments of earnings, student loans and other authorised deductions
Starters, leavers and changes in director status

Each item should have an owner and evidence of approval. The payroll team should not be expected to decide whether an unapproved payment is contractually due.

Step 4: calculate gross-to-net pay

The calculation starts with taxable and non-taxable pay elements, then applies Income Tax, employee National Insurance, pension contributions and other deductions. Employer costs include employer National Insurance, employer pension contributions and possibly apprenticeship levy or benefit-related charges. Directors and certain categories of employee can require different National Insurance treatment.

For 2026–27, the standard personal allowance remains £12,570, the employer secondary threshold is £5,000 a year and the main employer National Insurance rate is 15%. The National Living Wage for workers aged 21 and over is £12.71 an hour from April 2026. These are only selected figures; payroll software and HMRC guidance should be checked for the employee’s category, location and circumstances.

Step 5: review the draft payroll

A reviewer should use an exception-based approach rather than checking only the total. Useful reports include:

Starters, leavers and employees with no pay
Changes to gross pay, net pay and employer cost
Negative pay, unusually high deductions or refunds
Tax-code and National Insurance category changes
Statutory pay and leave payments
Bank-detail changes
Employees below expected minimum-wage levels after considering the relevant rules
Differences between payroll, HR and pension records

The final approval should identify the version approved and be retained with the payroll file.

Step 6: report to HMRC

A Full Payment Submission tells HMRC about pay and deductions and is generally sent on or before payday. It should include everyone paid, even where pay is below the PAYE registration threshold described in HMRC guidance. An Employer Payment Summary may be needed to claim reductions such as statutory-pay recovery or to report that no employees were paid in a tax month.

Submission receipts should be retained. If information is wrong, the employer should follow the current correction process promptly rather than waiting until year end.

Step 7: make payments

Employee payment files, HMRC payments and pension payments should be reconciled to approved payroll reports. The person releasing the bank payment should see the approved control total and should not rely solely on a file supplied by the payroll processor. HMRC is generally paid by the 22nd after the end of the tax month when paying electronically, or by the 19th when paying by post, subject to the rules applying to the employer.

Step 8: post and reconcile payroll

Payroll journals should separate gross pay, employer National Insurance, pension costs, deductions and liabilities. Reconcile net pay to the bank, PAYE liabilities to HMRC records, pension deductions to provider submissions and payroll costs to management accounts. Unreconciled balances should not simply roll forward.

Year-end and employee documents

Year-end includes the final FPS indication, P60s for eligible employees, review of benefits reporting, checking carried-forward payroll data and loading new rates and thresholds. Employers should also review outstanding corrections and ensure leaver information has been processed.

Common processing failures

Running payroll before manager inputs are complete
Using the wrong effective date for a salary or hours change
Failing to tell payroll about a starter or leaver
Applying the wrong tax code or National Insurance category
Missing pension eligibility changes
Paying from an unapproved report
Submitting the FPS after payday without a valid reason
Correcting the employee’s pay but not the HMRC or accounting records

Related ASH guides

Official guidance

Special payroll cases

Some employees or payments require additional care. Directors may use an annual or alternative National Insurance method. Irregular-hours workers need reliable hours and holiday data. Employees working abroad or arriving from overseas can raise tax, social-security and payroll-location questions. Termination payments, benefits, salary sacrifice, tips and expenses may have different tax and reporting treatments. The payroll processor should escalate uncertainty instead of forcing an item into the nearest familiar pay code.

Corrections and off-cycle payments

A correction procedure should distinguish between an error found before approval, after approval but before payday, and after reporting or payment. Record the original figures, reason, corrected figures, authorisation, employee communication and any revised FPS, pension or accounting entry. Off-cycle payments should use the same approval and reconciliation standards as the main payroll.

Repeated corrections are a control signal. Classify their causes—late manager input, setup error, unclear policy, software configuration or provider failure—and address the recurring source.

Payroll evidence file

For each pay period, retain an organised evidence pack containing approved inputs, draft and final reports, exception review, submission receipts, payment evidence, pension output, journal and reconciliation. This makes employee queries, year-end checks and external review much easier than trying to reconstruct decisions from email.

In-house software or a payroll bureau?

In-house processing gives direct control but requires trained cover, software maintenance and disciplined review. A bureau can provide expertise and continuity, but the employer still needs accurate inputs and independent approval. The choice should reflect employee numbers, pay complexity, internal skills, data-security expectations and the cost of errors—not only the per-payslip fee.

Payroll quality questions

Can every material change be traced to an authorised instruction?
Can the reviewer explain the largest movements from last period?
Do HMRC and pension submissions reconcile to the approved payroll?
Are access rights and bank-detail changes independently controlled?
Are corrections analysed so recurring causes are removed?

Change control

Software settings, pay elements, pension rules and report mappings should not be changed without testing and approval. Record the reason, effective date, test result and person who approved the change. This is especially important at tax-year end and when moving to a new provider or integration.