ERP Requirements Consultant, Kenya

What a Kenyan ERP specification holds

Implementers in Kenya price faster and argue less when every bidder receives the same well-organized document. I build it around sections that each answer one question.

• Business context: entities, branches, depots, users, transaction volumes and systems that stay in place, such as a point-of-sale tool or a payroll bureau.
• Process sections: sales and distribution, purchasing and imports, inventory across depots, projects or contracts where relevant, and finance and the close.
• Kenyan statutory section: eTIMS, VAT, withholding, payroll journals, record keeping and currency.
• Non-functional section: data protection, hosting, roles, audit trail, performance and outage behavior.
• Integration and migration sections: one entry for every interface and every data object.
• Glossary: local terms such as Paybill, Till number and KRA PIN, explained for any bidder based outside Kenya.

Against every line sit its number, the person accountable for it, its ranking, where it came from and why it is needed. The workshops and process discovery that produce this material are the subject of my Kenyan business analyst page. The focus here is the controlled document that bidders answer and testers rely on. The general approach is described under ERP BRD consulting.

eTIMS, withholding and M-Pesa as pass or fail lines

Kenyan specifications usually name the right topics. The weakness is wording that no demo could disprove. I rewrite each topic as a result that can be watched on screen or checked in a report:

• Each invoice and credit note is transmitted through the eTIMS integration route your tax advisor confirms, and the validated invoice details returned by the tax system appear on the printed or emailed document.
• When transmission fails, the document is held, flagged to a named user and retried, and no second number is issued for the same sale.
• Supplier invoices can be checked against eTIMS details before they are approved for payment, where your advisor confirms this matters for your expense claims.
• Withholding VAT and withholding tax deducted by customers are tracked against invoices until the certificate is received.
• Paybill and Till receipts import with their transaction reference and payer details and match to customer accounts using rules you define, with reversals handled visibly.
• The payroll provider's journal posts statutory deductions to the correct liability accounts by department.
• Sales in dollars are reported in shillings at a documented rate source.

I do not rule on which documents or taxes apply to you. That confirmation comes from your tax advisor, and the advisor's name sits next to each tax line.

Data protection, hosting and requirements for outages

Non-functional requirements decide whether a Kenyan rollout works outside head office, yet they are often reduced to a single line on security. I give them structure.

• Data protection and hosting: where production data and backups are held, who at the vendor or implementer can reach them and how the arrangement fits Kenya's data protection law. Your legal advisor or data protection lead assesses the answers.
• Roles: separation between creating customers or suppliers, approving credit and releasing payments, with approval limits matched to branch managers.
• Audit trail: who changed a price, a credit limit or an M-Pesa allocation, and how that history is reported.
• Outage behavior: what a depot, farm or upcountry branch must still do during a power cut or network failure, how documents queue and how they sync without duplicates.
• Performance: expectations for month-end runs, bulk invoicing and mobile users on slow connections, written as points to agree, not invented figures.
• Exit: how you receive a full copy of your data if the relationship ends.

Bidders can only cost these needs if they see them before quoting, which is why they belong in the document from the first draft.

Interfaces, migration and a trail from line to test

Kenyan ERP landscapes are rarely self-contained. A typical setup connects the tax system, M-Pesa, one or more banks, a payroll bureau, point-of-sale tools and sometimes a parent company's reporting. Each interface entry states direction, timing, trigger, data content, what happens on failure and who owns it.

Migration requirements follow the same rule. They define which customer and supplier balances, open invoices, withholding positions, stock by location and documents come across from QuickBooks, Sage, point-of-sale systems or spreadsheets, and how each object will be reconciled before the old system is closed.

Ranking matters more when budget forces a phased rollout. Process owners sort their lines into must, should, could and will not. The musts define the first phase; could lines may wait; will-not lines are recorded so the debate does not restart. Every line also cites its demo scenario during selection and its test case in user acceptance testing. With that chain in place, anyone can follow an eTIMS or M-Pesa requirement through the fit-gap analysis to the test that closed it.

Bids, contracts and common gaps in Kenyan specifications

Once approved, the document becomes the requirement annex every implementer answers line by line, and the scripted vendor demos on my Kenyan ERP selection page use it as their source. Organizations bound by public procurement rules use the tender format their procurement team requires, with the specification inside it. In the contract, the approved version is referenced in the scope, and milestone payments can be tied to acceptance of the lines it contains.

Version control keeps that link honest. Every release is numbered and signed, changed lines are listed with the reason for each change, and anything altered later goes through that same route.

Gaps that create risk in Kenyan specifications include:

• eTIMS described for invoices only, with credit notes, failed transmissions and supplier invoice checks missing.
• M-Pesa integration named without matching rules, reversal handling or ownership of unmatched receipts.
• Withholding certificates not tracked, leaving balances that never clear.
• No requirement for offline work at depots, so outages stop sales.
• Dollar pricing and shilling reporting left to whatever the system does by default.

The Kenya hub and the ERP consultant page for Kenya describe the wider remote support available.