eTIMS now checks your books — what that means for the systems you run

KRA has turned electronic invoicing from a compliance chore into a systems problem. If your software can't talk to eTIMS cleanly, it now costs you money.

For a while, eTIMS felt like one more KRA portal to log into. That’s over. As of this year, the Kenya Revenue Authority validates the income and expenses on your tax return against eTIMS as a primary data source — which means an expense without a matching eTIMS-generated invoice is no longer deductible. A cost your business genuinely incurred can be disallowed simply because the paperwork never made it into the system.

That changes the stakes. Invoicing compliance used to be a finance task you could do by hand at the edges. Now it’s wired directly to what you pay in tax, at the volume of every transaction you process. For any business doing more than a handful of invoices a day, that stops being a manual job and becomes a question about your software.

This is an integration problem, not a paperwork problem

eTIMS is the more modern successor to the old ETR-device world. Instead of a physical tax register, it can run on a computer, a phone, or — the part that matters here — connect to your own systems through an API. Every compliant invoice has to carry specific data: your PIN, a control unit serial, a unique invoice number, and a QR code, electronically signed and kept for at least five years.

You do not want your team re-keying each sale into a separate eTIMS tool after they’ve already entered it in your ERP or point-of-sale. That’s double work, and double work is where errors and missed invoices live. The right pattern is simple to say and harder to do well: the system where the sale happens should hand the invoice to eTIMS automatically, get the signed result back, and store it against the original record. One entry, one source of truth.

Where it gets hard — the parts vendors gloss over

A demo that fires one clean invoice into eTIMS proves almost nothing. The real work is in the awkward cases:

Credit notes, returns, and cancellations. A sale isn’t always final. Your integration has to handle reversing or amending an invoice correctly, not just creating one.
Downtime. Networks drop and the KRA endpoint isn’t always up. What happens to a sale made while eTIMS is unreachable? It needs to queue and reconcile later — not silently vanish or block the counter.
Branches and multiple systems. A distributor billing from three locations, or a business running both a POS and an ERP, needs every channel reporting consistently under the same rules.
Reconciliation. At month-end, what’s in your books and what KRA has should agree. If you can’t prove that quickly, you’ve moved the manual work, not removed it.

Get these wrong and the failure is expensive in a way that compounds: disallowed expenses, plus penalties that can reach KES 1 million or 10% of the tax involved.

Getting it right

If you’re on a modern ERP, the cleanest route is a proper integration between that system and eTIMS, built to handle the edge cases above and to reconcile without anyone exporting spreadsheets. If you’re on older or home-grown software, this is usually the moment that forces the question of whether it’s worth wiring up — or whether you’ve outgrown it.

Either way, treat eTIMS as what it now is: a live link between your operational systems and your tax position. That’s exactly the kind of integration we build — quietly, in the background, so your team keeps invoicing the way they always have and compliance just happens.

Not sure your current setup is handling it cleanly? Get in touch and we’ll take an honest look.

Tax rules change — confirm current eTIMS requirements and deadlines with KRA or your tax adviser before acting.