Why eTIMS item code not found happens
eTIMS item code not found is not random. It comes from one of a few specific causes, and once you know which one you are looking at, the fix is straightforward. Here is how the problem usually shows up first:
- An "item code not found" or "unmapped item" message
- The invoice will not submit until the item is fixed
- It appears for new products you have not classified yet
Match what you are seeing to the closest description above, then work through the fixes below in order, starting with the most common.
eTIMS item code not found is rarely random; match the symptom to the cause and the fix is usually minutes away.
How to fix eTIMS item code not found
Work through these in order. Most businesses resolve it at step one or two, without contacting KRA.
- 1
Assign the correct item code or category
Each product must map to a recognised classification so KRA knows what was sold. Open the product, set its item code or category, and save. The invoice will then submit.
- 2
Map your full product list during setup
Rather than fixing items one error at a time, classify your whole catalogue once during setup. New products then inherit a code as you add them, and the error stops appearing.
- 3
Use a sensible default for miscellaneous sales
For genuinely one-off or general items, map them to an appropriate general category so they still carry a valid code, rather than leaving them blank.
- 4
Keep tax rate and item code consistent
When you map an item, set its tax rate at the same time. An item with a code but the wrong rate will still be rejected, so handle both together.
What not to do
Do not leave the item code blank to push the sale through
A blank code fails. Take the moment to map the product; it is a one-time task per item.
Do not map everything to one random code
Forcing unrelated products under a single wrong code misclassifies your sales. Use codes that genuinely match what you sell.
A worked example
An electronics shop in Nairobi added new phone accessories and hit item code not found on the first sale. The owner thought eTIMS had rejected the products.
The accessories simply had not been classified yet. He mapped each to the right category once, and from then on they sold through without the error. He then spent twenty minutes mapping the rest of the catalogue so no new product would surprise him at checkout.
Mapping the whole product list once is far less disruptive than fixing item codes during a queue.
Trading without eTIMS-compliant tax invoices risks KRA penalties, blocked VAT input claims for your customers, and receipts a business buyer cannot expense.
Veira signs every sale to KRA eTIMS automatically, so each receipt is compliant the moment it prints, with no separate device to reconcile.
How Veira keeps this from happening
Veira handles eTIMS natively at the point of sale, so the conditions that cause eTIMS item code not found are managed for you. It validates the invoice before it is sent, records sales offline when the network drops and transmits them to KRA when the connection returns, and keeps your KRA details in order so the common causes never arise.
When something does need attention, Veira flags it in plain language with the next step, and local support is on hand rather than a queue. See how Veira works and book a free demo. It runs from KES 2,999 a month with a free terminal.
Frequently asked questions
What does item code not found mean on eTIMS?
How do I add an item code in eTIMS?
Why do new products trigger this error?
Do all items need a code, even small ones?
Does Veira handle item codes for me?
eTIMS item code not found is almost always one of a few known causes, each with a quick fix, so do not panic if you hit it during a sale. Work through the steps above, and if you would rather not deal with eTIMS errors at all, Veira handles compliance natively so most never happen. See how Veira works and book a free demo. Always confirm current KRA processes at kra.go.ke, as rules can change.