All articles
Inside payloop3 May 20263 min read

The anatomy of a calm payroll run

Compile. Calculate. Export. The three-act shape that turns month-end from a two-day exercise into twenty calm minutes.

Kyle McLaren
Kyle McLaren
Founder

Walk past any finance team on payroll-Tuesday and you can tell the state of their process from across the room. The calm ones are quiet. The other ones are very loud.

A calm payroll run has the same three-act shape every month. Sequential. Named. Bounded. The acts don’t change. That’s how you get to calm.

01 — Compile

The first act answers one question: what is different this month?

Not what anyone earns; not what the EMP201 will be. Just: who joined, who left, what changed, what once-off items belong against whom. The output is a frozen roster — one source of truth, refused all others. Close act 1 only when there are no “I think so”s left.

02 — Calculate

The second act answers: given this roster, what does everyone get paid?

This is the maths layer — PAYE against the 2026/27 tax tables, UIF capped at R 177.12, SDL, pre-tax deductions, fringe benefits. The maths is the easy part. The hard part is the prior-month diff: a side-by-side view of every line item against last month, with the delta in rands and percent.

The diff is the most important feature in any payroll system. It catches the PAYE that’s 8% lower because a pension contribution quietly changed, the once-off that got tagged as recurring, the salary jump nobody mentioned. Treat it as mandatory.

03 — Export

The third act answers: how does it all leave the building?

Four artefacts, in order:

  1. A bank-ready file in your bank’s exact format.
  2. Signed PDF payslips, dispatched the moment the run closes.
  3. An EMP201 staged for SARS.
  4. A journal entry to Xero or Sage.

You log into your bank, upload, approve, done.

Why three acts and not five

We’ve tried other shapes. Three won because they match the cognitive shape of a run: gather what changed, do the maths, ship the file. More granular slows people down. Less granular makes mistakes hard to spot.

The acts are also where audit trails naturally separate. If something goes wrong six months later you know which act to look in: what went into the run, what the engine produced, what we sent to the bank and SARS.

The end state

You will know the calm has arrived when your finance team has nothing to discuss in Monday standup about payroll, when HR pushes changes straight into the roster instead of queueing them for “the next run”, and when employees stop asking when payday is — because it’s always the 25th and it’s always on time.

Three acts. Same shape every month. That’s the whole job.

Try payloop

Want to see this in your payroll?

Book a 30-minute working session with your data.

Book a demo