Albo Book a demo

Blog

A posted payroll month should never be edited

Payroll mistakes happen. What matters is how they are put right. Opening a closed month and changing it feels like the quick fix. It is also the fix that stores up trouble.

Once a month is paid, it has left the building

By the time a payroll month is posted, it is no longer only in the payroll system. The bank has paid the net pay. Payslips have gone out. PAYE has been filed with ZRA and the schedules with NAPSA and NHIMA. The journal is in the ledger.

Edit the month in the payroll system and none of those change. The system now says one thing and the bank, the payslips and the returns say another. The difference shows only when an auditor, an employee or ZRA asks a question, and by then the figures that were edited away are gone.

What goes wrong when a month is edited

  • The payslip an employee holds no longer matches what the system says they were paid.
  • The year to date moves, so next month's PAYE is worked out from a figure that was never paid.
  • The returns already filed no longer agree with the payroll.
  • The record of what happened is gone. Only the edited version is left.
  • If edits are possible, so are quiet ones. That is how a salary changes without anyone approving it.

Restoring last night's backup and running the month again has the same problem, with the added risk of losing everything else that was entered that day.

Put it right with a new run, not an edit

Accounting settled this long ago: you never rub out a posted entry, you post a correcting one beside it. Payroll should work the same way. There are two kinds of correction.

An adjustment run, for something missed

Bwalya worked 10 hours of overtime in March that never reached the payroll. On a basic of K8,000, in a month of 176 working hours, at time and a half, that is K8,000 × 10 × 1.5 ÷ 176 = K681.82.

March stays exactly as it was paid. An adjustment run pays Bwalya the K681.82, and PAYE on it is worked out from her year to date, so the tax for her year comes out right. The adjustment is approved like any other run.

A reversal, for a run that should not have happened

Sometimes a whole run is wrong: the wrong month, or a run posted before half the overtime was in. A reversal is a run of its own whose payslips are the original's figures with the sign turned around. It cancels the run without deleting it, and the month is then run again properly.

Either way, both the mistake and the correction stay on the record, side by side. Anyone looking later can see what was paid, what was wrong, who put it right and when.

How Albo enforces it

In Albo, posting closes a run for good. There is no edit button on a posted run, and no setting to turn one on. A correction is a reversal or an adjustment run, and it goes through the same approval as any other run: the person who prepared it cannot approve it. Tax is worked out again from the year to date, so the next payslip is right, and every kwacha paid stays on the record.

It can feel strict the first time a mistake has to be put right this way. It is also the reason an Albo payroll can answer any question an auditor asks about any month, years later.

More from the blog

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
Email
info@elucive.co
Office
Lusaka, Zambia