Integrate a taxpayer invoicing system with Kenya's eTIMS via KRA's OSCU or VSCU API
domain: government-tax · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Choose an integration mode per KRA's own description: OSCU (Online Sales Control Unit) 'is suitable for taxpayers whose invoicing is always online,' while VSCU (Virtual Sales Control Unit) 'is suitable for taxpayers undertaking bulk invoicing and is not always online' — both 'allow for a system to system integration between the taxpayer's invoicing/ERP system and eTIMS' via API.
Decide whether to self-integrate or use a partner: KRA states the certification process 'will entail the development, testing, vetting, and certification of either the interested taxpayer who has the capacity to self-integrate or... 3rd party software developers (integrators)' and that taxpayers 'can choose to initiate the self-integration process or enlist the services of KRA-verified third-party integrators.'
Download the published specification documents before building: the OSCU Specification Document v2.0, the VSCU Specification Document v2.0, and the Technical Specification for the Trader Invoicing System, all listed on KRA's eTIMS System to System Integration page.
Register and test in the sandbox environment (etims-sbx.kra.go.ke) using the step-by-step sign-up guide KRA publishes for OSCU/VSCU before requesting production access.
Complete KRA's development, testing, vetting, and certification sequence for your chosen solution prior to issuing live invoices through the integration.
Known gotchas
OSCU and VSCU are not interchangeable drop-in options — the choice depends on whether the taxpayer's invoicing is continuously online (OSCU) or done in bulk/offline batches (VSCU), per KRA's own guidance; picking the wrong mode can misalign with your invoicing pattern.
Third-party integrators must appear on KRA's published list of approved eTIMS third-party integrators — using an unlisted integrator's connector is not equivalent to KRA certification of your own system.
The sandbox (etims-sbx.kra.go.ke) is a separate registration from the production taxpayer portal (etims.kra.go.ke); passing sandbox testing does not automatically grant production credentials.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?