What matters in payroll, once compliance is handled

Ask a founder what payroll is about and the answer is almost always tax. PAYE, UIF, SDL, the EMP201, the IRP5 at year-end. Compliance is real and it’s loud and it’s where every payroll article seems to live.

But compliance is the floor. A payroll function can be perfectly compliant and still be terrible. The things that make it good — the things that decide whether your team trusts the run and your finance lead sleeps the night before pay day — sit somewhere else.

Eight of them, in roughly the order they bite.

01 — Accuracy and data integrity

Payroll is unforgiving in a way most software isn’t. One wrong number and an employee notices immediately, because it’s their money. There’s no soft-launch, no “we’ll catch it in the next sprint”.

And nine times out of ten the wrong number isn’t a maths bug. It’s garbage upstream: a banking detail miskeyed during onboarding, hours captured against the wrong cost centre, a leave balance that drifted because three people maintained it in parallel. The discipline is therefore upstream too — clean inputs, validation at capture, and a single source of truth instead of three spreadsheets pretending to be one.

If you can’t point to where a number came from in under thirty seconds, you don’t have a payroll system. You have a wish.

02 — Reliability and timeliness

Same day, every cycle, no exceptions.

This is, more than anything else on this list, the single biggest driver of employee trust. People plan their debit orders, their rent, their school fees around your pay date. A late run or a short run does more reputational damage internally than any other single failure mode a small business has.

Compliance can slip a day and nobody outside the finance team notices. A late payroll is on the WhatsApp groups by lunchtime.

03 — The variable stuff

The fixed-salary case is trivial. Anyone can pay 12 people the same amount on the 25th of every month.

The actual work is everything around that:

• Overtime, at the correct multiplier, against the correct base.
• Commission, with its lag and its claw-backs.
• Bonuses — performance, retention, 13^th cheque.
• Shift differentials and weekend loadings.
• Allowances — travel, cellphone, tools.
• Tips and gratuities, if you have staff in hospitality.
• Pro-rata calculations for mid-cycle joiners and leavers.
• Final settlements on termination — notice pay, leave encashment, severance.

Termination calculations in particular are a common foul-up. They happen rarely enough that the muscle isn’t there, the dates matter to the day, and the employee leaving is the one most likely to read the payslip with a calculator.

04 — Reconciliation and controls

Every cycle, two reconciliations.

Payroll to bank. Does the batch total match what actually left the account? To the cent. If it doesn’t, you find out why before the next run. A signed CSV with a totals row and a matching bank statement line is the smallest possible audit trail, and it’s also the one that catches the most.

Payroll to general ledger. Does finance see the right cost against the right account? Salaries, employer UIF and SDL, pension, medical, fringe-benefit tax — each in its own line, each landing where the accountant expects.

Layered on top of those, the fraud controls. The two classic payroll frauds are:

1. The ghost employee. Someone on the master file who doesn’t exist; their salary lands in an account you don’t recognise.
2. The altered beneficiary. A real employee whose banking details were quietly changed to point somewhere else just before payday.

Both are prevented by the same control: segregation of duties. The person who adds or edits an employee should not also be the person who releases the payment. Even in a two-person finance team, this is enforceable — one person prepares, the other approves.

05 — Confidentiality and access

Salary data is among the most sensitive information a business holds. More than customer data in most cases, because it maps directly to people in the room.

Who can see and change it has to be deliberately restricted. That’s a privacy concern, but it’s also a fraud one — loose access is exactly how the two frauds above happen. Role-based controls, audit logs on every change, and a default posture of “view nothing” until proven otherwise.

The test is simple. If your payroll system can’t tell you who last viewed the CFO’s salary, it’s the wrong system.

06 — Cash flow

For most businesses, payroll is the largest, most predictable monthly outflow. And unlike a supplier, you can’t stretch it out. You can’t pay 80% on the 25^th and the rest on the 5^th.

That makes funding the run a treasury problem as much as an admin one. For an early-stage business with lumpy revenue — subscriptions landing on different days, big invoices running late — the cash buffer to cover payroll on its day is sometimes the most important number on the board pack. Not runway in months. Runway to the next run.

A good payroll process surfaces the number you’re about to need, days before you need it. Bad ones surface it the morning of.

07 — Joiners, movers and leavers

Steady state is easy. Most payroll errors don’t happen in the middle of someone’s tenure; they happen at the edges.

The transitions:

• A new joiner whose banking details were captured but never verified — their first salary goes to a typo.
• A mover between cost centres whose new code wasn’t pushed to payroll, so the GL is wrong for the month.
• A leaver whose access was revoked but whose recurring deduction wasn’t, so the final payslip has a phantom medical aid line.

A tight joiner/mover/leaver flow — one with banking details verified before first pay, role changes timestamped against the correct pay period, and a termination checklist that closes every recurring item — prevents the bulk of the problems you’d otherwise spend the cycle hunting.

This is where HR and finance actually have to talk to each other. The companies that do payroll well are the ones where that handoff is a single shared system, not an email thread.

08 — Tooling and integration

For a small business, the leverage point is picking a system that solves the data-integrity problem at the root.

Two tests:

• Does it automate the calc and the filings? If your team is copying numbers into the SARS eFiling form by hand, you’re one transcription error away from a penalty.
• Does it feed off the systems where the data already lives? Time and attendance, POS scheduling, leave management. Manual capture between systems is where the errors enter the building.

The point of integration isn’t elegance. It’s removing the keyboards between the source of truth and the payslip. Every keyboard is a place a digit can flip.

What compliance gives you, and what it doesn’t

Compliance gives you the right to operate. It keeps SARS off your back and your auditors happy at year-end. It’s necessary and non-negotiable and we write about it a lot.

But the eight things above are what decide whether payroll is a calm function or a loud one. Whether your team trusts the number on the payslip. Whether your finance lead spends pay day shipping work or chasing errors. Whether you can scale headcount without scaling pain.

Compliance is the floor. Everything above is the building.