PAYE Payroll Checklist: A Monthly Workflow for Zero Filing Stress

Every employer in Kenya runs into the same monthly deadline: PAYE has to be calculated correctly, deducted from every payslip, and remitted to KRA before the cut-off. Miss a band, apply the wrong relief, or forget to update a new hire's details, and you're not just risking a penalty — you're risking an employee opening their payslip and finding the wrong number on it. That's the kind of mistake that erodes trust fast, even when it was an honest arithmetic slip.

This isn't a sales pitch for our PAYE Calculator, though we'll get to where automation genuinely helps. It's a practical breakdown of how PAYE actually works in Kenya today, a full worked example so you can check your own payroll math, and a monthly workflow you can lift straight into your process.

Why PAYE Errors Cost More Than They Look Like They Should

PAYE mistakes rarely show up as one clean, isolated problem. KRA charges penalties for late filing and late payment, and interest accrues on unpaid tax until it's cleared — so a small under-remittance in January can quietly grow every month it goes uncorrected. Correcting a filing after the fact usually means amending returns, explaining the discrepancy, and in some cases fielding queries directly from KRA, which takes far more staff time than getting it right the first time.

Then there's the cost that doesn't show up on any tax notice: employee trust. If someone's net pay is wrong two months running, or their PAYE deduction doesn't match what a quick calculation says it should, that employee starts double-checking every payslip — and starts asking colleagues if they should too. Payroll is one of the few functions where "mostly right" doesn't feel right to the person on the receiving end. Getting the calculation right, consistently, is part of how a business earns the right to be trusted with people's income.

How Kenya's PAYE Bands Actually Work

PAYE is a graduated tax — meaning different slices of an employee's monthly taxable pay are taxed at different rates, not one flat rate applied to the whole salary. The current standard KRA bands are:

After the tax is calculated across those bands, every employee subtracts a flat personal relief of KES 2,400 per month from the result — this is a straight reduction of the tax bill, not a change to the taxable pay itself. On top of that, employees pay an Affordable Housing Levy of 1.5% of gross pay, which the employer matches with an equal 1.5% contribution of their own. The levy sits alongside PAYE rather than inside it — it's calculated on gross pay, not on taxable pay after relief.

Important: these bands, the relief amount, and the levy rate are all set through the Finance Act and are reviewed periodically. Treat the figures above as the framework to understand the mechanics — but before you run any actual payroll, confirm the current thresholds and rates on KRA's iTax portal or official KRA publications. A band boundary that shifts by even a few hundred shillings changes the tax due for everyone near that line.

Worked Example: KES 80,000 Gross Salary

