RhinoEtimsIssue a compliant invoice once.
Not twice.
Every business in Kenya has to file electronically signed invoices with KRA. Most do it by finishing a sale in their own system, then typing the whole thing again into a separate web dashboard. Rhino Etims removes the second typing — you sell, and the signed invoice files itself.
Get the till app
Takes sales offline and files them when the connection returns. Linux and Windows both have proper installers now. Android has a signed build. iOS has not been built at all, and this page will keep saying so until it exists.
Debian and Ubuntu. Bundles its own Java runtime, so nothing needs installing first.
Download · 76 MBOne setup, no internet needed: the app, the background receipt watcher and the Rhino Etims PDF printer (set as the default). Windows asks once, when setup opens. Uninstalling removes all of it and keeps your receipts.
Download · 215 MBSigned release build. Shares the offline queue with the desktop build. Not yet installed on a real device.
Download · 8.0 MBFurthest out. Nothing to download and no date worth quoting.
Not yet availableWhat actually happens when you press “Issue”
- 1The receipt prints immediately.
Including the QR code — before KRA has signed anything. The customer never waits on a network round trip, and the code resolves to a live status page that fills in the moment the signature lands.
- 2The invoice queues, durably.
Accepting a sale never blocks on KRA being reachable. If eTIMS is slow or down, the queue holds and drains on recovery — you can watch its depth rather than guess at a spinner.
- 3It files exactly once.
If a response is ever lost mid-flight, we ask KRA whether the invoice actually landed before we would ever send it again. A duplicate filing means a taxpayer over-declares, so the system is built to make that impossible rather than unlikely.
- 4The signature is theirs, not ours.
Signatures, invoice numbers and the VAT breakdown are read back from KRA and stored exactly as returned. We never compute a tax figure ourselves — there is only one authority on what you filed, and it is not us.
A signed invoice is never edited
Once KRA signs it, the record is frozen — enforced by the database itself, not by convention. The only reversal is a credit note, which is what KRA expects anyway.
Every submission is on the record
The exact request and the exact response, kept permanently. When an auditor asks what was sent and when, there is one answer and it is not a reconstruction.
Your books are yours
Each business is isolated at the database level, not by a filter someone might forget. When our support looks at your data, it is logged against their name and you can read that log.
Prices are VAT-inclusive
You enter what the customer pays. KRA decomposes it. This trips up integrations constantly — it is stated plainly here because getting it backwards makes every invoice 16% wrong.
Where this is today
The web application is live: items, invoicing, credit notes, receipts and queue visibility, filing against KRA through a licensed eTIMS integrator. An Android till app and a Windows desktop build share the same offline core and are in development — they are not shipped yet, and this page will say so until they are.