peterbamuhigire Government Grants and Donor Assistance (Section 24 / IAS 20)
Overview
Section 24 (IFRS for SMEs) provides two methods, electable by entity policy: the performance model (recognise income when performance conditions are met or when no conditions exist) and the accrual model (deferred income released to P&L as related expenses are incurred or assets are depreciated).
IAS 20 (full IFRS) follows the accrual model and a related-asset / related-income split, with the option of presenting grants related to assets gross (as deferred income) or net (deducted from the asset).
Both standards distinguish:
- Unconditional grants (recognised when receivable).
- Conditional grants (recognised when conditions are met).
- Repayable assistance (treated as liability until repayment terms are met).
Required first reads
doctrine/accounting-finance-doctrine.mddoctrine/references/ifrs-for-smes-default.md(Section 24)doctrine/references/full-ifrs-overlay.md(IAS 20)doctrine/references/chart-of-accounts.mdmanagement-accounting-dimensionsSKILL (donor restrictions)
Donor (NGO) specifics
NGOs typically operate with restricted funds:
- Unrestricted: general operating funds; recognise as income when receivable.
- Restricted (temporary): purpose- or time-restricted; release to unrestricted when restriction is satisfied.
- Restricted (permanent): endowment-like; income earned recognised as restricted unless terms permit reclassification.
The Chwezi NGO model uses dimensions (grant / donor-restriction) and a fund-balance model alongside the IFRS reporting:
- Donor reporting (utilisation per grant, eligible costs per donor budget).
- IFRS reporting (Section 24 / IAS 20 P&L and balance-sheet effect).
CoA implications
| Code | Name |
|---|---|
| 4400 Other Operating Income — Government Grants (or Donor Income) | P&L (gross presentation). |
| 2200 Deferred Income — Grants | Liability (accrual model). |
| 2210 Repayable Government Assistance | Liability. |
| Fund-balance accounts | Per restriction (in equity or in a restricted-fund equity section). |
Build implications
- Grant register: donor, agreement, grant amount, period, conditions, currency, restrictions, eligibility rules.
- Grant draw / receipt workflow.
- Performance / accrual model selection per entity.
- Conditions checklist per grant.
- Eligible-cost categorisation against grant budget.
- Utilisation report per donor per period.
- Restriction-release rules and journals.
- Repayment workflow where conditions are not met.
Forbidden patterns
- Conditional grant recognised before conditions are met (blocker).
- Donor restrictions ignored in journal flows (blocker).
- Repayable assistance recognised as income (blocker).
- Cross-grant funding (using donor A's funds for donor B's eligible costs) without explicit agreement and disclosure (blocker for NGOs).
- Grant netted against an asset without disclosure of the alternative gross presentation (major where material).
Files
SKILL.md.references/grant-register-schema.md.references/donor-restriction-pattern.md.examples/ngo-restricted-grant-cycle.md.
Last reviewed: 2026-05-12. Next review due: 2026-11-12.
Prerequisites
- Load
doctrine/accounting-finance-doctrine.mdbefore applying this skill. - Load
governance/finance-accounting-quality-gate.mdwhen the output is a release, client artefact, SRS, SDS, proposal, business plan, or implementation plan. - Use
doctrine/source-register/for final statutory, tax, payroll, FX, EFRIS, eTIMS, or authority-template values.
Inputs
| Artifact | Produced by | Required? | Validation |
|---|---|---|---|
| Finance context map | finance-module-audit |
Required | Entity, framework, jurisdiction, modules, users, and deployment context are named. |
| Doctrine baseline | Doctrine owner | Required | Doctrine version and reporting framework are stated. |
| Source-register snapshot | tax-statutory-source-register-and-country-packs |
Required for final statutory output | Entries are verified-current or reviewer-approved verified-with-caveat. |
| Ledger/posting context | ledger-posting-engine-core |
Required when postings are affected | Posting boundary, CoA mappings, control accounts, dimensions, and period state are known. |
Outputs
| Artifact | Consumed by | Acceptance evidence |
|---|---|---|
| Skill-specific decision record | Implementer, reviewer, quality gate | Scope, assumptions, chosen treatment, rejected alternatives, and caveats are recorded. |
| Implementation or workflow contract | Software, SRS, SDS, proposal, or business-plan engine | Contract names inputs, outputs, controls, evidence, and failure conditions. |
| Acceptance evidence | Finance quality gate | Tests, fixtures, examples, source links, reviewer sign-off, or evidence-pack references are present. |
| Plain-language explanation | Client, owner, manager, operator | Business meaning is stated before technical accounting treatment where client-facing. |
Decision Rules
- Prefer IFRS for SMEs for typical SME entities unless full IFRS, local law, donor requirements, or client policy requires otherwise.
- Treat every money-touching workflow as ledger, control, reconciliation, evidence, and reporting scope.
- Do not finalize statutory values without source-register support and reviewer status.
- Use business-language output for operators and accountant-language output for ledger, reporting, and audit users.
- Escalate uncertain framework, tax, or statutory interpretations to the required reviewer role instead of presenting them as final.
Acceptance Evidence
- Inputs and outputs above are present or explicitly marked not applicable.
- Relevant quality-gate blockers have been checked and no blocker remains unresolved.
- Examples or fixtures cover at least one happy path and one failure or caveat path for this skill's domain.
- Reviewer role, review date, and open caveats are recorded for release-grade artefacts.
Anti-Patterns
- Treating draft planning assumptions as final statutory or accounting facts.
- Hiding tax, payroll, FX, or authority-template caveats in prose instead of source-register state.
- Producing technically correct accounting output without a plain-language layer for non-accountant users.
- Closing a remediation or implementation item without observable evidence.
Required References
doctrine/accounting-finance-doctrine.md.governance/finance-accounting-quality-gate.md.docs/reference-manifest.mdfor declared reference states.- Domain-specific references listed earlier in this skill.
Examples
- Include at least one normal workflow example for this skill's domain.
- Include at least one exception, rejection, reversal, stale-source, or reviewer-caveat example where the domain can fail.
Review Metadata
Last reviewed: 2026-05-15. Next review due: 2026-11-15.