Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Payroll for Kenya
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.
If any of these ring true, you are exactly who this was built for.
NSSF tiers and SHIF rules changed; your formulas found out at penalty time.
Every 9th of the month is a scramble to make payroll, filings, and the ledger agree.
HR as the answer desk for payslips, balances, and leave days.
Enumerators and casual workers on M-Pesa with no consistent records.
Each capability links to a deeper feature tour.
PAYE, NSSF, SHIF, and housing levy computed on current rules — updates ship to you.
Outputs shaped for the portals, reconciled to the payroll register.
Balances, requests, and attendance feeding payroll from one source of truth.
Payslips, leave requests, and balances online — HR stops answering the same question.
Casual runs with proper records and rates, distinct from regular payroll but fully visible.
Every run posts to your books automatically — the reconciliation triangle closes itself.
Running in the product today
Absences — on the roadmap, and commissionable now
What we would decline, and would rather say now
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. No date 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.
Employees, salaries, benefits, and deductions loaded and verified.
Side-by-side with your current process; every difference explained.
Filings ready, payslips out, journals posted — deadline week becomes routine.
What each Kenyan compliance regime actually requires from your system — eTIMS invoicing, statutory payroll, withholding, records — plus vendor test questions.
The statutory stack done right, plus the NGO layer: allocating staff costs to grants, paying casuals and enumerators properly, and the monthly reconciliation triangle.
License models, the implementation costs nobody quotes upfront, honest three-year totals in KES, and the questions that expose hidden pricing.
Labour records are built for two readers: the employer and the regulator. Export manufacturing adds a third with commercial leverage — the buyer — and they are not asking whether your numbers are correct. They are asking whether anyone but you could have produced them.
American overtime is owed above forty hours in a workweek — a fixed seven-day period the employer designates, which need not start on Monday and need not match the pay period. Our records have no workweek in them at all, and the boundary they do enforce, by locking it, is the calendar month.
A court has told member states to require a system that measures each worker's daily hours. Ours stored a 22:00 to 06:00 shift perfectly and reported its duration as empty — because clock-out is a time with no date, and six separate copies of the same arithmetic each decided an end before a start has no answer. Fixed the day this was published.
Questions we are asked here
The product updates; you review the first affected run against official rates and carry on. No formula edits, no forum threads about new bands.
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.
Yes — self-service gives staff payslips, leave balances, and requests online, with role-based access keeping everything else out of view.
Yes, grant cost allocation is built in — see the dedicated page on NGO payroll for the donor-defensible setup.
Run one month in parallel and see the statutory math, filings, and postings handled.