Revenue & Debt
GRAP 23 Non-Exchange Revenue
Recognition of taxes, fines, grants and donations as non-exchange revenue under GRAP 23.
Why non-exchange revenue is an audit focus
The bulk of a municipality's income arrives without an equal exchange of value, taxes, fines, government grants and donations, and GRAP 23 governs exactly when and how much of it may be recognised.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Non-exchange revenue
R4.1bn
62% of total
Conditions outstanding
R186 m
Fines recognised
R94 m
▼ 12%
Recognition exceptions
6
Revenue split by quarter
Non-exchange revenue streams
| Stream | Amount (R m) | Conditions |
|---|---|---|
| Property rates | 1820 | None |
| Government grants | 1410 | Spending obligation |
| Traffic fines | 94 | None |
| Public donations | 38 | Restricted use |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The obligating event
Revenue from a non-exchange transaction is recognised only when a past event gives the entity control of resources, typically the levy date for rates or the date a fine is issued. Recognising on cash receipt or estimate instead of the obligating event is a classic cut-off error.
Conditions versus restrictions
A condition obliges the entity to use or return resources and creates a liability until satisfied, whereas a restriction merely limits use and does not defer recognition. Misclassifying the two is the most common GRAP 23 judgement error.
Measurement at fair value
Non-exchange revenue is measured at the fair value of the asset received at the date of acquisition. For donated goods and services in kind this requires a defensible valuation basis, not a nominal placeholder.
Taxes and transfers
Property rates are recognised when the taxable event occurs and the asset definition is met, while grants follow the conditions in the transfer agreement. Each stream needs its own recognition policy documented and applied consistently.
How AuditPro Core Bridges the Gap
- Stream-level recognition: each revenue source is mapped to its obligating event and tested against the GRAP 23 criteria rather than treated in aggregate.
- Condition tracking: conditional transfers are held as liabilities and released to revenue only as conditions are evidenced, with the unmet balance reconciled continuously.
- Exception workflow: amounts recognised before the obligating event or without a fair value basis are flagged for review and routed to a preparer for correction.
- Audit-ready export: the recognition working paper, including conditions met and deferred, exports in a format that traces directly to the source ledger and transfer agreements.
Key Takeaways
- Recognise on the obligating event, not on receipt of cash or budget estimate.
- Distinguish conditions (defer) from restrictions (do not defer) for every transfer.
- Hold a documented fair value basis for all in-kind and donated revenue.
- Reconcile unmet conditions to a transferable liability balance at year-end.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.