KRA eTIMS integration for POS, ERP and billing systems
KRA eTIMS integration connects your POS, ERP or billing system to the Kenya Revenue Authority's electronic Tax Invoice Management System, so every sale produces a valid electronic tax invoice automatically. It uses either an online (OSCU) or virtual (VSCU) sales control unit, and requires KRA testing and approval. Mjengo Corporate typically integrates eTIMS in 3–6 weeks.
Updated
| Option | How it works | Best suited to |
|---|---|---|
| OSCU (Online Sales Control Unit) | Your system signs and transmits each invoice to KRA in real time | POS and systems issuing invoices as sales happen |
| VSCU (Virtual Sales Control Unit) | A sales control unit runs within your environment and transmits invoices, suited to high volumes | Large-volume billing, ERPs and bulk invoicing |
| KRA's own eTIMS tools | Web portal or app where invoices are created manually | Very small businesses without a POS or ERP |
What is KRA eTIMS?
eTIMS (electronic Tax Invoice Management System) is KRA's system for issuing and transmitting tax invoices electronically. Businesses that are required to use it must ensure invoices are generated through eTIMS-compliant means. For a business that already sells through a POS or bills through an ERP, re-typing each invoice into a separate portal is slow and error-prone, so the practical answer is to integrate eTIMS directly into the system you already use.
Requirements and timelines are set by KRA and do change. Always confirm your obligations on KRA's official eTIMS pages.
What does an eTIMS integration involve?
- Choose the integration type (OSCU or VSCU) based on your invoice volume and how your system issues invoices.
- Map your data. Item codes, tax categories, units and customer PINs in your system must match KRA's required fields.
- Build and test against KRA's sandbox: invoice issuance, credit notes, stock and purchase information where required.
- KRA testing and approval of the integration before it goes live.
- Device/branch initialisation in production and monitoring that every invoice is acknowledged.
Common eTIMS pitfalls
- Messy item master data. Duplicate products and missing tax categories cause rejected invoices. Clean the product list first.
- Credit notes as an afterthought. Returns and refunds must also be reported correctly.
- No retry queue. If KRA's service is slow or the internet drops, invoices must be queued and retried, never lost.
- No visibility. Finance needs a screen showing which invoices were accepted, pending or rejected.
How Mjengo Corporate integrates eTIMS
We build eTIMS into POS and business systems as a separate, testable module: a queue for outgoing invoices, automatic retries, a reconciliation view for your accountant, and clear errors when data is wrong. POS systems are one of the system types we build most often, so eTIMS is designed in from the blueprint stage, not bolted on.
Frequently asked questions
Do I need eTIMS integration for my POS?
If your business is required to issue eTIMS invoices and you sell through a POS, integrating eTIMS into the POS is usually the most reliable way to comply. Confirm your obligations with KRA or your tax advisor.
What is the difference between OSCU and VSCU?
OSCU transmits invoices online as they are issued and suits most POS systems. VSCU is designed for high-volume or bulk invoicing systems such as ERPs. KRA's guidance sets which applies to your case.
How long does eTIMS integration take?
Building and sandbox testing typically takes 3–6 weeks at Mjengo Corporate, plus the time KRA takes to test and approve the integration.
How much does eTIMS integration cost?
eTIMS integration added to a Mjengo Corporate POS starts from about KES 60,000. Integrating an existing third-party system depends on its code quality and data, and is quoted after a review.
