Donor-Funded Spending Controls for Zimbabwean NGOs

A programme manager has a sizeable supplier invoice on her desk. The donor budget allows the purchase, but the file does not show which restricted grant will fund it, whether procurement cleared the supplier, or who checked the conflict register. Payment may look routine. Six months later, it can become the item that neither the board nor the donor can explain.

Donor-funded spending controls give Zimbabwean NGOs a practical way to trace each dollar from receipt to beneficiary activity. For registered Private Voluntary Organisations, the issue has greater weight following the Private Voluntary Organisations Amendment Act, effective 11 April 2025, and SI 98 of 2026, published on 5 June 2026.

Challenge: a budget does not prove expenditure

A donor budget sets an approved plan. It does not, by itself, prove that an organisation received the funds through the right channel, selected a supplier properly, obtained authority to spend, or delivered the promised activity.

The PVO Act requires resources and donations to support the organisation’s registered charitable objects and to be transparently accounted for to donors and beneficiaries. That is why a finance team needs more than a spreadsheet with budget versus actual figures. It needs an evidence trail that connects the donor, grant, budget line, approval and proof of delivery.

A common mistake is to mix restricted grants with general operating funds in one bank or ledger balance. Finance can still reconcile the bank account, but it cannot readily show which donor funded a specific purchase or whether a programme overspent its approved line.

The second mistake is waiting for year-end to reconcile advances, supplier commitments and beneficiary registers. By then, missing invoices and unsigned distribution lists have become a recovery exercise rather than a management decision.

Zimbabwe’s Registrar and Private Voluntary Organisations Board, under the Ministry of Public Service, Labour and Social Welfare, handles PVO regulation. Local applicants use Forms PVO 1 and PVO 2. International NGOs also need a government MOU, project proposal and budget estimate, and must operate within the programmes stated in that MOU.

That registration position should shape the finance workflow. If an international NGO’s MOU approves a maternal-health programme in specified districts, a payment request should identify that programme before it reaches the bank approver.

Approach: build the control around the grant code

We recommend one non-negotiable starting point: assign a grant or restricted-fund code when funds are received or committed. Apply that code to every donor receipt, purchase request, supplier invoice, staff advance, payment and beneficiary distribution.

The code creates a common reference across programme, procurement and finance records. Without it, teams rely on staff memory when a donor asks why a particular amount was spent or whether a balance remains available.

Set up the grant record before spending starts

Create a grant record that captures the donor name, agreement reference, currency, approved period, programme, budget lines and any restrictions. Add the responsible programme manager and finance reviewer, because ownership must be clear before the first commitment.

Record the donor source and the formal channel through which funding arrived. The 2025 amendments strengthened donor-source identification, formal-channel funding and transparent-accountability principles. A bank trail is therefore part of the control, not a document to find only during an audit.

If an organisation holds both unrestricted funding and a larger restricted education grant, do not use one generic code such as “donations”. Use separate codes and reconcile each balance monthly. The separation shows whether the education grant paid for approved education activity rather than head-office costs.

Stop incomplete payment requests at the first gate

Use a payment checklist that blocks submission until the requester attaches the core evidence. For a supplier payment, that normally means the grant code, approved budget line, quotation or procurement record, conflict check, approval record, invoice, bank details and delivery evidence.

Take the restricted-grant invoice described above. The workflow should hold it until the programme officer selects the correct grant code, confirms the budget line, attaches procurement evidence, records a conflict-of-interest check and secures two approvals. Finance then adds proof of bank payment, while the programme team uploads delivery confirmation or beneficiary evidence.

The benefit of the control is not a fictional saving figure. It is the ability to show, with one complete file, why the PVO paid the supplier and what the programme received.

For PVOs within the FATF-defined subset, SI 98 of 2026 expressly expects controls such as conflict-of-interest registers, dual authorisation, procurement procedures, donor and beneficiary due diligence, sanctions screening and suspicious-transaction reporting. Scale the process to the organisation’s risk, but do not remove the evidence trail because the payment amount seems small.

Separate approval authority from payment release

The programme manager should confirm need and donor-budget fit. Procurement should confirm supplier selection where procurement rules apply. Finance should check funds, documentation and coding. A different authorised person should release the bank payment.

