Contact Info
How do Kenyan companies handle eTIMS and M-Pesa in ERPNext?
In ERPNext, Kenyan companies typically handle eTIMS and M-Pesa through add-on apps rather than core features, built by implementers or the open source community, or through custom integrations. Choosing well means checking who maintains each app when KRA or the payment provider changes something, how failures are surfaced to users, and whether your hosting setup is dependable. I vet those apps and the surrounding design independently.
Last reviewed by Vikas Saroj
ERPNext appeals to Kenyan logistics operators, distributors, manufacturers, schools and service companies that want a full ERP without per-user licensing and with the freedom to adapt it. Its open source model has encouraged local developers to build Kenya-specific apps on top of it. I work remotely with these businesses to judge whether that ecosystem gives them a stable foundation.
The local layer is where ERPNext projects in Kenya succeed or struggle. Tax invoicing through eTIMS, M-Pesa collections and payouts, and possibly local payroll all tend to arrive as add-on apps or custom code. Each one is a dependency your business will live with for years, so I examine who wrote it, who maintains it, and how it behaves when something goes wrong.
My focus is the add-ons, hosting and support decisions that determine whether an ERPNext installation in Kenya stays reliable.
I review candidate eTIMS apps for your ERPNext version: what they transmit, how credit notes and errors are handled, who maintains them and how quickly they have tracked earlier KRA changes.
Incoming Paybill and Till payments and outgoing payments to suppliers or agents designed through an app or custom integration, with reconciliation rules and an owner for exceptions.
Frappe Cloud, a Kenyan or international hosting provider, or your own servers, compared on reliability, backups, upgrades, data protection questions and access from depots with uneven connectivity.
Shipments or jobs set up as projects with disbursements, revenue and costs captured per job, so clearing, forwarding and transport companies see margin before invoicing the client.
Entities across the East African Community run from a single installation with separate currencies and accounts, intercompany rules, and a plan for statutory pieces each country needs.
Review of custom apps and scripts for upgrade safety and version control, plus a support agreement setting out who fixes what, response expectations and how changes are approved.
Apps, hosting and processes
Configure and integrate
Run and upgrade safely
Core ERPNext does not, as far as I can tell for current versions, ship a KRA eTIMS integration. Kenyan implementers and community developers have filled that gap with add-on apps, some open source and some offered commercially. That is good for choice, but an eTIMS app is not a casual install: it sits between your invoices and the tax authority. Check the current state for your version rather than relying on my summary or a sales pitch.
My due diligence for any candidate app covers:
I then run a full test cycle in a staging site with your document types. Scope and specifications are questions for your tax advisor and KRA's own published material. The method follows my ERP integration service, and accounting depth is covered on my ERPNext Accounting page.
ERPNext's openness makes mobile money integration feasible, and Kenyan developers have built apps that connect it to M-Pesa for collecting payments and, in some cases, sending them. The same due diligence applies as for eTIMS, because a payment integration touches cash.
On the collection side, I list which business unit and settlement account sits behind every Paybill or Till, define the account reference customers should use, and decide whether payments arrive through real-time notifications, a scheduled statement import or both. Payment entries are created and allocated to invoices by reference, with a fallback queue for anything unmatched. Charges and settlements to the bank are posted and reconciled separately.
Payouts deserve extra controls. If the system will pay suppliers, transporters or field agents through mobile money, I design approval steps, limits, segregation between who prepares and who releases a payment, and a log that audit can follow. Some companies keep payouts outside the ERP and post results back, which can be the safer choice until volumes justify more automation.
All of this is tested with real but small transactions before go-live. For the automation approach behind it, see my automation service, and for the wider Kenyan context, the Kenya overview.
Kenyan ERPNext users can run on Frappe Cloud, choosing from the regions it offers, or with a hosting provider in Kenya or abroad, or on their own servers. The choice shapes upgrades, backups, cost and how depots with weak connections experience the system. Self-hosting gives full control over add-on apps and data location; managed hosting reduces the operational load but may restrict which custom apps you can install. I list your apps first, then check each option against them.
Data protection is part of the decision. Kenyan data protection legislation applies to the people records inside an ERP, and your legal advisor confirms what it means for hosting location and access. I make sure roles, permissions and logs follow that guidance.
A Nairobi-led group can keep its Ugandan, Tanzanian or Rwandan entities inside the same ERPNext installation, giving every company separate ledgers, a local base currency and distinct document numbering. Dollar transactions are recorded with exchange rates your accountant specifies. Statutory requirements in each country, including any electronic invoicing rules there, need their own answer, sometimes an app, sometimes a local accountant. For a country-neutral look at the platform, visit my ERPNext consulting page.
Kenya has ERPNext implementers, independent developers and firms that offer it alongside other systems. Because anyone can modify the code, quality ranges widely, and the business often ends up dependent on the person who wrote its custom apps. I help you set up the relationship so that dependency is managed.
Before appointing anyone, I write the requirement set: processes, documents, eTIMS and M-Pesa needs, migration from your current accounting package, hosting and support. Each bidder prices the same scope. During delivery, I check that custom work lives in proper apps under version control, that a staging site exists for testing, and that configuration matches the agreed design. I run acceptance tests with finance, operations and sales users, and I help negotiate a support agreement with clear responsibilities.
Sessions are online, in English, scheduled in Kenyan working hours that sit close to mine. Depot and branch staff can review recorded walkthroughs, and decisions are kept in writing for directors who missed a call. For how the implementation itself runs, see my ERP implementation page.
ERPNext's cost and openness are real advantages, but I suggest another path when:
An ERP evaluation sets these factors against your requirements. How ERPNext stacks up against the other candidates for Kenyan businesses is discussed on my Kenya ERP consultant page, and I am glad to run that comparison with your own data before you invest.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
Add-on apps for eTIMS have been built by Kenyan implementers and community developers, rather than coming in core ERPNext, at least as far as I can see for current versions. Check the position for your version. I vet any candidate app for coverage, failure handling and maintenance, then test it fully before go-live.
Yes, through an add-on app or a custom integration using the provider's interface, or through scheduled statement imports. Payments are allocated to invoices by reference, with unmatched items queued for a named owner. I review the app, design the controls and test with small live transactions.
It depends on your add-on apps, IT skills, connectivity and data protection guidance. Frappe Cloud reduces operational work; local or self-hosting gives more control and responsibility. I compare the options against your app list and confirm data location questions with your legal advisor.
That risk is why I insist on code in proper apps, version control, documentation and a staging site from the start. With those in place, another developer or implementer can take over. I also check licensing and source access for any commercial add-ons you depend on.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.