Expense Management for NGOs in Kenya: Donor-Ready Audit Trails

Short answer: A donor-ready expense process in a Kenyan NGO means every payment can be traced, in one step, from the request to its approval, its supporting documents, the M-Pesa or bank payment and the ledger entry, coded to the right grant and budget line. Get there by approving inside a system rather than email, paying field teams from approved requests, attaching documents at the point of approval, and coding each request to a programme before it is paid.

This guide is for finance directors, grants managers and programme finance officers at NGOs and donor-funded programmes in Kenya. Most such organisations do not have a spending problem. They have an evidence problem: the money was spent correctly, but the trail does not hold together when an auditor selects a sample. Creodata builds expense management software for Kenyan organisations, so we say plainly where we fit near the end. This is practical guidance, not audit or legal advice; your donor agreements and auditors set the actual requirements.

Why donor audits find documentation gaps

Donor and statutory auditors usually test expenses by sampling: they select a set of transactions from the ledger and ask for the full support behind each one. A typical request for each sampled item looks like this:

• The request or purchase requisition, and who raised it.
• Evidence of approval by someone with the authority to approve it.
• The invoice, receipt or attendance list behind the payment.
• Proof of payment: bank or M-Pesa reference.
• The grant, budget line and cost centre it was charged to, and why.

Findings rarely come from missing money. They come from support that exists somewhere but cannot be produced for a specific transaction: an approval in an email thread nobody can find, a receipt in a programme officer's folder, an M-Pesa confirmation saved under a file name that has drifted. A handful of such items in an audit sample can be enough for a finding, and repeated findings affect how donors see the organisation.

The Kenyan NGO reality: field payments over M-Pesa

Kenyan NGOs pay a large share of their programme costs through M-Pesa: community mobilisers, enumerators, transport refunds for training participants, field staff reimbursements and small local suppliers. M-Pesa is fast and reaches places banks do not. It also multiplies the evidence problem:

• Volume goes up. One training can mean dozens of small payments, each needing support.
• Payment gets ahead of approval. It is quick to send, so approval is often recorded afterwards, if at all.
• The statement lacks context. An M-Pesa line shows a phone number and an amount, not the activity, the grant or the attendance list.
• Personal phones get used. Paying from a staff member's line breaks segregation of duties and leaves no organisational record.

The answer is not to stop using M-Pesa. It is to pay through M-Pesa B2C from the organisation's own business account, triggered by an approved request, so the payment reference lands on the same record as the approval and the documents. Our article on reconciling M-Pesa disbursements with Business Central explains how.

What a donor-ready audit trail contains

If you can produce all seven for any sampled transaction in a few minutes, you are donor-ready.

Documentation linked to transactions, not folders

Most NGOs already use SharePoint or a shared drive. The problem is usually not storage but filing. Documents are filed by whoever uploads them, in a structure that made sense to that person. To find the invoice behind a ledger line, you need to know who submitted it and roughly when.

Linking documents to transactions reverses this. The invoice is attached to the request when it is raised, approvers see it when they approve, and the ledger entry carries a link back to it. Filing becomes a by-product of the workflow rather than a separate job. For wider records management beyond finance, see our EDMS solutions.

Running multiple programmes and grants

Multi-programme NGOs have one more layer: each grant has its own budget, eligible cost categories and, often, its own approval expectations. Practical controls:

• Code at request, not at posting. The person closest to the activity chooses the programme and budget line; finance reviews it. Recoding at month-end is where misallocations creep in.
• Route by department or programme. Different programmes can have different heads of department in the approval chain.
• Use amount thresholds. Small field payments and large supplier invoices should not follow the same chain. Treating a KES 4,000 transport refund like a KES 2 million contract causes delay without adding control.
• Report by programme. Grants managers need spend by programme and budget line without asking finance for a spreadsheet.

Ask any vendor how grant and budget-line coding is captured and whether it flows into your ledger dimensions. Requirements vary a lot between donors, so test with your own grant structure.

What to look for in expense management software for NGOs

• Approval chains by department, request type and amount, configurable by finance.
• Escalation when approvals are overdue, so field payments are not held up waiting for one person.
• M-Pesa B2C and B2B payment on final approval, with the result written back to the request.
• Document storage linked to every request.
• Ledger posting to your finance system, with dimensions and document links.
• Role dashboards and exports for programme managers, finance and auditors.
• Access control through your existing Microsoft 365 or Google accounts, so leavers lose access when their account is closed.

Our buyer's guide to expense management software in Kenya has a full demo script and a comparison of provider types.

Where Creodata fits

Creodata is a Nairobi software company. Our expense management system handles three request types (supplier invoices, petty cash and cashbook payments), each submitted with attachments by staff signing in with Microsoft Entra ID. Requests follow a multi-stage chain, for example Head of Department, Finance Reviewer, CFO, resolved per department and request type, with an amount threshold deciding the route. Overdue approvals escalate automatically, with an audit entry.

On final approval the system pays over M-Pesa B2C for petty cash and reimbursements, or M-Pesa B2B for suppliers, through the KentaPay / Eclectics Swivel gateway, with callback and status reconciliation and the payment reference written back to the request. Approved items post to Microsoft Dynamics 365 Business Central over OData, with SharePoint document links attached. Role dashboards and CSV exports support finance reviews and audits. It runs on Microsoft Azure.

In a composite scenario based on typical deployments, an NGO running programmes across several counties moved month-end close from 11 days to three and had no documentation findings at its next donor audit. The details are in Two Ledgers, One Truth. The scenario is representative, not a single named client.

What we do not do: we post only to Business Central, we do not have a staff imprest or per-diem module, we do not make bank or PesaLink payments, and we do not have a mobile app. If your field advances run through imprest surrenders, plan for that separately. For small field payments, see our petty cash management software.

To walk through a donor audit sample on your own approval chains, book a demo.

Frequently asked questions

What is donor-compliant expense tracking?

It means every expense can be traced to a request, an authorised approval, supporting documents, a payment reference and a ledger entry coded to the right grant and budget line. Donors differ in their detail, so read each agreement, but that chain is what most auditors test.

How can NGOs in Kenya pay field staff on M-Pesa and stay audit-ready?

Pay from the organisation's M-Pesa business account through B2C, only after approval, and record the M-Pesa transaction reference against the approved request. Attach the attendance list or receipt to the same request. Avoid paying from personal phones.

How do donor auditors sample expenses?

Auditors typically select a sample of transactions from the ledger, often weighted towards larger or unusual items, and ask for the full support behind each. The faster you can produce the request, approval, documents, payment proof and coding for any line, the smoother the audit.

Can one expense system handle several donor-funded programmes?

Yes, if it captures the programme and budget line on each request and routes approvals by department or programme. Test this in a demo with your own grant structure, and check how the coding reaches your ledger.

Do NGOs in Kenya need eTIMS receipts for expenses?

Since 1 January 2024, KRA has required business expenses to be supported by eTIMS electronic tax invoices to be deductible, and it checks expenses in returns against eTIMS records. How this applies to your NGO depends on its tax status and activities, so confirm with your tax adviser.