NGO & Donor-Funded Operations Across Southern Africa
Grants awarded in dollars, spent in kwacha, reported to a donor in a template nobody else uses — and audited two years later by someone who was not there. What donor-funded operations across Southern Africa actually require, and the honest boundary between an operations system and grant accounting.
A grant office in Lusaka, Harare, Lilongwe or Maputo runs a version of the same month. Money arrives in one currency and leaves in another. Field teams spend cash and mobile money in places with no card acceptance and intermittent signal. Three donors want the same expenditure reported three different ways. And somewhere in the building there is a laptop holding the only complete record of what a project actually bought.
None of that is a reason to buy software by itself. What makes it urgent is the asymmetry: the effort of assembling evidence rises steadily with the size of the portfolio, while the tolerance for missing evidence falls to nothing the moment a donor sends an auditor.
The four pressures, ranked by how expensive they get
In order of what they cost when they go wrong, not in order of how often they are discussed.
Evidence, and the reconstruction test
There is one test worth running on any system, process or vendor in this sector. Pick a purchase from eighteen months ago on a closed project. Ask for the requisition, who approved it and against which budget line, the quotations considered, the purchase order, the delivery note, the invoice, the payment, and the asset or consumption record at the other end. Time it.
If it takes an afternoon, your governance is real. If it takes a fortnight and three phone calls to a former employee, your governance was a set of intentions. Every other feature discussion is downstream of that result.
Donor governance is not judged on what you decided. It is judged on what you can still prove, two years later, without the person who decided it.
Currency: where restricted funds quietly go wrong
A grant awarded in dollars and spent in a floating local currency has a problem that no amount of careful bookkeeping fixes after the fact: the value of the award in spending terms depends on when it was converted, and the record of when and at what rate is usually a bank advice in someone's email.
The discipline is straightforward and almost never followed. Record the conversion as a transaction with the rate actually applied, held on the record. Then every downstream question — how much of the award is left in local terms, whether the budget line is overspent, what the burn rate really is — is answerable from the system instead of estimated from a spreadsheet.
The same grant, recorded two ways
Method A is not dishonest and it is what most portfolios do. It simply cannot surface an overspend until the year is closed, which is the one moment nothing can be done about it. Method B costs nothing extra at the point of entry and is the entire argument for recording rates as they happen. The general version is in multi-currency in kwacha, pula and a redenominated dollar.
Field advances and mobile money in this region
Field teams across the region are paid and pay in mobile money — EcoCash, MTN MoMo, Airtel Money, Orange Money depending on the country — and this is the point where the honest position needs stating before anything else.
No mobile money integration in this region
M-Pesa in Kenya is our only mobile money integration anywhere. There is no EcoCash, MTN MoMo, Airtel Money or Orange Money connection, and no automatic bank feed in any Southern African country. What that means practically: mobile money is handled as a reconciliation discipline — the payment is recorded against the advance or the invoice when it happens, the provider statement is imported, and the two are matched on a rhythm. It works, and a great many organizations run exactly this way. It is simply a different thing from a live connection, and a vendor who blurs the two has told you something useful.
Given that, the advance discipline itself carries more weight than it would in an integrated market.
-
Every advance is issued to a named person against a purpose
Not to "the field team" and not against "activities". A person, an amount, a project, an activity line and a date it is expected to be retired.
-
Retirement is a record, not an email
Receipts captured against the advance, ideally photographed on the phone at the point of spend rather than carried back in an envelope.
-
Outstanding advances are visible to someone whose job it is to care
An ageing view, reviewed weekly. Advances that quietly age past ninety days are the single most common audit finding in this sector.
-
No second advance before the first is retired
A rule that is trivial to state, unpopular to enforce, and the only one that actually works.
-
Mobile money statements are reconciled monthly, by someone other than the spender
Segregation matters more here than in most places, precisely because the transaction leaves no paper of its own.
The full treatment, written for a market where the integration does exist, is in field advances and mobile money — the controls transfer even where the connection does not.
Assets the donor still owns
Vehicles, laptops, generators, medical and lab equipment bought with restricted funds often remain the donor's property, sometimes for the life of the asset. At project close somebody must account for each one — where it is, who holds it, what condition it is in, and what happens to it next.
This is entirely a records discipline and it is nearly always retrofitted in a panic. The register needs the funding source on the asset from the day it is received, not derived afterwards from a purchase ledger. Everything else — custody, movements, verification history, disposal — follows the general discipline in donor-funded asset registers.
What the system holds and what stays with your accountant
Grant operations versus grant accounting
The operations system
Where the evidence is created and kept.
- Projects and funders, with budget lines and spend against them.
- Requisitions, approvals against thresholds that refuse, purchase orders, receipts, three-way matching.
- Supplier records with documents attached and expiry dates tracked.
- Advances issued, retired and aged, by named person and activity.
- Assets with funding source, named custody, movements and verification.
- Stock and distributions, including to remote sites, captured offline where needed.
- Every source document attached to the transaction it belongs to.
Your finance team and auditors
Where interpretation and statutory work stay.
- Fund accounting treatment and the restricted-versus-unrestricted determination.
- Donor report formats, each in its own required template.
- Statutory financial statements and the annual audit.
- Payroll calculation and statutory filing in each country.
- Tax registration, exemptions and returns.
What crosses the boundary
- Spend by project, funder, budget line and period, exportable on demand.
- Source documents retrieved from the transaction rather than a shared drive.
- An asset listing by funding source, with current custody and verification dates.
Write this seam down before implementation and give each side an owner. Most donor-funded implementations that disappoint do so because both parties assumed the other was producing the donor report.
The straight answer
What AWRA OpsHub does today
- Projects and funders with budgets and spend tracked against them, so burn rate is a report rather than a monthly reconstruction.
- Procurement governance — requisition, approval with thresholds that refuse, quotations held, purchase order, goods receipt, three-way matching.
- Supplier records with documents attached and expiry dates, which is where tax clearance, registration and due-diligence evidence belongs.
- Asset registers carrying funding source, named custody, movement history, physical verification and disposal.
- Advances issued to named people against activities, with retirement recorded and outstanding balances visible.
- Every currency in the region as a base currency, with foreign-currency transactions recorded at the rate actually applied.
- Offline capture on mobile for field and remote-site work, with duplicate-safe sync and a conflict view.
What it does not do
- No mobile money integration in this region. M-Pesa in Kenya is the only one anywhere; EcoCash, MoMo, Airtel Money and Orange Money are reconciled against, not connected to.
- No automatic bank feeds in any Southern African country. Statements are imported and matched.
- No donor-specific report templates. We hold the data and export it; the format each donor demands is assembled by your finance team.
- Not a fund accounting engine. Restricted-versus-unrestricted determination and fund accounting treatment stay with your accountants.
- Statutory payroll is not turnkey outside Kenya, in any country in this region.
- Nothing is transmitted to any revenue authority in Southern Africa.
The donor report line is the one to press us on in a demo, because it is where sector-specific vendors make their strongest claim. Our position is that a template built for one donor's current format ages badly and quietly, and that a clean, complete, exportable record is worth more than a report that was right in 2023. Reasonable people disagree — if templated donor reporting is decisive for you, say so early and we will tell you honestly whether to look elsewhere.
What is not built for Southern Africa today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in Southern Africa. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a revenue authority pipeline, a bank or mobile money feed, a statutory return format or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Tax pipelines and return output
Return output in the shape your revenue authority expects and electronic invoicing against any prescribed interface, with retries, a failure queue and a reconciliation report.
Banks, EFT and card acquirers
Bank statement feeds, EFT and debit-order files and card acquirer settlements pulled into the Payments Register so receipts match invoices without re-keying.
Payroll and statutory returns
Payroll tax and social security schedules produced in the layout your filing body expects, generated from live payroll records rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
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. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedWhere to go next
The sector fundamentals, written for a market where more is integrated but the controls are identical: multi-donor fund accounting, restricted versus unrestricted funds, grant burn rate and NGO audit readiness.
Regionally: operations software for Southern African SMEs and ERP for Zambian, Zimbabwean and Botswana businesses. Continentally, procurement software for African NGOs and enterprises covers the governance half at wider scale.
Our take
Run the reconstruction test before you shortlist anything — it will tell you more than a demo. Record every currency conversion at the rate actually applied, because an overspend found in month four is a decision and one found at year end is a disallowance. Put funding source on assets from day one. Enforce the no-second-advance rule even though it is unpopular. And keep fund accounting and donor reporting with your accountants, because that is genuinely their work and a vendor claiming it is usually selling a template that has already aged.
See donor-grade operations across the region
Projects and funders with budgets, procurement gates that refuse, advances that get retired, assets that carry their funding source — and evidence retrievable from the transaction two years later.
Talk to us about your portfolioFrequently asked questions
Do you integrate with EcoCash, MoMo or Airtel Money?
No. M-Pesa in Kenya is our only mobile money integration anywhere in the product. In Southern Africa, mobile money is handled as reconciliation: the payment is recorded against the advance or invoice at the time, the provider statement is imported, and the two are matched on a monthly rhythm by someone other than the person who spent. That is a workable and widely used arrangement, but it is not a live connection and we will not describe it as one. If an integration would decide your purchase, tell us and we will scope it as a build with a written spec and price.
Can you produce our donor reports?
Not in each donor's template, no. We hold spend by project, funder, budget line and period with source documents attached, and that data exports cleanly — but the specific format each donor requires is assembled by your finance team. Our reasoning is that templates built to one donor's current format age badly and silently, and a complete, retrievable record is worth more than a report that was correct two reporting cycles ago. If templated donor reporting is a decision-blocker, say so early and we will tell you straight whether to look elsewhere.
How do you handle a grant awarded in dollars and spent in local currency?
By recording every conversion as a transaction with the rate actually applied, stored on the record. The organization's base currency is locked, so everything is stored, invoiced and reported in one denomination, and foreign-currency movements are captured at their real rate rather than reconstructed at an average later. The practical benefit is timing: an overspend caused by a rate movement becomes visible in the month it happens instead of at year end, when nothing can be done about it.
Is this fund accounting software?
No. We are the operations layer — procurement, stock, assets, advances, projects and the evidence behind all of it. The restricted-versus-unrestricted determination, fund accounting treatment and statutory financial statements stay with your accountants, working from records we hold. Most organizations in this sector need both, and the arrangement works well provided the boundary is written down before go-live and each side has a named owner. What fails is assuming one product does both.
Will field teams in areas with no signal be able to record anything?
Yes. Distributions, receipts, counts, asset movements and verifications are captured on a phone or tablet offline and queued locally, syncing when the device reaches a signal. Each queued operation carries its own client-side identifier so nothing arrives twice, and administrators see a device register showing which devices are behind, what is queued, what failed and what conflicted. Optional GPS capture records where a transaction physically happened, which is frequently the evidence a donor actually asks for.
How does it help with an audit two years after project close?
By making retrieval a query rather than an excavation. Because source documents are attached to the transaction at the point of entry — quotations, purchase orders, delivery notes, invoices — and because approvals are recorded with who approved what against which budget line, a closed project can be reconstructed from the system rather than from a former employee's memory and a shared drive. That is the whole argument for the discipline, and it is worth running the reconstruction test on your current setup before you believe any vendor about it.
What about payroll for our national staff?
Employee records, compensation, statutory identifiers, leave, attendance and payroll cost allocation to projects and donors are built and work in any country. The national statutory calculation is not: our maintained payroll engine covers Kenya only, so income tax bands, social security contributions and statutory return formats for Zambia, Zimbabwe, Botswana, Malawi and the rest are not calculated or produced for you. Use a local payroll bureau for that layer and keep the cost allocation here, where the donor reporting needs it.
