Should payroll have caught that?

An employee tells you their pay is wrong.
They worked 20 hours of overtime, but their manager submitted 10. Those 10 hours were approved, sent to payroll on time and processed correctly.
The employee is underpaid.
It is tempting, once the mistake is visible, to ask why nobody caught it before the employee did.
But what exactly was there to catch?
Payroll received an authorised instruction for 10 hours. The amount was plausible. Nothing necessarily looked unusual and there may have been no independent information against which those hours could be checked.
The payroll is wrong from the employee's perspective. The information used to calculate it was wrong too. But neither fact automatically tells us that a payroll control failed.
Now change one detail.
The employee normally works around 20 hours of overtime each month. This month the manager accidentally submits 200.
The instruction is still authorised. Payroll could process exactly what it has been given. But the result now looks very different from what normally happens.
Would you expect somebody to notice?
Probably.
Not because payroll suddenly owns the manager's responsibility for supplying accurate hours, but because there is now something a payroll control might reasonably detect. A comparison with previous periods, an exception report or an experienced payroller reviewing an unusual movement could give somebody a reason to ask a question before payment.
The original mistake is the same in both cases: the manager supplied the wrong number of hours. What changes is how detectable the mistake becomes as it moves through the process.
Hindsight makes errors look easier to find
Once you know that 10 hours should have been 20, the incorrect figure can look obvious. You are looking at it with information the person processing payroll may not have had.
So when reviewing an error, finding where it originated is only part of the job. We also need to consider what information and controls were actually available before it reached the employee.
Was there conflicting information that should have been reconciled? Did the result move far enough from normal to trigger an established check? Was an approval missing? Did somebody have information that should reasonably have caused them to query what they were being asked to process?
Sometimes that will reveal a control that failed, or something the process could reasonably have been designed to detect. In other cases, there may simply have been nothing in the normal process that could distinguish the incorrect instruction from a correct one.
That matters because the answer to an error is not automatically another check.
What could the control reasonably have known?
Payroll cannot independently reconstruct every instruction it receives before processing it. Controls therefore have boundaries.
Approval can establish that an authorised person approved information; it cannot prove every fact within it is correct. Variance analysis can identify unusual movement; it cannot tell you that a perfectly plausible change is wrong.
Good controls increase the chance that things which should look wrong are noticed. They cannot make every wrong thing look unusual.
So instead of asking only:
“Why didn't payroll catch this?”
ask:
“What would somebody have needed to know, see or compare to recognise that it was wrong?”
If that information was available and an appropriate control should have used it, there may be something worth fixing. If it wasn't, adding another payroll check may simply create work without making the process meaningfully safer.
Ready To BeePayWise?
Let’s make your payroll the sweetest, calmest part of your month. Book a hive chat for a no-strings mini-diagnostic, or drop us a message and we’ll buzz right back.
