United Kingdom · 2026-11-12
Late P45 after first pay: check new HMRC instructions before payroll
Use a dated audit trail when a late P45 and an HMRC code notice arrive before the next pay run. Keep document receipt and payroll action separate.
What if an HMRC tax-code notice arrives after the late P45?
Recheck the applicable HMRC instruction before finalising the next payroll. HMRC’s late-document guidance says to use the code it has sent when a P45 or starter checklist arrives after first pay. Do not overwrite that instruction merely because a P45 has been uploaded again. Keep the document history and the payroll action history separately, including the relevant tax year and any effective instructions.
Original event log: one employee, several documents
| Fictional event | Record to retain | Control before the next run |
|---|---|---|
| First pay on 6 November | Code and declaration actually used | Keep the submitted payroll history. |
| Late P45 received on 12 November | Document received date and applicable details | Check whether an HMRC code has already arrived. |
| HMRC code notice received on 13 November | Notice and its instructions | Review the instruction before finalising payroll. |
| Next pay planned for 20 November | Reviewed software record and action note | Do not enter another start date on the next FPS. |
These dates are an audit example, not HMRC processing deadlines. If someone reviewed the P45 on the 12th, mark that review with its date; it does not prove that the record remained correct after the notice arrived on the 13th. A useful private note identifies the document considered, the instruction applied, the fields actually changed and the reviewer. A second upload of the same P45 is not another employment start. If a late starter checklist arrives instead of a P45, follow its separate route in the comparison below. Do not copy prior pay and tax figures into the current year just because the document is newly received. Where year-specific fields or software corrections are unclear, check the current HMRC route and payroll support before closing the review.
Before closing the payroll record
- Keep the first payment and FPS record intact as history.
- Distinguish a P45, starter checklist and HMRC code notice.
- Recheck new instructions before the next payroll is finalised.
- Record changes without creating another start date on the next FPS.
https://ukworkingdays.com/late-p45-after-first-pay-checklist/
Choose the document branch before editing payroll
| What arrived? | First check | Audit note |
|---|---|---|
| HMRC code notice | Its applicable instruction | Notice and payroll action date |
| Late P45, no HMRC code | P45 route and relevant tax year | Fields reviewed in payroll software |
| Late starter checklist, no HMRC code | Declaration update; retain first-FPS code | Answers changed and reason |
Example audit note: “First pay processed using the starter declaration. A starter checklist arrived later; no new HMRC code received. Declaration reviewed; existing FPS code retained pending HMRC instruction.” A P45 arriving in the same folder is a separate event to assess, not a reason to silently replace this note.
Questions
Is the document received last always the one that controls the tax code?
No. Identify the document type and the applicable HMRC instruction. An old P45 uploaded again does not become a new code notice. HMRC also treats a late starter checklist differently from a late P45 when it has not sent a code.
Source and limits
Independent UK payroll checklist, not individual tax advice. Confirm current tax-year fields, student-loan handling and effective code instructions with HMRC or your payroll provider.