eTIMS Integration in Kenya: OSCU, VSCU and What It Costs
eTIMS integration options in Kenya explained: eTIMS Lite, eTIMS Client, OSCU and VSCU system-to-system, what drives integration cost and how to choose.
· Reviewed by Danstan Akwiri, CISSP, CISA
KRA's electronic Tax Invoice Management System (eTIMS) requires businesses to issue tax invoices electronically, and buyers need valid eTIMS invoices to claim the expense. For a business issuing a handful of invoices, KRA's free tools are enough. For anyone running an ERP, accounting package or POS, the question is how to make that system issue eTIMS invoices itself.
This guide explains the eTIMS options, when system-to-system integration is worth it, and what drives the cost of integrating with QuickBooks, Odoo, a POS or a custom system.
| eTIMS Lite / web / USSD | eTIMS Client (desktop) | OSCU / VSCU integration | |
|---|---|---|---|
| Suits | Low invoice volume | Moderate volume, single location | Businesses with an ERP, POS or billing system |
| Invoices re-keyed by staff | Yes | Yes | No, issued by your system |
| Integration build needed | No | No | Yes |
| Error risk at volume | High | Moderate | Low |
| Upfront cost | Free | Free | Integration project |
OSCU and VSCU in plain terms
System-to-system integration connects your own software to eTIMS so every invoice it issues is signed and transmitted automatically. KRA offers two approaches. An Online Sales Control Unit (OSCU) suits systems that issue invoices in real time, typically a POS or ERP transacting continuously. A Virtual Sales Control Unit (VSCU) suits systems that issue invoices in bulk or need to work with intermittent connectivity.
Integrations are typically delivered through KRA-approved third-party integrators or by vendors certified for their own product, and go through KRA testing before production use.
When integration pays for itself
If staff are re-entering invoices from your accounting system or POS into an eTIMS tool, you are paying for that labour every day and accepting the error rate that comes with it. At more than a few dozen invoices a week, or when invoice details must match exactly between your books and KRA's records, integration usually pays back quickly.
It also removes a customer-service problem: corporate buyers increasingly refuse to pay suppliers until a valid eTIMS invoice arrives, so delays in manual invoicing become delays in getting paid.
What drives the cost
Integration cost depends far more on your system than on eTIMS itself.
- Your platform: a popular package with an existing connector is quicker than a custom or legacy system.
- Item master data: products must be classified and coded correctly, which often means cleaning your catalogue.
- Invoice types: sales, credit notes, imports and purchases each need handling.
- Branches and devices: each location or till may need its own configuration.
- Testing and certification with KRA, and support when KRA changes the specification.
Common problems we fix
Most failed eTIMS integrations fail on data rather than connectivity: products without correct classification, tax codes that do not match the item, credit notes that do not reference the original invoice, and invoices rejected while the queue silently grows. A good integration surfaces every rejection to a person with the reason, rather than leaving finance to discover a backlog at month end.
How to choose an approach
If your accounting or ERP vendor already offers a certified eTIMS connector, start there and ask for references. If you run a custom system, a POS without a connector, or several systems that all issue invoices, a dedicated integration is usually the cleaner answer. Either way, ask who maintains the integration when KRA updates its requirements, because they will.
Key takeaways
- eTIMS Lite and the Client are fine at low volume; integration suits anyone with an ERP, accounting package or POS.
- OSCU suits real-time invoicing systems; VSCU suits bulk invoicing and intermittent connectivity.
- Integration cost is driven by your platform, item data quality, invoice types and branches.
- Most failures are data problems: classification, tax codes and credit-note references.
- Agree who maintains the integration when KRA changes the specification.
Frequently asked questions
What is the difference between OSCU and VSCU?
Both connect your own system to eTIMS. An Online Sales Control Unit suits systems that invoice in real time, such as a POS or ERP. A Virtual Sales Control Unit suits bulk invoicing and systems that cannot rely on constant connectivity.
Can QuickBooks or Odoo be integrated with eTIMS?
Yes. Integrations exist for popular accounting and ERP platforms, delivered by approved integrators. Check that the connector handles credit notes and your item classifications, and who supports it when KRA updates requirements.
How much does eTIMS integration cost?
It depends mainly on your system: packaged platforms with existing connectors are quicker than custom or legacy systems, and cleaning item data, handling several invoice types and configuring multiple branches all add effort.
Do small businesses need eTIMS integration?
Not necessarily. Businesses with low invoice volumes can use KRA's free eTIMS Lite or Client. Integration becomes worthwhile once re-keying invoices costs real staff time or causes errors.