Date: Aug 31, 2026
Subject: Why Expenses Get Disallowed: Common eTIMS Invoicing Mistakes
$ retrieve --record=EXP-2291 --source=eTIMS
> Supplier PIN on invoice: P0512XXXXX7Z
> Supplier PIN on eTIMS registry: NOT FOUND
> Status: UNVERIFIED SUPPLY
> Recommendation: expense claim likely to be DISALLOWED on audit
> Reason: no matching electronic tax invoice trail
# This is illustrative only — KRA does not publish a public tool like this.
# It represents the kind of mismatch that gets flagged during review.
Every business owner in Kenya has had this experience in some form: you're confident your books are clean, your accountant files the return, and months later you're told a chunk of your expenses can't be deducted because the supporting documentation doesn't hold up. Since the rollout of the electronic Tax Invoice Management System (eTIMS), this problem has taken on a new shape. It's no longer enough to have a receipt in a drawer or a PDF invoice emailed by a supplier. What matters is whether that expense has a traceable, verifiable electronic invoice behind it — one that KRA's systems can actually match. When that trail is broken, incomplete, or inconsistent, the expense is at risk of being disallowed, even if the transaction was completely legitimate and the money genuinely left your account.
This matters more than it might seem at first glance. A disallowed expense doesn't just disappear quietly — it increases your taxable profit, which increases the tax you owe, sometimes with penalties and interest layered on top depending on how the assessment plays out. For a small business running on thin margins, or a SACCO managing member funds under scrutiny, or a clinic trying to keep both KRA and other regulators satisfied, this is not an abstract compliance issue. It's real money. The good news is that most disallowed expenses trace back to a small, predictable set of mistakes — mistakes that are entirely avoidable once you understand what eTIMS is actually checking for.
The mental shift many businesses still haven't made is this: eTIMS is not a receipt-generation tool for your own comfort, it's a matching system. Every invoice issued through eTIMS is meant to be visible to KRA in near real time, linked to a specific supplier PIN, a specific transaction, and a specific tax treatment. When you claim an expense, the expectation is that there's a corresponding electronic invoice on the other end — issued by a supplier who is themselves compliant — that KRA's systems can cross-reference. A paper receipt, a handwritten delivery note, or a screenshot of an M-Pesa payment confirmation is proof that money moved, but it is not, on its own, proof that qualifies for tax purposes. This distinction trips up a lot of otherwise careful business owners, because for years a receipt was a receipt. That's no longer the full picture.
This is probably the single biggest cause of disallowed expenses right now. Many small suppliers — a jua kali fundi, a market vendor, a small transport operator, a one-person consultancy — either haven't onboarded onto eTIMS or aren't consistently issuing compliant invoices even if they're registered. When you pay such a supplier, you may get a receipt book stub or an M-Pesa message, but nothing that shows up as a valid electronic tax invoice. From your side, the payment is genuine and the goods or services were delivered. From KRA's side, there's no verifiable supply behind the claim. Businesses that rely heavily on informal suppliers — construction firms, agencies buying casual services, schools sourcing from local vendors — are particularly exposed here. The practical fix isn't to stop working with small suppliers; it's to know in advance which of your regular suppliers are eTIMS-compliant, and to build that into how you choose who to buy from for anything material.
Related to the above, a lot of finance teams and business owners still treat any document with a total and a stamp as sufficient. Delivery notes, quotations, proforma invoices, and pro-rated statements are not the same as a proper tax invoice, and none of them substitute for what eTIMS requires. This confusion is especially common with online purchases, imported goods, or services billed in foreign currency, where the paperwork can look official without meeting local invoicing requirements. If your bookkeeper is filing expenses based on "looks legitimate" rather than "matches a valid eTIMS record," you have a gap waiting to surface at the worst possible time — usually during an audit, when it's hardest to go back and fix.
Even when a supplier is on eTIMS, invoices sometimes get issued against the wrong PIN, an outdated business name, or a branch/entity that doesn't match the one actually transacting. This happens a lot with businesses that have multiple branches, multiple legal entities, or that recently changed ownership or structure without updating registration details everywhere. It also happens when staff at the point of sale simply key in details incorrectly, or when a supplier's system hasn't been updated after a change. From the buyer's side, this is easy to miss — the invoice looks fine unless you specifically check the PIN and name against your own records. It's worth building a habit of spot-checking supplier PINs periodically, particularly for high-value or recurring suppliers, rather than assuming everything is correctly configured on their end.
A common pattern: a business gets onboarded onto eTIMS, sorts out the initial setup, trains staff once, and then treats the matter as closed. Months later, new staff haven't been trained, a new branch opened without proper configuration, or a change in how sales are processed (a new POS system, a new till, a new e-commerce checkout) creates a gap where transactions aren't being properly captured. Compliance isn't a project with an end date — it's an operating habit, the same way reconciling your M-Pesa till statements or backing up your accounting data should be routine. Businesses that build periodic checks into their monthly closing process catch these gaps early. Businesses that don't tend to discover the problem only when an assessment lands.
Kenya's power and connectivity reality is real, and it affects invoicing more than people account for. A power interruption or a mobile network outage during a busy trading period can mean transactions get processed outside the electronic system — recorded manually "to be entered later" and then, in the rush of daily business, never properly captured. This is a genuine operational challenge, not a compliance failure of intent, but it produces the same result: gaps in the invoice trail. If your business handles a meaningful volume of cash or in-person transactions, it's worth having a clear, written fallback procedure for outages — what staff should do, how manual records get reconciled back into the system once connectivity returns, and who is responsible for making sure nothing falls through. Leaving this to improvisation in the moment is how small outages turn into recurring gaps.
Many businesses run more than one system that touches money — a POS or till system, an accounting package, an M-Pesa till or paybill, sometimes a separate invoicing tool for a specific department. If these systems aren't reconciled against each other and against eTIMS records regularly, discrepancies accumulate quietly. An expense might be recorded in the accounting system with a total that doesn't quite match what was actually invoiced, or a purchase might get entered twice, or an invoice might get recorded against the wrong period. None of this is necessarily fraud or even carelessness in a deliberate sense — it's simply what happens when reconciliation isn't a disciplined monthly habit. For a SACCO or fintech handling higher transaction volumes, this risk compounds quickly if it isn't caught early.
Not every supply is taxed the same way, and getting this wrong on either the issuing or receiving side creates problems. A business might claim input relief on a purchase that was actually exempt, or record a VATable expense incorrectly because the supplier's invoice was itself wrongly categorised. This is a genuinely technical area where the rules are specific and can change, so this article won't attempt to lay out which categories apply to which goods and services — that detail should come from KRA's current guidance or a qualified tax advisor, not from a generic explanation that might be outdated by the time you read it. What's worth internalising is simply that the tax treatment shown on an invoice matters for whether an expense holds up, and it's not something to assume by habit or guesswork.
Returns, discounts, and billing corrections need to be reflected properly through credit notes issued and captured in the same system, not just adjusted informally on a spreadsheet or verbally agreed with a supplier. When a business claims an expense at the original invoiced amount but the actual transaction was later adjusted downward, and that adjustment never gets formally recorded, there's a mismatch waiting to be found. This is a small, unglamorous detail that a lot of finance teams skip because it feels like paperwork for its own sake — but it's exactly the kind of gap that surfaces first in a review.
The exposure looks different depending on what you run. An SME buying stock from a mix of formal and informal suppliers needs to be deliberate about which suppliers it relies on for larger purchases. A SACCO, which typically faces closer regulatory scrutiny already, has less room for casual recordkeeping and benefits from tighter internal reconciliation discipline. A clinic buying supplies from multiple small vendors, sometimes urgently and outside normal purchasing channels, faces a real tension between operational speed and documentation discipline — worth solving with pre-approved supplier lists rather than ad hoc purchasing. A school with many small, recurring local purchases (transport, maintenance, food supplies) tends to accumulate exactly the kind of informal-supplier risk described above. An agency billing clients and subcontracting other freelancers or small vendors needs to be as careful about what it receives from subcontractors as it is about what it issues to clients. None of these are exotic problems — they're the same handful of mistakes, showing up in different operational contexts.
A few practical shifts help most businesses close this gap without needing a large compliance department. Keep a short list of preferred suppliers you've confirmed are eTIMS-compliant, and default to them for anything above a threshold you set internally. Build a monthly reconciliation habit that checks accounting records against eTIMS records, not just against bank and M-Pesa statements. Train whoever handles purchasing — not just finance staff — on what a valid invoice actually looks like, since purchasing decisions are often made by people who never touch the books. Have a written procedure for what happens during connectivity or power outages so manual workarounds get properly reconciled afterward rather than forgotten. And treat any accounting or invoicing software you adopt, especially dollar-priced tools with forex exposure, as something that needs to stay current with local requirements — a cheap tool that doesn't keep pace with eTIMS changes can end up costing more in disallowed expenses than it saved in subscription fees.
Finally, it's worth saying plainly: the specifics of eTIMS requirements, thresholds, exemptions, and penalties are set and updated by KRA, and they do change over time. This article has deliberately avoided quoting figures, deadlines, or exact rules, because getting those details from a generic source is riskier than not having them at all. Before you make decisions about supplier selection, invoicing thresholds, or how to treat a specific category of expense, confirm the current position directly with KRA or with a tax professional who tracks these changes closely. The mistakes described here are structural and durable — they'll keep causing problems regardless of what the exact current rules say. Fixing the habits is the part that's actually in your control.
We build AI agents and automation for Kenyan businesses — and the infrastructure underneath them. Run the automation scan and find out what's worth building first.