Let's walk through an employee earning a gross monthly salary of KES 80,000. Taxable pay for PAYE purposes is gross pay reduced by allowable deductions, the main one being the employee's NSSF contribution. For this illustration, assume an NSSF deduction of KES 2,160 (your actual figure depends on NSSF's tiered contribution structure, so treat this as a placeholder to show the mechanic, not a quoted rate).

• Gross pay: KES 80,000
• Less NSSF (illustrative): KES 2,160
• Taxable pay: KES 77,840

Now apply the bands to KES 77,840:

• First KES 24,000 at 10% = KES 2,400.00
• Next KES 8,333 (24,001–32,333) at 25% = KES 2,083.25
• Remaining KES 45,507 (32,334–77,840) at 30% = KES 13,652.10

Total tax before relief = 2,400.00 + 2,083.25 + 13,652.10 = KES 18,135.35

Subtract personal relief of KES 2,400: 18,135.35 − 2,400 = PAYE payable ≈ KES 15,735

Separately, the Affordable Housing Levy is calculated on gross pay, not taxable pay: 80,000 × 1.5% = KES 1,200 deducted from the employee, with the employer contributing a matching KES 1,200 on top (an employer cost, not a further deduction from the payslip).

Putting it together for this employee's payslip:

• Gross pay: KES 80,000
• Less NSSF: KES 2,160
• Less PAYE: KES 15,735
• Less Housing Levy: KES 1,200
• Less SHIF (statutory, calculated on gross — confirm current rate): amount not shown here
• Net pay before SHIF: approximately KES 60,905

Run the same steps on your own payroll figures and you'll catch band or relief errors immediately if your software's output doesn't match.

The Deductions That Interact With PAYE

PAYE doesn't sit alone on a payslip — three statutory deductions interact with it, and the order they're applied in matters:

1. NSSF is applied first. The employee's NSSF contribution is subtracted from gross pay to arrive at taxable pay, which is the figure PAYE bands are actually applied to. Get NSSF wrong and your PAYE calculation is wrong even if the bands and relief are applied perfectly.
2. SHIF is calculated on gross pay as a statutory health contribution, deducted alongside PAYE rather than affecting the PAYE calculation itself.
3. Affordable Housing Levy is also calculated on gross pay at 1.5%, deducted from the employee and matched by the employer, sitting outside the PAYE calculation entirely.

The practical takeaway: NSSF has to be settled before you touch the PAYE bands, while SHIF and the housing levy are calculated independently off gross pay and simply added to the list of deductions on the payslip.

Filing and Paying PAYE on Time

PAYE is filed and paid monthly through KRA's iTax platform, and the standing deadline is generally the 9th of the month following the payroll month — so PAYE deducted in July is due by the 9th of August. That said, deadlines can shift when the 9th falls on a weekend or public holiday, and filing requirements are occasionally updated. Always confirm the exact current due date on iTax or KRA's official communications rather than assuming last year's deadline still applies — this is a five-minute check that prevents an avoidable penalty.

Employee Records That Must Stay Accurate

PAYE errors often start upstream of the calculation itself, in employee records that haven't been kept current:

• KRA PIN: every employee needs a correct, verified KRA PIN on file. A missing or mismatched PIN causes filing rejections and makes it harder for the employee to reconcile their own tax record.
• Employment classification: whether someone is casual, permanent, or on contract affects how their pay is treated. Casual workers, part-time staff, and contractors don't all sit in the same payroll bucket, and misclassifying a permanent employee as a casual (or vice versa) can mean the wrong deductions are applied entirely.
• Salary and benefit changes: a raise, a benefit-in-kind, or a change in allowances that isn't updated before the next payroll run means that month's PAYE is calculated on stale figures.

Misclassification is one of the quieter causes of PAYE errors because it doesn't look like a calculation mistake — the bands and relief might be applied perfectly, but to the wrong base figure or the wrong treatment altogether.

A Monthly PAYE Workflow You Can Actually Follow

Most PAYE stress comes from cramming everything into the days before the deadline. Spreading the same checks across the month removes almost all of it:

• Week 1: Confirm all new hires, exits, and salary or role changes from the previous month are reflected in payroll records. Verify KRA PINs for any new employees.
• Before the payroll run: Verify gross pay figures, NSSF contributions, SHIF, and personal relief eligibility are current for every employee — not just the ones who changed.
• After the payroll run: Reconcile the total PAYE withheld across all payslips against what you're preparing to remit. Any mismatch here is far easier to trace right after the run than a month later.
• Before the 9th: File the PAYE return and make payment through iTax, then archive the filed return alongside that month's payslips. Keeping this archive means you're never scrambling to reconstruct a month's numbers if KRA raises a query later.

Where Automation Actually Helps

None of the steps above are complicated in isolation — the risk is doing dozens of them by hand, every month, without a mistake compounding somewhere in a spreadsheet formula. This is where payroll software or a dedicated PAYE calculator earns its place: it applies the current bands, relief, and levy consistently to every employee, every month, without a copy-paste error creeping into row 47. It won't replace the judgment calls around classification or the discipline of keeping records current — but it removes the arithmetic as a source of error, which is usually where the costly mistakes start.

Run your own numbers through the worked example above against whatever tool or spreadsheet you're currently using. If the figures match, you've confirmed your process is sound. If they don't, you've just found a problem before KRA did — which is exactly the point of building a monthly workflow instead of a once-a-year scramble.