Donor Reporting Made Simple: Restricted vs Unrestricted Funds
The distinction that decides whether your donor reports reconcile — what each fund type is, where NGOs mix them by accident, and the structure that keeps them apart.
Every NGO finance officer knows the theory: restricted funds may only be spent on what the donor specified; unrestricted funds are yours to allocate. Yet "co-mingling of funds" remains one of the most common audit findings in the sector — almost never because anyone stole anything, but because the wall between fund types existed in policy and not in the books.
The three fund types, practically
| Fund type | What it is | Typical sources |
|---|---|---|
| Restricted | Spendable only on donor-specified activities, lines, and periods | Project grants, response appeals, contracted programs |
| Temporarily restricted | Restricted until a condition or date passes, then released | Multi-year grants, matched funding, capital pledges |
| Unrestricted | Board-allocated core funds | Membership fees, local fundraising, unrestricted core grants, cost-recovery income |
The practical test for any shilling in your account: who decides how it is spent? If the answer is a donor agreement, it is restricted — and it needs its own budget lines, its own reporting, and its own paper trail.
Where the mixing actually happens
- The single bank account. All funds land in one account and identity is lost on arrival. A separate account per major donor helps, but tagging every transaction to its grant at entry is what actually preserves identity.
- Salary "borrowing". Core payroll is short in a lean month, so program funds cover it "temporarily". Even when returned, the movement is a finding if undocumented.
- Shared costs with no allocation policy. Rent, internet, the finance officer's own salary — donors accept shared-cost allocation, but only against a written, consistently applied formula.
- Exhausted budget lines. Grant A's fuel line runs dry mid-activity, so fuel books quietly to Grant B. See our donor fund tracking guide for the burn-rate discipline that prevents this.
- Interest and exchange gains. Income earned on restricted balances often belongs to the donor — a detail many agreements specify and many NGOs miss.
Reporting: one ledger, two lenses
You do not need two accounting systems. You need one ledger where every transaction carries a fund classification, so you can produce two views on demand: the statutory financial statements (everything together, classified by nature) and per-donor reports (only that grant's activity, in the donor's budget structure).
The release moment
When a temporarily restricted condition is met — the match is raised, the year arrives — the funds are "released from restriction". Record that release explicitly. Auditors specifically look for restricted balances that quietly became unrestricted with no documented release.
The month-end checklist
Fund discipline in five checks
- Zero transactions this month without a fund/grant classification — make the field mandatory rather than trusting memory.
- Restricted fund balances reconcile to unspent grant budgets, donor by donor.
- Shared-cost allocations posted per the written formula, same as last month.
- Any inter-fund movement documented with approval and a repayment plan.
- Interest on restricted balances treated per each grant agreement.
If your system tags funds at entry, this checklist takes an hour. If it doesn't, it takes a week — which is exactly the gap donor fund tracking software closes.
What AWRA OpsHub does today
- A grant is a project, and the project tag sits natively on purchase orders, expenses, customer invoices and costed time.
- Fund class and grant reference as custom fields, which can be marked required — that is what makes "zero transactions without a fund classification" enforceable rather than aspirational.
- Amount-based approval rules, so a movement above a threshold cannot pass without the named approver.
- An audit log that shows the reclassification an auditor is looking for, including who made it and when.
- Budget vs actual per grant, so an exhausted line is visible before somebody quietly charges it elsewhere.
More we can add to your workspace
- A restricted/unrestricted fund type in the system. The wall this post argues for is a tag you define and a habit you keep — not a built-in fund-accounting structure.
- A release-from-restriction entry. When a condition is met, the release is a posting and a note you make deliberately; nothing prompts you on the date.
- A hard block on the wrong charge, preventing a restricted grant being charged an ineligible cost. Tagging records intent today and your approval chain is the control; testing eligibility is the build.
- An inter-fund borrowing tracker. A temporary movement between funds is documented the way you document any other posting, with no built-in repayment schedule.
- An automatic treatment of interest earned on restricted balances.
The honest summary: this system makes fund discipline visible and auditable, which is most of the battle, but it does not make it automatic. Every audit finding described above is still available to an organisation that tags carelessly. If you want the wall enforced rather than recorded — a validation that refuses the ineligible charge outright — that is a build, and worth asking us to price rather than assuming.
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 needsKeep the wall visible and auditable
Grants as projects, required fund and grant tags on every purchase and expense, approval gates by amount, and a full change log — so restricted and unrestricted stay distinguishable, and any blurring is traceable rather than silent.
See donor fund trackingFrequently asked questions
Do we need a separate bank account for each donor?
Only if the grant agreement requires it. Separate accounts help evidence but do not create line-level tracking — you still need every payment tagged to a grant and budget line. Some donors do mandate dedicated accounts; comply where required.
Can unrestricted funds cover a restricted project's overspend?
Yes — that direction is allowed and common. Unrestricted money can top up a restricted project; the reverse is the violation. Document the top-up so the project report shows the donor-funded portion accurately.
How should we allocate the finance officer's salary across grants?
Through a written cost-allocation policy — timesheet-based or a fixed percentage justified by effort — applied identically every month. Ad-hoc percentages that change with cash flow are what auditors flag.
What happens to unspent restricted funds at project end?
The grant agreement decides: return, reallocation by amendment, or rollover into a follow-on phase. What you may not do is absorb them silently into core funds — obtain written donor instruction and record it.
