NSSF Remittance Best Practices for Growing Kenyan Businesses | Emore Systems Blog
Stop wasting time debugging the Daraja API. Get a fully working M-Pesa STK Push & Callback Toolkit built in Pure PHP, ready to use on almost any PHP hosting. Check out ToolsMarketplace
Emore Systems
Ad

Track your business performance directly from all devices

Check out our Tools Marketplace for more information.

Interested

Stop wasting time debugging the Daraja API. Get a fully working M-Pesa STK Push & Callback Toolkit

Stop wasting time debugging the Daraja API. Get a fully working M-Pesa STK Push & Callback Toolkit

Interested

Managing school fees just got easier

Collect fees by M-Pesa, track balances by class and student, and get reports your finance team will actually use. Free 7-day trial, no card required.

Explore School Fees System
Ad

Does your business have a website?

Does your business have a website? If customers search for you online, can they see what you offer, your prices, location and contact you directly? We build affordable professional websites for Kenyan businesses.

Ad

Run your school's fees like a business, not a spreadsheet

Emore School System gives Kenyan boarding and day schools M-Pesa fee collection, class and student balance tracking, guardian and transport records, and CBC-ready reports — built for administrators, not accountants with a computer science degree.

Ad

New: School Fees & M-Pesa Management

Kenyan boarding and day schools can now collect fees by M-Pesa, track balances by class, and run reports admins actually understand — all in one dashboard.

Kenya Compliance

NSSF Remittance Best Practices for Growing Kenyan Businesses

Build a repeatable NSSF process that reduces errors and avoids costly compliance gaps.

nicholus munene

nicholus munene

Admin Team

Jul 28, 2026 7 min read 53 views
NSSF Remittance Best Practices for Growing Kenyan Businesses

Every month, payroll teams across Kenya push a number into an NSSF remittance form and move on to the next task. Most of the time nobody double-checks that number against the actual tier calculation, and most of the time nothing visibly breaks. But NSSF remittance is not a paperwork formality you can approximate — it is a running ledger of what an employee will eventually draw on in retirement. Get the arithmetic wrong every month for three years and you have not made a small clerical error, you have quietly shortchanged someone's pension.

This matters more as a business grows. A five-person shop can get away with a spreadsheet and a bit of luck. Once you are running payroll for thirty, sixty, or two hundred people across different salary bands, small errors in how the Tier I and Tier II contributions are calculated multiply into real money and real compliance exposure. This post walks through the mechanics of NSSF remittance under the NSSF Act 2013's tiered structure, shows the calculation with real numbers, flags the mistakes that trip up growing businesses, and lays out a process you can scale as headcount increases.

Why accuracy matters beyond avoiding a penalty notice

It is easy to think of NSSF compliance purely as a risk-avoidance exercise — remit correctly and on time, or face penalties and interest. That framing is true, but it understates what is actually at stake. Every shilling remitted (or not remitted) against an employee's NSSF number becomes part of the contribution history that determines their eventual retirement benefit. Under-remitting because a bookkeeper calculated the contribution on net pay instead of pensionable pay, or capped Tier II incorrectly, does not just create a compliance gap for the employer — it creates a permanent shortfall in that employee's contribution record. Correcting it later usually means backdated remittances, penalties, and an employee who has spent months or years underinsured for retirement without knowing it.

Treat NSSF remittance accuracy the same way you would treat payroll accuracy generally: it is not an administrative afterthought, it is a direct promise to your employees about their future.

The two-tier structure, explained

Under the NSSF Act 2013, pensionable earnings are split into two tiers, each contributed at 6% by the employee and matched at 6% by the employer — 12% combined per tier:

  • Tier I covers pensionable earnings up to the Lower Earnings Limit, currently KES 8,000. Contributions on this portion are capped at 6% of KES 8,000.
  • Tier II covers earnings above KES 8,000 up to the Upper Earnings Limit, currently KES 72,000. Contributions here are 6% of whatever falls between the two limits.
  • Anything earned above KES 72,000 is not subject to additional NSSF contribution — the scheme is capped at the Upper Earnings Limit.

Note: these Lower and Upper Earnings Limits are reviewed periodically under the Act's implementation schedule. Always confirm the current limits against NSSF's official publications before running payroll — do not assume the figures above are permanently fixed.

Worked example: an employee earning KES 50,000 per month

This salary falls between the Lower and Upper Earnings Limits, so both tiers apply in full on their respective portions:

ComponentCalculationEmployee (6%)Employer (6%)
Tier IKES 8,000 × 6%KES 480KES 480
Tier II(KES 50,000 − KES 8,000) × 6% = KES 42,000 × 6%KES 2,520KES 2,520
TotalKES 3,000KES 3,000

Combined remittance for this employee: KES 6,000 (employee and employer portions together).

