Blog
Seven signs your payroll system is past its best
A payroll system does not have to fail to cost you. It can be worked around, one spreadsheet and one late night at a time, until the workarounds are the payroll. These are the signs, and what the same month looks like with Albo.
The seven signs
1. Someone types the tax rates in
Every budget, somebody finds the new bands and types them into a table. The system trusts whatever they type, and nobody checks the payslips it does not show them.
2. A spreadsheet sits beside the payroll
An allowance the system cannot work out is calculated in Excel each month and loaded as a fixed amount. The real rule now lives in a file on one person's computer.
3. Closed months get opened again
A mistake is fixed by opening the posted month and editing it, or by restoring last night's backup and running it again. The record no longer shows what people were actually paid.
4. The person who prepares the payroll approves it
Nobody else sees the run before the bank does. It works, until the month it does not.
5. Returns are copied by hand
Totals are copied from reports into each authority's template and added up again to check. A figure that differs from the payslips is found later, if at all.
6. Nobody can say who changed a salary
The system holds today's figure and not the one before it. When the auditor asks, somebody searches old emails for the instruction.
7. Leavers are paid on a calculator
Final pay is worked out by hand, leave days counted from a paper file, and ZRA's certificate for a leaver typed up separately.
If three or more of these sound like your office, the system is not saving you work any more. It is making it.
The same month, two ways
| The moment | An old system | Albo |
|---|---|---|
| The budget changes the bands | Someone types the new bands into a table and checks a few payslips by hand | A signed rate pack arrives, dated from the day the law starts. Nobody types a rate |
| A run went out wrong | The posted month is opened and edited | The posted run stays as it was paid. A reversal or adjustment run puts it right |
| The payroll is ready to pay | The person who prepared it approves it too | A second person approves. Whoever prepared it never can |
| The returns are due | Totals copied into each authority's template | PAYE, NAPSA, NHIMA, skills levy and Workers' Compensation come straight from the posted run |
| The auditor asks who changed a salary | Nobody can say who, or when | Every change is on the person's history: who, when, and what it was before |
| Someone leaves mid-month | Final pay on a calculator, the certificate typed up | A settlement pays them to their last day, and the certificate comes out filled in |
| A new allowance is agreed | A spreadsheet, or a change request to the supplier | A formula you can read, tested on sample figures before it pays anyone |
Changing is less painful than it sounds
The hardest part of changing system is the move itself: years of history, tax that has to carry on, and a payday that will not wait. A move to Albo starts from the spreadsheets your old system already exports. Staff, grades, bank details, year to date, loans and leave come across, matched by the staff numbers you already use. One month is run in both systems and every payslip compared before Albo pays anyone, and you can switch in any month of the year without PAYE starting again from zero.
Read how a move to Albo goes, or book a demonstration with your own pay rules.
More from the blog
- A posted payroll month should never be edited
How to put a mistake right without rewriting history.
- Your conditions of service are formulas
Why fixed fields lose to a real collective agreement.
- Every article
Payroll in Zambia, written for the people who run it.
See Albo with your own pay rules
Tell us how many people you pay, how they are paid, and what you use today. We will show you Albo working on rules like yours, at your office or online.
- Call
- +260 979 068 878
- info@elucive.co
- Office
- Lusaka, Zambia