AWRA OpsHub Search

Built in Nairobi 1°17′S · 36°49′E EAT · UTC+3

Built for organizations operating in Kenya.

Billed in shillings. M-Pesa on your own till. KRA eTIMS inside the sales flow. A payroll engine that already knows PAYE, NSSF, SHIF and the Housing Levy. All of it is in the product, none of it is a partner connector, and the people who build it are in Nairobi, in your time zone.

Read the full Kenya market guide, with the payslip derivation
awra · ke-stack Africa/Nairobi
KES Currency of record, charged in shillings billing
M-PESA STK push · QR · C2B · B2C · B2B your Daraja keys
eTIMS OSCU · invoices · POS · reversals your PIN + device
PAYE Five bands, 2,400 relief versioned
NSSF Tier I and Tier II versioned
SHIF 2.75% of gross, 300 floor versioned
AHL 1.5% employee + 1.5% employer versioned
Support desk · Nairobi --:-- EAT
01 / 06

KES pricing

Priced and charged in shillings.

Plans are set in Kenya shillings and your subscription is charged in shillings through Paystack. The dollar figures on the plans page are converted from the shilling price at the live rate for visitors comparing across borders. The conversion only runs that way, so a bad week for the shilling does not change what you pay.

Billing profile · Kenya KES
Currency of record
Kenya shilling
Charged through
Paystack, in KES
Dollar figures
Converted from KES at the live rate
Priced by
Plan tier, not per seat
Staff on payroll
Employee records, no login needed
VAT
Prices quoted excluding VAT
  • No exchange-rate surprise on renewal

    The shilling price is the source of truth. Organizations paying a dollar-priced tool from a shilling budget absorb every swing in the rate; this one is priced in the currency your budget is written in.

  • Plan tiers, not per-seat arithmetic

    You can work out a three-year cost before speaking to anyone. Hiring does not reprice your software.

  • An employee is not a user

    Staff exist as employee records without taking up a login, so payroll for a 200-person operation runs on a plan sized for the people who actually sign in.

02 / 06

M-Pesa payments

M-Pesa on your own till, in both directions.

Collection and payment both run on your own Daraja credentials, into and out of your own shortcode. The money never passes through an account of ours, and the receipt lands against the invoice it pays.

Money in · collection

01

Your customer pays from their phone

A prompt sent straight to the handset, a QR on the invoice or the counter, or your paybill or till.

STK PUSHDYNAMIC QRC2B PAYBILLC2B TILL
KE

It lands on your shortcode

Your Daraja app, your paybill or till. We hold the credentials for your organization and nobody else’s.

03

The reference finds the invoice

A payment quoting the invoice reference attaches itself and updates the balance and the receivables ageing. A payment without a usable reference waits in a queue for someone to attach.

Money out · payment

B2C

To a phone

Pay a supplier straight to their M-Pesa number, recorded against the invoices it clears.

B2B

To a paybill or till

Business to business from your shortcode, recorded against the invoices it clears in the same way.

One thing to plan for: Safaricom sends no confirmation callback for a dynamic QR, so a QR payment is confirmed by your team rather than by the invoice changing on its own. STK push and C2B confirm themselves.

03 / 06

KRA eTIMS

eTIMS inside the sales flow, not beside it.

There is no separate tax step and no second product at the counter. Issuing an invoice or ringing up a sale is what files it, straight to KRA’s OSCU API on your own PIN, branch and device serial. Sandbox and production are a switch on your organization, so you test end to end before you go live.

01

Issue

An invoice files when it is issued, not when a draft is saved. A POS sale files at the till.

02

Transmit

To KRA on your PIN, branch and device. Invoices and POS sales draw from one numbering sequence, so they never collide.

03

Sign

KRA’s receipt signature and QR come back and print on the document your customer receives.

04

Reverse

Cancel an invoice, take a POS return or apply a credit note, and a reversal files against the original. A reversal that fails to send is retried every hour.

