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 eventRecord to retainControl before the next run
First pay on 6 NovemberCode and declaration actually usedKeep the submitted payroll history.
Late P45 received on 12 NovemberDocument received date and applicable detailsCheck whether an HMRC code has already arrived.
HMRC code notice received on 13 NovemberNotice and its instructionsReview the instruction before finalising payroll.
Next pay planned for 20 NovemberReviewed software record and action noteDo 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

https://ukworkingdays.com/late-p45-after-first-pay-checklist/

Choose the document branch before editing payroll

What arrived?First checkAudit note
HMRC code noticeIts applicable instructionNotice and payroll action date
Late P45, no HMRC codeP45 route and relevant tax yearFields reviewed in payroll software
Late starter checklist, no HMRC codeDeclaration update; retain first-FPS codeAnswers 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

HMRC, Late P45 or starter checklist, read 12 November 2026. The page still displays 2025 year cutoffs; they have not been relabelled as 2026–27 rules.

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.

Review the starter declaration · Plan the payroll cut-off