Why eTIMS OSCU not working happens
eTIMS OSCU not working 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:
- The control unit is unresponsive or shows an error
- Invoices will not sign
- It follows a power cut, a move, or a new setup
Match what you are seeing to the closest description above, then work through the fixes below in order, starting with the most common.
eTIMS OSCU not working is rarely random; match the symptom to the cause and the fix is usually minutes away.
How to fix eTIMS OSCU not working
Work through these in order. Most businesses resolve it at step one or two, without contacting KRA.
- 1
Check power and connection
Confirm the OSCU has power and is connected to the network and to your till. A loose cable or a dropped connection is the most common cause. Reconnect and watch for it to come back online.
- 2
Confirm the unit was onboarded
An OSCU must be registered to your eTIMS account to sign invoices. If it is new or was reset, complete the onboarding before expecting it to work.
- 3
Restart the control unit
Power the unit off and on, and restart the till it serves. A clean restart clears many temporary faults.
- 4
Contact your supplier or integrator
If the unit stays unresponsive after a restart, it may be a hardware or firmware fault. Your supplier or integrator can diagnose or replace it.
What not to do
Do not keep invoicing on a dead control unit
Invoices cannot be signed without it. Resolve the unit first, recording sales offline meanwhile if your system allows.
Do not open or tamper with the hardware
A control unit is a regulated device. Let the supplier or integrator handle hardware faults.
A worked example
After a power cut, a shop found its OSCU unresponsive and could not sign invoices.
The unit had not powered back up cleanly. Switching it off fully and on again, and restarting the till, brought it back, and invoicing resumed. The power cut, not a fault, had caused it.
Most OSCU problems trace to power, connection or onboarding. Check those before assuming the hardware has failed.
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 OSCU not working 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
Why is my eTIMS OSCU not working?
What is an OSCU in eTIMS?
How do I restart my eTIMS control unit?
Do I need an OSCU or can I use software?
Can I keep selling if the OSCU fails?
eTIMS OSCU not working 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.