eTIMS audit trail in Kenya: what KRA sees and how to prepare
Anne is a Nairobi-based CPA with experience advising Kenyan SMBs on KRA compliance. She works with Veira to help businesses stay tax-ready.
eTIMS creates a tamper-resistant audit trail of every transmitted invoice a business issued, against the business's KRA PIN. From KRA's perspective, this is a near-real-time picture of business activity: what was sold, when, to whom, at what tax rate, with what control number. For the business, the implication is that the audit story is already half-told before any officer arrives.
A KRA audit on a business with clean eTIMS records is short. A KRA audit on a business with gaps in eTIMS coverage is long, and the reconciliation work falls on the taxpayer.
What KRA actually sees
Every eTIMS transmission carries: seller PIN, invoice number, control number, date and time, line items with codes and tax rates, totals by rate, buyer PIN (where applicable), and the QR code. KRA receives this data in real time as the invoice is signed and transmitted.
Across an SMB's year, KRA holds a dataset that includes every transmitted sale and every received purchase in the SMB's PIN. This is the picture KRA validates against the SMB's declared income and claimed expenses on returns from January 2026 onward.
Why the audit trail is tamper-resistant
Once an invoice is transmitted, it cannot be deleted or rewritten by the seller. Corrections happen by issuing a compliant credit note that references the original invoice. The original transmission remains on file; the correction is layered on top.
This is what makes the eTIMS trail an effective audit artefact. A claim that an invoice was wrong cannot be backed by a corrected transmission alone; the original transmission still exists, and the difference between the original and the credit note is itself part of the trail. For honest corrections this is fine; for attempts to retrospectively rewrite history it is the wrong tool.
What KRA looks at during an actual audit
A KRA audit on a Kenyan SMB now typically begins with a pull of the SMB's eTIMS data for the audit period. The officer compares declared income on filed returns against transmitted sales invoices, and declared expenses against received purchase invoices in the PIN.
Where the numbers agree, the audit moves quickly to specific transactions: high-value sales, related-party transactions, anything unusual in the pattern. Where the numbers do not agree, the audit becomes a reconciliation: the officer wants to see why the gap exists and what corrective action has been taken.
The fastest way to a closed audit is to walk in with the reconciliation already done. A binder that shows transmitted-vs-declared, with every gap explained and documented, halves the time the officer needs to spend.
Preparing for an audit before one is announced
A business that prepares its audit file monthly carries no real burden when an audit is announced. A business that prepares only when notified spends weeks reconstructing data under pressure, and the pressure shows in the quality of the response.
The file that matters: monthly eTIMS exports (transmitted sales, received purchases), reconciliations to the same period's books and returns, supporting documentation for any non-routine transactions, and contemporaneous notes on any unusual items. Twelve clean monthly files is the position to be in.
Why audit dynamics have changed
Before eTIMS, KRA audits were reactive: an anomaly on a return triggered an inspection. The inspection was the data-gathering exercise. With eTIMS, the data is gathered continuously, and the inspection is a verification of the data the taxpayer already submitted.
This shift makes contemporaneous record-keeping cheaper than retrospective reconstruction. Under Legal Notice No. 64 of 2024, the penalty for a non-compliant invoice runs up to KES 1 million or 10% of the tax involved per occurrence; an audit that surfaces a year of these is a closure-level number for many SMBs.
Preparing an eTIMS audit file in five steps
- Export transmitted invoices monthly. Sales transmitted and purchases received, both by tax-rate code.
- Reconcile to the books for the same period. Find and document every gap as you go.
- Reconcile to the filed VAT and income tax returns. The third leg of the three-way match.
- Capture supporting documentation. Contracts, LPOs, credit notes, supplier correspondence on missing invoices.
- Keep the file in date order. Twelve monthly bundles, indexed. If an audit is announced, you hand over the file rather than starting work.
How Veira handles this
Veira keeps every transmitted invoice and every received purchase invoice in your account, indexed by month and rate. The audit file you would otherwise have to assemble is already assembled, with the eTIMS control numbers, the buyer PINs, and the reconciliation to your books in one place.
Related articles
How accountants audit, onboard and manage client eTIMS compliance, plus the professional liability angle.
How KRA auto-fills VAT returns from eTIMS, the common mismatches, and how to reconcile cleanly.
How eTIMS data integrates with bookkeeping, expense requirements and reconciliation.
The hub for every eTIMS topic, basics, how-to, by business type, and accountant resources.
Veira handles KRA eTIMS automatically, on your phone, even offline. See Veira pricing or try our free tax and business calculators.