Handing It Over
A payroll handover transfers a sequence, five credentials and a body of undocumented knowledge. Most handovers transfer the first two.
Nobody elseif the person who does this is away
What a handover has to transfer, beyond the obvious
The leaver
Written downIf they are away: The successor invents one, differently each month
The leaver
Two peopleIf they are away: Nothing can be run at all
The leaver
Written downIf they are away: Deadlines are discovered by missing them
The leaver
Nobody elseIf they are away: Arrangements agreed years ago quietly stop
The leaver
Nobody elseIf they are away: The same errors are rediscovered from the beginning
The leaver
Two peopleIf they are away: A year of history becomes a search
2 of 6 tasks have nobody else who can do it.
Two of six are documents and two are knowledge that exists only in conversation. One small employer's own handover, not a model for anybody.
A payroll handover has to transfer three things: a sequence, a set of credentials, and a body of knowledge that exists only in conversation. Most handovers transfer the first two and lose the third entirely.
The practical lesson in “Handing It Over” is that payroll depends on a sequence somebody can explain. When a small team reviews read more on the provider website for work hours in a year, the useful role is to organise time and project evidence before approval, with proportional settings and a clear correction route for employees.
The loss is invisible for about two months and then shows up as a series of small errors nobody can explain.
As a separate reference point for “Handing It Over”, see Namely HR resources. Current legal, tax and employment requirements should still be confirmed for the organisation’s location.
The third thing
Who the people are and what is unusual about each of them. The arrangement agreed with one person years ago. Which manager always sends hours late. Which figure is always worth checking. Why a particular setting is the way it is.
None of that is in any document and all of it affects runs.
How to transfer it
By running payrolls together, not by writing a document. Two or three runs performed jointly surfaces the knowledge in the only way it can be surfaced: as it comes up.
One run is enough for mechanics and not enough for this.
The minimum handover
One run watched, one run performed with the leaver present, the credentials transferred and tested, and the written sequence read together with corrections made.
That is two months of lead time, which is more than most handovers get.
When there is no lead time
The common case: somebody leaves suddenly, or is unwell. Then the handover is whatever documentation exists, which is the argument for having written it long before.
A business with a current written sequence and a credential list can survive this. One without is reconstructing payroll under time pressure from somebody's inbox.
Credentials, specifically
Transferred and tested, not listed. The successor logs in to each system while the leaver is still there, including any two-factor method, which frequently needs re-enrolling on a different device.
This is the step most often deferred to the last day and most often unfinished on it.
What to ask the person leaving
What goes wrong most often. What they check that is not in the sequence. What they would do differently. What they were about to change.
Four questions, half an hour, and it captures more than any document they will write under notice.
The records question
Where everything is: the exports, the receipts, the starter paperwork, the absence sheet, the change list.
A successor who cannot find last year is a successor who will be asked about it within a month.
Handing over to a bureau
The same problems with an extra one: the knowledge goes outside the business and may not come back.
Worth keeping an internal record of the arrangements and oddities even when the running of it moves out.
The first run alone
Worth checking line by line, and worth the leaver being reachable for a question if the departure allows it.
A successor's first run is where the gaps in the handover become visible, and it is much better for that to happen with somebody to ask.
Saying who runs it now
That payroll is now run by somebody else, who to ask, and that the dates are unchanged.
It costs a sentence and prevents a month of questions going to somebody who has left.
What changes afterwards
Access for the leaver removed, mandates updated, shared credentials changed, the deputy arrangement rebuilt because the deputy may now be the main person.
The last of those is routinely forgotten, and the business goes back to having one person.
The opportunity in it
A handover is the one moment when somebody is obliged to look at how payroll is actually done. It is the best time to write the sequence, fix the credential list and set up the deputy — all of which are being done anyway.
Why two runs and not one
One run transfers the mechanics, which are already in the written sequence. The second transfers the exceptions — the things that come up only sometimes, the person with the unusual arrangement, the report that is always worth looking at.
Those are what makes somebody able to run payroll rather than able to follow instructions, and they surface as they arise rather than on request.
The questions to ask before they go
What goes wrong most often. What you check that is not in the sequence. What you would change. What you were about to do.
Half an hour, and it captures more than anything the person will write during their notice period.
Rebuilding the deputy afterwards
The step everybody forgets. If the deputy has become the main person, the business has one person again and has not noticed, because the arrangement looks the same on paper.
A handover is complete when a new second person has access, not when the first one has it.
The thing that makes handovers easy
Having documented it before anybody was leaving. Every handover problem in this note is a documentation problem that became urgent.