# KRA eTIMS Integration in Kenya: What Your System Actually Has to Do
Short answer: Every business in Kenya — VAT-registered or not — has been required to
generate and transmit invoices through KRA's eTIMS since 1 September 2023, and business
expenditure not supported by an eTIMS invoice has been non-deductible since 1 January
2024. From 2026 KRA validates return entries against eTIMS data directly, which turns a
rule that was already on the books into one that is checked automatically. For anything
issuing invoices at volume, that makes eTIMS an integration problem, not a portal you log
into.
---
The rule is older than most people think
This is the part that catches businesses out, because the commonly repeated version of the
timeline is wrong.
KRA's position, in its own words, is that
["all persons carrying on business including those who are not registered for VAT are
required to electronically generate and transmit their invoices to KRA via… eTIMS from 1st
September, 2023"](https://www.kra.go.ke/news-center/public-notices/2077-electronic-tax-invoicing-for-non-vat-registered-persons).
And the consequence has teeth from the following January: "any business expenditure not
supported by an eTIMS generated tax invoice shall not be deductible for tax purposes with
effect from 1st January, 2024."
So deductibility has depended on eTIMS invoices since the start of 2024. What changed more
recently is enforcement, not the rule: KRA now validates the income and expense entries
in returns against eTIMS records rather than relying on the taxpayer's own declaration, and
has linked eTIMS to IFMIS, the government financial management system, so invoices from
suppliers to state entities are checked at source.
The practical effect is that the cost of your non-compliance lands on your customers —
they cannot deduct what they paid you. A B2B buyer running its own numbers will notice, and
will buy elsewhere. If you sell to businesses in Kenya, eTIMS compliance has become a
condition of being a viable supplier.
Verify before relying on this. eTIMS rules and deadlines come from KRA and continue
to move. Confirm your position at kra.go.ke before planning
against any date here.
---
Pick the right integration tier before you write code
KRA offers several routes, and teams routinely over-engineer by reaching for the API when
their volume does not justify it.
For micro and small non-VAT taxpayers KRA provides
which needs no integration at all — eTIMS Lite Web via eCitizen, eTIMS Lite USSD on
\*222#, and the "eTIMS Non VAT" mobile app on Play Store and the App Store. If you
issue a handful of invoices a month, this is the answer and building anything is waste.
For businesses issuing invoices from a system — an ERP, a POS, a SaaS product billing
Kenyan customers — you integrate, so that invoices generated by your software are
transmitted to KRA and returned validated. This is where the engineering sits.
The decision is volume and origin: if invoices are generated by software, they have to be
transmitted by software. A human retyping system-generated invoices into a portal is a
reconciliation failure waiting to happen, and it does not scale past a few dozen a day.
---
What integration actually involves
The shape will be familiar to anyone who has done ZATCA in Saudi Arabia or e-invoicing in
Brazil or Italy. The regulator differs; the engineering problem does not.
- Invoice transmission. Each invoice is sent to KRA and comes back with validation. Your
invoice is not final until that round trip completes.
- A control unit or its software equivalent. eTIMS replaced the older hardware-TIMS
model with software options, which is what makes system integration practical at all.
- Mandatory invoice fields. Buyer PIN for B2B, correct tax classification per line, and
the KRA-assigned identifiers that make the invoice valid. Missing or wrong classification
is the most common rejection.
- Credit notes as their own document type, correctly referencing the original invoice —
not a negative invoice, which is how most systems model a refund and why most systems fail
their first compliance pass.
---
The parts that consume the schedule
Transmission sits in your critical path. If validation is required before the invoice is
valid, your billing run now depends on an external service being reachable. Decide
deliberately what happens when it is not — queue and retry, or block — and write the
decision down. Teams that leave this undefined discover it during month-end.
Your tax classification data is probably wrong. Not missing — wrong. Rates and
exemptions per line item are usually approximated in systems built before this mattered,
and the approximation passes internal reporting while failing KRA validation. Budget real
time for a data pass, not an afternoon.
Reconciliation is a permanent job, not a launch task. Invoices accepted by your system
but rejected by KRA will accumulate quietly unless something surfaces them. Build the
exception queue on day one; you will need it every month.
Your customers will ask for evidence. Because their deduction depends on your invoice
being valid, B2B customers will want to see it. Making validated invoices retrievable is a
customer-facing feature, not an internal record.
---
Build direct, or buy a middleware provider
The same decision that comes up with every e-invoicing regime, and the same trade-off.
Direct integration means you hold the KRA relationship and the transmission code. No
per-invoice fee, no third party in your billing path, and you can move as fast as your own
release cycle. You also own keeping pace with KRA's changes, which have not been infrequent
— eTIMS has been revised repeatedly since 2024, and each revision is yours to absorb.
A compliance provider absorbs those changes and usually reaches working compliance
faster. You accept a dependency sitting between your ERP and the tax authority, per-invoice
pricing, and a question about where your invoice data is processed.
The deciding factor is rarely engineering capability. It is whether your invoicing logic is
unusual. Standard invoices from a standard ERP are exactly what providers are built for.
Complex multi-party billing, unusual tax treatments, or invoices assembled from several
systems are where a provider's model starts fighting you, and direct integration stops
looking expensive.
---
If you are building a product that bills Kenyan customers
Two things worth deciding early:
Does eTIMS belong in your product or beside it? A SaaS platform billing Kenyan
businesses can integrate directly, or leave invoicing to the customer's own accounting
system. Direct integration is a genuine selling point in this market — but it puts you in
the compliance path for every customer, which is a commitment.
Multi-tenant makes it harder. Each tenant is a separate taxpayer with its own PIN and
its own KRA relationship. Credential storage, per-tenant failure isolation, and per-tenant
reconciliation all have to be designed in. One tenant's rejected invoices must not stall
another's billing run.
---
Frequently asked questions
Is eTIMS mandatory for non-VAT registered businesses in Kenya?
Yes. Since 1 September 2023 all persons carrying on business must generate and transmit
invoices through eTIMS, whether or not they are VAT-registered. Micro and small non-VAT
taxpayers can use eTIMS Lite — web via eCitizen, USSD on *222#, or the eTIMS Non VAT app —
rather than integrating.
What changed for eTIMS in 2026?
Enforcement, not the rule. Expenditure unsupported by an eTIMS invoice has been
non-deductible since 1 January 2024. What is new is that KRA now validates return entries
against eTIMS records directly, and has linked eTIMS to IFMIS so government suppliers are
checked at source.
Do I need an API integration, or is the portal enough?
It depends on where invoices come from. If they are generated by software — an ERP, a POS,
a SaaS billing engine — they should be transmitted by software. The portal and USSD routes
are built for low-volume taxpayers who are not invoicing from a system.
How does eTIMS affect suppliers to government?
KRA has linked eTIMS to IFMIS, the government financial management system, so invoices from
suppliers to state entities are validated against eTIMS. For government suppliers this is
enforced now rather than forthcoming.
How long does an eTIMS integration take?
The transmission itself is modest. The schedule usually goes on cleaning tax classification
data across your existing catalogue, modelling credit notes as a distinct document type,
and building the reconciliation queue for rejected invoices.
---
*Researched September 2026 from KRA notices and specialist e-invoicing coverage. Rules and
dates change — confirm your position with KRA or your tax advisor before acting.*