ERP Audit Consultant, Kenya

Signs a Kenyan ERP is working against you

An ERP that is quietly underperforming rarely produces a single dramatic failure. It shows up as recurring effort that everyone has learned to accept. In Kenyan businesses the signals to look for are fairly specific:

• The suspense account for mobile money receipts never reaches zero, and clearing it takes days at month-end.
• Some invoices, often at a branch or for cash sales, are raised outside the ERP and have to be keyed in afterwards.
• Customers deduct withholding VAT, but nobody can say quickly which certificates are still outstanding.
• Depot managers keep their own stock sheets because the system figure is not trusted.
• Dollar bank balances and supplier accounts need manual revaluation adjustments.
• Several staff share one login at a branch, so nobody knows who changed what.

Each of these has a cause that can be found and usually fixed through configuration, rules, training or a better-built integration. The audit exists to find those causes, rank them and give your team and your implementer a clear list to work from, following my ERP health check method.

It is worth being clear about scope. This is a review of the business system. It is not a tax audit, it does not replace the work of your external auditor and it does not predict how KRA would view any transaction. Where a finding has a tax angle, I describe what the system does and pass the question to your tax advisor.

Matching ERP documents to eTIMS records

For businesses within its scope, eTIMS is how invoice data reaches Kenya Revenue Authority. During an ERP audit, the question is not how eTIMS works in general but whether every relevant document in your system actually went through, and whether the ERP shows that clearly.

I take a sample period and work with your team to compare three lists: the invoices and credit notes in the ERP, the validated documents your staff can retrieve from eTIMS, and any documents issued from other tools such as a POS or a standalone invoicing app. Differences usually fall into a few groups:

• Documents that failed to transmit with no alert, so nobody retried them.
• Credit notes created in the ERP but never sent, leaving the original invoice uncorrected on the tax side.
• Sales raised in a second tool and posted to the ERP only as a daily total.
• Invoices edited after transmission, so the ERP copy no longer matches the validated version.

For each group I note where it originates in the setup or the connector, and who would fix it. I do not interpret KRA rules or decide what must be transmitted; the findings go to your tax advisor, who confirms the obligations before your implementer changes anything. How eTIMS should be specified in a new system is covered on the ERP business analyst page for Kenya.

M-Pesa receipts, suspense balances and withholding certificates

Receivables in Kenya combine mobile money, bank transfers and deductions made by customers, and an ERP can handle all three well or turn them into a daily chore. The audit follows the money through each route.

For M-Pesa, I review which Paybill and Till numbers feed which entity or branch, how statements or payment notifications reach the ERP, and what reference customers are asked to enter. Then I take the unallocated list, age it and trace a sample of entries to the reason they failed to match: a phone number instead of an account code, a payment split across invoices, a reversal posted twice or a Paybill mapped to the wrong company. The pattern of causes points to the fix.

For withholding, I look at how certificates received from customers are recorded and linked to the invoices they relate to, and whether the system can show which deductions still lack a certificate. On the payables side I check how withholding on supplier payments is calculated and documented. Treatment and rates are for your tax advisor to confirm; my part is showing where the records are incomplete or disconnected.

Bank receipts in shillings and dollars complete the picture, including how bank statements are imported and how exchange differences on dollar receipts are posted. Many of these fixes are matching rules and configuration, the territory of ERP optimization.

Depots, branches and who can do what

Distribution, manufacturing and retail businesses in Kenya often run depots or branches far from head office, sometimes with patchy connectivity. These sites are where system discipline erodes first, and where the audit spends real time.

On stock, I compare a sample of system quantities with recent counts, then trace the differences through delivery notes, transfers and returns. Typical causes include transfers dispatched but never received in the system, returns booked as new stock, and sales recorded on paper during an outage and keyed in days later with the wrong date. Each one distorts both stock value and margin reports.

On access, branch practice often diverges from head office policy. I check for:

• Shared logins used by several people at a counter or depot.
• Users who can create a customer, set credit limits and approve their own sales on credit.
• Staff who can change supplier bank or mobile money payout details and also release payments.
• Accounts belonging to staff who have left.
• Branch users with access to payroll or head office financial reports they do not need.

Where a small branch cannot realistically separate every duty, I suggest compensating checks that head office can run. Personal data held in the system is noted so whoever is responsible under Kenya's data protection law can review the arrangements. If depot connectivity is causing deeper operational failures, the ERP rescue page for Kenya covers resilience in more depth.

Payroll postings, dollar balances, licenses and the report

The remaining areas cover what flows into the ERP and what the company pays for. Payroll in Kenya is commonly processed outside the ERP, in dedicated software or by an outsourced payroll bureau that deals with statutory deductions. I do not review the payroll calculations, but I check the posting interface: whether salaries, deductions and employer costs arrive in the right accounts, departments and entities, and whether someone corrects the journal by hand each month.

Dollar balances get a focused check. I look at how exchange rates are entered and by whom, whether bank accounts, debtors and creditors in dollars are revalued consistently, and whether management reports show currency exposure in a way your accountant accepts.

Licenses are compared with real use, and add-ons or connectors nobody depends on are listed. Commercial decisions stay between you and your vendor.

The report gives directors a short summary of the most important findings, then the full list with cause, business effect, recommended fix and a priority rating. Tax-related observations, such as eTIMS gaps or withholding records, sit in a separate section for your tax advisor. I present the findings in an online session and can stay involved while your implementer works through them.

For wider context, see the Kenya overview, the ERP consultant page for Kenya and the Nairobi page.