Per Diem, Field Advances & Mobile Money Reconciliation for Field Teams
Per diems, activity advances, and M-Pesa payments are where NGO money moves fastest and evidence moves slowest — the field-finance discipline that closes the gap.
Field work runs on advances. A training in Garissa needs venue deposits, participant transport refunds, per diems, and airtime — most of it paid in cash or M-Pesa, far from the finance office. This is legitimate, necessary spending. It is also, reliably, the largest pile of unsupported expenditure in NGO audits. The problem is never the field; it is the gap between when money moves and when evidence is captured.
The advance lifecycle, done properly
- Request — tied to an approved activity and grant, with a line-item estimate (venue, transport, per diems), not a lump sum.
- Approval — by the budget holder, against the grant's remaining line budget, before the money moves.
- Payment — through a traceable channel referenced to the advance, ideally direct to suppliers where they can be prequalified.
- Spending — evidence captured at the moment of spending, on a phone: receipts photographed, participant lists signed, and stored somewhere retrievable by grant and activity rather than in a personal gallery.
- Liquidation — within a fixed deadline (commonly 7 days after the activity): documented spend + returned balance = advance, to the shilling.
- Closure — reviewed by finance, posted to the grant's budget lines, exceptions escalated.
The two rules that do the heavy lifting
One: no second advance while one is unliquidated. Two: liquidation deadlines are held to, not quietly extended. NGOs that keep these two rules rarely have advance findings; NGOs that waive them always do. Note carefully that both are policy rules — very few systems, ours included, enforce them in software. Ask any vendor claiming otherwise to show you the rule refusing the second advance, on screen.
Per diems without the drama
- A published rate card — by role and location, board-approved, aligned to KRA's non-taxable thresholds (see NGO payroll in Kenya for the tax side).
- Per diems paid against attendance: signed participant/staff lists per day, not per event.
- Partial days and provided meals adjust the rate — write the arithmetic into the policy so nobody negotiates it in the field.
- Per diems to participants (transport refunds, allowances) get ID-verified recipient lists; ghosts on participant lists are a classic fraud vector.
M-Pesa: traceable by nature, chaotic by habit
Mobile money should be the most auditable channel you have — every transaction has a code, a timestamp, and a registered recipient. It becomes chaos when payments run through personal lines and the reconciliation never happens:
- Use organizational paybill/bulk-payment accounts, never staff personal numbers, for organizational payments.
- Reference every payment to its advance or activity at send time — a schedule of "who, why, which grant" attached to the bulk run.
- Reconcile M-Pesa statements to the ledger monthly, like a bank account — because it is one.
- Transaction costs are real costs: budget them and post them to the same grant lines as the payments they carry.
What finance reviews monthly
The field-finance dashboard
- Advance aging: nothing past its liquidation deadline without an escalation on record.
- Advances per person: nobody holding two open advances.
- Liquidation quality: receipts legible, participant lists signed, arithmetic closing to zero.
- M-Pesa reconciliation: statement to ledger, differences explained.
- Exceptions report: waived rules, emergency advances, and write-offs — visible to management, not buried.
All of this is mobile-first work: the evidence exists in the field, so capture belongs in the field. That is precisely what offline-capable mobile workflows are for — and why field finance matters to AWRA's NGO suite. It also deserves the plainest answer in this whole guide, because this is the area where our own gap is widest.
What AWRA OpsHub does today
- M-Pesa integrated both directions — collections and vendor payouts — configured per organisation, so the traceable channel this post recommends is real.
- Expenses coded to a grant, with a payment method and a reference field for the transaction code.
- Approval chains that read the amount, so spending above a threshold needs the budget holder before it moves.
- Vendor records and supplier prequalification, which makes paying known suppliers directly — rather than advancing cash — a genuine option.
- A document vault for evidence, with classification, checksums and an access log.
- Custom fields on expenses, so activity, location and rate basis can be captured structurally rather than in a notes box.
- A full audit log of who changed what, and GPS-stamped records on asset checks and scan events.
More we can add to your workspace
- An advances module: an advance request, approval against a remaining line, a liquidation and a closure step. Every stage of the lifecycle above is modelled with expenses, payments and human discipline today.
- Enforcement of the two rules above. A block on a second advance while one is open, and a deadline mechanism that refuses or escalates a late liquidation. An earlier version of this post implied both existed; that was wrong, and correcting it matters more than the sentence it cost us.
- Receipts attaching to an expense. The vault holds them and attaches natively to tasks, tickets and HR records; extending that to an expense or purchase order is the build, and until then the link is a reference convention you enforce.
- A per-diem rate card. Rates by role and location, partial days and provided-meal deductions live in your policy, not as a computed schedule.
- M-Pesa statement reconciliation. Payments transact through the integration; matching a bulk field-disbursement statement to the ledger line by line is manual.
- A participant or attendance register. Signed lists and ID verification are documents you hold, not records the system validates.
- A GPS stamp on field spending. Those audit fields exist on asset movements and scans, not on expense capture.
This is the widest distance between what the sector needs and what ships today, and blurring it would be a disservice: field advances are the most common NGO audit finding, and the advances module is a build. What exists is a visibility layer — traceable payments, grant-coded spend, approval gates, an audit trail. The control layer is your policy plus a monthly review, or a scoped build with a price. Weigh that honestly against any vendor promising the lifecycle out of the box, and make them demonstrate it rather than describe it.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsClose the evidence gap
Traceable M-Pesa payments, grant-coded expenses, approval gates by amount, and an [audit trail](/glossary/audit-trail) — with the advance-liquidation control named as work to be scoped rather than sold as a feature. Bring your advance policy and we will show you exactly which parts we cover today.
See field finance in AWRAFrequently asked questions
What is a reasonable liquidation deadline?
Seven calendar days after the activity ends is the sector norm; ten for genuinely remote areas. Longer deadlines do not produce better liquidations — they produce forgotten ones. The deadline matters less than enforcing it consistently.
Can staff use personal M-Pesa for organizational payments in emergencies?
Define it as a documented exception: allowed only where organizational channels failed, reimbursed against the trail (messages, codes, recipient confirmation), and reported in the monthly exceptions list. As routine practice it destroys traceability and exposes staff personally.
How do we handle receipts from informal markets that issue none?
Market-purchase vouchers: item, quantity, price, seller name and phone, buyer signature, plus a photo of the goods. Pair with periodic market price surveys so rates are benchmarked. Donors accept context-appropriate evidence applied consistently.
Should we stop cash advances entirely and pay suppliers directly?
Direct payment is better where suppliers are known — venues, established transporters. But participant refunds and village-level purchases will always need money in the field. The goal is shrinking the advance envelope, not pretending it away.
