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.

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
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
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.