Worked example: an employee earning KES 100,000 per month

This is where a lot of manual spreadsheets get it wrong. The contribution is not calculated on the full KES 100,000 — it is capped at the Upper Earnings Limit of KES 72,000:

ComponentCalculationEmployee (6%)Employer (6%)
Tier IKES 8,000 × 6%KES 480KES 480
Tier II(KES 72,000 − KES 8,000) × 6% = KES 64,000 × 6%KES 3,840KES 3,840
TotalKES 4,320KES 4,320

Combined remittance: KES 8,640. The KES 28,000 earned above the KES 72,000 ceiling is simply not pensionable under NSSF — it does not get added into either tier, and it does not push the contribution any higher. KES 4,320 per employee is the maximum monthly employee contribution regardless of how much above KES 72,000 someone earns, whether that's KES 100,000 or KES 500,000.

Common remittance mistakes

The tier structure itself is straightforward once you have seen it worked through. Where growing businesses actually lose money and create compliance risk is in a handful of recurring mistakes:

  • Calculating on net pay instead of gross pensionable pay. NSSF contributions are based on pensionable earnings, not take-home pay after statutory and voluntary deductions. Running the tier calculation on net pay understates both tiers.
  • Forgetting the employer's matching portion. Some businesses remit only the amount deducted from the employee's payslip and treat the employer match as an afterthought, or miss it entirely in cash-flow planning. The employer 6% is not optional — it is a mandatory matching contribution due at the same time as the employee's.
  • Misapplying the tier cap. This shows up two ways: applying Tier II's 6% to the full salary instead of only the amount between the two limits, or forgetting to cap Tier II at the Upper Earnings Limit for high earners (as in the KES 100,000 example above).
  • Late remittance. Delays trigger penalties and interest on the outstanding amount, and repeated lateness draws closer scrutiny during compliance checks.
  • Manual formula drift. A spreadsheet formula that correctly handles one salary band can silently break when a new hire's salary crosses a tier boundary, or when a formula gets copied into the wrong row during a headcount change.

Remittance timing

NSSF contributions are remitted monthly, and the statutory deadline is generally the 9th day of the month following the one in which the earnings were paid. Because deadlines and enforcement details can be adjusted administratively, confirm the exact current due date directly with NSSF or through the official remittance channels before you finalize your monthly payroll calendar — do not rely on a deadline you remember from a previous year without checking it still holds.

Record-keeping best practices

Good remittance habits are only half the job. The other half is being able to prove, months or years later, exactly what was calculated, deducted, and paid for every employee in every period.

  • Maintain an accurate payroll register that shows gross pensionable pay, the Tier I and Tier II contribution for each employee, and the employer match, broken out separately from other statutory deductions like PAYE and NHIF/SHIF.
  • Reconcile NSSF statements against what was actually remitted. Don't assume a successful payment confirmation means the amounts posted correctly to each employee's account — pull the statement periodically and check it against your payroll register.
  • Keep proof of payment — remittance receipts, bank confirmations, and the payroll register used to generate each month's figures — organized by period, so you can produce them quickly if NSSF or an auditor asks.
  • Retain historical records even after an employee leaves. Contribution history disputes often surface years later, when the original payroll files are the only way to resolve them.

A remittance process that scales with headcount

What works for ten employees on a spreadsheet will not work for a hundred. As you grow, move toward a process rather than a one-off monthly scramble:

  • Standardize the payroll export format so that gross pensionable pay, per-employee tier breakdowns, and totals come out in a consistent structure every month, regardless of who runs payroll that cycle.
  • Automate the tier calculation instead of relying on hand-built spreadsheet formulas. A dedicated calculation tool applies the Lower and Upper Earnings Limits consistently across every salary band and removes the risk of a formula breaking when someone's pay crosses a tier boundary.
  • Reconcile before the deadline, not after. Build in a few days between finalizing payroll and the remittance due date specifically to check the numbers, not to file them under pressure on the last day.
  • Separate calculation from submission. Have one step that produces the numbers and a second, independent step that checks them against the previous month's totals and headcount changes before anything is remitted.
  • Review the earnings limits periodically. Build a recurring calendar reminder to confirm the current Lower and Upper Earnings Limits with NSSF, since these are subject to periodic review under the Act.

None of this requires sophisticated infrastructure — it requires treating NSSF remittance as a calculation that deserves the same rigor as the payroll run itself, not a percentage you eyeball and round off. Get the tier math right, remit on time, keep your records straight, and the compliance side takes care of itself. More importantly, every employee's contribution history ends up reflecting what they actually earned and actually contributed — which is the whole point of the scheme in the first place.

Share article

Related Articles

Sign In

Welcome back to Emore Systems

Forgot password?

No account yet?

Create Account

Join Emore as a blogger

Check Your Email

Already have an account?