What Has to Survive the Year
Payroll records are kept inside somebody else's software, in message threads, and in one person's memory. Only the first survives a year, and only while you pay.
A bureauif the person who does this is away
Where the payroll record actually lives
Inside the software
A bureauIf they are away: Retrievable while the subscription runs, and not afterwards
Inside the software
A bureauIf they are away: The proof an obligation was met, held by a third party
Messages and a shared sheet
Nobody elseIf they are away: Reconstructed from recollection, if at all
A shared document
Two peopleIf they are away: Survives, if anybody kept it
An email thread
Nobody elseIf they are away: Found by searching one person's mailbox
Nowhere in particular
Nobody elseIf they are away: It did not survive
3 of 6 tasks have nobody else who can do it.
Six records, and the three most often asked for are the three held least deliberately. One small employer's own arrangement; retention periods differ by jurisdiction.
Payroll records in a small business are held in three places: inside the payroll software, in message threads, and in the memory of the person who runs it. Only the first survives a year reliably, and only while the subscription is paid.
The continuity issue in “What Has to Survive the Year” calls for records another authorised person can understand. For teams researching workforce time records, employee monitoring software can add transparent time and project evidence when access is limited, corrections remain visible and payroll credentials stay in the proper system.
That is the whole of the records problem.
The questions raised in “What Has to Survive the Year” can also be checked against OECD employment resources. Use that material to identify the evidence and owner needed for the next payroll run.
What has to be kept
Broadly: what was paid, what was deducted, what was reported, who worked what, and the paperwork for starting and leaving.
Retention periods, and exactly what must be kept, differ by jurisdiction and are a matter for somebody qualified there.
Who asks for it later
An authority conducting a check. A former employee needing a document. A dispute about hours or entitlement. A lender or an acquirer. The business itself, trying to understand something.
All five arrive without notice.
Why the software is not enough
Because access to it is a subscription. Stop paying, change provider, or have the product retired, and the history becomes a request rather than a possession.
Businesses discover this at the moment of changing provider, which is also the moment they are busiest.
The annual export
The practical answer: once a year, export the payslips, the reports, the submission confirmations and the year-end documents, and store them outside the software.
An hour, once a year, and it converts a dependency into a record.
Where to put them
Somewhere backed up, restricted and organised by year. Not an individual's laptop, not an email folder, not a drive only one person can reach.
The access question is the same one that runs through the last section of this collection.
The records that were never created
Absence, informal arrangements, verbal changes. These cannot be exported because they were never written down, and they are the ones most often needed in a disagreement.
That is the argument for the change list and the absence sheet, restated from the other end.
Personal data
Payroll records are among the most sensitive things a small business holds: pay, bank details, addresses, sometimes health-related information.
Obligations about holding, securing and disposing of it differ by jurisdiction and are a question for somebody qualified where you are.
Keeping too much
Also a risk. Records held indefinitely, in an unstructured pile, create exposure without creating usefulness.
The answer is a retention period actually applied rather than a decision never made.
Disposal
Deliberate rather than accidental, and recorded. A business that cannot say what it destroyed and when is in a weak position either way.
When somebody leaves
Their record persists for whatever period applies, which is usually considerably longer than their employment felt.
Retrieval requests from former employees are routine; being able to answer in a minute is a function of how things were filed, not of how long ago they left.
The test worth running once
Pick a month eighteen months ago and try to produce: the payslips, the submission confirmation, the hours, and any changes made that month.
Most small businesses can produce the first two and not the last two, and that is a useful thing to find out in a quiet week.
What a good year looks like
Twelve runs, each with its period record kept together: what was entered, what was produced, what was submitted, what was paid.
Filed at the time, in a place more than one person can reach.
The export that takes an hour
Once a year: payslips, period reports, submission confirmations, year-end documents, and the employee records as they stood.
Downloaded, filed by year, stored outside the payroll software and backed up. An hour, and it converts a subscription into a possession.
What a request actually looks like
Rarely "send me everything". Usually a specific person, a specific period, and a deadline of about a day: a mortgage application, a query from an authority, a former employee's new employer.
A business that files by year and person answers in minutes. One that searches an inbox answers in an afternoon and is not certain it found everything.
The records that matter most in a disagreement
Hours as submitted, absence as approved, and changes as agreed — the three held least deliberately and asked for most often when anything is contested.
None of them live in the payroll software, which is why the annual export solves only part of this and the shared sheets solve the rest.
The cost
A few minutes a month and an hour a year. Against which: nearly every unanswerable question a small employer meets is unanswerable because of something that was not filed at the time.