Payroll · corrected FPS

Corrected FPS after a payroll mistake: fix the record without creating a second problem.

When a payroll error is found after submission, the operational risk is not just the original mistake. This checklist helps record what changed, which FPS is affected and how the correction is evidenced.

SEO focus

corrected FPS payroll error checklist

Reduce UK payroll correction mistakes after FPS submission. Updated 2026-06-22.

Checklist controls

StepWhat to checkWhy it matters
Original FPSEmployee, pay date, tax month and submitted values.Defines the record being corrected.
Error typePay, deduction, start/leaving date or employee detail.Different errors may follow different software routes.
Correction routeNext regular FPS, additional FPS or software-specific action.Avoids duplicate or late-reporting issues.
TimingTax month and deadline for the correction to affect PAYE bill.Controls reconciliation.
Audit noteReason, source evidence and person who approved change.Makes later payroll review defensible.

Record

Correct the exact FPS.

Do not treat every correction as a new starter or new payment.

Timing

Tax month matters.

A technically correct change can still reconcile in the wrong period.

Boundary

Software differs.

Use HMRC rules and the payroll product workflow together.

FPS correction workflow

  1. Find the submitted FPS and affected employee record.
  2. Classify the error and supporting evidence.
  3. Choose the correction route in payroll software.
  4. Record the tax month and submission timing.
  5. Save a short audit note with before/after values.

FAQ

Can I just fix it in the next payroll?
Only if that matches HMRC guidance and your software workflow for that error type.
Does every error need an additional FPS?
No. The route depends on the error and timing.
Is this official payroll instruction?
No. HMRC guidance controls.

Updated 2026-06-22. This page is independent and does not replace official services, professional advice or site-specific rules.