SERPA | ODOO ERP FOR NGO PAYMENTS IN AFRICA

A programme manager approves a mobile-money beneficiary run on Friday afternoon. By Monday, finance has a payment file, the field team has a different beneficiary list, and the donor report still sits in three spreadsheets. This is where NGO payments Africa becomes a control issue, not merely a finance process.

For NGOs operating across African countries, payment approvals, tax, foreign exchange, registration and record-retention duties are set locally. There is no Africa-wide NGO payments regulator or single compliance threshold. The workable baseline is the country regulator, revenue authority, central bank and the donor agreement, all reflected in one auditable operating model.

At Serpa, we use Odoo ERP to connect grant management, payment controls, accounting and donor reporting. The objective is clear: every approved cost must be traceable from a donor report back to the person who requested it, the budget line, the approval, the payment record and the supporting document.

Why NGO payment controls break under donor pressure

The issue we see most often is not a missing policy. It is a broken chain of evidence.

A grant manager may hold the approved budget in one workbook. Finance records invoices in accounting software. The field team uses a mobile-money provider portal. Payroll sits with HR. At month-end, someone rebuilds the donor report manually. That approach can produce a report, but it struggles to prove how each declared cost was incurred and approved.

EU NGO grant guidance requires a reliable system that collects, records and reports transactions, then reconciles declared costs and revenue to supporting evidence. The principle applies beyond EU-funded programmes because it addresses the question an auditor will ask: can you follow this number back to source documentation?

The control problem becomes sharper when one person can create a supplier, approve the payment and release the funds. Request, approval, execution and reconciliation should be separated. IFRC Africa-region practice includes monthly account and document reviews by finance personnel, which gives finance a recurring point to identify missing records and unusual transactions.

The four records every payment needs

A grant management system Africa teams can rely on should record these elements against every transaction:

1.       Grant and budget line: The transaction must show which donor-funded activity it supports. Without this tag, finance cannot establish whether the expense is eligible.

2.       Request and approval: The system should retain who requested the cost, who approved it and when. An email kept outside the transaction record is difficult to retrieve during an audit.

3.       Payment evidence: This includes the invoice, supplier or beneficiary reference, payment status and proof of execution. Payment confirmation alone does not show that the payment was authorised or correctly allocated.

4.       Reconciliation result: Finance must match the payment to the bank or mobile-money settlement and resolve exceptions. A paid status in a portal is not a completed control until it has been reconciled.

This structure supports real-time visibility without giving programme staff unrestricted authority over funds.

A step-by-step control model for NGO payments Africa operations

Step 1: Define the jurisdiction and donor rules before configuration

Do not configure one generic African workflow. Start by documenting each operating country, the NGO registration requirements, applicable tax treatment, central-bank or foreign-exchange requirements, payment rules and the donor agreement.

This step matters because a donor rule can be stricter than the local legal minimum. Record retention is a practical example. Under EU LIFE NGO operating grants, original accounting and tax records, including digitised originals where national law permits, must be retained for five years after payment of the EU balance. A project close date is therefore not automatically a record-destruction date.

We recommend a compliance register inside the implementation plan. It should state the rule, the country or donor it applies to, the document to retain, the responsible owner and the review date. If your organisation works in multiple countries, do not consolidate retention periods into the shortest one. That choice can leave the organisation unable to support a later review.

Step 2: Build the grant structure before processing transactions

Set up each donor, grant, programme, activity, budget line and reporting period as controlled dimensions in Odoo ERP. Every commitment, invoice, payroll allocation, receipt and payment should carry the appropriate tags.

The practical test is simple. Select a line in the donor report and ask finance to retrieve its evidence without asking a staff member to search their inbox. If the answer depends on a particular employee remembering a folder name, the process is not auditable.

Take an illustrative health programme funded through an EU grant with EUR 100,000 in actual-cost contribution. The finance manager records vendor invoices but allows field advances to be logged only in a spreadsheet. At reporting time, the team cannot establish which advances were cleared against each activity, and the independent factual-findings requirement at EUR 100,000 or more becomes harder to satisfy. The better design is to create each advance, clearance and supporting document as linked records under the correct grant. The cost of correcting the process appears at audit time, when staff must rebuild evidence that should already have been captured.

Step 3: Separate duties in the approval workflow

Configure different roles for payment request, budget approval, finance review, payment execution and bank or wallet reconciliation. The exact approval levels depend on the NGO’s delegation of authority and donor conditions, but the roles should not collapse into one user account.

For example, a programme officer can raise a purchase request against the approved grant budget. The budget holder can approve the programme need. Finance can check coding, supporting documents and available budget. An authorised payment officer can execute the payment. A separate finance user can reconcile the settlement.

This is not bureaucracy for its own sake. It prevents a single person from introducing a supplier, approving a transaction and confirming that it was paid correctly without independent review.

