Tax authorities are validating the seller's document in real time. That is a genuine step forward, and it solves a problem that was never yours. It says nothing about whether the quantity matches your receipt, whether the price matches what your supplier accepted, or whether you have already paid this invoice through a different channel.
For decades the hardest part of accounts-payable automation was supplier enablement — persuading thousands of suppliers to submit invoices in a structured format. Ardent Partners calls it the "Achilles heel" of these deployments, and the numbers bear it out: even among organisations that have bought e-invoicing tools, only around 57% of suppliers actually submit electronically.
Clearance mandates solve that by force of law. In Kenya, Nigeria, Egypt, Rwanda, Uganda, Saudi Arabia and soon the UAE, your suppliers will issue structured, authority-validated invoices because they have no choice. The enablement is done by the state, not by you.
What is left is the part the state does not do. Nobody at the revenue authority checks that 432 cartons arrived against 480 ordered, that the unit price drifted 4% above what the supplier accepted, or that the same invoice already came in by email last Tuesday. That is a buyer-side control problem — and in Kenya it is now also a buyer-side tax exposure.
| Question | Answered by |
|---|---|
| Is this a valid tax invoice? | The tax authority's clearance |
| Is it attributed to my entity? | Clearance, if the buyer identifier is right |
| Did the goods arrive? | Your receiving evidence |
| Did the supplier agree this price? | Your acknowledged commitment |
| Have I already paid this? | Your duplicate controls |
| Who authorised the variance? | Your audit trail |
Four of those six are yours. A clearance-integrated invoicing tool answers the first two. A control layer answers the rest.
Section 23A of the Tax Procedures Act and the Tax Procedures (Electronic Tax Invoice) Regulations, 2024 require that declared income and expenses be supported by a valid electronic tax invoice, correctly transmitted with the buyer's PIN, where applicable.
KRA validates income and expenses declared in income-tax returns against three sources: TIMS/eTIMS data, withholding income-tax records and customs import data. The check bites at the point of filing. An expense that does not appear in your eTIMS purchase schedule — or that appears without your PIN correctly attached — is disallowed as a deduction.
If a supplier issues an eTIMS invoice but omits or mis-keys your PIN, the invoice never lands in your schedule. You hold a document that looks perfectly valid and claim a deduction you are not entitled to. The failure is silent, it is caused by someone outside your organisation, and you discover it at filing.
Reconcile your AP ledger against your KRA purchase schedule before you file. Flag every supplier invoice that was never transmitted, or transmitted without your PIN, while there is still time to have the supplier reissue it. That is a matching problem with a statutory deadline — the exact shape of problem this platform exists to solve.
OSCU for taxpayers whose invoicing is always online, processing in real time. VSCU for bulk invoicing that is not always online, processing and storing locally then transmitting in batches — the relevant path for an ERP-integrated or on-premises deployment. Both are API-based, both have a sandbox, and both require KRA vetting and certification before production. Budget for that cycle.
Summarised in good faith from public sources as at September 2026. Mandate scope and dates change frequently — confirm your own obligations with the relevant authority or your tax adviser before acting on anything here.
The wrong way to build for eleven different tax regimes is to encode eleven different invoice models. Each authority's connection is a replaceable adapter sitting behind the same canonical business objects — which is why adding a country is an adapter project, not a product release.
Tax validity is evaluated alongside quantity, price and duplicate — with the same expected/actual/variance/rule structure. A case can be held on a compliance failure exactly as it would on a quantity failure.
Authority endpoints go down. When verification is unavailable, the case enters an explicit unverified state rather than silently passing or silently blocking. Someone can see what is waiting and why.
Reading a tax identifier off a document is a different operation from confirming it with the authority. The platform treats them as separate controls, because conflating them is how an invalid invoice gets through a system that looked compliant.
Kenya's VSCU and Rwanda's VSDC exist precisely because connectivity is not guaranteed. A platform that assumes an always-on link to a tax authority is a platform that stops your month-end when the link drops.
Nigeria requires six years with signatures that remain verifiable; Italy requires ten under a formal conservation regime. The append-only audit ledger and document store are built for retention obligations, not just for operations.
KRA vetting, RRA certification, Nigerian APP accreditation and UAE ASP appointment are each a project with a queue in front of it. We scope them in discovery rather than discovering them at go-live.
Bring your entity list. We will map the obligations against your current controls and show you where the gaps are.
