What the OSCU is and when it fits
The OSCU, or Online Sales Control Unit, is one of KRA's control units for connecting a business system to eTIMS. As the name suggests, it is oriented to online operation, transmitting to KRA over a connection, and suits environments with reliable connectivity where invoices are sent to KRA online.
Setting up an OSCU is a technical integration: configuring the unit per KRA's specification, connecting your system, and following KRA's certification and testing so invoices transmit and validate. The choice between OSCU and the software-based VSCU depends on your volume, connectivity and architecture. Because the exact setup and certification depend on KRA's current process, scope it against KRA's official documentation and a qualified integrator, and remember that compliant software removes the need to set up a control unit at all.
Setup is tied to the device, which is the fact that governs everything else here. Replacing hardware is therefore not a copy-and-paste exercise: the new device goes through registration rather than inheriting the old one’s identity, and attempts to shortcut that are what produce device-not-registered errors later.
Plan replacement while the old device still works. Registering the new one before the old is out of service means you are choosing your moment rather than reacting, and it keeps a working till available if the new setup needs a second attempt.
Want to see it running in your own business first?
Sign UpThe cheapest eTIMS integration is often the one you do not have to build, certify and maintain yourself.
How to approach it
A practical path. Confirm exact technical details against KRA's official documentation.
- 1
Confirm OSCU suits your connectivity
The OSCU is online-oriented. Confirm it fits your connectivity and architecture versus the VSCU, per KRA's requirements.
- 2
Scope setup against KRA's process
Get KRA's current OSCU setup and certification requirements and plan with a qualified integrator.
- 3
Connect and map your invoice data
Connect your system to the OSCU and map invoice data with correct tax treatment and buyer PINs.
- 4
Certify and test before go-live
Follow KRA's certification, validate in the sandbox, and confirm invoices transmit and validate before going live.
- 5
Register a replacement before retiring the old device
Set the new one up while the old one is still functioning, so you always have a working till and can choose when to switch.
- 6
Do not clone or copy a setup between devices
Copying files across to skip registration is what causes device-not-registered errors. Follow the registration route for each device.
What to check before you build
Choosing OSCU without assessing connectivity
The OSCU is online-oriented. If your connectivity is unreliable, assess whether the VSCU fits better.
Treating setup as a quick install
OSCU setup is a certified technical integration. Scope it properly rather than expecting a one-click install.
Skipping certification and testing
Follow KRA's certification and test in the sandbox so problems surface safely before go-live.
A business with stable connectivity chooses OSCU
A business in Nairobi with reliable connectivity assessed that the online OSCU suited its setup well.
They scoped the setup against KRA's requirements with an integrator, connected their system to the OSCU, mapped invoice data correctly, and followed KRA's certification and testing.
With the OSCU certified and tested, invoices transmitted and validated reliably online, while a sister branch with patchier connectivity considered the VSCU, and a smaller outlet simply used compliant software.
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.
When you can skip the integration
The biggest decision here is whether you need to build an integration at all. Veira is already a compliant eTIMS system: it issues compliant KRA invoices automatically, applies the right tax treatment, captures the buyer PIN, transmits to KRA, and works offline. For many businesses that removes the need to build, certify and maintain a custom integration yourself.
If you do run an ERP or a custom stack, weigh the cost of building and maintaining an integration against running point of sale and invoicing on Veira and reconciling. Veira runs from KES 2,999 a month, terminal included on annual billing and a 30-day money-back guarantee. See how Veira works, or book a free demo to talk through your setup.
Frequently asked questions
What is the eTIMS OSCU?
How do I set up an OSCU?
What is the difference between OSCU and VSCU?
Do I need an OSCU if I use compliant software?
Do I have to build my own eTIMS integration?
Where is the authoritative eTIMS technical spec?
eTIMS OSCU setup comes down to the concepts above plus KRA's official documentation for the exact details, and for many businesses the simplest path is compliant software that handles it for you. See how Veira works, or book a free demo. Always build against KRA's current official eTIMS documentation.
Need help, or want to talk it through first? Chat with us on WhatsApp