There's a quiet disaster unfolding across Kenyan finance departments right now.
It started on 1st January 2026, when KRA quietly switched on a validation system that cross-checks every income tax return against three data sources: TIMS/eTIMS invoices, withholding tax records, and customs import data. If your declared figures don't match what KRA already has, the return gets flagged. Sometimes rejected outright.
The rule is simple on paper. Every expense you claim must be backed by a valid eTIMS invoice transmitted with your buyer PIN. No invoice means no deduction. It's that blunt.
But here's where it gets messy. The same businesses that dutifully onboarded to eTIMS are now discovering that having the system isn't the same as using it correctly.
A tax tribunal case from July 2026 tells the story. The appellant had transmitted Kshs 9,800,959 through eTIMS but declared only Kshs 8,400,959 in VAT returns. The variance triggered additional assessments of Kshs 1,344,153. Nothing exotic here. Just a gap between what the system recorded and what the taxpayer reported.
That gap is the problem.
Most businesses aren't deliberately underreporting. They're drowning in reconciliation. Sales recorded in eTIMS sit in one system. Purchases sit in another. Bank statements show money moving in ways that don't always map cleanly to invoices. Withholding tax certificates arrive from customers who file them months later. Customs records live in a completely separate system.
Somebody has to manually stitch all of that together. And that somebody is usually a finance officer with a spreadsheet and too little time.
The result is predictable. Small mismatches that compound. An invoice entered with the wrong buyer PIN. A credit note that never got transmitted. A duplicate entry in KRA's downloadable data that inflates expected income. Each one is minor. Together, they trigger rejections, audits, and penalties.
What makes this worse is that KRA's validation gives you almost nothing to work with. A rejection notice tells you the number is wrong. It doesn't show you which transaction caused it or how much the variance was. You're left digging through thousands of rows to find one error.
Manual reconciliation worked when returns were self-contained. You declared what you knew, and the burden was on KRA to prove otherwise. That's flipped now. The burden is on you to prove your numbers match what KRA already knows.
This is the reconciliation trap. Compliance stopped being about filing correctly. It became about proving you've always been consistent. And most finance teams don't have the tools or the hours to do that consistently.
The businesses navigating this well aren't necessarily the ones with the biggest accounting departments. They're the ones that stopped treating reconciliation as an annual chore and started treating it as infrastructure.
AutoRecs runs a four-pass matching engine against KRA iTax data and a six-pass engine against bank statements. Reconciliation that takes eight hours in spreadsheets takes fifteen minutes here. The free tier gives you five jobs a month, no card required.
If your returns keep getting flagged and you're tired of guessing why, start at AutoRecs