Why eTIMS VSCU not connecting happens
eTIMS VSCU not connecting 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 VSCU shows offline or disconnected
- Invoices will not get a signature or control number
- An error mentioning the control unit connection
Match what you are seeing to the closest description above, then work through the fixes below in order, starting with the most common.
eTIMS VSCU not connecting is rarely random; match the symptom to the cause and the fix is usually minutes away.
How to fix eTIMS VSCU not connecting
Work through these in order. Most businesses resolve it at step one or two, without contacting KRA.
- 1
Check the internet connection
The VSCU needs a connection to authenticate and sign invoices with KRA. Confirm the device is online by opening any website, and switch to a stronger network if needed, then retry.
- 2
Check the VSCU configuration and credentials
A VSCU is configured with your account details during setup. If those are wrong or have changed, it cannot connect. Confirm the configuration and credentials in your setup, or ask your integrator to check them.
- 3
Restart the VSCU service
The virtual control unit runs as a service or app. Close and reopen it, or restart the device, so it re-establishes the connection. Many drops clear with a restart.
- 4
Keep selling offline while it reconnects
Record sales offline so customers are served, and let the VSCU sign and transmit them once it reconnects. You do not need to stop trading.
What not to do
Do not reinstall everything blindly
A full reinstall risks losing local configuration. Try the connection, credentials and a restart first.
Do not issue uncontrolled invoices
An invoice that the VSCU has not signed is not compliant. Wait for the unit to reconnect, then transmit.
A worked example
A shop changed its router and the next day its VSCU showed disconnected, so invoices would not sign.
The new network had changed the connection the VSCU relied on. Reconfiguring it for the new network and restarting the service brought the VSCU back online, and the queued invoices signed and transmitted.
A VSCU usually drops because something about the connection changed. Reconnect and restart before suspecting a deeper fault.
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 VSCU not connecting 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 VSCU not connecting?
What is a VSCU in eTIMS?
Can I still sell if the VSCU is offline?
What is the difference between VSCU and OSCU?
How do I reconnect my VSCU?
eTIMS VSCU not connecting 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.