NGO Grant and Programme Management Software: Why Nobody Can Say Whether an Award Is On Budget

Why programme, finance and monitoring data never meet at the award

Quarter end at a regional office. Five country offices have submitted their contributions to a consolidated report. The indicator data sits in DevResults, where it was entered by monitoring officers against a logframe. The budget versus actual comes out of the finance system in the functional currency of the head office, while three of the country budgets were agreed with the donor in euros and spent in local currency at whatever rate applied on the day. Two partner subawards have submitted liquidation packages as scanned PDFs, one of which arrived four days late and contains a procurement above the competitive bidding threshold with a single quotation attached. The awards manager is trying to answer one question from the country director: is this award on budget and on target. Nobody can answer it before Thursday.

The specialist tools in this sector are honest about their scope. DevResults and ActivityInfo are built around indicators, results frameworks and geographic disaggregation, and they do that well. TolaData covers a similar space with a lighter footprint. What all of them share is that they are monitoring and results systems that touch finance lightly, if at all. Your accounting package, whether that is a Dynamics deployment, Serenic, Unit4 or something older, holds the money in a chart of accounts that was designed for statutory reporting, not for award compliance. So the join between the results and the money happens in Excel, in a template that one person maintains, every quarter, in three currencies.

Problem 1: donor rules are per award, not per organisation

Every organisation writes one procurement policy and then discovers that this award requires three quotations above one threshold while that one requires a different threshold and a different documentation set. One donor allows a fixed indirect rate, another negotiates it, a third disallows certain cost categories entirely. Cost share obligations apply to some awards and not others. Prior approval requirements for budget realignment differ by funder and sometimes by agreement clause.

No standard project management tool encodes rules at the award level, because no standard project management tool has ever needed to. So the rules live in the award agreement PDF, in the grants manager's head, and in a compliance matrix that was accurate when it was written. The people who most need those rules, meaning the country office staff raising a purchase request, never see them at the moment of decision.

What a custom build does: the award is the configuration object. Procurement thresholds, allowable cost categories, prior approval triggers, reporting deadlines and cost share obligations are attributes of the award, and they are enforced in the workflow where the transaction happens. A purchase request over the threshold for that award cannot proceed without the required quotations attached. Compliance stops being a document people are trained on once and becomes a constraint the system applies. This is the single highest value thing to build in this category and it is the one nobody buys.

Problem 2: the money exists in three currencies and the variance is not real

A budget is agreed with a donor in one currency. The country office spends in another. The organisation reports in a third. When the exchange rate moves, a line that is on budget in local currency shows as an overspend in donor currency, or the reverse, and the programme manager spends an afternoon proving a variance is a rate movement rather than a control failure.

Finance systems handle multi currency for statutory purposes, which is a different problem. They revalue at period end against a functional currency. What an award needs is simultaneous truth: the same expenditure viewed in donor currency at the agreed rate for reporting, in local currency for the field team's decision making, and in functional currency for the statutory accounts, with the difference identified as rate movement rather than buried.

What a custom build does: expenditure carries the original transaction currency and amount, the rate applied, and the rate basis, so any view can be reconstructed exactly. Budget versus actual is presented in the currency the viewer needs, with rate effect shown as its own line rather than as unexplained variance. This is not glamorous engineering and it is the reason your country directors will actually use the system.

Problem 3: subawards need their own compliance lifecycle, and yours does not cover them

A partner subaward is not a supplier invoice. Under United States federal award rules, pass through entities carry defined responsibilities for subrecipient risk assessment and monitoring, and equivalent expectations exist under other major funders. In practice this means a pre-award capacity assessment, a risk rating, a monitoring plan proportional to that rating, spot checks, advance and liquidation cycles, and evidence that you did all of it.

Project management tools model a partner as a stakeholder. Finance systems model them as a vendor. Neither models a subrecipient with a risk rating that drives a monitoring frequency, an advance balance that must be liquidated before the next tranche, and a document set that an auditor will ask to see. So the register lives in Excel and the programme team approves the next advance without checking it, because checking it takes twenty minutes and the partner is waiting.

What a custom build does: the subaward has a lifecycle with capacity assessment, risk rating, monitoring schedule, advance ledger and liquidation review. The next advance is blocked until the previous liquidation is reviewed and the outstanding balance is within policy. Monitoring visits generate findings with corrective actions and due dates that escalate. When an auditor asks how you monitored a partner, you produce the record instead of the intention.

Problem 4: the audit finding is nearly always procurement documentation

