Choosing an ERP system is one of the most consequential technology decisions an organisation makes. Done well, it gives you one reliable view of finance, stock, people and customers, and removes hours of manual work every week. Done badly, it becomes an expensive system that staff work around with spreadsheets.
This guide sets out a practical way to approach ERP selection, with particular attention to the requirements that matter for organisations operating in Kenya.
Signs that you need an ERP
Not every organisation needs an ERP straight away. These are the common signals that you have outgrown standalone tools:
- Month-end close takes weeks because figures have to be gathered from several systems and spreadsheets.
- Stock figures in the warehouse or shop do not match what the accounts say.
- Purchase approvals happen over email or paper, and nobody can see what has been committed against the budget.
- Each branch or department keeps its own records, and consolidated reports are slow and unreliable.
- Payments received through M-Pesa and banks are reconciled by hand.
- Management decisions rely on reports that are already out of date when they arrive.
If several of these sound familiar, an integrated system will usually pay for itself in time saved and errors avoided.
Start with processes, not features
The most common mistake in ERP selection is comparing feature lists. Almost every ERP claims to handle finance, procurement, inventory and HR. The real question is how well a system fits your way of working, and how much it will cost to close the gaps.
Before speaking to vendors, document:
- Your core processes. How do requisitions become purchase orders? How does stock move between stores and branches? How is revenue collected and receipted? How is payroll run?
- Your reporting needs. Which reports do management, the board, auditors, donors or regulators need, and how often?
- Your pain points. Where do errors, delays and workarounds happen today?
- Your integration points. Which systems must the ERP exchange data with, such as POS, banks, M-Pesa, KRA eTIMS, payroll or e-commerce?
- Your growth plans. New branches, entities, product lines or users over the next three to five years.
This document becomes the yardstick for every option you evaluate.
Kenyan requirements to check early
Many ERP products are designed for other markets. Make sure any system you consider can handle the following, either out of the box or through reliable integration.
M-Pesa payments and reconciliation
For most Kenyan organisations, M-Pesa is a major collection and payment channel. The ERP should be able to receive paybill and till payments, match them to invoices or customer accounts using the account reference, and initiate disbursements where needed, all through the Safaricom Daraja API rather than manual entry. Read more in our guide to how M-Pesa Daraja API integration works.
KRA eTIMS invoicing
Tax invoices must be issued through KRA’s electronic Tax Invoice Management System (eTIMS). If you raise invoices from the ERP, it needs a system-to-system eTIMS integration so that invoices and credit notes are transmitted automatically and carry KRA’s control details. See Understanding KRA eTIMS integration.
Statutory payroll
Payroll must handle Kenyan statutory deductions such as PAYE, NSSF, SHIF and the Affordable Housing Levy. Rates and rules change, so check how quickly the system can be updated and who is responsible for making those changes.
Connectivity and resilience
If you operate branches or sites with unreliable internet, ask how the system behaves when the connection drops. Some modules, particularly POS and field data capture, may need offline capability.
Data protection
Your ERP will hold personal data about employees, customers and suppliers. Confirm how access is controlled, where data is hosted and how it is backed up, in line with the Data Protection Act, 2019.
Off-the-shelf, configurable or custom?
ERP options broadly fall into three groups:
| Approach | Best for | Watch out for |
|---|---|---|
| Off-the-shelf packages | Standard processes and smaller organisations that can adapt to the software | Gaps that end up handled in spreadsheets |
| Configurable platforms | Most mid-sized and large organisations; a proven core extended with custom modules | Over-customisation that makes upgrades hard |
| Custom-built systems | Highly specialised processes or regulated workflows with no good packaged fit | Longer delivery and dependence on a capable development partner |
In practice, many organisations end up with a configurable platform plus a small number of custom modules and integrations. The right balance depends on how distinctive your processes really are.
Cloud, on-premise or hybrid?
Cloud deployment reduces the need for in-house servers and makes multi-branch access straightforward, but it depends on reliable internet.
On-premise deployment keeps data on your own servers and can suit organisations with strict data residency requirements or unreliable connectivity, but you take on responsibility for hardware, backups and security.
Hybrid setups combine the two, for example a cloud ERP with local POS terminals that can trade offline.
Consider connectivity at every site, data sensitivity, in-house IT capacity and long-term cost before you decide.
Evaluating vendors and implementation partners
The implementation partner matters as much as the software. When evaluating options:
- Ask for a demonstration using your scenarios, not a generic sales demo. Give vendors two or three of your real processes and see how the system handles them.
- Check local support. Who will you call when payroll fails on the 25th of the month? How quickly can they respond, and can they come on site?
- Understand the implementation method. How will requirements be confirmed, data migrated, users trained and the system tested before go-live?
- Ask about data migration. Migrating master data and opening balances is often the hardest part of an ERP project. Ask how it will be done and reconciled.
- Speak to existing users where possible, ideally in a similar sector.
Calculate the total cost of ownership
Licence or subscription fees are only part of the cost. A realistic budget includes:
- implementation and configuration;
- customisation and integrations;
- data migration;
- hosting or server infrastructure;
- training and change management;
- annual support and maintenance;
- the internal time your staff will spend on the project.
Comparing options on total cost over several years gives a far more accurate picture than comparing headline prices.
Implement in phases
Large “big bang” ERP launches carry high risk. A phased approach usually works better: start with the modules that deliver the most value, such as finance, procurement and inventory, stabilise them, then add HR, payroll, CRM or projects. Each phase builds confidence and lets the organisation absorb change.
A short selection checklist
- Have we documented our core processes, reports and integration points?
- Does the system support M-Pesa, KRA eTIMS and Kenyan payroll requirements?
- Have we seen the system run our real scenarios?
- Is there credible local implementation and support capacity?
- Do we understand the total cost of ownership over at least five years?
- Is there a realistic, phased implementation plan with data migration and training?
If you would like an independent view of your requirements or the options in front of you, our team can help. Learn more about our ERP solutions or talk to us.