Grant Agreement Singapore | Charities Act & COC

A grant agreement is a binding contract under which a grantor commits funds to a grantee for charitable, community or programme purposes, subject to conditions on use, reporting and repayment. It is not a donation receipt and it is not a sponsorship deal. A plain donation transfers money with no strings; a sponsorship exchanges money for marketing benefits and is commercial in nature. A grant sits between them: the funder expects no commercial return, but it does attach conditions, and those conditions are legally enforceable because the document is a contract supported by consideration under Singapore common law.

The distinction matters for how the money is treated in the grantee's accounts. Where a funder imposes conditions on how the money may be spent, the grant becomes a restricted fund, which must be used only for its stated purpose and reported separately in the financial statements. A grant given with no conditions falls into unrestricted funds. Getting this classification right at the drafting stage saves the grantee's treasurer from awkward year-end reconciliations and keeps the audit trail clean. You will also see the term "funding agreement" used interchangeably, particularly for multi-year or programme-level support, and the same drafting principles apply. Whether the grantee is a society registered under the Societies Act 1966, a charity, or a company limited by guarantee incorporated under the Companies Act 1967, the agreement should name the correct legal entity and the person authorised to bind it.

No single statute codifies grant agreements in Singapore; the document lives at the intersection of contract law and charity regulation. Its enforceability rests on ordinary common law contract principles: offer, acceptance, consideration and an intention to create legal relations. The conditions a funder attaches, and the repayment or clawback mechanism it relies on, are only as strong as the drafting, which is why the operative clauses must be specific rather than aspirational.

The regulatory overlay comes from the Charities Act 1994 and the Commissioner of Charities, who oversee the sound administration of charities and IPCs through mandatory annual submissions and regulatory scrutiny of how charitable assets are managed. The Code of Governance for Charities and IPCs, issued by the Charity Council on a comply-or-explain basis, expects the board to run a system for the delegation of authority and limits of approval, and to account transparently for how funds were received, used and carried forward. Restricted funds carrying donor-imposed conditions must be used only for their intended purposes and reported separately, which makes the "approved use of funds" clause in a grant agreement a governance instrument, not just a contractual nicety. You can read the Commissioner's own explanation of these duties in the Ministry of Culture, Community and Youth's guidance on compliance with the Code of Governance for charities and IPCs.

Two further points shape the drafting. Where the grantee holds IPC status, government and institutional funders increasingly require utilisation reports or separate project audits, so the reporting clause should anticipate that level of scrutiny. And a repayment clause must survive the rule against penalties. A clawback that demands a sum out of all proportion to the funder's actual loss risks being struck down as an unenforceable penalty. The Court of Appeal in Denka Advantech Pte Ltd v Seraya Energy Pte Ltd [2021] 1 SLR 631 confirmed that a repayment triggered by breach must be a genuine pre-estimate of loss, not a deterrent. A clause that simply requires unspent or misapplied funds to be returned is the safer construction, because it recovers the funder's real exposure rather than punishing the grantee.

The clearest trigger is a restricted or programme-specific grant, where a funder gives money for a named project and needs a written record that the grantee will spend it only on that project. Corporate foundations and community funds almost always insist on this before disbursing, because their own boards must account for where the money went. A second common scenario is multi-year or tranched funding, where the funder releases money in instalments tied to milestones. Here the agreement carries real weight: it lets the funder pause or stop later tranches if the grantee falls behind, without walking into a breach of its own.

Government-linked grants form a third category. Funders channelling money through schemes run by the National Council of Social Service or similar bodies pass reporting obligations down to the grantee, and the grant agreement is where those obligations are captured in writing. A fourth trigger is any grant to an IPC, because the tax-deductible status of the recipient raises the bar on documentation and audit trail. Do not treat a grant to an IPC as an informal handshake.

Two edge cases deserve flagging. First, cross-border or foreign-sourced funding attracts additional scrutiny, since Singapore regulates foreign donations above certain thresholds to guard against foreign influence, and the agreement should record the source clearly. Second, a grant that funds staff salaries or capital assets rather than programme delivery needs a repayment clause tailored to what happens if the role ends early or the asset is disposed of, a point a generic template usually misses.

