Why eTIMS device not registered happens
eTIMS device not registered 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 error that the device or branch is not registered
- A new till or phone cannot issue invoices
- It appears after adding a device or opening a branch
Match what you are seeing to the closest description above, then work through the fixes below in order, starting with the most common.
eTIMS device not registered is rarely random; match the symptom to the cause and the fix is usually minutes away.
How to fix eTIMS device not registered
Work through these in order. Most businesses resolve it at step one or two, without contacting KRA.
- 1
Complete the device or branch onboarding
Each device or branch that issues invoices must be registered to your eTIMS account first. Finish the device or branch registration in your eTIMS setup so the till is recognised.
- 2
Register the control unit (OSCU or VSCU)
eTIMS uses a control unit, online or virtual, tied to your account. If it is not set up, invoices cannot be signed. Complete the OSCU or VSCU onboarding for the device.
- 3
Have your integrator register it
If you use an integrated POS, the device registration is usually handled by the integrator. Ask them to onboard the new device to your account.
- 4
Select the correct branch
If you run more than one branch, make sure the device is assigned to the right branch in your setup, so its invoices are attributed correctly.
What not to do
Do not keep trying to invoice on an unregistered device
It will keep failing until the device is onboarded. Register it first.
Do not register the same device twice
Duplicate device registrations cause conflicts. Onboard each device once.
A worked example
A growing shop added a second till and got a device not registered error on the first sale from it.
The new till had not been onboarded to the eTIMS account. Once it was registered and its control unit set up, the till issued compliant invoices normally. The first till had been fine because it was registered during the original setup.
Every new device that issues invoices needs onboarding first. Register it, then sell.
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 device not registered 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 eTIMS device not registered mean?
How do I register a new till on eTIMS?
What is OSCU and VSCU?
Why does only one of my tills work?
Can I move my eTIMS to a new phone?
eTIMS device not registered 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.