Kenya · KRA eTIMS
Kenya KRA eTIMS Integration
Connect your ERP, POS or billing system to KRA eTIMS through OSCU or VSCU. We handle item codes, sales, purchases and stock sync so invoices carry valid KRA data without manual work.
Who must comply with Kenya e-invoicing?
The Kenya Revenue Authority requires all businesses, including those not registered for VAT, to generate tax invoices through eTIMS. Supporting rules mean that business expenses must be backed by valid eTIMS invoices to be deductible, so both your sales and your purchasing are affected.
Smaller businesses can use KRA's simpler eTIMS options (online portal, client or mobile). Businesses issuing invoices from an ERP or POS, or with significant volumes, typically need system-to-system integration.
How does eTIMS system-to-system integration work?
eTIMS works through a control unit that sits between your invoicing system and KRA:
- OSCU (Online Sales Control Unit): for online systems that transmit each invoice in real time.
- VSCU (Virtual Sales Control Unit): for high-volume or bulk invoicing systems.
Your ERP sends invoice data to the control unit, which signs it and exchanges data with KRA. The signed details and QR code are printed on the invoice. Purchases, imports and stock movements are also exchanged.
- Definition: OSCU / VSCU
- KRA eTIMS control-unit options for system-to-system integration: OSCU for online, real-time invoicing systems and VSCU for high-volume or bulk invoicing systems.
What are the eTIMS integration requirements?
- Device and branch initialisation using your KRA PIN and registered branch details.
- Item registration with KRA item classification codes, tax types, packaging and units.
- Sales transmission for invoices and credit notes, receiving signatures and QR data.
- Purchase and import confirmation from suppliers and customs.
- Stock movements kept in sync with your ERP.
- Testing and approval in the KRA sandbox before production.
How does Co-Mate integrate your ERP with KRA eTIMS?
We connect to your ERP or POS through its API or database, build the OSCU or VSCU integration with durable queues, map items to KRA codes, and write KRA signatures and QR data back to every invoice for printing. A dashboard shows pending, successful and failed transmissions per branch.
Which ERPs and billing systems do we support for Kenya?
- SAP Business One
- Microsoft Dynamics 365
- Oracle NetSuite
- Odoo
- ERPNext
- Zoho Books
- Tally
- QuickBooks
- Xero
- Sage
- Custom PHP / .NET / Java
- POS systems
Don't see yours? If it stores invoices in a database or exposes an API, export or webhook, we can connect it. See all ERP e-invoicing integrations.
Implementation steps
A predictable path from first call to live, monitored e-invoicing.
- 1
Choose the integration type
Decide between OSCU and VSCU (or a lighter eTIMS option) based on your volumes, connectivity and number of branches.
- 2
Data mapping
Map items to KRA item classification codes, tax types, units and packaging; set up branch and device information.
- 3
Integration build
Implement device initialisation, item and stock sync, sales and purchase transmission, and storing KRA signatures and QR data on invoices.
- 4
KRA sandbox & testing
Run test cases in the KRA sandbox and complete the testing and approval process for system-to-system integration.
- 5
Production go-live
Activate production devices per branch, print compliant invoices and monitor transmissions closely.
- 6
Support
Resolve failed transmissions, reconcile purchases and stock, and keep up with KRA specification updates.
Common Kenya e-invoicing challenges and how we handle them
| Challenge | Why it matters | How we handle it |
|---|---|---|
| Item classification codes | Every item needs KRA classification and tax codes. | Bulk mapping tools and a maintained item code table in the connector. |
| Multiple branches | Each branch needs its own device setup and data. | Per-branch configuration with central monitoring. |
| Unstable connectivity | Failed transmissions leave invoices non-compliant. | Durable queues, retries and the right control unit type for your setup. |
| Purchase and stock sync | Integration covers more than sales invoices. | Two-way sync of purchases, imports and stock movements with the ERP. |
| Supplier invoices without eTIMS | Expenses may not be deductible. | Purchase validation checks and supplier compliance reports. |
Kenya e-invoicing FAQ
What is KRA eTIMS?
Who must use eTIMS?
What is the difference between OSCU and VSCU?
Can my ERP integrate with eTIMS directly?
Do I need to send purchases and stock data too?
Is Co-Mate a KRA-approved third-party integrator?
Official sources
Last reviewed:
E-invoicing rules, timelines and technical specifications change often. This page summarises the official guidance as we understood it on the review date. Always confirm obligations and dates with the tax authority or your tax adviser before acting. Co-Mate provides integration engineering, not tax or legal advice.
Related e-invoicing guides
- E-invoicing integration hubAll countries, models and our approach in one place.
- ERP e-invoicing integrationsSAP Business One, Dynamics, NetSuite, Odoo, Zoho, Tally and more.
- Philippines BIR e-invoicingSales data transmission to the BIR EIS.
- Malaysia MyInvois integrationLHDN validation via API.
- Integrate e-invoicing with your existing ERPHow connectors fit around your current system.