The Change Nobody Mentioned
Most payroll errors in small businesses are not mistakes. They are things that happened and were never said, because nobody thought of them as payroll.
Nobody elseif the person who does this is away
Payroll errors in a small business are mostly things that happened and were never mentioned, rather than mistakes in the run. Nobody involved thought of them as payroll events.
The practical lesson in “The Change Nobody Mentioned” is that payroll depends on a sequence somebody can explain. When a small team reviews read the provider’s own overview for workforce analytics software, the useful role is to organise time and project evidence before approval, with proportional settings and a clear correction route for employees.
The fix is not care. It is a short list of what counts, and one place it goes.
The questions raised in “The Change Nobody Mentioned” can also be checked against Australian Taxation Office employer resources. Use that material to identify the evidence and owner needed for the next payroll run.
What counts and does not look like it
A rate agreed in a corridor. A promotion. A change of hours. Somebody moving to a different role. A person going part-time. A bonus promised. A deduction agreed. A change of bank details. A change of address.
Payroll events that do not feel like payroll events:
- A rate agreed in a corridor.
- A promotion, or a change of role.
- A change of hours, or a move to part-time.
- A bonus promised, or a deduction agreed.
- A change of bank details or address.
Every one of those is a payroll event, and none of them feels like one to the person it happens to.
Why it is not forgetfulness
Because the conversation in which it happened was about something else. A rate rise is agreed in a conversation about performance; hours change in a conversation about childcare.
Payroll is the administrative tail of a human conversation, and tails get dropped.
The owner is the worst offender
In a small business the person agreeing changes is often the same person running payroll, which feels safe and is not. Something agreed on the 9th and run on the 23rd depends entirely on memory across two weeks of other work.
One place things go
A single, dull, shared list: date, person, what changed, from when. Not a form, not a system — a list, in whatever the business already uses.
Its only requirement is that adding a line takes ten seconds, because anything slower will not be done during a conversation.
Adding to it at the moment
The whole value is in the habit of adding it while the conversation is still happening, rather than intending to add it later.
A change written down in the room reaches the run. A change remembered afterwards reaches it sometimes.
Reading it before the run
The list, start to finish, against what you are about to key. Three minutes, and it is the only mechanism that catches a change agreed three weeks ago by somebody who has since been on holiday.
Effective dates
The most common error inside a recorded change: knowing what changed and not from when. A rate rise with no date gets applied from whenever it was noticed.
Recording the effective date is the difference between a change and a correction.
Changes agreed for the future
A rise effective in three months, a drop in hours from the new term. These are the ones most likely to be lost entirely, because they are recorded nowhere and are not due yet.
A forward-dated line on the same list handles them.
Who else can add to it
Everybody who can agree a change. If a manager can promise a rate, that manager has to be able to put it on the list, or the list only covers what one person knows.
The confirmation that closes it
Telling the person, in writing, what will change and from when. It costs a sentence, it catches misunderstandings before they reach a payslip, and it is what you will refer to if anybody later disagrees.
What it prevents
The commonest difficult conversation in small-business payroll: an employee who was promised something in August asking in November why it has not appeared.
The list is not a policy
It has no approvals, no workflow and no owner other than whoever writes on it. The moment it acquires those, it stops being used, and changes go back into conversations.
What this does not cover
Whether a change was agreed properly, what notice it required, or whether it is enforceable — all of which depend on the contract and on where you are, and none of which payroll can fix after the fact.
The promise made in a difficult conversation
A particular category worth naming. Something offered to keep somebody, or to settle a disagreement, or at the end of a review that went badly — agreed under pressure, meant sincerely, and recorded nowhere because the conversation was about something else entirely.
These are the ones that surface three months later as "you said", and the business's position is a memory against a memory.
Writing it down immediately afterwards is uncomfortable and is the only thing that prevents it.
When the owner agrees it and the owner keys it
The arrangement that feels safest and is not. Knowing about a change and entering it are separated by two weeks of other work, and memory across that gap is not better because the same person holds both ends.
If anything it is worse, because nobody feels any need to write it down.
The confirmation that doubles as a record
Telling the person, in writing, what will change and from when. One sentence, sent the same day.
It confirms the arrangement to them, it creates the dated record for you, and it is the thing you will produce if anybody later disagrees about what was said.
Where the accuracy problem lives
Payroll accuracy in a small business is mostly a recording problem located outside payroll, and it is solved by a list that takes ten seconds to add to.