eTIMS

eTIMS SAP Integration in Kenya: Connecting SAP to KRA (2026)

K By Kev 23 June 2026 8 min read
Share
eTIMS guide

eTIMS SAP integration is a question for any Kenyan business or developer connecting their own systems to KRA eTIMS. To make SAP issue compliant eTIMS invoices, you integrate it with KRA through a control unit approach (OSCU or VSCU) or middleware, so SAP billing documents transmit to KRA and validate. This is an enterprise integration project: scope it against KRA's official documentation and test thoroughly before go-live. This guide explains the concepts and the practical approach, what to confirm in KRA's official documentation, and when you can skip the build entirely with compliant software. Technical specifics change, so treat KRA's official eTIMS documentation as the source of truth.

Key takeaways
  • SAP eTIMS integration is an enterprise project using a control unit (OSCU or VSCU) and usually middleware
  • Map SAP billing documents to eTIMS fields with correct tax treatment and PINs
  • Scope against KRA's documentation and involve a qualified integrator
  • Test in the sandbox and stage the go-live rather than switching all at once
On this page
  1. How SAP connects to eTIMS
  2. How to approach it
  3. What to check before you build
  4. An enterprise stages its rollout
  5. When you can skip the integration
  6. Frequently asked questions

How SAP connects to eTIMS

SAP is used by larger Kenyan enterprises, and the requirement is the same as for any system: billing documents must become compliant KRA eTIMS invoices that transmit and validate. The difference is scale and complexity, so this is an enterprise integration project rather than a quick connector.

The connection is made through KRA's system-integration approach, a control unit such as OSCU (Online Sales Control Unit) or VSCU (Virtual Sales Control Unit), usually with middleware that maps SAP billing data to eTIMS and handles transmission. Because the exact approach, certification and field mapping depend on your SAP landscape and KRA's current requirements, scope it against KRA's official documentation and involve a qualified integrator. Plan for sandbox testing and a controlled go-live.

The cheapest eTIMS integration is often the one you do not have to build, certify and maintain yourself.

How to approach it

A practical path. Confirm exact technical details against KRA's official documentation.

  1. 1

    Scope your SAP landscape

    Document your SAP modules, billing flows and volumes, since these drive the integration design and middleware needs.

  2. 2

    Choose the control unit and middleware

    Decide between OSCU and VSCU and any middleware, based on KRA's current requirements and your need for offline or high-volume handling.

  3. 3

    Map billing data to eTIMS fields

    Map SAP billing documents to the eTIMS fields, ensuring tax treatment and customer PINs are correct, per KRA's documentation.

  4. 4

    Test thoroughly, then stage go-live

    Validate in KRA's testing environment, run reconciliations, and stage the go-live rather than switching everything at once.

What to check before you build

Treating it as a small connector job

SAP eTIMS integration is an enterprise project. Underscoping it leads to compliance gaps at go-live.

Skipping certification and testing

Confirm the approach against KRA's documentation and test in the sandbox. Do not validate on live billing.

Ignoring offline and volume needs

Choose the control unit approach that suits your connectivity and volume, so transmission is reliable at scale.

An enterprise stages its rollout

Worked example

A large manufacturer in Kenya running SAP needed its high volume of billing documents to become compliant eTIMS invoices without disrupting operations.

Working with a qualified integrator, they scoped the SAP landscape, chose a control unit approach with middleware, mapped billing data to eTIMS fields, and tested against KRA's environment.

They staged the go-live by business unit rather than all at once, so issues surfaced safely, and reconciliations confirmed SAP and eTIMS agreed before full cutover.

Business impact

Trading without eTIMS-compliant tax invoices risks KRA penalties, blocked VAT input claims for your customers, and receipts a business buyer cannot expense.

Veira signs every sale to KRA eTIMS automatically, so each receipt is compliant the moment it prints, with no separate device to reconcile.

When you can skip the integration

The biggest decision here is whether you need to build an integration at all. Veira is already a compliant eTIMS system: it issues compliant KRA invoices automatically, applies the right tax treatment, captures the buyer PIN, transmits to KRA, and works offline. For many businesses that removes the need to build, certify and maintain a custom integration yourself.

If you do run an ERP or a custom stack, weigh the cost of building and maintaining an integration against running point of sale and invoicing on Veira and reconciling. Veira runs from KES 2,999 a month with a free terminal and a 30-day money-back guarantee. See how Veira works, or book a free demo to talk through your setup.

Frequently asked questions

Can SAP issue KRA eTIMS invoices?
Yes, once integrated with eTIMS through a control unit approach (OSCU or VSCU) and usually middleware that maps SAP billing to eTIMS and transmits to KRA. It is an enterprise integration scoped against KRA's documentation.
How do I integrate SAP with eTIMS?
Scope your SAP landscape, choose the control unit and middleware per KRA's requirements, map billing documents to eTIMS fields with correct tax treatment and PINs, and test thoroughly before a staged go-live.
OSCU or VSCU for SAP?
It depends on your connectivity, volume and architecture. Both are KRA control unit approaches; confirm which suits your landscape against KRA's documentation and with your integrator.
How long does SAP eTIMS integration take?
It is an enterprise project, not a quick connector, so plan for scoping, build, certification, sandbox testing and a staged go-live. Timelines depend on your landscape and volume.
Do I have to build my own eTIMS integration?
No. Compliant software like Veira already issues and transmits compliant eTIMS invoices, so many businesses do not need to build, certify and maintain a custom integration. Build only if your stack genuinely requires it.
Where is the authoritative eTIMS technical spec?
KRA's official eTIMS API documentation is the source of truth for endpoints, payloads, control units and requirements. Specifics change, so build against the current official documentation, not third-party summaries.

eTIMS SAP integration comes down to the concepts above plus KRA's official documentation for the exact details, and for many businesses the simplest path is compliant software that handles it for you. See how Veira works, or book a free demo. Always build against KRA's current official eTIMS documentation.

For more eTIMS guides and compliance resources, visit our free resource site.

Terms explained

Keep reading

See all eTIMS guides

Veira for your business

Browse Veira by business type