Paying school staff correctly is harder than it looks. It isn't just salary minus a few deductions. You have PAYE tax bands that change with income, pension contributions split between employee and employer, staff who joined mid-month, and teachers on unpaid leave. Do it in a spreadsheet and you will, eventually, underpay someone or over-remit tax. Either way, trust erodes.
Here is how school payroll actually works in Nigeria, and how to run it so that pay day is boring, which is exactly what pay day should be.
Understand the three things that come out of gross pay
For most schools, a staff member's net pay is their gross minus three things.
First, PAYE tax, worked out on a banded scale where the first slice of income is taxed at a low rate and later slices at higher rates. You don't apply one flat percentage; you work up the bands. Second, pension, where the employee contributes a percentage of qualifying pay and the school adds an employer portion on top. Third, any other agreed deductions like loans or cooperative contributions.
The banded PAYE calculation is where spreadsheets break. Bands change with legislation, and a formula written two years ago quietly goes stale. The safer approach is a system that holds tax bands as dated versions, so when the law changes you add a new set of bands with an effective date and the old payslips stay correct.
Handle mid-period joiners and leavers with proration
A teacher who starts on the 15th shouldn't be paid a full month. Proration multiplies basic pay by the days actually worked over the working days in the period. The same logic handles unpaid leave, where approved unpaid days reduce pay while paid leave like sick or annual does not. Getting this automatic removes a whole category of "why was I paid this much?" conversations.
Separate the person who prepares pay from the person who approves it
Payroll is a control problem as much as a maths problem. The bursar who prepares a pay run should not be the only person who can release the money. A healthy flow looks like this: payroll is generated and reviewed, a director or authorised signatory approves it, and only then are transfers sent to staff bank accounts.
This is how UnifyLearn runs payroll. A pay run is generated, variances against last month are flagged for review, an authorised signatory approves, and payments go out as bank transfers, with each staff member marked paid only when the money actually moves. If one transfer fails, it's isolated and retried without re-running the whole batch.
Issue payslips when money moves, not before
A common and damaging mistake is telling staff "your payslip is ready" at generation time, before approval and before payment. Then a transfer fails and a staff member is holding a payslip for money that never arrived. Payslips should go out per staff member at the moment their payment succeeds. Boring, correct, and trustworthy.
Keep tax and pension filing painless
At some point you have to file. The month is far less painful if your payroll can produce the schedules for you: a PAYE schedule listing each staff member's taxable pay and tax, and a pension schedule showing employee and employer contributions. Exporting these as ready-to-file files turns a day of reconciliation into a click.
The proprietor's view
The reason to get payroll right isn't only compliance. It's that your best teachers stay when they're paid correctly, on time, every month, with a payslip they can trust. That reliability is a retention tool.
Payroll works best when the money it draws on is already organised. If fee collection is still messy, start with managing school fees in Nigeria first. And because payroll touches sensitive staff data, it's worth reading how we handle student and staff data protection under the NDPR.
Want to see a pay run against your own staff list? Start a free trial or see pricing.