"Please send us your supporting documents." Six words that trigger, depending on the nonprofit receiving them, either a ten-minute export or three weeks of archival panic. Between the funder who doesn't dare ask for anything and the one who demands a photocopy of every receipt, there is a reasonable standard, graduated by amount, that this guide lays out in detail: what to ask for, in what format, within what deadline — and which red flags signal that something is off.

Supporting Documents and Financial Reports: A Checklist of What a Funder Can Ask a Nonprofit

Reading time: ~6 min

Table of Contents

1. The foundation: the financial report and its template
2. Supporting documents: what, when, and how deep
3. The checklist, graduated by amount
4. Deadlines, format, and the default clause
5. Reading a report: red flags
6. The decisive factor: the beneficiary's tooling
7. Mini FAQ

1. The foundation: the financial report and its template

For earmarked public grants, the financial report is a legal requirement (due within six months of the end of the implementation period) governed by a reference form — the Cerfa 15059 (the standard French administrative financial-report form) — structured around three parts: a table of the action's costs and revenues compared against the projected budget, an explanatory annex covering variances, and a qualitative report. Private funders have every reason to draw on this proven structure rather than inventing their own: actual spending by line item versus the projected budget, an explanation of significant variances (beyond 10–15% per line item), valued in-kind contributions, and a narrative of what was achieved. Supplying this template as early as the grant agreement stage substantially improves the quality of what comes back.

2. Supporting documents: what, when, and how deep

There are three levels of depth, to be calibrated by amount and risk: the expense list (the project's general ledger or an itemized statement: date, supplier, nature, amount, budget line) — this is the backbone, without which no control is possible; a sample of supporting documents: invoices and proof of payment for a selection of expenses (the largest ones plus a random draw), the best effort-to-assurance ratio; the full set of supporting documents: reserved for large grants, high-risk contexts, or as a follow-up to anomalies — at that point, it's already an audit.

Two clarifications that head off misunderstandings: an invoice without proof of payment justifies nothing (require both for your sample); and for staff costs charged to the project, ask for the allocation key (time spent) rather than pay slips — more useful, and less intrusive.

3. The checklist, graduated by amount

4. Deadlines, format, and the default clause

Three parameters to set in the grant agreement. The deadline: six months after the action ends is the standard; plan for a midpoint check-in on any project running longer than twelve months. The format: native documents (an export from the accounting system, PDFs of supporting documents) — reject re-keyed spreadsheets with no link back to the accounting records, a major source of errors and unintentional window-dressing. The default clause: a missing or insufficient report means suspension of the remaining balance and of future funding, spelled out in writing. Without a stated consequence, the deadline doesn't really exist.

5. Reading a report: red flags

Reading a financial report is an exercise in structured common sense: expenses that match the projected budget down to the last cent (real life has variances); "miscellaneous" or "overhead" line items that are abnormally inflated; recurring suppliers that are never documented; the inability to produce a specific document from the list; mismatches between the narrative and the figures; and deadlines that keep slipping with every follow-up. None of these signals proves fraud on its own — each one warrants a written, dated, and archived question.

6. The decisive factor: the beneficiary's tooling

All of this machinery rests on a capability the funder doesn't control: the beneficiary's ability to produce accurate documentation quickly. It's mechanical: a nonprofit that manages its projects on spreadsheets has to rebuild every report by hand — delays, errors, and a lack of verifiability follow. A nonprofit equipped with a platform like Abvius already has everything in place: every expense is linked to the project and the funder as soon as it's entered, every supporting document is filed in the project's audit trail, and suppliers are screened against sanctions lists. Your complete checklist — expense statement, supporting documents, screening certificate — exports in minutes, in native formats.

The practical takeaway for funders: ask about tooling at the appraisal stage ("what do you use to manage your projects? how long does it take you to produce an expense statement by funder?"). And consider the virtuous version of this requirement: the same data that fills out your checklist also feeds your own activity report and communications — quantified results, documented fieldwork. A traceable beneficiary doesn't just buy you security: it supplies your raw material for storytelling.

7. Mini FAQ

Can we ask for the nonprofit's bank statements?

That's disproportionate as a routine matter (and not very useful: a statement doesn't show project allocation). The expense list plus a sample of invoices and proof of payment offers stronger assurance for less intrusion. Bank statements belong in an audit, triggered by an anomaly.

Must supporting documents be kept, and for how long?

Require the beneficiary to retain them for ten years (the standard accounting retention period) and to make them available on request. On your side, keep the report and the sample you were sent — that's your due-diligence file.

How should in-kind contributions be handled in the report?

Have them shown at their valued amount (the Cerfa template provides for this): they illustrate the project's real economics and highlight the nonprofit's own contribution — including skills-based volunteering from other partners.

In summary

Asking for supporting documents is neither distrust nor a formality: it's a graduated checklist — Cerfa-style template, expense list, sample of supporting documents, annual accounts depending on the amount — backed by realistic deadlines and a default clause. How well it works depends on a single variable: the beneficiary's tooling. Funding nonprofits that are natively traceable turns the chore of justification into an export — and turns your oversight into communications material. To go further: how to track fund use, auditing a beneficiary nonprofit, and third-party screening. To see what Abvius enables on the nonprofit side, contact our team via abvius.org.