You selected the right partners, signed the agreements, notified the grants. And yet, six months in, a third of your portfolio has spent barely 15 % of its budget. One CSO writes to say it has suspended activities for lack of cash, waiting to be reimbursed for a quarter it has already committed. Another pre-financed the work from its own reserves and has just sent you a rushed financial report, put together at the last minute by a part-time accountant. Meanwhile your finance department asks why disbursements are lagging so far behind the plan, and your upstream donor is questioning the facility''s absorption rate. The problem is neither your selection process nor your partners'' commitment: it is the disbursement schedule you imposed on them.
The disbursement schedule is probably the most structuring and least debated clause in your agreements. It determines who carries the cash-flow risk, which organisations can realistically apply to your calls, how fast your funds reach the field, and how much time your teams will spend processing payment requests. This article takes the funder''s seat — the organisation that pays out, supervises and reports to an upstream donor — to examine how to build a disbursement schedule that protects your exposure without mechanically transferring the cash-flow burden to the least capitalised organisations. At Abvius we build a Finance, Operations and MEAL ERP for international solidarity organisations and their funders, and we consistently observe that disbursement is treated as an administrative formality when it is in fact the single biggest lever on portfolio quality.
Disbursement schedule: the main management tool in your portfolio
Reading time: ~16 min
- Why the disbursement schedule decides everything else
- The four disbursement models and who carries what
- The hidden cost of reimbursement against receipts: silent exclusion
- Sizing advances: a risk decision, not a favour
- Disbursing fast without disbursing blind
- Abvius: disburse on data, not on PDFs
- Five steps to redesign your disbursement schedule
- Mini FAQ
1. Why the disbursement schedule decides everything else
In most CSO support facilities, the disbursement schedule is drafted once, copied from one agreement to the next, and rarely revisited. It is treated as a technical clause. In practice it produces four major effects on your portfolio, three of which are invisible from your dashboard.
It shapes the composition of your portfolio upstream. A schedule based on reimbursing expenditure already paid assumes the partner holds enough of its own cash to pre-finance several months of activity. That condition rules out any organisation without reserves — which, very often, means precisely the local actors your mandate asks you to fund directly. The trade-off happens before appraisal, unrecorded: some CSOs simply do not apply, because they know they could not keep up.
It sets the real pace of your programmes. A six-week gap between a tranche request and the actual payment rarely translates into six weeks of delay: in the field, a demobilised team, a supplier who refuses to deliver, or a missed agricultural season cost far more. The absorption rate you observe at year end is often the mechanical reflection of your own internal processing times.
It determines the quality of the data you receive. A partner paid only after its receipts are validated has a strong incentive to produce quickly rather than accurately. Financial reports arrive ahead of the real accounting close, documents are scanned in haste, cost allocations are approximate. You discover the discrepancies at the control stage, six months later.
It concentrates your teams'' workload. Processing forty annual tranche requests, each with a heterogeneous financial report to check line by line, absorbs your grant managers well beyond what a facility of that size should require. The disbursement schedule is therefore also a decision about your own staffing.
In other words, the question is not "how often should we pay" but "how much cash-flow risk are we prepared to carry, and under what monitoring conditions". That is an explicit trade-off, and it deserves to be documented in your funding policy alongside your eligibility rules.
2. The four disbursement models and who carries what
CSO support facilities use, in varying combinations, four broad models. Each shifts risk and administrative burden to a different point in the contractual cascade.
| Model | Who carries the cash | Funder exposure | Supervision burden | Relevant when |
|---|---|---|---|---|
| Single advance at signature | The funder | Maximum, for the whole period | Low in administration, high in ex-post control | Small amounts, known partners, emergency contexts |
| Fixed periodic tranches (quarterly, half-yearly) | Shared, depending on the first tranche | Limited to one tranche | Moderate, predictable | Homogeneous portfolios, steady activities |
| Tranches triggered by a spending threshold | Shared, calibrated on the actual pace | Limited and correlated to progress | High if monitoring is manual, low if data flows continuously | Heterogeneous portfolios, variable activity rhythms |
| Reimbursement against receipts | The partner, entirely | Close to zero | Very high: document-by-document checking before every payment | Capitalised partners only |
Threshold-based disbursement: the most robust compromise
The threshold model — releasing the next tranche once the partner has justified spending a set share of the previous one, typically 70 to 80 % — is the one that best aligns funder exposure with actual progress. It avoids two symmetrical pitfalls: idle cash sitting in the account of a partner whose project has slipped, and the strangulation of a partner spending faster than planned.
Its drawback is familiar to your grant managers: it requires knowing the spending rate in near real time. As long as that information travels via a PDF financial report, re-keyed into a monitoring spreadsheet and reconciled against payments made, the threshold model becomes heavier than fixed tranches. That is why many facilities abandon it — not as a risk-management choice, but as a tooling constraint.
This matters: the disbursement schedule cannot be separated from the question of how information flows back to you. We return to it below, and it connects directly to grant portfolio monitoring.
3. The hidden cost of reimbursement against receipts: silent exclusion
Reimbursement against receipts has an apparent elegance: the funder pays only against proven expenditure, exposure is nil, the audit trail is impeccable. It is also the model that causes the most invisible damage in a portfolio geared towards localisation.
A national CSO with three months of reserves can pre-finance a quarter of activity. A community organisation with ten staff, no reserves and no access to bank credit cannot. It has three options: not to apply, to accept and risk insolvency, or to go through a lead NGO that will pre-finance on its behalf — taking a share of indirect costs along the way. In all three cases, your direct local funding objective is neutralised by a payment clause.
It is essential not to misdiagnose this. The problem is not that these organisations are less reliable or less rigorous. Pre-financing capacity measures historical capitalisation, not management quality. Many local organisations keep impeccable accounts with limited means, and many well-capitalised international structures produce mediocre financial reports. Conflating the two lets a balance-sheet criterion stand in for a competence criterion — that is an appraisal error, not prudence.
Weak tooling, by contrast, is fundable: it is corrected with a budget line, support and a shared system. A lack of cash cannot be corrected within an agreement — unless you decide to carry it yourself, which is exactly what a well-designed disbursement schedule is for. We develop this reasoning from the selection angle in our article on appraising calls for proposals without mechanical exclusion, and from the capability angle in the one on strengthening CSO financial capacity.
What pre-financing really costs the system
- A real but unrecognised financial cost. When a partner pre-finances on an overdraft or a loan, it bears interest charges that most eligibility rules classify as ineligible. The cost exists; it is simply invisible in your accounts.
- A premium on intermediaries. The contractual cascade gains a layer every time a structure needs a pre-financier, with indirect costs stacking at each level.
- Distorted activity planning. Partners push heavy spending — equipment, training, grouped travel — towards the end of the agreement, when cash has been rebuilt, concentrating ineligibility risk at the worst possible moment.
- Degraded reporting quality. A financial report produced under cash-flow pressure is a report produced in a hurry.
4. Sizing advances: a risk decision, not a favour
Many facilities treat the advance as an exception negotiated case by case, often late in appraisal and without method. It is far more robust to treat it as a parameter of the agreement, calibrated on two objective variables: the cash requirement of the activity plan, and the risk profile emerging from your financial management capacity assessment.
Size the advance on a cash-flow plan, not a flat percentage
A uniform 30 % advance applied across the portfolio is almost always wrong: too much for a project whose spending ramps up slowly, far too little for one that must buy inputs in month one. Asking for a simple forecast cash-flow plan — eight to twelve lines, monthly or quarterly — at appraisal changes the conversation. It immediately reveals spending peaks, allows tranches to be matched to real needs, and is an excellent indicator of the partner''s management maturity.
Match the advance level to the risk profile
A partner assessed as high risk does not necessarily need a smaller advance: it needs an advance paired with tighter monitoring. Mechanically cutting the advance amounts to penalising the partner for a weakness you nonetheless agreed to fund.
| Dimension | Tighter-control approach | Equipped-partner approach |
|---|---|---|
| High-risk partner | Reduced advance, more frequent tranches, receipts required before each payment | Advance sized on real need, continuous expenditure reporting in a shared system, targeted spot check |
| Effect on partner cash flow | Permanent strain, activities slowed | Enough cash to execute the plan |
| Burden on your teams | Grows linearly with the number of agreements | Broadly constant regardless of portfolio size |
| Anomaly detection | At control stage, usually after the spending | At data entry, before the next payment |
| Effect on partner capacity | None, sometimes negative | Cumulative: practices acquired serve future grants |
The difference fits in one sentence: in the first case you buy security by degrading execution; in the second you buy visibility while preserving execution. Risk sharing is covered more broadly in our article on partner risk management across the portfolio.
5. Disbursing fast without disbursing blind
Speeding up disbursement without weakening assurance means moving the control: less documentary verification before payment, more continuous visibility and targeted checking afterwards.
Shorten your own lead time before blaming the partner
In most facilities we observe, the time between receiving a complete tranche request and the actual transfer runs between four and ten weeks. It almost always breaks down the same way: a few days waiting for assignment to a grant manager, one to three weeks of verification, a round trip for missing documents, then your validation circuit and your finance department''s payment run. Timing each of those steps across your last twenty requests is the highest-return exercise you can run this quarter. It usually shows that half the delay has nothing to do with the quality of the partner''s file.
Separate eligibility control from payment control
Checking every receipt for eligibility before every payment is a default choice that is rarely re-examined. A proportionate assurance system combines instead: eligibility rules applied automatically at data entry, a budget consistency check at the tranche request, and spot checks on a risk-based sample. Payment no longer waits for exhaustive verification; verification becomes continuous and targeted.
Harmonise the tranche request format
If every partner sends its expenditure statement in a different format, processing time is incompressible and consolidation stays manual. Harmonising the template — and better, receiving structured data rather than documents — is covered in detail in our guide to harmonising partner reporting. It is the technical prerequisite for any durable reduction in lead times.
Write the blocking scenarios explicitly
A complete disbursement schedule also states what happens when things stall: under what conditions a tranche is suspended, what level of decision is required, what remediation period the partner is given, and how disbursement resumes. Without these clauses, every difficulty turns into an improvised negotiation, generally to the disadvantage of the most fragile partner.
6. Abvius: disburse on data, not on PDFs
Most of the difficulties described above share one root cause: between a partner''s expenditure and the information you have to decide on a payment, there is a PDF report, a spreadsheet and several weeks. Abvius removes that interval.
A monitoring dashboard for funders. Each funded CSO or partner works in its own space: its budget, its expenditure with supporting documents attached, the progress of its activities. On your side, you get a consolidated, real-time view of your portfolio. Concretely, the spending rate that triggers the next tranche is no longer a figure someone declares and you re-key: it is a figure you read. A tranche request stops being a file to process and becomes a decision to take on information you already hold.
Capacity strengthening for the NGOs you support. Abvius equips the partners, not just the funder. Your upstream donor''s eligibility rules are configured once and applied across the whole contractual cascade, down to the sub-recipient: a non-compliant expense is flagged at the moment of entry, in the field, not six months later during a control. Consolidated reporting is built without re-keying, and the audit trail stays continuous down to partner level, document by document.
The economic consequence is the interesting one for a fund manager: the cost of supervision falls structurally, because control and capacity strengthening stop being two separate activities. The tool that gives you visibility is the same one that structures the partner''s management. You no longer arbitrate between funding fast and controlling seriously — and you can open your facilities to organisations that reimbursement against receipts would have excluded. This facility logic is detailed in our article on managing cascading sub-grants.
7. Five steps to redesign your disbursement schedule
- Measure your real lead time, step by step. Take the last twenty tranche requests processed and time each segment: receipt, assignment, verification, missing documents, validation, transfer. Identify the longest segment. In most cases it is internal.
- Map the pre-financing capacity across your portfolio. For each partner, estimate how many months of activity it can carry on its own funds. Cross-reference with the observed execution rate. Where a correlation appears, it says something about your schedule, not about your partners.
- Replace the flat advance rate with a cash-flow plan. Add a simple monthly or quarterly cash-flow plan to your appraisal file. Set the advance amount and tranche rhythm from it. It is also an excellent indicator of management maturity at appraisal.
- Move control upstream of the spending. Configure the upstream donor''s eligibility rules inside the system your partners use, rather than checking them document by document after the fact. Reserve in-depth verification for a risk-based sample.
- Write the suspension and resumption clauses. Define trigger thresholds, remediation periods and required decision levels in advance. Share them with partners at contracting, not during the crisis.
None of these steps requires renegotiating your current agreements. They can be introduced in the next generation of calls and tested on a subset of the portfolio before being rolled out.
8. Mini FAQ
Does paying a larger advance mechanically increase our risk?
It increases your nominal exposure, not necessarily your risk of loss. Risk depends on the probability that funds are misused and on your ability to detect it in time. A large advance paid to a partner whose expenditure you follow continuously, document by document, is less risky than a modest advance paid to a partner you will hear nothing from for six months. Exposure is managed through visibility as much as through amount.
What should we do with a partner who consistently spends more slowly than planned?
Find the cause before adjusting the schedule. Slow execution may come from impossible pre-financing, an administrative delay on your side, a security context, or an unrealistic activity plan built during appraisal. The remedies are opposites: cutting the next tranche of a partner blocked by a cash problem will make the delay worse. A short quarterly review, grounded in actual spending data, settles the question quickly.
Our disbursement rules are imposed by our upstream donor. How much room do we have?
More than it appears. The schedule your donor applies to your agreement does not oblige you to replicate the same conditions downstream. An operator can carry, on its own cash or a dedicated working capital fund, a gap between what it receives and what it pays out — this is in fact one of the expected value-adds of a delegated fund manager. The binding constraint is on expenditure eligibility and the audit trail, not on the rhythm of payments to partners.
How do we justify a large advance to our own auditors?
Through traceability, not through the amount. An auditor seeks assurance that funds were used in line with the agreement and that spending is documented. An advance backed by a reasoned cash-flow plan, continuous spending monitoring and an accessible audit trail down to partner level defends itself better than a series of poorly documented small payments. We develop this in our article on the digital audit trail.
Conclusion
The disbursement schedule is not an administrative clause: it is the decision that allocates cash-flow risk between you and your partners, and that consequently determines who can apply to your facilities, how fast your programmes execute, and what quality of data you will receive. Reimbursement against receipts offers real accounting security at the price of silently excluding the least capitalised organisations — the very ones the localisation agenda asks you to fund directly. Threshold-based disbursement is the best compromise, on one condition: continuous visibility over the real pace of spending. That is exactly what a system shared between funder and partners provides, where control and capacity strengthening stop being two separate budget lines. Start by measuring your own internal lead times: that is usually where half the problem sits.
Further reading: Grant portfolio monitoring: building your dashboard · CSO support facility: managing cascading sub-grants · Partner risk management and risk sharing · Indirect costs of local partners in the cascade · Localisation: funding local NGOs directly
Managing a CSO support facility or a portfolio of agreements, and want to look at how a shared space with your partners would change your disbursement schedule? Talk to our team.