Guides · 16 July 2026 · compliance · etims · vat

eTIMS compliance, explained for Kenyan retailers

What KRA's electronic invoicing actually requires at the till, where businesses trip up, and how to make compliance a by-product of selling rather than a month-end scramble.

If you sell in Kenya, KRA’s eTIMS (electronic Tax Invoice Management System) is the rulebook your receipts now live under: tax invoices are generated and transmitted to KRA electronically, and the invoice your customer holds should be one KRA already knows about. For a retailer this isn’t a filing-season concern — it’s a per-receipt concern, hundreds of times a day.

What it means at the till

The requirements sound simple and get hard at volume:

  • Every sale needs a compliant invoice — POS receipts, credit sales and B2B invoices alike, carrying the KRA-required details and QR verification.
  • Credit notes are fiscal documents too. A return or price correction must be submitted the same way as the sale it reverses. Untracked “minus sales” are exactly what audits find.
  • Your VAT return should reconcile to your invoices. What you transmit during the month and what you file after it need to be the same numbers, provably.

Where retailers trip up

Three failure patterns come up again and again:

  1. The offline gap. The internet drops, sales continue, and the transmissions never catch up. You need a queue that retries automatically and a report showing anything that failed — silence is not compliance.
  2. The second system. Sales happen in one tool and invoices are re-keyed into another for eTIMS. Every re-keyed document is a chance for the till, the tax system and the ledger to disagree — and eventually they do.
  3. Credit notes done informally. Refunds handled from the drawer, without a fiscal credit note, leave your transmitted sales overstated relative to your books.

The principle that fixes all three

Compliance should be a by-product of doing the work, not a separate job. If the system that prints the receipt is the system that fiscalises it, posts it to the ledger and builds the VAT return from the same record, there is nothing to reconcile at month-end — because nothing was ever allowed to diverge.

That is how Asili is built: eTIMS submission happens as the receipt prints, credit notes follow the same fiscal path as sales, failed transmissions queue and surface instead of vanishing, and the VAT return is computed from the same ledger your invoices already posted to. Ask your books a question and the answer cites the documents behind it.

Want to see the whole flow on your own products? Try the live demo or write to begin@ipos.co.ke.

Get started

See it working on your own numbers.