Some grant programmes require not just that recipients report on how they used their funding, but that an independent third party confirms those reports are accurate. This is the verifier role — and it sits at the more rigorous end of the grants accountability spectrum.
Understanding when verifiers are used, what they do, and what the process requires from a systems perspective helps funders decide whether verification is appropriate for their programme — and if so, how to implement it without creating excessive administrative burden.
A verifier is an independent party — typically an accountant, auditor, or suitably qualified professional — who reviews a grant recipient's claims and provides independent confirmation of their accuracy before the funder acts on them.
The specific scope of verification varies. It might involve:
- Confirming that costs claimed match invoices and bank records
- Confirming that activities described were actually completed
- Confirming that a milestone has been reached and documented
- Signing off a final acquittal to confirm that grant funds were used as intended
The key characteristic of a verifier is independence from both the recipient and the funder. They are a check on the integrity of the reporting relationship, not an extension of the funder's programme team.
Verifiers are typically required in programmes where:
The grant size justifies the cost. Verification has a transaction cost — the recipient pays for the verifier's time. For small grants, verification overhead is disproportionate. For grants above a certain threshold (often $50,000–$100,000 depending on the programme), verification provides assurance that justifies its cost.
The funder has reduced capacity for direct oversight. Community foundations, government agencies, and intermediary organisations that manage large grant portfolios with small teams may use verification as a scalable accountability mechanism. The verifier does due diligence that the programme team could not practically perform across a full portfolio.
The programme involves significant public or charitable funds. Government-funded programmes and charitable trusts administering endowment funds are accountable to regulators, auditors, and the public. Verification provides an additional layer of assurance that satisfies those accountability obligations.
Multi-year or complex grants. Grants that run over multiple years, involve substantial capital expenditure, or cover complex programmes of work benefit from milestone-based verification rather than a single final acquittal.
Recipients have variable financial management capacity. Some grant programmes fund small community organisations that may not have strong internal financial controls. Verification provides a structured external check that is proportionate to the risk.
A typical verification process includes:
1. Defining the verification scope at the point of award. The grant agreement should specify what the verifier is being asked to confirm, what evidence they need to review, and what standard their sign-off must meet. This is a design decision, not something to figure out at acquittal.
2. Recipient selecting a qualified verifier. Most programmes allow recipients to select their own verifier, subject to independence requirements. Some programmes maintain a panel of approved verifiers. The recipient typically bears the cost, which is sometimes included as an eligible expense under the grant.
3. Verification occurring at defined milestones. For multi-year grants, verification typically occurs at scheduled milestones — often tied to payment tranches. Each payment tranche requires verification sign-off before release.
4. Verifier reporting back to the funder. The verifier's report is submitted to the funder (not just held by the recipient). This creates an independent record that the funder can act on.
5. Funder reviewing and releasing payment. The programme team reviews the verification report and releases the milestone payment if requirements are met. Exceptions — where verification raises concerns — are escalated for programme manager review.
Verification adds a step to the post-award workflow. Software that handles verification natively makes the process manageable; software that doesn't turns it into email overhead.
Verifier assignment. The system should allow the funder to record the verifier for each grant — name, organisation, contact details, and independence confirmation.
Verification task management. When a grant reaches a milestone that requires verification, the system should route the verification task appropriately — notifying the recipient to engage their verifier, and tracking whether verification has been received and reviewed.
Verifier portal or submission mechanism. Verifiers need a way to submit their reports to the funder that creates a structured record. An email attachment with no tracking is a poor process.
Payment linkage. The milestone payment should not be releasable until verification is complete. The system should enforce this dependency, not rely on a programme manager to remember to check.
Audit record. The verification report and the funder's review of it should be part of the permanent grant record — attributable, timestamped, and retrievable for audit purposes.
Verification is part of a broader accountability architecture. It works best when it is designed in at the outset — where the grant agreement specifies verification requirements clearly, the recipient understands what is expected, and the system supports the workflow.
Programmes that bolt on verification requirements after problems arise — asking recipients to verify claims retrospectively — create adversarial dynamics and rarely produce the accountability record that the original problem required.
The design question is whether the programme risk profile and funding level justify the overhead. When they do, verification provides an independent check that serves the interests of funders, recipients, and the public whose funds are being distributed.
Tahua's grants management platform supports the full verifier workflow — from assigning verifiers at award to releasing milestone payments on verified completion. The government grants management and community foundations pages cover how accountability structures work within the platform.