Kenya's eTIMS Mandate Is Not a Tax Problem. It Is a Systems Problem.

What eTIMS Actually Requires

At its core, eTIMS requires that every VAT-registered business generate tax invoices through a KRA-approved system, in real time, with each invoice transmitted to KRA's servers.

For a firm with a proper billing system, this is a relatively minor integration. A few API calls, some additional fields on an invoice, automated transmission. Done.

For a firm running on QuickBooks and manual invoice numbering in a shared spreadsheet, it is a rebuild.

The problem most firms are facing is not the eTIMS requirement itself. It is that eTIMS has exposed how much of their invoicing, client management, and billing workflow was held together with informal workarounds.

• Invoices created in Word documents and saved to Dropbox
• Client payment tracking in colour-coded Excel rows
• Receipt confirmations via M-Pesa screenshots forwarded on WhatsApp
• Revenue reporting compiled manually at month-end from three different sources

eTIMS is asking these firms to transmit structured, real-time invoice data to a government server. But the data was never structured in the first place.

The compliance deadline did not create the problem. It made the problem visible.

Why Accounting Firms Are Hit Hardest

There is an irony in this: the firms most affected by eTIMS adoption struggles are often the accounting firms advising other businesses on how to comply.

Many small and mid-sized accounting practices in Kenya operate on the same informal systems as their clients. Fee management in spreadsheets. Client communications scattered across email and WhatsApp. Billing handled manually by the same people doing the client work.

This creates a compounding problem. The firm is spending time managing its own compliance chaos while simultaneously trying to help clients navigate theirs. Neither gets done well.

According to industry research, the main barriers for professional services firms trying to digitize are:

• High cost of eTIMS-compliant equipment and software (particularly for smaller practices)
• Integration complexity when you are starting from manual systems
• Skills gaps: accountants are not IT people, and bridging that gap is expensive
• Fear of getting it wrong: KRA audit exposure means firms are paralysed between the risk of non-compliance and the risk of incorrect implementation

The result: firms sit still, hoping the next deadline extension buys them more time.

What a Fixed System Actually Looks Like

We built Petrus CRM for a Nairobi accounting firm managing 137-plus clients and KES 30 million in annual profit. Before the build, their client and billing management looked like this:

• Client records split across two different spreadsheets and an old accounting package that no one fully understood
• Invoicing done manually, sent via email, tracked in a separate log
• Revenue visibility was a month-end exercise that took two days to compile
• Client communication history lived in individual team members' email inboxes

When we mapped their actual workflow, what they needed was not a SaaS CRM. It was a system that reflected how they actually worked: a single place where every client, every engagement, every invoice, and every payment lived together.

The system we built handles:

• Client management: all 137 clients, with full engagement history, notes, and documents in one place
• Billing: invoices generated from the system, with payment tracking and automated reminders
• Revenue reporting: real-time, not a month-end exercise
• eTIMS readiness: invoice data structured from the start, ready for KRA transmission

The firm did not need to change how it worked. The system reflected what it already did, just without the manual steps and the scattered spreadsheets.

The best systems are the ones that feel obvious after you have them. Not because they are simple, but because they were built around how you actually operate.

Firms looking to build beyond compliance into a full client management platform will find [a complete guide to building a custom CRM for African businesses here](/blog/2025-09-02-custom-crm-african-business).

The Forced Upgrade Moment

eTIMS is one of those rare regulatory moments that creates a genuine forcing function. Unlike most compliance requirements that can be handled with a workaround or a one-time fix, eTIMS requires ongoing, real-time integration with government systems.

You cannot handle this with a manual process. You need a system.

For professional services firms that have been putting off the investment in proper systems, this is the moment. Not because KRA says so (though that matters), but because the cost of not having proper systems has become more visible and more painful than the cost of building them.

• The compliance risk is real and escalating
• The manual overhead is growing as the business grows
• The reporting blind spots are costing leadership decision-making quality
• The talent market now expects firms to have functioning systems

The firms that get ahead of this in 2026 will not just solve an eTIMS headache. They will come out the other side with a practice management system that gives them a structural advantage over competitors who kept patching the spreadsheets.

If your firm is at this inflection point, Kaara Works builds exactly this kind of system. Not generic software adapted for Kenya. Purpose-built systems for how professional services firms in this market actually operate.

Let us talk.