Before signing a funding agreement, one question conditions everything else: will this organisation manage the funds by the rules? Donors and fund managers answer it through ex ante financial management capacity assessment — micro-assessments, due diligence, organisational analysis grids. Done well, it matches controls to actual risk and turns detected weaknesses into a support plan. Done poorly, it mechanically excludes the local organisations that the localisation agenda precisely asks to fund.
This article is written for those who appraise: programme officers at donors, partnership managers of support funds, application assessors. It details the six domains of an assessment grid, the real warning signs (and the false ones), and how to translate the assessment into funding modalities — with a look at what a system like Abvius changes in the partner-risk equation.
CSO financial management capacity assessment: the funder's grid
Reading time: ~6 min
- Why assess before funding
- The six domains of the assessment grid
- Real warning signs, false signals
- From assessment to mitigation plan
- The anti-localisation bias, and how to avoid it
- What a management system changes in the risk equation
- Mini FAQ
Why assess before funding
Ex ante assessment is not a defensive formality: it is the tool that matches controls to risk. That is the logic of harmonised micro-assessment approaches: the assessed risk level determines disbursement modalities (advances or reimbursements), verification frequency and support intensity. It is also the logic of the European pillar assessment: check the systems before entrusting the funds. Without assessment, two symmetrical errors: over-controlling solid partners (costly for everyone), or discovering mid-project that an organisation structurally could not meet the requirements. A scope note: we have published a guide to partner due diligence written from the viewpoint of an NGO selecting its implementing partners; this article takes the other seat — the funder's.
The six domains of the assessment grid
1. Governance and accountability. Bodies that actually function (minutes, frequency), separation between governance and management, existence and application of key policies (conflicts of interest, anti-fraud, safeguarding).
2. Accounting and systems. Books that are kept, current, on a tool that guarantees the audit trail; analytical allocation able to isolate expenditure by project and by donor; financial statements produced and, depending on size, audited. This is the most predictive domain: an organisation that cannot isolate a project's expenditure will not be able to justify it.
3. Internal control and treasury. Segregation of duties (who commits, who pays, who records), dual bank signatures, monthly bank reconciliations, framed cash management.
4. Procurement. A manual with realistic thresholds, applied: documented competition, complete procurement files.
5. Human resources and payroll. Compliant contracts, documented payroll, timesheets where staff work across several grants.
6. Grant management track record. History of grants managed, reports delivered on time, past audit findings and — above all — how they were addressed.
For each domain: rate (four levels work well), document findings with documents seen (not statements heard), and note gaps between written procedures and observed practice.
Real warning signs, false signals
Real signals: books reconstructed after the fact for the assessment; inability to produce a past project's ledger; non-existent bank reconciliations; authorisation and payment concentrated in one person with no compensating control; past reports systematically late; audit findings repeated identically year after year — the signal is not the finding, it is its repetition.
False signals, which wrongly exclude: small size (a five-person team with good reflexes is less risky than a large disorganised structure); organisational youth; the absence of a thick manual (three applied pages beat a hundred decorative ones); spreadsheet-based accounting — that is an equippable fragility, not an incapacity: it calls for an equipment plan, not a rejection. The experienced assessor distinguishes what stems from intent and practice (hard to change) from what stems from tooling (fundable and quick to change).
From assessment to mitigation plan
The product of a good assessment is not a binary verdict but a risk-response pair: adapted disbursement modalities (shorter tranches, smaller advances at start-up widening with confidence), progressive ceilings, reinforced reporting on the first quarters, targeted verifications on weak domains, and a budgeted support component — accounting equipment, help setting up procedures, side-by-side support on the first deadlines (see our article on strengthening CSO financial capacity). The assessment must be revisited: a supported CSO that meets its first three deadlines has objectively changed risk profile, and its modalities should follow.
The anti-localisation bias, and how to avoid it
A grid designed in the image of international NGOs — requiring their manuals, their org charts, their certifications — mechanically sidelines local organisations, contradicting the localisation commitments most donors have made. Three correctives: assess functions (are payments controlled?) rather than forms (is there an 80-page manual?); treat equippable weaknesses as lines of the support plan, not grounds for exclusion; and size requirements to the amount entrusted — you don't demand a UN agency's systems for a €30,000 grant.
What a management system changes in the risk equation
The real cost of a risky partner is not in the grant: it is in supervision — the follow-ups, the re-keying, the verifications, the reports redone. That is the equation a shared management system changes. A CSO equipped with a tool like Abvius enters its expenses with their supporting documents in a framework that applies the grant's eligibility rules, keeps its per-donor analytical allocation natively, and produces reports reconciled with its accounts — while the funder or fund manager sees progress continuously instead of discovering it at deadlines. For the appraiser, this opens a mitigation option often more effective than tightening controls: equip the partner, and structurally lower the supervision cost of the whole portfolio.
Mini FAQ
Who should run the assessment: the internal team or a firm?
Both are practised. A firm brings independence and standardisation at volume; the internal team brings context knowledge and continuity with the support that follows. What matters is one grid for all and documented findings.
Should the assessment be shared with the assessed CSO?
Yes — that is what makes it useful: findings shared and discussed become the basis of the support plan. A confidential assessment produces only distrust.
How often should we reassess?
At each significant new funding cycle, and continuously through management signals (reporting delays, quality of justifications). An assessment frozen for three years is obsolete.
Can a CSO without computerised accounting be funded?
Yes, with adapted modalities and an equipment plan in the agreement — precisely the kind of weakness that is fixed quickly and durably.
Measure the risk, then equip it: tell us about your partner portfolio.