NGO asset management and donor reporting
NGO asset management carries a requirement most organisations do not have: every asset has to be traceable to the grant that paid for it, sometimes years after the project closed. In the development sector the asset register is not primarily an accounting document. It is a compliance document, and the obligations attached to grant-funded equipment routinely outlast both the project that bought it and the staff who ran it.
In this article
NGO asset management: the short version
- The sector’s register is a compliance document first, an accounting document second.
- Capture funding source as a structured field at tagging time. Retrofitting it is the expensive path.
- Assets stay on the register of the organisation accountable to the funder, with the partner as custodian.
- Check grant terms on disposition before anything moves at close-out, not after.
- Physical numbers, structured funding data, named custody and annual verification survive staff turnover.
Why the sector’s problem is different
A commercial organisation asks what it owns and what that is worth. A development organisation has to answer a harder set of questions: which grant paid for this, what did that grant say about what happens to it at project end, and can we prove it still exists.
Three features of the sector make that difficult. Staff turnover is high, so institutional memory is short. Equipment moves between projects, partners and field locations. And the reporting obligation frequently survives the project, sometimes by years.
The asset register is the only thing in the organisation designed to outlast all three.
Capture funding source as a field, not a note
This is the single most important design decision for a development sector register, and it costs nothing at tagging time.
A structured field lets you filter by grant, project or funder in seconds. A note in free text means somebody reads three thousand records looking for a project code that was spelled four different ways.
Capture the grant or project reference, the funder, and the acquisition date, at asset level. If an asset was part-funded, record the basis. Retrofitting this later means reconstructing it from procurement files, which is precisely the exercise everyone is trying to avoid.
What funders typically ask for
| Requirement | What the register must hold |
|---|---|
| Individual identification | A unique number on the physical asset, not a category and a quantity. |
| Traceability to the grant | Funding source as a structured, filterable field. |
| Current location and holder | Location, department or partner, and a named custodian. |
| Evidence of verification | Date of last physical verification and who carried it out. |
| Condition | Current condition, updated at verification rather than at purchase. |
| Disposal accounting | Date, method, proceeds and the approval, including funder approval where required. |
Requirements vary by funder and by agreement, so read the specific terms rather than assuming a general standard. What does not vary much is that increasingly funders want evidence of verification rather than a self-declared list.
Equipment held by implementing partners
Assets transferred to or held by partners are where sector registers most often break down, because responsibility is split and neither side is quite sure who records what.
Three rules that resolve most of it. The asset stays on the register of the organisation accountable to the funder, regardless of who physically holds it. The partner is recorded as the custodian, with a named individual rather than an organisation name. And the sub-agreement states explicitly who verifies, how often, and what happens at agreement end.
Without that last clause, equipment quietly becomes the partner’s at the end of the project by default rather than by decision, which is exactly the outcome funders ask about.
Build a donor-compliant asset register
Tell us the asset types, locations and reporting requirements. We will recommend the register fields, tag materials and verification approach. Discuss an NGO asset register →
Project close-out
Close-out is where the obligations that were captured or not captured three years earlier become visible.
Produce the asset list for the grant. Filter by funding source, with cost, acquisition date, current location, custodian and condition.
Verify it physically. Not from the file. The gap between the file and reality is what close-out is meant to surface.
Check the grant terms on disposition. Options typically include transfer to a partner or government counterpart, transfer to another project of the same funder, sale with proceeds treated per the agreement, or retention. Which of these is available is decided by the agreement, not by convenience.
Get approval in writing before anything moves. Retrospective approval requests are the least comfortable conversation in project close-out.
Document what happened to every item, and retain it for the period the agreement specifies, which is often years after close.
Building a register that survives staff turnover
The sector’s defining constraint is that the people change. A register that depends on somebody remembering which vehicle belonged to which programme is a register with a fixed expiry date.
Four things make it survive. Every asset carries a physical number. Funding source is structured data. Custody is a named person, updated at every handover. And verification happens on a fixed cycle so that the gap between reality and record never grows beyond one year.
None of these are expensive. All four are much cheaper than reconstructing five years of equipment history for a funder who has asked a reasonable question.
Common questions about nGO asset management
What happens to equipment when a project ends?
It depends entirely on the grant agreement. Common outcomes are transfer to a counterpart, transfer to another project of the same funder, sale with the proceeds treated as the agreement directs, or retention. Read the terms rather than assuming.
Do we need a separate register per donor?
No, and it is a bad idea. One register with funding source as a field lets you produce a per-donor view in seconds while keeping a single organisational picture.
How do we handle assets bought with pooled funding?
Record the basis of the split and keep it consistent. Where funders have differing requirements, the strictest usually governs practical handling.
What if equipment was bought before we tagged anything?
Capture funding source during the tagging exercise from procurement records where they exist, and record where it could not be established. A documented gap is far better than a silent one.
Do funders accept a spreadsheet?
Some do, but the trend is towards individually identifiable assets with evidence of verification. A spreadsheet with no unique identifiers and no verification date increasingly does not satisfy the question being asked.
How often should we verify?
Annually at minimum, and at every project close-out regardless of when the last one was. Field locations with high turnover justify twice a year.
Build the grant field into NGO asset management from the first asset rather than adding it during a donor audit. Retrofitting funding source across a register is one of the slowest corrections there is.
Continue with the right next guide
Build a donor-compliant asset register
Tell us the asset types, locations and reporting requirements. We will recommend the register fields, tag materials and verification approach.