This separation matters because one person should not be able to request, approve and pay the same transaction. Personal accounts and cash payments weaken that separation and make formal-channel funding harder to demonstrate.

Consider an illustrative community-development PVO distributing livelihood inputs across three wards. It should not treat a signed invoice as complete evidence. It should retain the approved activity budget, supplier selection records, delivery notes, beneficiary registers and confirmation that the distribution matched the approved grant code.

If staff take a field advance from that grant, record it as an advance rather than an expense until they retire it with receipts and activity evidence. The team should reconcile the advance before issuing another one. Otherwise, the accounting ledger may show programme spending while the organisation still holds no proof of who received the inputs.

Reconcile before the donor asks

Run a monthly restricted-fund reconciliation for every active grant. Compare donor receipts, approved commitments, payments, advances, budget variance and unspent balance against the general ledger and bank statement.

Five operational indicators give trustees and senior management a useful view:

• Percentage of payments with a complete evidence pack.

• Average approval-cycle time from request to payment release.

• Budget-variance rate by grant and budget line.

• Unreconciled restricted-fund balance at month-end.

• Percentage of beneficiary distributions matched to beneficiary registers.

These indicators identify where the process breaks. A 98 percent evidence-completion rate may still hide a serious control gap if the missing 2 percent contains the largest supplier payments, so review exceptions by value as well as count.

Results: evidence that holds together

A well-designed workflow produces a payment file that a donor, auditor, board committee or regulator can follow without asking staff to reconstruct the story from email messages. It also gives programme leaders a current view of remaining funds before they commit to the next activity.

PVOs with annual gross income above a lower threshold must submit a simplified annual financial summary. Above a higher threshold, they must submit audited financial statements prepared by a registered public auditor. These thresholds make clean underlying records important, because annual reporting depends on transaction-level evidence.

The audit threshold does not necessarily remove the separate requirement for a registered PVO’s annual audit within three months of financial year-end. Management should obtain current legal and audit advice before setting its year-end timetable.

SI 98 of 2026 requires domestic and international transaction records to be kept for at least five years, while accounting and financial records must be kept for at least seven years. The Registrar, the Financial Intelligence Unit or another competent authority can request those records, so store documents in a controlled repository rather than on individual staff phones or private email accounts.

The same instrument requires reporting of cash or near-cash donations and disbursements above the prescribed threshold within seven working days. It also sets enhanced-due-diligence triggers for cross-border physical cash carried per trip, a single large foreign donation and cumulative annual funding from one high-risk foreign jurisdiction.

These are not triggers to leave for the annual audit file. Set alerts when a donation is received, when a cross-border cash movement is planned and when cumulative funding from a higher-risk jurisdiction approaches its trigger.

Quote

“No grant code, approved budget line and evidence pack, no payment.”

M&J control principle

This is a practical discipline, not an attempt to slow programme delivery. It gives staff a clear decision point and protects beneficiaries when funding scrutiny increases.

Frequently Asked Questions

What is the first control an NGO should introduce?

Start with a unique grant or restricted-fund code for every donor agreement. Apply it to receipts, commitments, payments and distributions, because this creates the basic trail needed for restricted-fund reporting.

Does a donor-approved budget authorise every payment?

No. The budget supports the purpose and amount, but each payment still needs procurement evidence where applicable, the right approval, bank proof and evidence of delivery or activity.

How long should a Zimbabwe PVO keep records?

Keep domestic and international transaction records for at least five years. Keep accounting and financial records for at least seven years under SI 98 of 2026, because competent authorities may request them.

When does a PVO need audited financial statements?

A PVO with annual gross income above the audit threshold must submit audited financial statements prepared by a registered public auditor. Review any separate annual-audit obligation with your adviser, particularly the three-month timing point marked.

A workflow review can show whether your restricted-fund ledger, approval matrix and donor reporting process support the commitments in your PVO registration and donor agreements. SERPA builds grant-coded workflows where every payment carries its budget line, procurement evidence, approvals and delivery proof, so you can answer any donor, board or auditor question from one complete file. Speak With Our Team to assess the controls around your next donor-funded payment cycle, and request a quote tailored to your organisation.