When Payroll Week Means Late Nights for One Person

In a lot of small and mid-sized businesses there is one person who knows how payroll works. Not the payroll software, necessarily, but the whole thing: which timesheets arrive late, which manager forgets to approve overtime, which employee changed banks last month, which leave days were taken but never captured, and which figure has to be on the SARS return by the seventh.

For most of the month that person does their ordinary job. Then the last week arrives, and the job changes shape. Evenings stretch. Messages go out asking for hours and approvals. The spreadsheet that feeds the payroll gets opened, checked, corrected and checked again. Everyone else experiences payroll as a payslip. One person experiences it as a week.

This piece is about that week, and about the person who carries it.

A fixed deadline with moving inputs

Payroll is unusual among business processes because its deadlines are not negotiable and its inputs are not under the payroll person's control.

The deadlines are external. SARS requires employers to declare PAYE, UIF and Skills Development Levy amounts on the monthly EMP201 and to pay within seven days after the end of the month in which the tax was deducted. Twice a year there is a reconciliation on top of that: SARS's PAYE page sets the interim EMP501 period from 21 September to 31 October, and the annual period from 1 April to 31 May, with penalties for late submission. Employees, quite reasonably, expect to be paid on the agreed day.

The payslip itself has to carry real detail. The Department of Employment and Labour's basic guide to pay slips lists what must be shown in writing: the period covered, gross pay, deductions, net pay and, where they affect the calculation, ordinary and overtime hours, rates, and hours worked on Sundays or public holidays.

The inputs, meanwhile, come from everywhere. Hours from supervisors. Overtime approvals from managers. Leave from whoever keeps the leave record, which in some businesses is still a book or a spreadsheet. Starters, leavers and changes in banking details from whoever spoke to the employee. Commission from sales. Each input has its own owner, and each owner has a different sense of when "end of the month" begins.

So the deadline is fixed and the inputs drift. The gap between them is absorbed by one person's time.

Why it lands on one desk

None of this is anybody's fault in particular. Payroll tends to concentrate on a single person for understandable reasons: it involves confidential information, it rewards care, and in a business of twenty or forty people it rarely justifies a team. Over time the person who does it accumulates knowledge that is nowhere else: the employee whose overtime is calculated differently, the allowance agreed verbally years ago, the reason one deduction looks odd.

That knowledge is valuable. It is also the mechanism that keeps the late nights in place. When the rules live in one person's head and the inputs arrive by message, the only way to get payroll right is for that person to do the chasing, the interpreting and the checking themselves, and to do it after the inputs finally arrive, which is usually late.

Mellorca has written about the broader shape of this in how to tell whether a business depends too much on one person, and about the cost side in what repeatable manual payroll work costs. This piece looks at what the arrangement asks of the person in the middle.

An illustrative payroll week

Take an illustrative example, not a real business: a Pietermaritzburg engineering supplier with about thirty-five staff, some on fixed salaries and some on hourly rates with overtime. Payroll is run by the office manager, who also handles purchasing and reception cover.

In this scenario, timesheets for the workshop are paper forms signed by the foreman and dropped on the office manager's desk, usually on the 23rd or 24th. Two are always missing. Overtime is approved by WhatsApp message. Leave is kept in a spreadsheet that the office manager updates when someone remembers to tell them. Bank detail changes arrive by email, sometimes forwarded from a personal address.

The office manager's payroll week therefore starts with chasing, moves into capturing and reconciling, and ends with a careful check of every payslip against the previous month, because they know from experience that a missing leave day or a misread overtime figure will become an awkward conversation on payday. The checking happens in the evening because the day is taken up by the other half of the job.

Nothing here is unusual. It is an ordinary arrangement with a predictable cost, and the cost falls on one person.

The human tax

The first tax is time: evenings in the last week of the month that belong to payroll rather than to whatever the person would otherwise do with them.

The second is energy. Payroll work is detailed and consequential. Doing it at the end of a full working day, after the inputs have arrived late, means doing careful work when attention is at its lowest.

The third, and perhaps the least visible, is predictability. The person cannot plan the last week of the month, because how late they work depends on when other people send their information. It would be overstating the evidence to say how any individual feels about that. It is reasonable to say that a recurring week whose length is set by other people's habits is harder to plan a life around than one whose length is known.

What could realistically change

The useful interventions are mostly about moving work earlier and making the rules visible. Software helps, but only after the inputs are organised.

Publish a payroll calendar. A short, agreed timetable: timesheets by a fixed day, overtime approved by a fixed day, changes after the cut-off go into next month unless urgent.
Capture inputs where they happen. Leave requested and approved in one place, overtime approved in the same system that records the hours, banking changes submitted through a controlled form rather than an email. Each input then arrives in a usable shape rather than needing translation.
Write down the exceptions. The special allowances, unusual deductions and one-off agreements belong in a short document the business owns, not only in one person's memory.
Reconcile during the month. Checking leave balances and new starters mid-month leaves the final week for running payroll, not discovering problems.
Train a second person. Not to share every payroll, but to be able to run one when needed.

Payroll software and integrations between time, leave and payroll systems can then remove much of the re-keying. But a payroll package fed by late messages and paper forms will still produce a late payroll week, just with better payslip formatting.

What changes first, and for the business

The first change is that payroll inputs arrive complete and on time more often, because the rule is visible and the place to submit them is obvious. The office manager's week begins with checking rather than chasing.

For the business, the outcome is fewer payroll corrections, more confidence in statutory submissions, and less exposure if the one person who knows payroll is ill or leaves.

The human dividend

The dividend here is time and predictability. Payroll week becomes a known quantity: a set number of hours, mostly in working time, on days the person can see coming. Evenings in the last week of the month can be planned again, for whatever the person chooses to do with them.

There is a quieter dividend as well. When the rules are written down and a second person can run payroll, the job stops being a personal burden that the business depends on and becomes a process the business owns. For some people that is a relief. For others it may feel like a loss of standing, which brings us to the trade-offs.

The trade-offs

Cut-offs create friction. A manager whose overtime approval misses the cut-off will have an employee paid late for those hours. That is fairer than the payroll person absorbing the delay, but it moves the discomfort elsewhere.
Documented knowledge reduces indispensability. The person who has carried payroll may value being the one who knows. Writing it down can feel like being made replaceable, and that deserves an honest conversation rather than a rollout.
More structure for supervisors. Capturing hours and approvals properly asks more of foremen and managers, who may experience it as admin added to their day.
Systems need upkeep. A leave or time system that nobody maintains drifts back into spreadsheets within a year.

Why it matters

Payroll is one of the few processes where the whole workforce feels the result on the same day. When it works, nobody notices how. The late nights that make it work are part of the price of a reliable payslip, and in many businesses that price is paid by one person, quietly, every month.

Mellorca's reading is that this is a design choice, even if nobody ever made it deliberately. A business can choose to move the effort earlier, spread the knowledge and fix the inputs, so that the person who protects everyone else's payday gets their own evenings back. The connection to cash pressure is explored in a related Moment, the cash-flow week that keeps the owner awake, and the risk of critical work living in one workbook in when a spreadsheet becomes a business-critical system.

Sources and further reading

Pay As You Earn - South African Revenue Service (last verified 10 October 2026)
Basic Guide to Pay Slips (last verified 10 October 2026)
Basic Guide to Annual Leave (last verified 10 October 2026)