For businesses across Nairobi, Mombasa, Kisumu, Nakuru, and Eldoret, KRA eTIMS compliance is now a daily operational requirement. Manually re-typing every POS or ERP invoice into the KRA eTIMS portal wastes hours and introduces costly discrepancies. Integrating KRA eTIMS directly via API turns compliance into an automatic background step on every sale.
Direct Answer
KRA eTIMS API integration (OSCU / VSCU) connects your custom POS, ERP, or invoicing software directly to the Kenya Revenue Authority. Every completed sale—whether paid via M-Pesa, cash, or card—is signed automatically and returns an official eTIMS Control Unit (CU) number and QR code on the customer's receipt.
OSCU vs VSCU: Which Integration Mode Fits Your Business?
| Mode | Best For | Key Advantage |
|---|---|---|
| OSCU (Online Sales Control Unit) | Cloud web apps, SaaS ERPs, centralized multi-branch POS | Direct server-to-KRA API signing with zero local hardware dongle dependencies |
| VSCU (Virtual Sales Control Unit) | Desktop/local-network POS setups needing local signing service | Runs a virtual signing module for branch servers with periodic sync |
Essential Features of a Production eTIMS Integration
- 01Automated SKU & Tax Mapping: Sync item codes, HS codes, and VAT categories (16%, 0%, Exempt) directly from your inventory master.
- 02Credit Notes & Returns: Handle partial refunds and cancelled invoices cleanly with compliant credit-note transmission.
- 03Offline Resilience: Queue invoices locally when branch internet drops and auto-sync to KRA once connectivity returns.
- 04M-Pesa + eTIMS Unified Checkout: Trigger M-Pesa STK Push, verify settlement, and immediately print an eTIMS-signed 80mm thermal or PDF receipt.
Frequently Asked Questions
- Can you add eTIMS to our existing custom POS or ERP? Yes. Whether your system runs on Node.js, Next.js, Laravel/PHP, or Python, we embed a clean eTIMS connector without replacing your existing software.
- Does it work for multi-branch retail and B2B suppliers? Yes—each branch or till maps cleanly to its assigned KRA branch ID and CU sequence.





