Getting a business ready for eTIMS

Most businesses treat eTIMS as a software purchase. It is better understood as a records problem that software can help with, and the sequence matters: the businesses that find this painful are almost always the ones that bought something before fixing what was underneath it.

Fix access before anything else

The most common blocker has nothing to do with eTIMS. It is that nobody currently at the business can sign in to iTax, because the person who set it up has left, or the registered phone number was theirs, or the email is one nobody checks. This becomes urgent at precisely the moment it is hardest to resolve. Check it now, while nothing depends on it. If the registered details are wrong, correcting them is a separate process with its own timeline, and discovering that on the day you planned to onboard is how a week disappears.

Work out what you actually issue

Before choosing anything, count. How many documents does the business produce in a month? How many of those go to another business that will claim the purchase, as opposed to a walk-in customer who wants proof of payment? A consultancy issuing six invoices a month and a distributor issuing four hundred from vans have different problems and should not choose the same way. This count is also the one that tells you whether the difficulty ahead is technical or operational. A business that cannot answer it does not have an eTIMS problem yet; it has a records problem, and eTIMS will make that visible rather than solve it.

Choose for the counter, not the demo

The feature that decides whether a system survives contact with a real shop is rarely the one demonstrated. Ask what happens when the connection drops, because a business that cannot sell during an outage has a worse problem than a compliance one. Ask how a correction is made when an invoice goes out wrong. Ask how the buyer's PIN is captured at the counter, with a queue behind them, rather than reconstructed afterwards. Those three answers predict adoption better than any feature list, because the failure mode is not missing capability. It is staff quietly reverting to the old way when the new way is slower under pressure.

Test before you depend on it

Issue one invoice and confirm it validates before the first real customer is standing there. This is skipped constantly, and the cost of skipping it is always paid in front of someone.

Train for the exception, not the happy path

Whoever stands at the counter needs to know three things: how to capture a business customer's PIN, what to do when a customer returns something, and what to do when the network is down. The routine sale trains itself. The exceptions are where the records break, and they break silently.

What this does not settle

Whether a particular business is required to issue electronic tax invoices depends on its registration, its turnover and the kind of transactions it makes. That is a question for KRA or a registered tax agent, and no readiness checklist answers it. What the sequence above does is make sure that when the answer comes back, the business can act on it.