• The grant purpose and approved use of funds clause defines exactly what the money may be spent on, in language specific enough to create a restricted fund. Vague purposes like "general support" defeat the point; the template ties the funds to named activities, budget lines or a project scope schedule, which is what the Code of Governance expects for restricted-fund reporting.
• The disbursement and tranche schedule sets out how and when money is released, whether as a lump sum or against milestones. Where funding is tranched, each release is conditioned on the grantee meeting the prior milestone and submitting the required report, giving the funder a clean contractual basis to hold back later payments.
• The deliverables and milestones clause records what the grantee must achieve and by when, expressed as measurable outputs rather than good intentions. This is the backbone that the reporting and clawback clauses hang off, so the template pushes you to state concrete targets.
• The reporting obligations clause specifies the frequency, format and content of progress and financial reports, including whether a utilisation statement or independent project audit is required. For IPC grantees, this clause anticipates the separate reporting that government and institutional funders demand.
• The clawback and repayment clause sets out when unspent, unaccounted-for or misapplied funds must be returned. It is drafted as a recovery of the funder's actual loss rather than a punitive sum, keeping it on the right side of the rule against penalties confirmed in Denka Advantech.
• The variation, suspension and termination clause lets the parties adjust scope, pause disbursement or end the arrangement on defined grounds, with a mechanism for dealing with the balance of funds on termination.

Societies. A grantee registered under the Societies Act 1966 is not a separate legal person in the way a company is, so the agreement should be signed by authorised office-bearers and the committee should minute its acceptance of the grant and its conditions. Because a society's committee can carry personal exposure, the reporting and fund-handling terms matter more here, not less. The template pairs naturally with the society's own governance records, and committees often adopt a committee resolution recording the decision to accept funding alongside signing the grant.

Charities and IPCs. A registered charity must slot the grant into its restricted-fund accounting and reflect it in the annual submissions the Commissioner of Charities publishes on the Charity Portal. An IPC faces the highest documentation standard: funders routinely require utilisation reports and may commission separate project audits, and a red flag on the portal can jeopardise both future grants and IPC renewal. The reporting clause should therefore be drafted to the funder's audit expectations, not the bare statutory minimum. A charity governance pack aligned with the Code of Governance gives the board the conflict, reserves and delegation policies that a diligent funder will want to see before releasing money.

Companies limited by guarantee. A CLG incorporated under the Companies Act 1967 is a separate legal entity, which simplifies signing but adds a layer: the board must resolve to accept the grant, and larger CLGs pursuing government grants must show clean statutory filings and financial statements prepared under the applicable reporting standards. The grant agreement should name the company precisely and be executed by directors authorised under its constitution.

You start by identifying the two parties: the grantor by its correct legal name and the grantee by its registered entity type, whether society, charity or CLG, together with the person authorised to sign. From there the form asks you to state the grant amount and the disbursement method, so you choose between a single payment and a tranche schedule tied to milestones. You then define the approved use of funds, and this is where the template prompts you to be specific enough to create a restricted fund rather than a vague pot of money.

Next you set the deliverables and the reporting rhythm, selecting how often the grantee reports and whether a financial utilisation statement or audit is required. The clawback section then lets you describe what happens to unspent or misapplied funds, drafted as a return of the funder's actual exposure. You finish with the term, variation and termination provisions, and the execution block for signatures. The completed agreement downloads in Word and PDF, so you can circulate it for negotiation or sign it as final. For grantees also formalising helper roles under the funded project, a matching volunteer agreement with a conflict-of-interest declaration keeps the whole project file consistent.

The most damaging error is a purpose clause too broad to bite. When "approved use of funds" reads like a mission statement, the grantee cannot treat the money as a restricted fund, the funder cannot enforce misuse, and the auditor has nothing concrete to test against. A second frequent mistake is treating reporting as a formality: agreements that say the grantee will "report periodically" without fixing frequency, format or content leave both sides guessing, and for an IPC that vagueness can surface as a governance gap in the annual submission. Grantors also forget to link tranche release to milestone completion, which strips them of the one lever that makes staged funding safe.

On the repayment side, the classic trap is drafting a clawback as a punishment rather than a recovery. A clause demanding return of the full grant plus a penalty sum on any minor breach risks being unenforceable under the Denka Advantech line of authority, leaving the funder worse off than a modest, well-calibrated recovery clause would. Finally, parties overlook who has authority to sign. A society office-bearer or CLG director signing without a recorded committee or board decision creates a gap that a diligent funder, or a later dispute, will expose. A short resolution accepting the grant closes it. Non-profits handling donor and beneficiary data under the funded project should also confirm their data-handling practices meet PDPA requirements, since grant reporting often involves personal information.