Payroll · late FPS

FPS late submission reason: record the payroll timing before the next report.

A late FPS can create a compliance trail that is hard to explain later. This checklist helps record what happened, which payday was affected and which evidence supports the reason.

SEO focus

FPS late submission reason checklist

Reduce UK payroll reporting mistakes after late FPS submissions. Updated 2026-06-20.

Checklist controls

StepWhat to checkWhy it matters
PaydayActual pay date and tax month.FPS timing is tied to payday.
ReasonWhy the FPS was late or corrected.Supports the audit note and any follow-up.
Employee setWhich employees and payments are affected.Avoids over-correcting unrelated records.
SubmissionWhether software sends a late reason or correction route.Keeps HMRC reporting consistent.
EvidencePayroll run, approval, system issue or bank timing proof.Explains the late trail later.

Timing

Payday first.

The calendar question starts from the payment date.

Scope

Affected records only.

A late FPS issue should not disturb unrelated payroll data.

Boundary

Software differs.

Use HMRC rules and your payroll product workflow together.

Late FPS control workflow

  1. Find the affected payroll run and payday.
  2. Write the late-submission reason in one sentence.
  3. Identify employees and payments included.
  4. Follow the software route for late FPS or correction.
  5. Save evidence and before/after submission details.

FAQ

Does every late FPS need the same reason?
No. The reason should match what happened for that pay run.
Can I correct it in the next FPS?
Only if that matches HMRC guidance and your payroll software workflow.
Is this official payroll instruction?
No. HMRC guidance controls.

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