KRA ETIMS COMPLIANCE KENYA | SERPA ODOO ERP AFRICA

A finance manager closes the month, then finds that supplier invoices in the expense file are ordinary PDFs rather than valid electronic tax invoices. Since 1 January 2024, that gap can affect whether expenditure supports an income-tax deduction.

KRA eTIMS compliance is therefore an operating issue for Kenyan businesses, not a VAT task for the tax team to handle after invoices have gone out. It affects invoicing controls, branch processes, procurement records and the ERP data that management relies on. For organisations issuing from Odoo, our Odoo KRA eTIMS integration work focuses on connecting fiscal compliance to the same financial workflow used for sales, stock and reporting.

As of 15 October 2026, the Kenya Revenue Authority, KRA, states that all persons engaged in business must onboard eTIMS and issue electronic tax invoices. That scope includes companies, partnerships, sole proprietors, associations, trusts, informal-sector businesses, and taxpayers liable for MRI, TOT or annual income tax.

What KRA eTIMS is

The Electronic Tax Invoice Management System, eTIMS, is KRA’s system for generating, validating and transmitting electronic tax invoices. The requirement has applied from 1 September 2023. KRA provides the central eTIMS onboarding environment and several ways to issue invoices, depending on how a business trades.

For an enterprise, the important distinction is between an invoice that happens to be created in an accounting system and an invoice that has been validated through the KRA process. A document carrying internal invoice details may still fail the test for an electronic tax invoice if it was not issued through the applicable eTIMS channel.

KRA offers free eTIMS options, including Online, eClient, ePOS and Non-VAT Lite. These are KRA software options, so a business should not describe eTIMS software itself as chargeable. An ERP integration can still involve implementation, configuration, testing and support costs because it connects the enterprise system to KRA’s fiscal workflow.

For businesses with their own invoicing system or ERP, KRA provides system-to-system integration through an Online Sales Control Unit, OSCU, or a Virtual Sales Control Unit, VSCU. This route matters where invoices originate in multiple branches, sales channels or entities. Re-keying an ERP invoice into a separate tool after it has been issued creates an avoidable control break.

Official basis: KRA eTIMS guidance and KRA FAQ, checked 15 October 2026. Odoo’s official Kenya localisation documentation, checked 15 October 2026, states that its localisation uses an OSCU to validate, encrypt, sign, transmit and store invoices.

Which Kenyan businesses must comply in 2026

The short answer is broader than many finance teams expect: businesses cannot treat eTIMS as a VAT-only obligation. KRA’s current guidance says the requirement applies to all persons engaged in business, including non-VAT businesses and those liable for MRI, TOT or annual income tax.

This is the practical scope to test against your operating model:

| Business type or activity | eTIMS position in 2026 | What the finance team should check | | Incorporated company | Must onboard and issue electronic tax invoices when engaged in business | Confirm every sales source uses the approved invoicing flow | | Partnership or sole proprietor | Must onboard and issue electronic tax invoices when engaged in business | Do not assume non-VAT status removes the obligation | | Association, trust or informal-sector business | Included in KRA’s stated scope when engaged in business | Map income-generating activities and invoice issuance points | | MRI, TOT or annual income-tax taxpayer | Included in KRA’s stated scope | Align tax registration records with the invoicing process | | Government supplier | Must generate a valid eTIMS invoice before IFMIS payment submission | Reconcile the submitted invoice details against eTIMS records |   The government supplier rule changed on 31 August 2026. KRA and the National Treasury announced eTIMS-IFMIS integration, requiring suppliers to government entities to generate a valid eTIMS invoice before submitting it for IFMIS payment. The submitted invoice details must match eTIMS records. For a supplier with public-sector receivables, this is a cash-collection control, not merely a compliance check.

The KES 5 million point that teams often get wrong

KES 5 million annual turnover is not a general eTIMS exemption. KRA’s guidance uses that threshold for Buyer Initiated Invoicing: where supplies are received from a small business enterprise at or below KES 5 million annual turnover, the purchaser must issue the invoice on the supplier’s behalf using Buyer Initiated Invoicing.

Buyer Initiated Invoicing is available through eCitizen. The purchaser needs a clear supplier-master process, because an incorrect PIN, supplier identity or supply detail can create a mismatch between procurement evidence and the fiscal invoice. If your business purchases from many small suppliers, assign ownership to procurement and accounts payable together. Leaving it entirely with tax creates late invoice requests after goods have already been received.

Take an illustrative Nairobi distributor that purchases consumables from small traders and operates three depots. Its accounts payable team had treated the KES 5 million threshold as proof that small suppliers did not need eTIMS records. The correction is not to stop buying from those suppliers. It is to identify which qualifying supplies need purchaser-issued invoices through Buyer Initiated Invoicing, then retain an auditable link between purchase order, goods receipt, supplier and fiscal invoice. The team should have built that check into supplier onboarding, before the first payment run.

Why valid electronic invoices now matter to tax deductions

From 1 January 2024, KRA requires expenditure to be supported by a valid electronic tax invoice for income-tax deduction purposes. This changes the question CFOs should ask at month-end. Instead of asking whether an expense has a receipt, ask whether the expense has the correct electronic tax invoice and whether that invoice can be traced to the underlying transaction.

A supplier statement, delivery note or ordinary receipt may still have operational value. It does not replace the stated electronic-invoice requirement for the income-tax deduction test. Finance teams need a documented exception process for invoices that are missing, rejected or issued with incorrect data.

