1. The retroactive shift swap payroll never hears about
The most common case: two employees swap shifts, the supervisor approves it verbally, and it either makes it into the schedule or it doesn't. Payroll works from the scheduled data, while the employee expects the premium for the work actually performed. That is where the mid-month phone call comes from.
The problem is not that a swap happened — that is unavoidable. The problem is that there is no clear point up to which the swap can still be recorded, and no clear form in which it has to be reported.
What to do
- Set a fixed cut-off date after month end up to which a change still enters that month's settlement.
- Allow only one reporting channel — no verbal, no text-message, no "I'll mention it" version.
- Changes arriving after the cut-off appear as a documented correction in the following month.
2. Badly configured premiums
Night, Sunday, public-holiday and shift premiums, extraordinary work, stand-by, on-call duty — and the accumulation of all of these. The legal background is given, yet the error occurs regularly. In our experience it is usually not a question of legal interpretation: the pay titles and calculation bases were configured in the payroll system years ago, and since then the collective agreement, the work pattern or the legislation has changed.
This kind of error is particularly insidious because it is consistent: it is wrong the same way every month, so a comparative check never flags it. Only a line-by-line review brings it out.
Payroll configuration is sound when you can trace which pay title follows from which rule — and when someone last reviewed it.
3. The end-of-period surprise
Under working-time banking, closing the period is the point where the accumulated excess work becomes visible. If that only emerges in the final week of the period, all you can do is settle — not intervene.
This is a production-management question rather than a payroll one, but it lands on payroll: the pay for extraordinary work, the settlement of holiday and the accounting for lost time all arrive at once. And the cash-flow effect is concentrated into a single month.
What to do
Ask for a monthly banking monitor by production unit. You don't need a detailed report — you need one number: where does the period stand against the pro-rata expectation? If that is on the table every month, closing the period is administration rather than an event.
4. Two holiday records
A classic case: HR keeps a spreadsheet, the payroll system also tracks holiday, and by mid-year the two have drifted apart. From then on every holiday question has two answers and nobody is sure which is right.
The solution is not to keep both more carefully. The solution is to have one primary record from which the other is derived — or to abolish the other. Sort it once at the start of the year, and after that it only needs maintaining.
5. The "HR will send it over" syndrome
Payroll needs more than attendance data: it needs the full details of a new joiner, contract amendments, changes of role, pay changes and the exact leaving date. If these arrive ad hoc, by email, in different formats, then error is not a possibility but a statistical certainty.
The only solution that works is a uniform form and a fixed cut-off date. It looks bureaucratic at first, but in practice it means less work for both sides: nobody has to chase missing data after the fact.
Summary
What the five mistakes have in common is that none of them is a question of professional knowledge. Each stems from a process gap, and each can be prevented with the same three tools: a uniform data request format, fixed cut-off dates, and a monthly variance analysis before the close.
If any of these sounds familiar at your company, it is worth following the path of the data once, from the attendance sheet to the bank transfer. The error is almost always created at a transfer point — and usually at the same one.
