United Kingdom · 2026-11-11

Payroll cut-off at Christmas 2026: an early FPS and changed pay

Keep the Christmas payroll plan current after an early FPS. Reconcile the calculation, payment file and reporting version without changing the usual payday.

What if the payroll amount changes after an early FPS?

An early submission is not a freeze on payroll facts. HMRC says changes can require a corrected FPS and directs employers to correct errors as soon as possible. Keep the payroll calculation, payment instruction and reported information linked to the same reviewed version. The usual payday recorded in the FPS remains distinct from an earlier bank payment date. The example below illustrates version control, not a prescription for completing correction fields.

Original control record: normal payday 25 December 2026

Record in this fictional planVersion before changeCheck after change
Payroll calculation£2,000 illustrative net payRevised approved calculation says £2,050.
Bank payment file£2,000 planned for 24 DecemberCheck whether it is draft, released or settled.
FPS already submitted earlyBased on earlier payroll factsUse the appropriate HMRC/software correction process.
Usual payday field25 December 2026Do not replace it with the date you corrected the record.

The £50 difference is a reconciliation flag, not an instruction to send another full £2,050. First establish whether the £2,000 payment is still editable or has already been processed, then confirm the appropriate action with the payroll system and payment provider. Do not infer the gross adjustment or tax deduction from this simplified net-pay difference. Record who approved the revised calculation, which file was released and which submission acknowledgement relates to the update. A bank receipt does not prove that HMRC received a correction; an FPS acknowledgement does not prove that employees received money. Avoid resubmitting blindly when a response is delayed. Keep the Christmas dates in the earlier planning table below, but replace its invented provider cut-off with the provider’s actual confirmed instructions.

Before closing the payroll record

https://ukworkingdays.com/payroll-cut-off-bank-holidays/

Christmas 2026: a fictional payroll planning record

RecordExampleMeaning
Normal paydayFriday 25 December 2026Usual payday in this fictional arrangement.
Planned actual paymentThursday 24 December 2026Earlier date, subject to provider confirmation.
FPS payment-date field25 December 2026Keep the normal payday for this holiday shift.
Internal approvalTuesday 22 December, chosen internallyA planning target, not an official provider cut-off.
Provider submission cut-offNot yet confirmedObtain exact date, time, time zone and processing requirements.
FPS submissionPlanned before the early paymentRetain the submission response separately from bank confirmation.

The 25th and Monday 28 December are bank holidays in the GOV.UK 2026 calendars. Thursday 24 December is not a listed UK bank holiday, but that does not establish your provider’s opening hours or processing capacity. In this original scenario, payroll remains unready until the provider confirms its cut-off and a named approver can meet it. A bank-file acknowledgement is not an HMRC FPS response. Record both outcomes, and flag a rejected file or changed amount for the responsible payroll operator. Do not replace the FPS payment-date field with the internal approval date.

Questions

Does a corrected FPS prove the bank payment has also changed?

No. They are separate records. Check the payment instruction and its outcome independently. Keep the relevant acknowledgements and do not mark both tasks complete from one confirmation.

Source and limits

HMRC, Running payroll: Reporting to HMRC, read 11 November 2026. Amounts and workflow example are original.

Independent UK planning checklist, not payroll or tax advice. No universal provider cut-off is asserted; use the actual software, payment service and HMRC instructions.

HMRC payroll corrections · UK holiday dates · Check a holiday deadline