Getting the Payslip to the Person
A payslip generated is not a payslip issued. How it reaches people decides whether an obligation is met and whether anybody can read it in three years.
A bureauif the person who does this is away
A payslip generated inside payroll software has not been issued to anybody. How it reaches the person decides whether the obligation is actually met, whether they can read it, and whether they can still read it after they leave.
The practical lesson in “Getting the Payslip to the Person” is that payroll depends on a sequence somebody can explain. When a small team reviews see the software at its official source for time tracking software, the useful role is to organise time and project evidence before approval, with proportional settings and a clear correction route for employees.
Three routes are common and each fails differently.
For an outside reference relevant to “Getting the Payslip to the Person”, consult World Bank jobs resources. Compare general guidance with the employer’s jurisdiction, contracts and current payroll process.
Printing it
Works for everybody, requires no account, and produces a physical thing people keep. It also costs time every period, depends on somebody being in the same building, and leaves the business with no copy unless one is deliberately kept.
| Route | Fails when |
|---|---|
| Printed | Nobody is in the building; no copy is kept |
| Emailed | An address is mistyped, or stops working at exit |
| A portal | Somebody cannot log in during the week they need it |
Still the right answer in some workplaces, particularly where people do not use a computer for work.
Emailing it
Fast and the commonest approach. The difficulties are that payslips are personal data arriving in whatever inbox the business holds, that a mistyped address sends somebody's pay details to somebody else, and that an address stops working the day a person leaves.
Where it is used, sending to a personal address rather than a work one solves the last problem and sharpens the second.
A portal
The employee logs in and sees their own. Good for access control, good for history, and dependent on people having and remembering a login they use twelve times a year.
The predictable failure is somebody who cannot get in during the week they need a payslip for a mortgage application.
What all three have to satisfy
Confidentiality, timeliness and the ability for the person to get a copy later. What is actually required of an employer differs by jurisdiction and is a question for somebody qualified there.
The mistyped address
The most consequential small error in this area. One character wrong sends a person's pay, deductions and sometimes address to a third party, and there is no recall.
Checking addresses when adding somebody, and again if a payslip bounces, is the whole of the prevention.
Password-protected attachments
Common, and worth doing properly or not at all. A password sent in the same message protects nothing; a password nobody can remember generates a request every month.
A consistent scheme, explained once, is the version that works.
After somebody leaves
They will ask for copies. If delivery was to a work address or a portal tied to employment, they cannot get them, and the business has to retrieve and send them individually.
Deciding in advance what happens here — and telling people at exit — removes a recurring small task.
What the business must keep
Its own copies, for whatever period applies, outside the payroll software.
A provider change, a subscription lapse or a product retirement otherwise takes the history with it.
Where to keep them
Somewhere restricted, backed up, and organised by period and person. Payslips are among the more sensitive things a small business holds and are frequently the least deliberately stored.
Confirming delivery actually happened
Once, after any change: did the payslips go, did they arrive, can a person open theirs. Software that reports sending is reporting its own intention.
The month it goes wrong
A changed email address, a portal outage, a printer. Worth having a fallback that does not depend on the usual route, because the obligation does not pause.
Telling people where to find them
Once, at induction, and again if the route changes. A surprising number of payslip requests are from people who have them and do not know it.
The three-month test
A person applying for a tenancy on Monday needs their last three payslips by Tuesday. Whether your arrangement can produce that, without involving you, is the practical measure of whether delivery works.
A portal passes if people can log in. Email passes if it went to an address they still have. Paper passes if they kept them, which many do not.
Deciding what happens after employment ends
Worth settling once: former employees get copies on request, from this address, within this long. Told to people at exit and written down.
Without it, the request arrives in two years to whoever happens to read the inbox, and the answer depends on who that is.
The sensitivity nobody weighs
Payslips carry pay, deductions, and often an address and a national identifier. A business that would never email a customer's bank details routinely emails these to fourteen people a month.
That is not an argument against email; it is an argument for checking addresses when adding somebody, and for a password scheme applied consistently rather than occasionally.
The one worth getting right
Not the route. The copies the business keeps, which is the part that costs nothing now and is irreplaceable later.