Kenyan compliance Kenyan compliance · KRA eTIMS

KRA eTIMS and Dynamics 365 Business Central.

eTIMS changed where an invoice is born. It is no longer a document your system prints; it is a record the Kenya Revenue Authority has to accept. Here is what that asks of the ledger, and how we build it.

← Kenya hub

What eTIMS asks of an ERP

Under KRA's Electronic Tax Invoice Management System, invoice data is transmitted to KRA, and the invoice carries KRA-issued signature and QR information. Since 2024 KRA has also tied deductible expenses to eTIMS-generated invoices, so what suppliers send you matters as well as what you send customers. Confirm the current rules and phases with KRA.

Sales invoices, credit notes and debit notes are transmitted and signed
Items and units must carry KRA classification and unit codes
A transmission can fail or be rejected after posting
Purchase invoices from suppliers need to be eTIMS-compliant to support expense claims

The design question that matters

Most failed eTIMS integrations bolt a signing tool beside the ledger and reconcile later. The ledger then contains invoices KRA has never seen, and KRA has invoices the ledger never booked. The better design puts submission inside posting: a document that the authority has not accepted does not become a ledger fact.

How DigiTaxFlow 365 works

DigiTaxFlow 365 submits the invoice from inside posting on Business Central or Finance & Operations. The chart of accounts, the sales order and the till stay shared; the country is a connector.

Submission inside posting; an unaccepted invoice cannot post
Credit and debit notes linked to the original
Retail and POS receipts submitted per transaction, queued offline and sent on reconnect
A submission report in place of the month-end spreadsheet
Item and unit code mapping held on the item card

What we do not claim

We do not publish a KRA certification or approval status on this page. Control-unit options, certification requirements and phase dates are set by KRA and change; we confirm them with you and with KRA documentation before go-live, and record the evidence in the project file.

A practical rollout

Classify items first. Map units. Decide the control-unit approach with your IT team. Test in KRA's sandbox with real document types, including credit notes and offline receipts. Train the people who post invoices and the people who answer a rejected one. Then switch on, site by site.

Frequently asked questions

Do we need DigiTaxFlow 365 if our current system already signs invoices?

Not necessarily. The question is whether the ledger and KRA agree without a spreadsheet. If your reconciliation depends on exports, the design is worth reviewing.

Does this work for retail and POS?

Yes. Receipts are submitted per transaction, queued offline and sent on reconnect.

What about invoices we receive from suppliers?

Supplier invoices that support expense claims should be eTIMS-compliant. We design purchase-invoice validation and exception handling into the accounts-payable process.

Is DigiTaxFlow 365 KRA-certified?

We do not make a certification claim on this site. Ask us for the current position and the evidence, and confirm with KRA.

General information, not tax or legal advice. Rates, limits and filing rules change; confirm the current position with the Kenya Revenue Authority, the relevant statutory body or your tax adviser before relying on it.

Last reviewed 2026-10-11

Let's talk Solutions.

Plan Your ERP & CRM Roadmap with Our Experts.

Book a consultation Estimate your return
Call Book a consultation
Software Dynamics
Typically replies within business hours (EAT)
Hello. What are you trying to solve? Pick one and we will route you to the right person. I want to see a demo I am an existing client and need support Tell me about electronic invoicing