Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Payroll for Kenya
Payroll that keeps up with KRA so you don't have to
Current statutory rules shipped as updates, filings ready on time, payslips online, and every run posted to your books — payroll as a by-product of good records.
Sound familiar?
If any of these ring true, you are exactly who this was built for.
The spreadsheet with last year's bands
NSSF tiers and SHIF rules changed; your formulas found out at penalty time.
Filing-week reconstruction
Every 9th of the month is a scramble to make payroll, filings, and the ledger agree.
Payslip requests all day
HR as the answer desk for payslips, balances, and leave days.
Casuals paid off the books
Enumerators and casual workers on M-Pesa with no consistent records.
What you get with AWRA OpsHub
Each capability links to a deeper feature tour.
The full statutory stack
PAYE, NSSF, SHIF, and housing levy computed on current rules — updates ship to you.
Filing-ready returns
Outputs shaped for the portals, reconciled to the payroll register.
Leave & attendance
Balances, requests, and attendance feeding payroll from one source of truth.
Employee self-service
Payslips, leave requests, and balances online — HR stops answering the same question.
Casuals & stipends
Casual runs with proper records and rates, distinct from regular payroll but fully visible.
Ledger posting
Every run posts to your books automatically — the reconciliation triangle closes itself.
Running in the product today
- Kenya is the only country in our statutory rule engine. Not first and not best-supported — the only one. PAYE, NSSF, SHIF and the Affordable Housing Levy are maintained here rather than in a connector to somebody else's engine.
- Cross-checked to the cent against a real employer payslip on 13 July 2026, including the order the levies apply in — gross less housing levy, SHIF and NSSF — which is the part that is wrong most often and visible least often.
- Versioned rule sets with effective dates. A rate change is a new version rather than an edit, so last year's payslips keep computing the way they computed last year.
- The P9A rebuilt from frozen payslip snapshots and the exact rule versions each payslip referenced, so a certificate reproduced in three years is identical to the one issued today whatever happened to the rates in between.
- An employee is not a user. Staff exist as records without consuming a login, so a 200-person workforce does not need 200 seats.
- An approved run posts into the payments register as money-out per employee, plus a double-entry journal posting for the run's total net pay — so payroll lands in the same ledger as everything else rather than beside it.
More we can add — on the roadmap, and commissionable now
- A payout rail. Today the run records payroll as already paid: approving it writes the payments and the journal, it does not move money, and no bank file or mobile-money disbursement is produced. You pay staff however you pay them today and the record matches it. This is the single most important sentence on this page and it is the one most likely to be assumed past.
- Return-ready output for iTax. We compute the deductions and produce the P9A today. Filing itself stays with you and your accountant — that separation is a position we hold, in the column to the right — and a formatted return file you upload is the build that sits inside it.
- One country. Every other market page on this site says local payroll is not ours and points you at a local provider, because it is not, and discovering that in month two would be worse than reading it here.
- NSSF Tier II's upper ceiling of 72,000 is unconfirmed. The verifying payslip's gross fell below it, so that one figure rests on the published schedule rather than on evidence we have personally seen.
What we would decline, and would rather say now
- We will not file on your behalf. A filing obligation cannot actually be transferred to a software vendor — you carry the assessment either way — so a vendor who accepts it has sold you comfort rather than protection. What we do instead is make the position reconstructable to the cent when your accountant asks.
- We will not advise on how somebody should be classified or paid. Whether a worker is an employee or a contractor, and how a benefit should be treated, are questions with liability attached and they belong with your adviser. We compute what the rules say and show the working.
The payout rail is the obvious build and it is commissionable now: a real disbursement integration would hold the run as pending and flip it on a webhook, exactly as the existing M-Pesa and Paystack vendor payment flows already do — so the pattern exists and the work is wiring rather than research. Written specification, timeline and price, agreed before any money moves. A date belongs in a quote rather than on this page.
Take the first item in the middle column into any demo you run. Ask to approve a payroll run and then ask where the money went. The answer here is that it went nowhere and the record says paid, which is correct behaviour for a system that computes rather than disburses — but only if you knew that before you bought it.
How teams get started
Import staff & contracts
Employees, salaries, benefits, and deductions loaded and verified.
Run one month in parallel
Side-by-side with your current process; every difference explained.
Go live before the 9th
Filings ready, payslips out, journals posted — deadline week becomes routine.
Guides from our blog
eTIMS, PAYE, NSSF & SHIF: Compliance Features Your ERP Must Have
What each Kenyan compliance regime actually requires from your system — eTIMS invoicing, statutory payroll, withholding, records — plus vendor test questions.
NGO Payroll in Kenya: PAYE, NSSF, SHIF for Program Staff
The statutory stack done right, plus the NGO layer: allocating staff costs to grants, paying casuals and enumerators properly, and the monthly reconciliation triangle.
ERP Pricing in Kenya: What to Expect (KES Breakdown)
License models, the implementation costs nobody quotes upfront, honest three-year totals in KES, and the questions that expose hidden pricing.
One Person, Two Departments
HR records which department an employee belongs to. Procurement asks which department a login belongs to. Two columns on two tables — and when HR provisions that employee a login, the department does not travel with it.
Eleven Things on a Payslip
Singapore prescribes what a payslip contains, item by item. Two are dates of payment, two are the first and last days of a period, and one is a period that need not be the salary period at all — so we held our payroll against all eleven.
Three Classifications the Report Wants
South Africa's employment equity regime sets numerical targets by sector and occupational level, and a certificate for government work turns on them. The report asks your HR record for three classifications, and a conventional employee record carries none of them as fields.
Questions we are asked here
Frequently asked questions
What happens when statutory rates change?
The product updates; you review the first affected run against official rates and carry on. No formula edits, no forum threads about new bands.
Does it handle benefits and taxable perks?
Yes — housing, car, and other taxable benefits enter gross correctly, and per-diem policies can align with KRA thresholds so reimbursements stay non-taxable where they should.
Can employees see their own payslips?
Yes — self-service gives staff payslips, leave balances, and requests online, with role-based access keeping everything else out of view.
We are an NGO — can costs split across donors?
Yes, grant cost allocation is built in — see the dedicated page on NGO payroll for the donor-defensible setup.
Make the 9th boring
Run one month in parallel and see the statutory math, filings, and postings handled.