A payroll run can finish on time and still be wrong. An unapproved salary change, an employee who remains on the register after leaving, or a statutory payment that never reaches the right account can all sit behind a successful bank transfer. Good payroll governance makes those failures harder to create and easier to detect.
The objective is straightforward: pay the right people the right amounts, protect their information, and keep evidence that explains each decision. That requires an agreed process across HR, finance and management. Buying payroll software helps with calculations, but the controls around its inputs and outputs determine whether the result can be trusted.
Start with clear ownership
Write down who maintains employee records, who approves pay changes, who runs calculations, who reviews exceptions and who releases funds. A manager approving a bonus should not automatically be able to add it to payroll and authorise the payment. Where a small team cannot separate every duty, give a director or another independent reviewer access to the change report and bank totals before release.
Assign deputies as well. A control that disappears when one payroll officer is on leave is a dependency, not a reliable process. Each role should have a deadline, a required evidence file and an escalation contact.
Control changes before calculating pay
Keep one approved change register for starters, leavers, bank details, salary revisions, deductions and variable pay. Every entry should show the employee identifier, effective date, authorising person and supporting document. Confirm bank changes through a trusted contact channel rather than relying on an email containing new account details.
- Reconcile new starters to approved appointments and signed terms.
- Match leavers to the final working date and approved final-pay calculation.
- Check promotions and salary changes against their effective dates.
- Require approved attendance or performance records for variable payments.
- Lock the change register at the payroll cut-off and record later exceptions separately.
Review movements, not just the total
A stable total can conceal an overpayment to one person and an underpayment to another. Compare the current register with the previous month at employee level. Flag unexpected changes in gross pay, net pay, allowances, deductions and headcount. Investigate duplicate bank accounts, missing identifiers, unusually large arrears and employees receiving zero or negative net pay.
A flag is a question to resolve, not proof of wrongdoing. A legitimate backdated promotion can explain a large increase. Record the explanation and the reviewer so that the same issue does not have to be reconstructed during an audit.
Connect payroll to filings and finance
Maintain a calendar for PAYE, NSSF, SHIF and the Affordable Housing Levy, using the current regulator guidance for the relevant period. A payroll deduction is not evidence that money was remitted. Match the approved register to the return, payment instruction and receipt for each obligation.
For PAYE responsibilities, refer to KRA's employer guidance. Keep an owner for checking updates and documenting the effective date of a configuration change.
| Control | Evidence to retain | Reviewer |
|---|---|---|
| Employee and pay changes | Approved change register | HR lead |
| Calculation and exceptions | Payroll register and resolved exception log | Independent payroll reviewer |
| Bank release | Authorised bank file and payment confirmation | Finance approver |
| Statutory settlement | Returns, receipts and reconciled balances | Finance or compliance lead |
Protect payroll information
Restrict access by role, use individual accounts and remove permissions promptly when responsibilities change. Share payslips through an appropriate private channel. Avoid sending an entire salary register when a manager only needs information about their own team. Store working files in approved locations and apply the organisation's retention rules to both final records and temporary exports.
A useful monthly sign-off
Before release, the reviewer should confirm headcount, approve material movements, reconcile the bank file and check statutory totals. After release, reconcile returned payments and actual receipts. Track unresolved differences with an owner and completion date. Close the cycle only when the accounting entries and payment evidence agree with the final approved register.
Start with a one-page control checklist and improve it after each exception. Trinity's Payroll and HR Operations service can help establish the workflow, while the Payroll Risk Scanner provides an initial view of areas worth investigating.