A useful judgement call: if your NGO has a small finance team, do not create six approval layers just to imitate a large institution. Assign the minimum number of distinct people needed to prevent self-approval and independent review from disappearing. Where staffing makes complete separation impossible, document the compensating control, such as a monthly review by a board treasurer or country director.

Step 4: Treat mobile-money disbursements as finance transactions

Digital beneficiary payments are increasingly central to programme delivery. On 28 February 2026, the World Bank reported that the share of digital social-protection payments in the Sahel rose from 20% in 2021 to 64% in 2025. That growth makes integration between beneficiary records and financial records more urgent.

A mobile-money payment file needs more than a successful upload. It needs beneficiary data, payment status, settlement confirmation, exception handling and a grievance channel. These controls help identify duplicate payments, failed wallet transfers, unclaimed amounts and disputes about entitlement.

Consider an illustrative cash-assistance project in the Sahel. The project uploads 2,000 beneficiary payments to a mobile-money provider, then records only the total amount in the ledger. Several transfers fail, while some beneficiaries report that their details were incorrect. Finance can see the aggregate expense but cannot explain the difference between the requested, paid, failed and reversed amounts. The corrected process imports or records each payment status, routes exceptions to the programme team, and reconciles the final settled total to the ledger. The programme should also retain the approved beneficiary list and the grievance outcome, because payment delivery and financial evidence are connected.

World Bank evidence for the Sahel associates stronger payment mechanisms with improved transparency, reduced fraud and lower delivery costs. The mechanism itself is not proof of control. The reconciliation and exception process are.

Step 5: Control payroll and staff time against grants

Payroll allocations often create the largest gap between an approved grant budget and evidence of actual delivery. Where staff work across grants, their payroll costs must be allocated using evidence that the donor accepts.

For EU LIFE NGO operating grants, personnel who are not assigned full-time to a grant need daily time records. Unreliable timesheets can reduce eligible costs or result in recovery of payments. The step people skip is obtaining timely approval for timesheets before reporting starts. Signing a reconstructed record months later creates a weak audit trail.

Configure timesheet approval to capture the employee, date, activity, grant and approver. Then reconcile approved time to payroll allocations before the month closes. A donor reporting ERP process is strongest when payroll, timesheets and general ledger entries use the same grant and activity codes.

Step 6: Make monthly close a donor-control process

Donor reporting should not begin a week before the deadline. IFRC Africa-region practice includes monthly reminders, grant-orientation sessions when donor requirements change, finance feedback after monthly close, and training in donor reporting and financial-project management.

A monthly close checklist should include:

What Odoo ERP should provide for NGO financial management Africa teams

Odoo implementation for an NGO should be driven by controls and reporting needs, not by a generic chart of accounts. We configure a unified record of grants, budgets, purchase requests, invoices, payroll allocations, payments, documents and reporting dimensions.

For multi-entity NGOs, the design should also distinguish the legal entity that pays, the country programme that receives the cost, and the grant that funds it. A consolidated management view is useful, but it must not remove the entity-level audit trail.

The core Odoo ERP requirements are:

●        Grant, donor, programme, activity and reporting-period tags on financial records.

●        Configurable approval workflows based on payment type, value, entity or funding source.

●        Document attachment and retention controls for invoices, agreements, approvals and payment evidence.

●        Budget-versus-actual reporting that includes approved commitments, not only posted expenditure.

●        Reconciliation workflows for bank, cash and mobile-money settlement files.

●        Role-based permissions that support separation of duties.

●        Exportable, auditable donor reports that can be reconciled to the underlying general ledger and documents.

Tax localisation remains important even where a grant is tax-exempt. Local supplier invoices, payroll obligations and statutory reporting may still require country-specific treatment. Confirm the applicable position with the relevant revenue authority and professional adviser before configuring tax rules.

Frequently Asked Questions

Can one NGO payment policy cover every African country?

It can set internal principles, such as separation of duties and monthly reconciliation. It cannot replace country-level checks for NGO registration, tax, foreign exchange, payment rules and record retention. Use the country regulator, revenue authority, central bank and donor agreement as the compliance baseline.

Is mobile money an adequate audit trail for beneficiary payments?

No. A transaction confirmation is only one record. An adequate trail also needs beneficiary validation, approved payment instructions, payment status, settlement reconciliation, exception handling and a grievance process.

How long should NGO grant records be retained?

Follow the donor agreement and applicable local requirements. For EU LIFE NGO operating grants, original accounting and tax records must be retained for five years after payment of the EU balance, subject to national rules on digitised originals.

When are daily timesheets necessary for donor-funded staff?

For EU LIFE NGO operating grants, daily time records are required when personnel are not assigned full-time to the grant. Confirm the specific donor agreement before applying this rule to another funding programme.

A payment process is ready for donor scrutiny when finance can select any reported cost and retrieve the grant code, approval, source document, execution record and reconciliation result. Request a Consultation to assess your NGO payment controls, grant structure and Odoo ERP implementation requirements.