The Cut-Off Nobody Else Keeps
A cut-off is not an administrative preference. It is the slack that makes the statutory dates reachable, and it is usually kept by one person alone.
Nobody elseif the person who does this is away
What the cut-off is actually protecting
Done by: Everybody who has something to tell
Done by: The owner
Done by: The owner
Done by: Nobody
Done by: The owner
Done by: The owner
Done by: The bank
Ten days of slack between the cut-off and the money, and every late change spends some of it. One small employer's own schedule, not a recommended one.
A payroll cut-off is the slack that makes every later date reachable. It is usually treated inside a small business as a preference held by the person who runs payroll, which is why it is the first thing to be overridden by anybody in a hurry.
The deadline in “The Cut-Off Nobody Else Keeps” becomes more workable when collection and approval happen before the final payroll cut-off. Organisations considering what to review for employee activity tracking for employee activity tracking can make that timing visible without assuming that activity data alone explains whether a payroll step is complete.
Naming what it protects changes how it is received.
The questions raised in “The Cut-Off Nobody Else Keeps” can also be checked against Employment New Zealand pay resources. Use that material to identify the evidence and owner needed for the next payroll run.
What it buys
Days. Between the cut-off and the money leaving there are usually seven to ten of them, and they absorb a late change, a bank holiday, a rejected payment, a correction found in checking, or a day of illness.
Spend them on late inputs and there is nothing left for the rest.
Why it is routinely ignored
Because the consequence falls on somebody else. A manager who sends hours three days late has not experienced any cost; the cost appears as the payroll person working late, which is invisible.
What makes a cut-off hold
Being a date rather than a request, being the same date every month, being known by everybody who has to meet it, and having a stated consequence.
Three of the four are free.
The consequence that works
Changes arriving after the cut-off go in the following period. Not as a punishment — as the only arrangement that keeps the later dates reachable.
Stated once, in advance, and applied consistently, it moves behaviour within two or three months.
The consequence that does not work
Accepting everything and absorbing it. A cut-off that is always waived teaches everybody that the real deadline is the pay date, and the real deadline becomes the pay date.
What has to be genuinely exempt
Anything that would leave somebody unpaid or substantially underpaid. A new starter whose details arrive late is not a case for the following month, whatever the rule says.
A cut-off with no exceptions is as unworkable as one with no force.
Where to set it
Far enough before the run to leave the slack described above, and in a part of the month that is quiet for the people who have to meet it.
A cut-off falling in everybody's busiest week will be missed every month regardless of what anybody intends.
Telling people
Once a year with the calendar, and once in any month where it moves. Not repeatedly, which trains people to wait for the reminder before acting.
The reminder that helps
Sent two days before, to the handful of people who normally have something to send, naming what you need rather than asking whether they have anything.
A specific ask produces a specific answer; a general one produces silence from the people who have something and a reply from those who do not.
What arriving late actually costs
The check. In nearly every small business the first thing dropped when the run is compressed is the comparison against last month, which is the only control that catches an input error.
That is the real cost of a late change, and it is worth saying out loud.
The quiet version of lateness
A change mentioned in conversation rather than sent. It was told to you, it is not written down, and it reaches the run or does not depending on memory.
A cut-off only works if there is a place things go, which is the subject of a later note here.
What to do in the month it fails
Run what you have, correct in the following period, and tell the person affected before they notice. A correction made visibly is a much smaller event than one discovered.
What to do about the person who is always late
Usually one, sometimes two, and almost always the same ones every month. General reminders do not reach them, because general reminders are read by the punctual.
What works is specific: a direct message naming what is outstanding from them, two days before, every month, until the habit changes or until the business accepts that this person's inputs always need chasing and schedules for it.
Either outcome is better than being annoyed monthly.
The cut-off for things you are told rather than sent
A conversation is not a submission. Something mentioned in passing on the 19th has not met the cut-off in any useful sense, because it exists only in somebody's recollection.
Saying so plainly — put it on the list or it does not count — feels bureaucratic in a business of fourteen people and is the only version of a cut-off that functions.
The thing that makes it stick
The person who runs payroll not being the only one who knows the date exists. A cut-off on a shared calendar is a business arrangement; a cut-off in one head is a personal preference everybody else is free to ignore.