Changing Payroll Systems: Kenya Migration Checks

Move Kenyan payroll systems with checks for opening balances, employee records, PAYE exports and parallel runs before authorising the first payment.

4 min readReviewed 12 November 2026
Two payroll professionals comparing reconciliation papers between two laptops with coral office folders

True cost to employ

Gross plus employer NSSF and levy

Open calculator →

When a Kenyan employer changes payroll systems, the most useful test is whether the same approved inputs produce an explainable payroll in both systems. A successful import message is not evidence that employee balances, deductions or return files are correct.

Use the employer cost calculator as an independent check of standard gross salary and employer-cost components. It is a baseline check, not a replacement for validating every employee's benefits, reliefs and deductions in the new system.

Agree the cutover month and preserve the old records

Name the final period processed in the old system and the first period in the new one. Record who can approve imports, payroll changes, payment files and statutory submissions. Keep a read-only export of the final approved payroll, employee master data, year-to-date totals, payslips and outstanding balances before changing anything.

Build an import register showing the source field, destination field, conversion rule and reviewer. Pay special attention to dates, decimal places, employee numbers and identifiers stored with leading zeros. Follow the broader payroll record checklist when deciding what must remain accessible after the old subscription ends.

Reconcile opening balances by employee

Compare employee counts and totals first, then investigate individual differences. A matching grand total can hide two employees' balances being swapped. Use a stable employee reference alongside the name and relevant statutory identifiers.

  • Reconcile year-to-date earnings, taxable amounts, PAYE and relief records to the approved monthly history.
  • Transfer loan and advance balances with their repayment instructions and end dates.
  • Carry forward leave balances with the correct leave type and period.
  • Check recurring allowances, taxable benefits, voluntary deductions and employer contributions separately.
  • Keep joiners, leavers and employees on leave in the correct status, without reviving ended deductions.

For example, a loan opens at KES 36,000 and an authorised KES 6,000 instalment is deducted in the first new-system month. The closing principal should be KES 30,000 if there are no other principal movements. Importing KES 30,000 as the opening balance and deducting again would incorrectly leave KES 24,000. Preserve the balance date as well as the amount.

Run the same payroll in both systems before payment

Use one agreed set of inputs for a parallel test run. Compare gross earnings, taxable benefits, allowed deductions, reliefs, PAYE, net pay and employer costs. Include ordinary salaries and real edge cases: a joiner, a leaver, a benefit recipient, a salary adjustment and an employee whose recurring deduction has ended.

Investigate every material difference. Separate a corrected old configuration from a new import error and a documented rounding difference. Do not force the new system to reproduce an old mistake simply to make totals match. Record the reason and approval for any intentional difference.

Validate return and payment exports separately

KRA's simplified PAYE-return notice directs employers to its Excel return and sample CSVs, with full rollout from 1 July 2025. Check the current official template when configuring the export. A vendor's claim that a file is “iTax ready” should still be tested against the relevant fields and totals.

Reconcile the return output with the approved payroll, then reconcile the bank-payment total with net pay. Prevent test files from being released as payments or filed as real returns. Changing software does not restart tax periods or remove existing obligations: KRA's PAYE obligations page explains the employer's deduction and remittance duty.

If identifier errors appear, use the name and KRA PIN mismatch checks to distinguish a master-data correction from an already-filed return issue. Avoid silently rewriting historical submissions during migration.

Approve the first live run and give employees a comparison

Obtain sign-off on opening balances, unresolved exceptions, the first live payroll and the files actually released. Keep a recovery plan that identifies the last approved data and who can stop a duplicate payment. After payment, reconcile the bank result and statutory acknowledgements back to the authorised run.

Tell employees when the payslip layout changes and where to raise discrepancies. An employee should be able to compare old and new gross pay, deductions and net pay even if the labels differ. The employer payroll guide provides the wider monthly workflow; these migration controls focus on preserving continuity between systems.

Sources and review date

Reviewed 12 November 2026. Official KRA sources are linked above. The migration sequence and balance example are practical editorial controls, not a claim that KRA certifies a particular payroll product.