Ask any grants director what their last audit finding was about and the answer is usually procurement. Not fraud. Documentation. A purchase that needed three quotations has two on file. A sole source justification was verbal. A vendor was selected before the evaluation was documented. A payment was made against a proforma rather than a compliant invoice. The purchase was legitimate, the price was reasonable, and the cost gets disallowed anyway because the file cannot prove it.

What a custom build does: procurement is a workflow inside the system with the award's threshold rules applied, so the required evidence is collected at the point of the transaction rather than reconstructed later. Quotation documents, the evaluation record, the approval chain with named approvers and timestamps, the purchase order and the invoice all live against one procurement record linked to the expenditure and the award. Second, this is where machine assistance earns its place: liquidation packages and invoices arrive as scanned PDFs in every layout imaginable, and a document extraction pass turns them into draft expenditure lines with vendor, date, amount, currency and suggested budget line for a finance officer to confirm. In our builds that removes most of the manual keying from partner liquidation, which is otherwise a week of somebody's month.

Problem 5: field offices have poor connectivity and real approval authority

A system that requires a stable connection to approve a purchase request will be bypassed within a month, and the bypass is a WhatsApp message followed by retroactive data entry, which is worse than no system. Country offices operate with intermittent connectivity, power interruptions and staff who travel to field sites for days.

What a custom build does: request creation, evidence attachment and approvals queue locally and sync when connectivity returns, with a clear conflict rule when two approvals occur out of order. Approval authority is delegated with limits by role, award and amount, and delegation during travel is a recorded act with an expiry rather than a shared password. That last point sounds administrative and it is exactly what an auditor tests.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, here is the honest shape. A first release covering award records with donor rules as enforced configuration, multi currency budget versus actual synchronised with your accounting system, indicator targets tied to the results framework, and a subaward register with risk rating and monitoring status runs $85,000 to $170,000 and ships in 14 to 20 weeks. A full platform adding procurement workflow with threshold enforcement, partner advances and liquidations with document extraction, offline capable approvals, cost share tracking and donor specific report generation runs $220,000 to $550,000 phased over 9 to 14 months.

What pushes cost up specifically here: the number of distinct funders, because each one's rules and report formats are separate work and there is no shortcut. Integration with your accounting system, which varies enormously in difficulty depending on whether it exposes a usable interface. Number of country offices and whether they operate different charts of accounts. Offline capability for approvals. And whether you intend to replace or integrate with an existing results system, since integrating with DevResults or ActivityInfo is usually cheaper and better than replacing it.

What keeps cost down: keeping your results and indicator system, keeping your accounting system, and building the award compliance and consolidation layer between them. That is our standard recommendation and it removes both the riskiest engineering and the most painful data migration.

Build versus buy, and when buying is the right call

Buy if you run fewer than about six concurrent awards in one or two countries with few or no subawards. DevResults or ActivityInfo for results, a competent finance system for money, and a disciplined grants manager will carry you, and a custom build at that scale is an overhead you would come to resent. TolaData is worth a look if budget is tight and your indicator work is straightforward.

Build when two or more of these are true. You have more than 15 concurrent awards across several country offices. Your funders impose materially different procurement and cost rules and staff cannot see those rules at the point of decision. You pass funds to partners and your subrecipient monitoring evidence would not survive scrutiny. Your award burn rate is always weeks stale. Or you have already taken an audit finding on procurement or subaward monitoring.

Our position, stated plainly: build the compliance layer, not another dashboard. The organisations in this sector that have wasted the most money are the ones that bought or built a beautiful indicator visualisation while their procurement documentation stayed in a shared drive. The dashboard does not protect the award. Enforced rules at the point of transaction do.

How to choose a developer for NGO programme and grant software

Ask them to model the award before you sign anything. A developer who has done this will draw an award with donor rules as configuration, a budget in multiple currencies with a rate basis, an expenditure with its original transaction currency, a subaward with a risk rating driving a monitoring schedule, and a procurement record with threshold logic. A developer who draws projects and tasks has built a project management tool and will hand you a prettier version of the problem you have.

Ask how they would show a variance that is caused by exchange rate movement rather than overspending. If they have not thought about it, your country directors will not trust the numbers and the system will be ignored.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the infrastructure accounts and the right to hire anyone else. At Digital Heroes the client owns the code from the first commit. In a sector where a single restricted award funds a system build, a vendor holding your repository puts your compliance infrastructure inside someone else's commercial decisions.