BAMML Executive Insights

Two-Pot, Minimum Wage and Equity Targets Are One Payroll Problem

Industry: Cross-sector C-suite & Board · Primary pillar: Workforce Governance · Secondary: Financial Governance; Risk & Compliance

5 min read

Over recent years a series of separate obligations have landed on the payroll function.

Each arrived on its own timetable. Each was announced separately, understood separately, and implemented separately — usually by the same small team, usually alongside their existing work, usually without additional resourcing.

Individually, each was manageable. Cumulatively, they have changed what payroll actually is. Very few organisations have noticed, because nobody was watching the cumulative view.

What is actually happening

Payroll used to be a processing function. Its job was to pay the right people the right amount, on time, every month. Accuracy mattered enormously, but the domain was bounded and stable.

A row of lever-arch files in different colours lined up separately on a payroll office desk, with a payroll clerk reaching for one

It is now a compliance function with processing attached.

Retirement fund arrangements carry administrative requirements that did not previously exist. Minimum wage obligations are subject to periodic adjustment, which means the compliance position has to be re-established rather than assumed. Employment equity obligations require data that has to be captured correctly at source — in payroll and HR systems — long before any reporting obligation falls due. Alongside these sit the standing obligations that were always there: tax, contributions, statutory deductions, record retention.

The domain has widened considerably. In most organisations the resourcing, the seniority, the systems and the reporting line have not moved at all.

Why it matters

Payroll compliance failures have three features that make them worse than most compliance failures.

A small payroll team of two working late, one checking a printout against her screen and the other taking a phone call and making notes

They are retrospective. A payroll error is not fixed by doing it correctly from next month. It is fixed by correcting the period affected, which may be many periods, across many employees, with consequences for each of them individually.

They affect people directly, and people notice. Most compliance failures are discovered by an auditor or a regulator. Payroll failures are discovered by employees — who have recourse, who talk to each other, and whose trust is difficult to rebuild once the organisation has been wrong about their pay.

They are structurally invisible to the executive. Payroll reports into finance in some organisations and HR in others. In both cases it sits several levels below the executive table and is regarded as an administrative function. So it has no route to report risk upward. The executive learns about a payroll compliance problem when it has already become a dispute.

That third feature is the one worth acting on, because it is the one entirely within the executive's control.

The Integrated View

Discipline What it should be asking What usually happens
Workforce Governance Has the obligation set changed, and are we still compliant? Handled when each change arrived; not revisited since
Financial Governance What would correcting an error across affected periods cost? Never modelled until it happens
Risk & Compliance Is payroll on the risk register at all? Usually not — it is treated as administration
Operational Performance Does the team have capacity for compliance as well as processing? Capacity measured against processing only
Executive Decision Intelligence When did payroll last report risk to the executive? In most organisations, never

What good looks like

Map what has landed. List every obligation affecting payroll over the past few years, when it took effect, who implemented it and who confirms it is still being met. The list is usually longer than the executive expects, and the last column is usually empty.

A payroll lead, HR manager and finance manager at one table reviewing a shared checklist and calendar together

Separate compliance from processing. Name someone accountable for whether payroll is compliant, as distinct from whether payroll ran. In smaller organisations this may be the same person — but it should be a distinct, named responsibility rather than an assumed part of the processing job.

Give payroll a route to report risk. A short standing item, quarterly, reaching the executive: obligations current, changes pending, errors identified and corrected, capacity position. Four lines. The value is that the route exists before it is needed.

And model the correction cost once. Take a plausible error, across a plausible number of employees and periods, and calculate what putting it right would cost including the employee relations consequence. That number makes every subsequent resourcing conversation straightforward.

What to do on Monday

  1. Ask for a list of every obligation affecting payroll and when each took effect.
  2. Ask who confirms each is still being met, by name. Note where the answer is nobody.
  3. Ask when payroll last reported a risk to the executive. If the answer is never, that is not evidence of no risk.
  4. Ask whether payroll has capacity for compliance work as well as processing, or whether compliance happens in the gaps.
  5. Put payroll on the risk register with a named owner.

Payroll is treated as an administrative function in most organisations. It stopped being one some time ago, and the organisations that get caught are generally the ones where nobody noticed the change.

Share this insight LinkedIn Email Book a conversation

← All Executive Insights