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, GPS-stamped where connectivity allows.
- 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 enforced by the system, not by reminder emails. NGOs that hold these two rules rarely have advance findings; NGOs that waive them always do.
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 is a core part of AWRA's NGO suite rather than an afterthought.
Close the evidence gap
Advances requested, approved, spent, and liquidated in one system — with mobile capture where the spending happens.
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.
