
True cost to employ
Gross plus employer NSSF and levy
A payroll contingency plan sets out what the employer will do when the normal process becomes unavailable. It should cover lost access, unavailable staff, failed exports and interrupted payment or filing services. The objective is to recover a controlled payroll, with evidence of what happened, rather than create an unreviewed second process in a hurry.
Use the employer cost calculator to sense-check a standard salary case. It is not a replacement payroll system, payment service or statutory filing tool. The employer payroll guide provides the normal workflow that the contingency plan should protect.
Identify the failure and the last completed stage
Start with a simple incident record: time noticed, affected system, affected payroll period, known scope and responsible owner. Separate inability to calculate from inability to approve, pay or file. If only filing is unavailable, rebuilding an already approved salary calculation may create more risk without solving the problem.
Record the last confirmed action and its evidence. An export created on a computer is not proof that a bank accepted it. A payment instruction is not proof that employees received money. Avoid treating an uncertain status as either definitely failed or definitely successful.
Prepare the recovery pack before an incident
- A controlled copy of the last approved payroll and current authorised changes.
- Totals for cash earnings, deductions, net payments and employer costs.
- Payment and filing references with their confirmed statuses.
- Named preparer, reviewer, approver and authorised deputies.
- Provider support contacts and the employer’s escalation route.
- Instructions for restoring records and checking the restored version.
Store the pack with appropriate access restrictions and test that the designated deputy can retrieve it. Keep passwords and one-time codes out of shared instructions. The payroll handover checklist covers role continuity; contingency planning additionally tests what happens when the usual route itself is unavailable.
Choose a fallback with a reviewer
List which alternative methods are actually authorised and tested for your business. A controlled backup calculation might be appropriate for some employers, but a copied spreadsheet with unverified formulas is not a dependable fallback. Specify who checks the rules, who approves the version and who is authorised to release money.
Do not bypass bank approval controls or share a former employee’s credentials to save time. If no safe fallback is available, escalate promptly to management and the relevant provider. Give employees a factual update distinguishing confirmed payments from unresolved ones, with a named contact and time for the next update rather than an unsupported promise.
Example: a bank submission times out
Suppose the approved register contains net payments totalling KES 480,000. The submission screen times out before displaying a result. Resubmitting the whole file immediately could duplicate payments if the bank accepted the first attempt.
The authorised finance contact should establish the first submission’s status using its reference and bank records. If some entries succeeded and others failed, reconcile at employee level before approving any replacement file. The replacement should contain only the confirmed outstanding amounts. Keep both file versions and their references linked to the same incident.
The failed salary-payment checklist explains employee-level tracing. The payroll approval checklist remains relevant even when a fallback is used.
Keep filing deadlines in view
KRA’s PAYE guidance sets filing and payment by the ninth of the following month. Do not assume that a local outage automatically changes a statutory deadline. Check official notices and contact the relevant authority through its published channels if a problem affects compliance.
Retain timestamps, error messages and support references without exposing employee data unnecessarily. An incident record documents the facts; it is not a guarantee of penalty cancellation or an extension. Track each obligation separately instead of marking the month complete because salaries have been paid.
Reconcile recovery and test the plan
When service returns, compare the restored payroll with the approved fallback, bank outcomes and returns already filed. Enter authorised corrections once, with a clear audit trail. Do not import the fallback as an additional salary run when it represents the same earnings.
Hold a short practice exercise before a real outage: ask the deputy to locate the pack, identify an uncertain payment and explain the approval route. Record gaps and correct them. After an incident, update the plan with what failed, which evidence was missing and who owns the improvement.
Sources and review date
Published and reviewed on 18 November 2026. Official sources are linked above. Examples and checklists are editorial guidance, with assumptions stated.