Payroll Approval Checklist Before Releasing Salaries

Review payroll changes, reconcile the bank file, separate employee deductions from employer costs, and record approval before releasing Kenyan salaries.

4 min readReviewed 14 November 2026
Two finance colleagues reviewing a blank checklist beside a calculator and coral folder

True cost to employ

Gross plus employer NSSF and levy

Open calculator →

A payroll approval should identify exactly which calculation and payment file may be released. A message saying “payroll looks fine” is weak evidence if the spreadsheet changes afterwards. Use a final review pack that links the employee register, payment instructions and funding totals to one approved version.

The employer cost calculator helps estimate salary and the employer-funded contributions it includes. Add other costs separately and use actual payroll totals for approval. The employer payroll guide covers the wider obligations. The controls below are practical recommendations, not a prescribed statutory approval form.

1. Identify the run and its changes

Put the payroll period, planned payment date, version and preparer on the review cover sheet. State whether this is the normal monthly run, a supplementary run or a correction. Include the number of employees paid and the totals for gross cash pay, employee deductions and net pay.

Reconcile headcount to the previous run: previous employees, plus joiners, less leavers, with any unpaid or separately paid employees explained. Review new starters, exits, salary changes, unusual overtime, leave adjustments and changed payment details against their approvals. An unchanged overall total does not prove that each employee is correct.

For late inputs, follow the payroll cut-off and exception process. Record an unresolved item with an owner and action date. Do not hide it in an unexplained balancing adjustment.

2. Reconcile earnings, deductions and employer costs

Start with gross cash earnings and subtract employee deductions to reach net cash pay. Keep non-cash taxable benefits visible without adding them to the bank payment. Reconcile statutory liabilities and other deduction schedules separately; an employer-funded contribution must not accidentally reduce employee net pay.

As an illustrative control example, assume gross cash pay is KES 1,000,000 and employee deductions total KES 250,000. Net pay is KES 750,000. If additional employer-funded contributions total KES 75,000, the salary-and-contribution funding subtotal is KES 1,075,000: KES 750,000 to employees, KES 250,000 in deducted amounts to the appropriate destinations, and KES 75,000 in employer amounts. This assumes all those deducted amounts remain payable; internal loan recoveries or salary advances need their own reconciliation. It is not a Kenyan tax-rate example.

Review exceptions such as negative net pay, a new benefit, an unusual relief or a large month-on-month movement before approval. Request the calculation and supporting evidence, rather than accepting a plausible total alone.

3. Match the bank file to the approved register

Compare the final exported payment file with the approved net-pay schedule by employee identifier, destination account and amount. Check its record count and total, duplicate payment rows and any employee who appears in both the normal and supplementary files. If there are separate payment methods, reconcile each subtotal and their combined amount.

Have an authorised reviewer independently confirm changed bank details using the established process. Our bank-detail and failed-payment checklist explains why a payment instruction and a confirmed credit are different records. Avoid copying full account details into a general approval email.

4. Record the decision against a fixed version

Where staffing allows, separate preparation, review and payment release. In a small organisation, arrange an authorised second-person review of the final export and high-risk changes. Never share login credentials to simulate separate approval.

  • Preparer: confirms the run, totals and outstanding exceptions.
  • Reviewer: records the checks completed, queries resolved and any items still requiring action.
  • Payment authoriser: confirms the approved file, amount, funding and intended release date.

Keep the approved register and export identifiable and protected from accidental editing. If any payment amount or destination changes afterwards, produce a new version and obtain approval for that version. Retain the earlier version as superseded so it cannot be uploaded again.

5. Close payment and statutory follow-up separately

After release, reconcile the bank’s accepted and rejected transactions to the file. Investigate a rejected salary before resending it; first establish whether the original could still settle. Record who will issue payslips and close each exception.

KRA requires PAYE filing and remittance by the ninth day of the following month. Salary approval does not complete either action. Maintain each obligation’s own deadline and keep submission acknowledgements separate from payment confirmations.

Store the completed review pack with the payroll records. The useful outcome is a traceable chain from approved earnings to the money actually paid, with unresolved differences clearly assigned.

Sources and review date

Published and reviewed on 14 November 2026. The statutory PAYE deadline is supported by KRA’s official guidance linked above. Approval roles, version controls and worked reconciliation are editorial process recommendations.