Payroll in Nigeria Without the Month-End Panic

Get payroll wrong and you hear about it the same day. That makes it the process most likely to be rushed, and rushing is exactly what causes the errors.

The goal is not speed. It is to make payroll boring — the same steps, the same order, no recalculation from scratch each month.

What makes it harder here than it looks

Salary is rarely one number. There is basic pay, plus housing and transport allowances, plus whatever your business adds. Statutory deductions are calculated on defined portions of that structure, not on the total, so how you split the package changes the deductions.

Then there are the pieces that change monthly: overtime, absence, a staff loan repayment, an advance taken mid-month, a new joiner part-way through. Each is small; together they are why the spreadsheet gets rebuilt every month, and rebuilt things break.

Note that PAYE bands, reliefs and thresholds have changed under recent tax reforms. Confirm current rates with your State Internal Revenue Service or your accountant before relying on any figure — including anything a system calculated last year.

Set up once, properly

• A defined salary structure — basic, housing, transport and any other components, as a consistent split. Decide it once so deductions are computed the same way every month.
• Grades rather than individual negotiations — attach staff to a grade. It keeps things consistent and makes a raise a single change.
• Bank details verified — account name matched against the number before the first run, not during it.
• Statutory registrations in place — PAYE with the correct State IRS, and pension with the employee's PFA.

The monthly run

1. Close variable input first. Overtime, absence, loan deductions, advances — a cut-off date, after which changes wait for next month. Without this, payroll never finishes.
2. Generate, then review before paying. Compare each person's net to last month. Anything that moved should have a reason you can name. This single check catches most errors.
3. Pay, then remit. PAYE to the State IRS, pension to the PFAs. Remitting in the same run as salaries is the only reliable way — "later" becomes never.
4. Issue payslips. Every month, to every employee. It prevents disputes and it is what staff need when applying for anything.
5. File the evidence against the month it belongs to.

Where audits actually go wrong

Rarely the arithmetic. Almost always the evidence: PAYE deducted but remittance receipts missing, or remitted as a lump sum that cannot be broken down per employee. Annual returns need per-employee figures — if your records only hold monthly totals, that reconstruction is painful.

Keep it per employee, per month, from the start.

The staff-loan trap

Advances and loans are where SME payroll most often drifts. Someone takes an advance, it is deducted twice, or not at all, or the balance is tracked in a notebook that disappears when its owner leaves.

Hold loan balances in the payroll itself, with the deduction scheduled and the remaining balance visible on the payslip. Then nobody has to remember.

Frequently asked questions

We are five people — is a spreadsheet not fine? It works until someone joins mid-month, takes a loan, or leaves. The problem is not the arithmetic, it is the record you will need two years from now.

Can I pay net and sort out PAYE later? That gap is precisely what audits assess, with interest. Remit with the run.

What if an employee disputes their payslip? Show the structure, the deductions and the remittance. If you cannot produce all three, the dispute is already lost.