Short answer: Choose OSCU when the invoicing system is designed to stay online and transmit transactions as they happen. KRA positions VSCU for bulk invoicing and systems that are not always online. Both are system-to-system eTIMS integrations and require development, testing, vetting, and certification.
What OSCU and VSCU Have in Common
OSCU and VSCU connect a taxpayer's existing invoicing, POS, ERP, or billing system to KRA eTIMS through an API. They are appropriate when a business wants staff to continue working in its own software instead of re-entering each transaction in a separate portal.
Both routes require a deliberate integration process. KRA says a capable taxpayer may self-integrate, or the taxpayer may use a KRA-verified third-party integrator.
OSCU vs VSCU at a Glance
| Decision area | OSCU | VSCU |
|---|---|---|
| KRA description | Online Sales Control Unit | Virtual Sales Control Unit |
| Best fit | Invoicing that is always online | Bulk invoicing or systems not always online |
| Typical flow | Transaction data sent during the live invoicing workflow | Transactions prepared for controlled bulk or intermittent transmission |
| Business example | Cloud invoicing, connected POS, online service platform | ERP batch runs, distributed or connectivity-constrained operations |
| Core requirement | Reliable online workflow and failure handling | Reliable batching, synchronization, duplicate control, and reconciliation |
When OSCU Is Usually the Better Fit
- ✓Invoices are created in a cloud or connected application throughout the day.
- ✓Customers expect a KRA response and completed receipt during the live sale.
- ✓The system can queue, retry, and clearly show failed or pending submissions when connectivity drops.
- ✓The business needs a direct connection between its item, customer, payment, and invoice workflow.
When VSCU Is Usually the Better Fit
- ✓The business creates a high volume of invoices in scheduled or controlled batches.
- ✓Some operating locations or systems are not continuously connected.
- ✓The ERP or billing process naturally closes, validates, and exports groups of transactions.
- ✓The business has strong controls for batch identity, duplicate prevention, error isolation, and later reconciliation.
The KRA Integration Path
1. Select the route
Document the invoicing volume, connectivity, timing, branches, and failure-recovery requirements before choosing OSCU or VSCU.
2. Get specifications
Use KRA's current OSCU or VSCU specification and Trader Invoicing System requirements.
3. Build in sandbox
Register for the sandbox, implement the required transaction flows, and test both success and error conditions.
4. Complete vetting
KRA describes development, testing, vetting, and certification for self-integrators and third-party software providers.
5. Prepare operations
Train users, define retry and reconciliation ownership, and document what happens when KRA or connectivity is unavailable.
6. Monitor production
Track submitted, pending, failed, and corrected invoices so finance records agree with eTIMS records.
Questions to Ask an eTIMS Software Provider
- ✓Does the product use OSCU or VSCU, and why does that route fit this business?
- ✓Who completed the KRA integration and certification process?
- ✓What status does a user see before KRA accepts an invoice?
- ✓How are offline invoices, retries, duplicates, and partial batch failures handled?
- ✓Can finance reconcile local invoice numbers with KRA receipt and control-unit details?
- ✓How are credit notes linked to the original invoice and issuing solution?
Official sources
Direct KRA guidance used to prepare this guide.
Frequently asked questions
Open a question to read the answer.
What is the main difference between OSCU and VSCU?
KRA positions OSCU for invoicing systems that are always online, while VSCU is suitable for bulk invoicing and systems that are not always online.
Can a business build its own OSCU or VSCU integration?
Yes, if it has the capacity. KRA says taxpayers may self-integrate or use a KRA-verified third-party integrator, with development, testing, vetting, and certification required.
Is OSCU only for large businesses?
KRA defines OSCU by the online system workflow rather than a turnover threshold. The practical question is whether direct software integration is justified by the business's invoicing needs.
Does OSCU eliminate internet failures?
No. OSCU is the always-online integration model, but the application still needs clear pending states, safe retries, and reconciliation for temporary connectivity or service failures.
Last reviewed: June 2026. This guide summarizes current public KRA information and is not tax or legal advice. Confirm unusual cases with KRA or a qualified tax professional.