Somebody Was Not Paid At All
The worst routine failure in small-business payroll, and the one with the simplest response: fix it today, explain afterwards.
Nobody elseif the person who does this is away
Somebody not being paid at all is the worst routine failure available in small-business payroll, and it has the simplest correct response: get them the money today, and explain afterwards.
The exception in “Somebody Was Not Paid At All” needs evidence that can be checked rather than one unexplained total. Used for getting teams to meet deadlines, what to review for getting teams to meet deadlines can provide time and project context, but a payroll correction should still rely on approved records, the payroll ledger and a documented human review.
The explanation can wait. The person cannot.
As a separate reference point for “Somebody Was Not Paid At All”, see Notion workspace guides. Current legal, tax and employment requirements should still be confirmed for the organisation’s location.
How it happens
A starter never added. A leaver processed too early. A payment that failed and was not noticed. A person missing from the run because a record was closed. Bank details that had changed.
Five causes, all mechanical, none of them the person's doing:
- A starter never added.
- A leaver processed too early.
- A payment that failed and was not noticed.
- A record closed, so the person is absent from the run.
- Bank details that had changed.
Five causes, all mechanical, none of them the person's doing.
The response, in order
Confirm it is true, pay them the same day by whatever method is fastest, tell them it is being done and when it will land, then find out what happened.
Investigating first is the instinct and is the wrong order.
Paying the same day
Usually possible: an immediate transfer, made from the bank rather than through the payroll run, with the run corrected afterwards.
The cost of doing it this way is a small amount of administrative untidiness. The cost of not doing it is somebody's rent.
Recording it properly afterwards
The payment has to be reflected in payroll and in whatever was reported, not left as a bank transfer nobody tracked.
This is where the untidiness gets resolved, and it has to actually happen rather than be intended.
What to say
That they were not paid, that it was the business's error, that the money is on its way and when it will arrive. Four facts, immediately.
No explanation of the cause at this stage — they do not need it yet and it reads as excuse-making.
What they may have incurred
A failed direct debit, a returned payment charge, an overdraft fee. A business that caused those should expect to cover them and should offer rather than wait to be asked.
The new starter case
The most common and the most damaging. Somebody who has worked a month and been paid nothing has formed a view of their employer that takes a long time to change.
It is also entirely preventable by telling payroll at the offer rather than at the start.
The leaver case
Processed too early, and the final payment never made. Frequently discovered weeks later by the person, who by then has concluded they are being avoided.
Checking for others
Same principle as elsewhere: if the cause was systemic, somebody else may be affected and may not have said anything.
A headcount check against the run answers this in ten seconds.
The five preventive steps
For each of the five causes there is one preventive step: tell payroll at the offer, process leavers on the final run and not before, confirm payments went, check the count before approving, verify bank changes through a second channel.
All five are in this collection already.
The check that catches it at the right moment
Headcount, before approving. The number of people in the run against the number of people you employ.
It is the shortest check available and the only one that catches a person who is simply absent from the file.
The note that closes it
A short written note to the person once it is settled: what happened, what has been changed. It converts an event they will remember as chaos into one they remember as handled.
The ten-second check that catches it
Headcount, before approving: the number of people in the run against the number of people you employ.
It is the only check that finds somebody who is simply absent from the file, because a person who is not there produces no figure to compare and no difference to notice.
What it costs them beyond the money
A failed direct debit, a returned payment charge, an overdraft fee, a late rent conversation with somebody else.
A business that caused those should offer to cover them rather than wait to be asked, and the offer matters more than the amount.
The order that is counter-intuitive
Pay first, investigate afterwards. The instinct is to establish what happened before committing to anything, and it is wrong here: the facts will be the same in an hour, and the person's position will not.
Nothing is lost by paying somebody money they have earned before you know precisely why they did not receive it.
The thing not to do
Wait for the next run. Under almost no circumstances is that the right answer, and a business that offers it is telling somebody that its administrative convenience outranks their month.