Business Process Consultant, Kenya

From order to tax invoice to cash

In Kenya, order to cash has more steps than the textbook version, and some of them carry tax consequences. I map it from the first quotation through delivery, invoicing, collection and any credit note, with the people who perform each step.

The questions that reveal the most are practical:

• At what point is the tax invoice issued, and where does the eTIMS step happen in that flow? Your tax advisor confirms which documents are in scope and when.
• Who issues credit notes for returns and price corrections, and how are they linked to the original invoice?
• Which customer details, such as a PIN where your advisor says one is needed, are collected when the customer is created rather than at the till?
• What happens when an invoice cannot be transmitted because the connection is down or data is missing: who is told, and who fixes it?
• Who releases goods on credit, and who checks the limit?

Those answers tend to trace trouble back to the first steps of the flow. A customer created without the right details produces invoices that need correcting later, and a credit note issued without a reference becomes a reconciliation puzzle. So the redesigned routine places every check as early as it can go. How a future system must handle these documents is spelled out on my Kenyan ERP business analyst page.

Allocating M-Pesa and bank receipts

Collections in Kenya arrive through several doors: M-Pesa Paybill and Till numbers, bank transfers, checks and sometimes cash at branches. The money arrives; the problem is knowing whose it is and which invoice it settles. Without a clear routine, unallocated receipts build up and customer statements become unreliable.

I agree a collections process with finance and sales that answers:

1. References: what customers are asked to enter as the account number or reference when they pay, and how sales staff remind them.
2. Ownership: who allocates receipts each day, for which collection numbers and bank accounts, and by when.
3. Unknown payers: how a payment from an unrecognized phone number or narration is investigated, and how long it may stay unallocated before escalation.
4. Partial and combined payments: how one payment covering several invoices, or a part payment, is applied.
5. Branch cash: how cash collected at branches is counted, banked and reported, and who checks it.

The routine is written so a new finance assistant can follow it from day one. It also gives management a simple daily or weekly view of what remains unallocated and why. Once the rules are settled, many of these steps become good candidates for business automation in Kenya, but the rules come first.

Withholding certificates, suppliers and payments

Withholding taxes add steps to both sides of the business, and they are easy to lose track of. When a customer deducts withholding from your invoice, you usually need their certificate to support the credit you claim. When you deduct from a supplier, you have obligations to remit and to issue certificates. Your tax advisor confirms which rules apply to which transactions.

In procure to pay and order to cash mapping, I make these steps visible and owned:

• Customer deductions: how a short payment due to withholding is recognized, recorded against the invoice and followed up until the certificate arrives.
• Certificate register: one list of expected and received certificates, so finance knows what is missing before it matters.
• Supplier payments: who decides whether withholding applies to a payment, who calculates it and who issues the certificate to the supplier.
• Supplier onboarding: which details and documents are collected when a supplier is set up, and who verifies bank or M-Pesa payout details.
• Payment release: who prepares the payment batch and who approves it, kept as separate people.

None of this requires new software to start. A clear routine and a register can be run in today's tools. Later, the same rules become requirements for any ERP and for the procurement automation that may follow.

Petty cash, casual labor and tender paperwork

Some of the most important Kenyan processes rarely appear on a formal process map, yet they cause a large share of month-end questions.

Petty cash and imprest. Field teams, drivers and site supervisors often receive advances for fuel, repairs or small purchases. I map how an advance is requested and approved, how it is paid, often by M-Pesa, how receipts are returned and how the balance is cleared before a new advance is issued.

Casual and contract labor. Businesses in construction, agriculture, logistics and events may pay casual workers frequently through mobile money. The process questions are about control: who confirms attendance, who approves the payment list, who sends the payments and who reconciles them. Statutory deductions and contracts are questions for your payroll provider or advisor.

Tender preparation. Companies that bid for public or institutional contracts gather the same documents repeatedly. A defined routine, with an owner, a checklist of documents the tender requests and a record of expiry dates for certificates and registrations, avoids last-minute searches. Which documents a given tender requires is set by the tender itself and checked by your team.

Writing these routines down tends to reduce disputes and make audits less painful. My ERP consultant page for Kenya describes how they later shape system choices.

Owners, documents and the move to software

A process improvement only lasts if someone is responsible for it. At the end of the design work, management names an owner for each flow in scope: usually the manager who suffers most when that flow breaks. That person signs off changes, keeps the procedures up to date and is the contact for branch questions.

Documentation is kept short and practical. Each flow gets a swimlane map, a one-page procedure for each role and a checklist where it helps, such as for month-end or tender preparation. The approval matrix shows limits by role and branch, with stand-ins for approvers who travel between sites. The working language of every document is English, and Kiswahili quick guides for depot or field staff are produced by your own people if wanted.

Software comes next, not first. The design produces a gap list, and each gap is classified:

• a routine change that needs only agreement and discipline;
• a change in how current tools are configured or used;
• a requirement for automation, integration or a new system.

If a new platform does prove necessary, vendors receive the agreed routines as their brief, and the system is set up around choices already made by the business. The Kenya overview lists every way I support Kenyan companies remotely, and the method itself is described under business process consulting.