The Date You Chose Once
The pay date was picked in week one and never revisited. It silently sets five other deadlines, and some choices of date are much worse than others.
Written downif the person who does this is away
What the pay date drags behind it, in one business paying monthly on the 25th
If missed: Keying starts late, and the comparison with last month is the first thing dropped
If missed: A rate rise lands a month late and is then owed in arrears
If missed: No slack left before the filing, and no time to check
If missed: A penalty, and it does not scale down because the employer is small
If missed: The payment fails on the 25th and fourteen people notice within the hour
If missed: People chase, trust goes, and somebody's rent is late
Six dates, and only the last one was ever chosen deliberately. One small employer's own calendar; which statutory dates apply, and what missing them costs, differ by jurisdiction.
The pay date in most small businesses was picked in the first week of having employees, for no particular reason, and has never been looked at again. It sets five other deadlines behind it, and some dates make all five harder than they need to be.
The deadline in “The Date You Chose Once” becomes more workable when collection and approval happen before the final payroll cut-off. Organisations considering follow the official implementation guide for clock in and clock out app can make that timing visible without assuming that activity data alone explains whether a payroll step is complete.
Changing it later is possible and awkward, which is an argument for thinking about it once rather than never.
Additional context for “The Date You Chose Once” is available from CIPD pay-structures factsheet. A sound review distinguishes general practice from the rules and records that apply to one employer.
What the date actually fixes
Working backwards from it: when the money has to be in the account, when the run has to be approved, when it has to be keyed, when changes have to be in, and when hours have to be in.
None of those were chosen. They follow.
Paying on the last day of the month
Common and awkward. Month end collides with everything else that happens at month end — invoicing, reconciliation, a sales push — and the payroll cut-off lands in the busiest week.
It also makes the gap between the cut-off and the end of the month very short, so late changes have nowhere to go.
The first of the month
Clean for employees and inconvenient for you: the run has to be keyed and funded before the previous month has closed, and anything that happened in the last few days arrives too late.
Mid-month
Underrated. A pay date around the 20th to 25th puts the cut-off in a quiet stretch, keeps the run away from month-end accounting, and leaves several working days of slack before the date itself.
The cost is that it looks unusual to new employees, which lasts one month.
A Friday
Good for weekly pay, mixed for monthly. A fixed weekday means the date moves each month, which makes the backward schedule move too, and makes it harder to hold a habit.
What makes a date bad
Collisions. With month end, with your busiest trading week, with the statutory filing deadline falling the next day, or with the day the person who runs payroll is routinely elsewhere.
Any of those turns four calm hours into a scramble every month, for years.
The slack worth having
At least two clear working days between approving the run and the money leaving. That is what absorbs a bank holiday, a failed payment, a correction found late, or somebody being off.
Businesses with no slack discover it is missing on the one month that needed it.
The question to ask about your current date
Whether the cut-off falls in a quiet week or a busy one, and whether there are two working days of slack before the money has to move.
If the answer to either is no, the date is the cause of a problem being blamed on something else.
Changing it
Possible, and it has to be done carefully: people have standing orders, rent dates and direct debits built around the old date, and moving pay later by even a few days causes real difficulty for some of them.
Moving it earlier is easier than moving it later, and either needs notice, explanation, and usually a one-off transitional arrangement.
What it is not reasonable to do
Move the date quietly, move it in both directions, or move it for the business's cash convenience in a month when money is short. Each of those costs more trust than the cash is worth.
When to change it
At a natural boundary, with notice, once, and only if the current date is genuinely causing the collisions described above.
What not to change
The frequency and the date at the same time. One change at a time, with a run in between, so that anything that goes wrong has a single cause.
The thing worth writing down
The date, and the five derived deadlines, on a calendar everybody involved can see.
A date held only in one person's head is a date that moves whenever that person is busy, which is the opposite of what a pay date is for.
What the date says to the people being paid
A pay date is one of the few things about an employer that everybody knows and nobody discusses. It anchors rent, standing orders, direct debits and childcare payments, and people build their month around it within about two cycles of starting.
That is why moving it is a bigger event than it looks from the business's side, and why consistency is worth more than optimality. A date that is slightly inconvenient for the business and completely reliable for everybody else is a better arrangement than one that is convenient and occasionally moves.
The date for a business with uneven cash
A genuine consideration and a dangerous one to act on. Aligning the pay date with when money reliably comes in is reasonable at the point of choosing; moving it afterwards because a particular month is tight is not.
The first is planning. The second is using people's wages as working capital, and it is noticed immediately.
The honest position
Most small businesses will never change their pay date, and most do not need to. Knowing what it drags behind it is useful regardless, because the derived deadlines are the ones that actually get missed.