The direct statutory exposure for failure to comply with a requirement to issue an electronic tax invoice is two times the tax due. This applies after KRA gives written notice and finds the taxpayer’s reasons unsatisfactory. The reason to address failures before a tax review is straightforward: the penalty is linked to tax due, not a fixed administrative amount.

Take an illustrative Kisumu-based engineering contractor that invoices commercial customers from a project team while the head office accounts team posts billing later. A project administrator issued an internal invoice sequence from a spreadsheet, while finance used a different sequence for the same job in the ERP. The problem is not simply duplicate numbers. KRA invoice sequences and the ERP’s internal numbering serve different purposes, and the two must be mapped without assuming they are interchangeable. The contractor should define one fiscal issuance point, with a clear record of who can cancel, correct or reissue an invoice.

A practical KRA eTIMS compliance process

For a mid-sized or multi-entity business, we recommend treating eTIMS as an implementation programme with tax, finance, operations and IT owners. The tax manager may understand the obligation, but cannot control every point where an invoice is raised.

1. Map every place an invoice starts

List branch counters, field sales devices, e-commerce orders, head-office billing, recurring contracts and credit notes. Include every legal entity and every revenue stream. This is necessary because the common failure is implementing eTIMS at head office while branches continue issuing ordinary receipts or locally numbered invoices.

For each source, record the application, the responsible team, the current invoice number pattern and the correction process. A multi-entity group should also confirm which Kenyan entity is making the supply. Shared services teams regularly see transaction data, but visibility does not make the shared-services entity the supplier.

2. Select the KRA route that fits the operating model

Use KRA’s free options where they fit the volume and process. Use OSCU or VSCU integration when invoices are generated from an existing invoicing system or ERP and the business needs real-time, unified control across locations.

There is no universal answer. If a business has a single low-volume issuing point and no established ERP billing workflow, an enterprise integration may be disproportionate. If sales are raised across branches, channels or legal entities, do not rely on manual duplicate capture. The control cost and reconciliation risk usually exceed the apparent simplicity of separate tools.

3. Configure the ERP and fiscal sequence deliberately

Odoo’s Kenya localisation uses an OSCU to validate, encrypt, sign, transmit and store invoices under the official Odoo documentation. It requires OSCU initialisation and a KRA eTIMS service request. These are implementation dependencies, not settings to leave until user acceptance testing.

Define what happens when an invoice is posted, when it is sent to KRA, and when KRA validation returns an exception. The ERP should retain the operational invoice record while preserving the fiscal response required for an auditable trail. Finance also needs clear rules for credit notes, cancellations and corrected customer details.

4. Test with real transaction patterns

Test a standard sale, a return, a credit note, a customer with incomplete details, a branch-issued invoice and a Buyer Initiated Invoicing case if your procurement model uses it. Test these before go-live because exceptions reveal who actually owns the work.

The step teams skip is reconciling the fiscal output to the general ledger and the customer statement. An invoice can look correct on screen while posting to the wrong tax account, entity or receivable account. Test the end-to-end evidence, not only the connection status.

5. Build daily exception ownership

Assign a named owner for rejected transmissions, missing invoices and mismatched reference data. Review exceptions daily during the first operating period, then set a controlled review cadence based on transaction volume. A queue with no owner becomes an unrecorded tax exposure.

For government suppliers, add an IFMIS pre-submission check. The invoice submitted for payment must match the eTIMS record, so an accounts receivable team should compare the relevant details before the invoice enters the public-sector payment workflow.

Common errors we see in eTIMS planning

What boards and executive teams should ask for

Board oversight should focus on evidence rather than a general statement that eTIMS is complete. Ask for a register of invoicing sources, the selected KRA channel for each source, exception volumes, unresolved failed transmissions and the result of ledger-to-invoice reconciliations.

Ask management to separate tax-law requirements from system design choices. KRA specifies the electronic invoice obligation and the deduction rule. Whether the business uses eTIMS Online, eClient, ePOS, Non-VAT Lite, OSCU or VSCU depends on transaction volume, existing systems and the level of integration required.

For Odoo ERP programmes, the decision should also include data governance. Customer and supplier records, branch configuration, tax settings and user permissions all affect whether a technically connected system produces compliant, auditable output.

Frequently Asked Questions

Is eTIMS only for VAT-registered businesses?

No. As of 15 October 2026, KRA says all persons engaged in business must onboard eTIMS and issue electronic tax invoices. KRA’s stated scope includes non-VAT businesses, companies, partnerships, sole proprietors, associations, trusts and informal-sector businesses.

Is a business below KES 5 million turnover exempt from eTIMS?

No. KRA’s KES 5 million annual turnover reference concerns Buyer Initiated Invoicing for supplies received from a small business enterprise at or below that threshold. It is not a general exemption from eTIMS.

What happens if an expense has an ordinary receipt but no valid electronic tax invoice?

KRA states that, from 1 January 2024, expenditure must be supported by a valid electronic tax invoice for income-tax deduction purposes. The finance team should obtain the correct invoice and retain a traceable record before treating the item as supported for tax purposes.

Can Odoo connect to KRA eTIMS?

Yes. Official Odoo documentation for Kenya states that the localisation uses an OSCU to validate, encrypt, sign, transmit and store invoices. The implementation requires OSCU initialisation and a KRA eTIMS service request, with configuration and testing around the business’s own invoicing flows.

KRA eTIMS compliance becomes manageable when invoice issuance, tax evidence and ERP controls are designed as one process. Request a Consultation through our Odoo KRA eTIMS integration hub.