Grant expenses need more than receipts. Finance teams should retain a complete evidence chain that shows why a cost was necessary, who approved it, how procurement requirements were met, what was received and how payment was made.
Think in evidence chains
A reviewer should be able to start with a reported cost and trace it back to the approved budget, authorization, procurement record, invoice or claim, proof of receipt, accounting entry and payment. A receipt on its own may not explain the business purpose or approval.
Match evidence to the cost type
Different expenses need different records. Payroll may require employment records, payroll schedules, time-allocation evidence and proof of payment. Travel may require prior approval, itinerary, ticket, accommodation invoice, per diem calculation and advance reconciliation. Procurement may need quotations, evaluation records, purchase orders, delivery notes and payment evidence.
Keep approvals with the transaction
Where approval is required, retain it in a form that can be traced later. An email approval, workflow record or signed form should identify the person, date, amount and purpose. Do not rely on staff memory during an audit.
Use consistent reference numbers
Voucher numbers, purchase-order numbers or transaction IDs help connect documents across accounting, procurement and banking systems. Consistency makes sample testing faster and reduces the chance that evidence is misplaced.
Test files before reporting
Each month or quarter, sample a few transactions and ask whether the entire chain can be located. Missing documents are easier to recover while staff and suppliers still remember the transaction. The donor audit-trail guide explains how these records connect from budget to bank payment.
Practical supporting-document checklist
- Approved budget line.
- Request and authorization.
- Procurement evidence where required.
- Invoice, receipt or claim.
- Proof goods or services were received.
- Ledger entry.
- Proof of payment.
- Any donor-specific evidence.
What to do next
Use the Grant Evidence Inventory to identify missing documents and unsupported claims before reporting or audit.
For funding opportunities and practical grant guidance, subscribe to Africads Grant News.
Example: what a complete procurement file may contain
For a grant-funded laptop purchase, the evidence could include the approved budget, purchase request, quotations, evaluation or selection record, purchase order, supplier invoice, delivery note, asset-register entry and proof of bank payment. If an exception was used, the written justification and approval should also be present.
Do not create evidence after the fact
Missing records should be investigated, but staff should not fabricate approvals, quotations or signatures later to make a file look complete. If documentation is genuinely missing, record the gap, recover what can legitimately be recovered and strengthen the process for future transactions.
Build evidence checks into payment approval
One practical control is to require the essential supporting documents before a payment is released. The exact checklist can differ by transaction type. This reduces the amount of chasing finance teams must do months later.
For recurring cost types such as travel, payroll and procurement, create short document checklists that staff can use before submitting a payment request.
Retain documents for the required period
Donors and local regulations may require records to be retained for a specified number of years after the award ends. Document the applicable retention period and make sure digital and physical files remain readable and accessible. Closing a project should not mean deleting the evidence that supports it.
Where original paper documents are required, define who holds them and how scanned copies are linked to the accounting record. A digital copy can speed retrieval, but it should not lead staff to discard originals when the donor, auditor or local rules still require them.
Make document completeness part of routine finance review. A transaction should not be considered fully closed merely because payment has been made. The file should also contain the evidence needed to explain and defend the cost later.
Frequently Asked Questions
What supporting documents are needed for grant expenses?
The exact package depends on the transaction, but common records include approvals, contracts, invoices, receipts, delivery evidence, payroll documents, travel records and proof of payment.
Is a receipt alone enough?
Often not. A receipt may show payment but not the business purpose, approval, procurement process or connection to the grant budget.
Should documents be stored electronically?
Electronic storage can work well if files are complete, secure, backed up, searchable and retained for the period required by the donor and law.
Who should check document completeness?
The staff member processing the transaction should assemble the file, while finance or another designated reviewer checks that the evidence meets policy and donor requirements.
What should happen when evidence is missing?
Record the gap, seek replacement evidence or clarification, and avoid treating the cost as fully supported until the organization can defend it under the applicable rules.
Conclusion
Supporting documents should allow a reviewer to understand what was bought, why it was needed, who approved it, how it was paid and why it was eligible. Building that evidence at transaction level is far easier than reconstructing it during donor reporting or audit.