● We transmit

Every invoice, POS sale and reversal, with the signature and QR held on the record.

● You file

The VAT return and every iTax submission stay with you and your accountant. That is a position, not a gap.

04 / 06

Kenya payroll

PAYE · NSSF · SHIF · Housing Levy.

Kenya is the only country in our statutory rule engine. Each of the four is a maintained rule set with an effective date, applied in the order the law sets, and a rate change becomes a new version rather than an edit, so last year’s payslips still compute the way they did last year.

PAYE
Pay As You Earn
10 → 35%

Five bands at 10, 25, 30, 32.5 and 35 per cent, less the 2,400 monthly personal relief.

NSSF
National Social Security Fund
6% + 6%

Employee and employer, Tier I against its ceiling and Tier II on the balance. Both tiers reduce the PAYE base.

SHIF
Social Health Insurance Fund
2.75%

Of gross with a 300 floor, and it reduces the PAYE base, which is the line spreadsheets most often get wrong.

AHL
Affordable Housing Levy
1.5% + 1.5%

Employee and employer, and also deductible before PAYE is worked out.

One real payslip, to the cent.

On 13 July 2026 the Kenyan rule set was checked line by line against an actual employer payslip, not a worked example. The engine produced 14,112.54 before relief and the payslip said 14,112.54.

The order matters most: taxable pay is gross less the Housing Levy, SHIF and NSSF, and getting that sequence wrong produces a small error every month, in the same direction, on every employee.

The P9A is rebuilt from frozen payslip snapshots and the exact rule versions each one used, so a certificate reproduced in three years matches the one issued today.

  1. Gross payFor the month 71,789.00
  2. Affordable Housing Levy1.5% of gross 1,076.84
  3. SHIF2.75% of gross 1,974.20
  4. NSSF Tier I6% of the 9,000 ceiling 540.00
  5. NSSF Tier II6% of the balance above it 3,767.34
  6. Taxable payGross less all three, in that order 64,430.62
  7. PAYE before reliefAcross the first three bands 14,112.54
  8. Personal reliefFixed monthly 2,400.00
  9. PAYE payableMatched the payslip to the cent 11,712.54

All figures KES · bar length is share of gross · verified 2026-07-13

06 / 06

Nairobi-based team

The people who change the rate are the people who answer your ticket.

AWRA OpsHub is built and supported from Nairobi by a remote-first team. When a Finance Act moves a rate, nobody is waiting on a partner overseas: the change is made, versioned and shipped by the same team that runs your onboarding.

Nairobi · right now
--:--
East Africa Time, UTC+3. Support runs on this clock.
Support in EATYour working day, not ours overnight
Pilot on your dataSuccess criteria written down first
Training in person or liveNot a PDF manual
Module by moduleStarting where the leakage is

From Nairobi, outward

Built in Kenya. Designed for organizations that operate across Africa.

Branches in Kampala and Dar, a regional office in Kigali, suppliers in Johannesburg. The operations platform, multi-currency records and offline capture work the same in every market, and we have written a researched guide for 24 African markets that says what is local there and who carries it. eTIMS and the statutory payroll engine are Kenyan; each guide names the local system that does that job elsewhere.

Plus tax and currency profiles for 25 more African countries. Browse every market

Scope in Kenya: what runs today, what we can add, and what stays with you

What AWRA OpsHub does today

  • Billing in Kenya shillings. KES is the currency of record and the subscription is charged in shillings; the dollar figures on the plans page are converted from it.
  • M-Pesa in and out on your own Daraja credentials: STK push, dynamic QR and C2B paybill or till to collect, B2C to a phone and B2B to a paybill or till to pay.
  • KRA eTIMS on invoices, POS sales and reversals, straight to the OSCU API on your own PIN, branch and device serial, with a sandbox to validate first.
  • PAYE, NSSF, SHIF and the Housing Levy as versioned rule sets, checked to the cent against a real employer payslip on 13 July 2026.
  • The P9A rebuilt from frozen payslip snapshots, so a certificate reproduced years later matches the one first issued.
  • Payroll return files from every calculated run: the P10 CSV in KRA’s Simplified PAYE layout, the NSSF return workbook and a SHIF contribution schedule, with a readiness list naming anyone missing a KRA PIN, NSSF number or national ID. You upload each one; nothing is filed for you.
  • Offline capture for four operations: stock transfers, inventory check-out and check-in, and asset movements.

