ERP Consultant for Kenya

eTIMS and electronic tax invoicing inside the ERP

Kenya Revenue Authority has moved tax invoicing toward electronic systems, and its electronic Tax Invoice Management System, eTIMS, is the channel through which businesses it applies to transmit invoice data. For an ERP project, the practical questions are how invoices and credit notes leave your system, how the validated details come back onto the document, and what your team does when a transmission fails.

Platforms differ here. Some vendors or local integrators offer connectors, others expect you to use a separate invoicing tool and post totals into the ledger, and the integration options KRA provides each carry their own setup and maintenance burden. I ask vendors to demonstrate the full flow with your real document types, including returns, discounts and foreign currency invoices, rather than accepting a slide that says the feature exists.

I do not interpret tax law. Applicability, timing and technical specifications change, so I always recommend confirming the current requirements with your tax advisor and with KRA guidance before design is signed off. My role is to make sure the ERP produces consistent invoice data and that the chosen integration is tested properly. The broader method is described on my ERP requirements gathering page.

Reconciling M-Pesa and mobile money without spreadsheets

Mobile money changes the shape of accounts receivable. A customer may pay part of an invoice through M-Pesa, the rest by bank transfer, and use a phone number or a mistyped account reference that does not match anything in your books. When the ERP cannot recognize these receipts, a finance clerk exports statements every day and matches them by eye.

I design the receipt flow before configuration starts. That covers which Paybill or Till numbers belong to which entity or branch, what reference customers are asked to enter, how statement data or payment notifications reach the ERP, and the rules for automatic and manual allocation. Unidentified receipts go to a queue with an owner, and outgoing payments to suppliers or agents are recorded with the same discipline.

Integration can be direct through the provider's APIs, through a payment aggregator, or through regular statement imports, depending on volume and budget. Each route is documented with its trigger, data fields and failure handling, then tested with real transactions. See my ERP integration and automation services for how I approach these connections.

Shillings, dollars and East African subsidiaries

Many Kenyan businesses keep their books in shillings but buy, sell or borrow in dollars. Importers pay suppliers in foreign currency, exporters invoice in dollars, and some customers hold dollar accounts. The ERP has to record each transaction in its original currency, apply a documented exchange rate and report realized and unrealized differences in a way your accountant accepts.

Groups that also run companies in other East African countries add another layer. Each subsidiary has its own tax authority, invoicing rules and statutory reporting, while head office wants one consolidated view of sales, stock and cash. I design entity structures, a shared chart of accounts where it makes sense, intercompany pricing and elimination rules, and decide which local requirements need a separate configuration or partner.

Platform choice matters at this point. Odoo and ERPNext handle multi-company setups natively, Zoho often suits smaller groups that value simple administration, and Microsoft Dynamics 365 appears when a parent group already standardizes on Microsoft. I check localization support for each country rather than assuming it.

Hosting, connectivity and data protection choices

Cloud software is only as dependable as the connection behind it, and depots, farms and upcountry branches may rely on mobile data with uneven coverage. Before choosing a platform I find out where your users actually sit, which tasks they perform away from a desk and whether mobile apps need to capture orders, deliveries or stock counts offline and synchronize later.

Hosting decisions also touch Kenya's data protection law, which governs how personal data about customers, employees and agents is collected, stored and shared. I am not a lawyer, so I describe the questions rather than the answers: where the vendor stores data, which staff and partners can access it, how access is logged and how long records are kept. Your legal advisor confirms what the law requires; I make sure the ERP's roles, permissions and retention settings follow that guidance.

Payroll is usually best run by a local provider that tracks statutory deductions, with journals posted into the ERP and employee data shared only as far as reporting needs. For a structured review of an existing system against these points, my ERP health check is a practical starting point.

How remote ERP work runs for Kenyan teams

I work remotely with businesses in Kenya, and the time difference with India is short, so live workshops fit easily into a normal Nairobi working day. Between sessions, recorded walkthroughs and a shared tracker let depot managers, sales teams and finance staff review designs when it suits them.

Each sector brings its own emphasis. Distribution companies need route sales, agent stock and credit control. Logistics firms need job costing per shipment, disbursements and customer billing in more than one currency. Agricultural exporters and food and beverage processors need traceability from intake to dispatch, grading and export documentation. Service firms care most about time, projects and collections.

Before recommending any technology I spend time understanding who approves what and which reports directors depend on. Sometimes the answer is to fix processes and keep the current software for a while. When a new system is justified, I help with selection, oversee the implementation partner and stay involved through testing and go-live. Read my Kenya overview, look at my international work, or send me a note describing where your systems stand today.