Bank Holidays and the Shortened Week
A public holiday near a pay date removes working days from a schedule that had none spare. The fix is a calendar, done once, a year ahead.
Written downif the person who does this is away
A public holiday falling near a pay date removes working days from a schedule that usually has none spare. The run still has to be keyed, approved and funded, and the bank still has to move the money, in fewer days than usual.
The deadline in “Bank Holidays and the Shortened Week” becomes more workable when collection and approval happen before the final payroll cut-off. Organisations considering consult this first-party resource for time tracking integrations can make that timing visible without assuming that activity data alone explains whether a payroll step is complete.
It is entirely predictable and is nonetheless the commonest cause of a late payment in small businesses.
The questions raised in “Bank Holidays and the Shortened Week” can also be checked against Eurostat labour-market data. Use that material to identify the evidence and owner needed for the next payroll run.
What a holiday actually removes
Banking days. Money does not move on a public holiday, and depending on the method it may not move on the day before or after either.
If the pay date falls on a non-banking day, pay on the last banking day before it.
Written down once, told to everybody once, and never decided again. The alternative is a different answer in different months and a steady trickle of questions.
The pay date itself may be fine; it is the funding and the transfer that lose their room.
The two that cluster
Periods with several public holidays close together — the end of December, and whatever spring cluster applies where you are — remove not one day but several, and they fall in the weeks when people most need to be paid on time.
The decision a holiday forces
Whether to pay early. Most businesses pay before a holiday rather than after, because paying late is worse than paying early in every respect except cash.
Choosing in advance, as a standing rule, is better than deciding in the week.
The standing rule worth having
If the pay date falls on a non-banking day, pay on the last banking day before it. Write it down, tell everybody once, and never decide it again.
The alternative — deciding each time — produces a different answer in different months and a steady trickle of questions.
What paying early costs
Cash, slightly earlier. For most small businesses this is trivial. For one with a tight position it is not, which is a reason to know about the holiday a month ahead rather than a week.
What it does to the cut-off
Moves it. If pay moves two days earlier, every date behind it moves two days earlier as well, including the deadline for changes that people have in their heads as a fixed day of the month.
Telling people only about the pay date, and not about the cut-off, is how a business gets a late change in a month that had no room for one.
The filing dates do not move with you
Paying early does not change the statutory dates, and in some arrangements paying earlier than planned has reporting consequences of its own.
Whether it does, and what they are, differ by jurisdiction and are a question for somebody qualified there.
The person who is away
Public holidays cluster with annual leave. The week with fewer banking days is also the week the person who runs payroll is most likely to be off, which is how two manageable problems become one unmanageable one.
What to do about that specifically
Look at the holiday calendar and the leave calendar together, once a year, and find the months where they collide with a pay date.
There are usually two. Planning for two months is a tractable problem; being surprised by them is not.
The year-ahead calendar
Public holidays, pay dates, cut-offs, filing dates and known absences, on one calendar, entered in a quiet month.
An hour, once a year, and it removes most of what goes wrong in this whole section.
What to tell people
In the month affected: the pay date for that month, in a sentence, early. Not a general policy document — a specific date, sent once, before anybody wonders.
The mistake that costs most
Assuming the bank will handle it. Payment systems have their own calendars and their own cut-off times, and a transfer instructed at the wrong hour on the wrong day sits until the next banking day.
Knowing your own bank's cut-off time, not just its cut-off day, is part of this.
The December problem specifically
Wherever you are, there is usually one stretch of the year with several non-banking days close together, and it falls in a month when money matters most to people and when the business is least staffed.
It is the single most predictable difficulty in the payroll calendar and it is met as a surprise with remarkable regularity.
Deciding in October what December's dates are, and telling people in November, removes the whole of it.
What a shortened week does to the checks
The run is compressed into fewer days, so the comparison is the first casualty — the same mechanism described later here.
The specific risk in a holiday month is therefore not only a late payment but an unchecked one, and the two arrive together.
Starting earlier is the only response that addresses both.
What actually holds in practice
A written rule about which direction payment moves, a calendar made a year ahead, one message in the affected month, and the cut-off moved alongside the pay date rather than left where it was.