More we can add to your workspace

  • Bank statement matching alongside the M-Pesa matching that runs today, for organizations collecting mostly by bank transfer.
  • The buyer PIN on business-to-business eTIMS invoices, so a sale to a VAT-registered customer files as B2B rather than B2C.
  • KRA item classification codes held per item, in place of the single fallback classification sent today.
  • Line-by-line credit notes, so a partial credit reverses against the original lines at KRA rather than as one amount.
  • Unmatched-receipt attachment across more than 300 open invoices, for operations whose receivables run past that list.
  • Statutory payroll rules for a second country, for groups running staff in Kenya and beyond.

Where we point you to a specialist

  • We will not file your returns. We work out the deductions, transmit the invoices, produce the P9A and hand you the payroll return files to upload; the VAT return, the PAYE return and every iTax submission stay with you and your accountant. A vendor cannot take on a filing duty, so one that offers to has sold you comfort rather than protection.
  • We will not decide how a transaction is taxed. That is an adviser’s judgement with an adviser’s liability. We hold the evidence, compute what the rules say and show the working.

Each item in the middle column is commissionable now: a written specification, a timeline and a price, agreed before any money moves. eTIMS transmission and the statutory engine were both built that way, because organizations here asked for them.

Questions we are asked in Nairobi

Straight answers.

Is AWRA OpsHub actually built in Kenya?

Yes. It is built and supported from Nairobi by a remote-first team, and support runs in East Africa Time. Kenya was the first market the product was built for, which is why M-Pesa, eTIMS and the Kenyan payroll rules are part of the product rather than partner add-ons.

Can we pay for AWRA in Kenya shillings?

Yes. Plans are priced in KES and the subscription is charged in KES through Paystack. The plans page shows US dollars converted from the shilling price at the live rate, for visitors comparing across borders; the shilling price is the one you pay.

Is KRA eTIMS included or an add-on?

Included, and it runs inside the sales flow. Customer invoices file when they are issued and POS sales file at the till, straight to KRA’s OSCU API on your own PIN, branch and device serial. The receipt signature and QR come back onto the document. Cancelling an invoice, a POS return or a credit note applied to an invoice files a reversal against the original. We transmit; you still file your returns on iTax.

Which M-Pesa payments does it handle?

To collect: STK push, a dynamic QR, and C2B paybill or till. To pay: B2C to a phone and B2B to a paybill or till. All of it runs on your own Daraja credentials into and out of your own shortcode. A payment quoting the invoice reference attaches to that invoice automatically; the rest wait in a queue for someone to attach. The QR has no confirmation callback from Safaricom, so a QR payment is confirmed by your team.

Does the payroll handle PAYE, NSSF, SHIF and the Housing Levy?

Yes. Kenya is the only country in our statutory rule engine. The four deductions are versioned rule sets with effective dates, applied in the order the law sets, and were checked to the cent against a real employer payslip on 13 July 2026. Staff are employee records and do not each need a login, so payroll for 200 people does not mean 200 users.

We operate in Kenya and other African countries. Does that work?

Yes. The operations platform, multi-currency and offline capture work the same in every market. eTIMS and the statutory payroll engine are Kenyan, so each of our African market guides names the local system that carries those duties elsewhere, and payroll rules for another country are work we can scope with you.

Bring one payslip and one invoice.

We will run the payslip through the statutory engine and file the invoice to the eTIMS sandbox while you watch. An hour, on your numbers, with the team that built it.