Continuity · Key Person Risk

What Happens When Your Payroll Person Leaves

June 2026
Ask an AI to explain this:

Nearly every business we take on has the same structure: one person understood payroll, and the business quietly depended on them staying.

It is rarely dramatic. Someone resigns, works a notice period, and leaves on good terms. There is a handover meeting, and it covers the process, the logins and the calendar. Everything that can reasonably be written down gets written down, and on the day it looks complete to everybody in the room.

Then the first pay run happens without them, and the distance between what was documented and what was actually known starts to show. Not dramatically, and not all at once — but it shows.

Two people reviewing a laptop screen at a desk beside an open moving box packed with a mug, notebooks and a small plant.

What Actually Walks Out the Door

It is not the process. The process is usually documented, or at least reconstructable from the software. What leaves is the accumulated set of exceptions that never got written down, because to the person doing them they were not exceptions — they were just part of their job.

Things like: which two employees have a grandfathered allowance from an old agreement. Why one site's timesheets always arrive a day late and that is fine. Which employee's KiwiSaver was opted out and when. That the vehicle allowance is taxable but the tool allowance is a reimbursement. Which of the three people called Sarah is which in the bank file.

The handover document covers how to run the pay run. It almost never covers the many small decisions that make the pay run correct.

What Breaks First, in Order

01
Week one: the pay run still goes out. It usually does. The software does what it did last time. This is the dangerous part, because it creates confidence.
02
Week two to four: the exceptions surface. Someone's allowance is missing. A leave request was approved verbally and never entered. A new starter is on the wrong rate.
03
Month two to three: the queries start. Employees notice their own pay before you do. Every query takes an hour to answer because nobody knows why the original decision was made.
04
Month six and beyond: the compounding errors. Anything that touches a twelve-month average — leave rates, final pays — is now quietly wrong, and will stay wrong until someone checks.

The Bit That Makes It Worse

Payroll is the only business function where a processing error directly disrupts your employees' personal finances. A finance error can be quietly corrected next month. A payroll error is a conversation with a colleague.

That is why payroll failures escalate socially far faster than their financial size would suggest. A $40 mistake, repeated, becomes a trust problem.

Three Things to Do This Month

011. Write down the exceptions, not the process. Sit with whoever runs your payroll and ask a single question: "what do you know about this pay run that isn't written down anywhere?" Then write the answers down. Half an hour will get you most of the value.
022. Make someone else run one pay run. Not shadow it — run it, with the usual person watching. You will find the gaps immediately, while the person who can explain them is still in the building and can answer in a sentence rather than a phone call.
033. Get the configuration checked independently. Not by the person who set it up, and not by your software vendor. An independent review tells you whether the decisions embedded in your system are actually right, which is the one thing a handover document can never tell you.

Or Take the Person Out of the Equation

This is the honest pitch, so here it is plainly. The reason businesses move to a managed service is not usually cost. It is that a service does not resign.

When payroll sits with a team rather than a person, the exceptions live in a system that several people can see, the knowledge does not depend on anyone's memory, and nobody has to hope that a particular individual does not get sick in a pay week.

You can achieve a lot of that in-house with documentation and a second trained person. It is genuinely worth doing either way.

But if you read the first paragraph and recognised your own business, that is worth paying attention to.