AUDIT

IPSAS 47: what finance leaders need to do before the year-end closing

Executive summary
  • IPSAS 47, Revenue, is effective for annual reporting periods beginning on or after 1 January 2026. It replaces IPSAS 9, IPSAS 11 and IPSAS 23 with a single revenue recognition framework. 
  • The analysis begins by determining whether a binding arrangement exists, rather than classifying transactions as exchange or non-exchange. 
  • Transactions with binding arrangements follow a five-step recognition model adapted from IFRS 15. while transactions without binding arrangements follow recognition criteria for asset and liability associated with the revenue transaction.  
  • Key implementation challenges include assessing enforceability, identifying compliance obligations, updating accounting policies and systems, and preparing expanded disclosures. 
  • Entities may apply either the full retrospective or modified retrospective transition approach.
  • Entities that act early will be better positioned to achieve a smooth transition and avoid time-consuming adjustments during the year-end close.
Contents

What is IPSAS 47?

The objective of IPSAS 47 is to establish principles that enable entities to report useful information about the nature, amount, timing and uncertainty of revenue and related cash flows.

The standard applies to revenue transactions of entities preparing accrual-based IPSAS financial statements, subject to the specified scope exclusions.

Transactions outside the scope of IPSAS 47

  • Social benefit transactions within the scope of IPSAS 42
  • Public sector combinations
  • Leases
  • Insurance contracts
  • Financial instruments
  • Contributions from owners
  • Certain non-financial asset disposals
  • Agricultural activities
  • Mineral extraction activities

 

Key concepts

Term Definition
Binding arrangement
  An arrangement that confers both rights and obligations, enforceable through legal or equivalent means, on the parties to the arrangement.
Compliance obligation
  An entity’s promise in a binding arrangement to either use resources internally for distinct goods or services or transfer distinct goods or services to a purchaser or third-party beneficiary.
Resource provider
  The party that provides a resource to the entity.
Third-party beneficiary
  An entity, household or individual who will benefit from a transaction made between other parties by receiving resources.
Transfer
  A transaction, other than taxes, in which an entity receives a resource from a resource provider (which may be another entity or an individual) without directly providing any good, service or other asset in return.
Binding arrangement asset
  An entity’s right to consideration for satisfying its compliance obligations in compliance with the terms of the binding arrangement when that right is conditioned on something other than the passage of time.
Binding arrangement liability
  An entity’s obligation to satisfy its compliance obligation in compliance with the terms of the binding arrangement for which the entity has received consideration (or the amount is due) from the resource provider.
Capital Transfer
  An inflow of cash or another asset that arises from a binding arrangement with a specification that the entity acquires or constructs a non-financial asset that will be controlled by the entity.
Other compulsory contributions and levies
  Cash or another asset, paid or payable to the entity, in accordance with laws and/or regulations, established to provide revenue that is to be used in the provision of specified government programs.

 

Identifying the revenue transaction

IPSAS 47 begins the analysis with a single question: does a binding arrangement exist? The answer determines which revenue recognition model applies.

To assess whether an arrangement is binding, entities evaluate whether enforceable rights and obligations exist for all parties involved. Enforceability may arise through legal or equivalent means — for example, legislation, executive authority, or cabinet and ministerial directives.

Where no binding arrangement exists, the entity applies the model for revenue from transactions without binding arrangements.

 

Revenue from transactions without binding arrangements

These transactions do not create both enforceable rights and enforceable obligations for all parties and, therefore, do not meet the definition of a binding arrangement. Accordingly, the accounting treatment follows an asset-and-liability recognition criteria:

Asset recognition: The entity recognises an asset when it obtains control of resources as a result of a past event and the asset can be measured reliably.

Liability recognition: The entity assesses whether the transaction gives rise to a present obligation requiring a future transfer of resources. Where such an obligation exists and the recognition criteria are met, a liability is recognised.

Revenue recognition: Revenue is recognised when (or as) the entity satisfies any obligations associated with the inflow of resources, or immediately If no enforceable obligation is associated with the inflow of resources.

Taxes

IPSAS 47 includes detailed guidance for taxation revenue. Revenue is recognised when the taxable event occurs, such as:

  • Income being earned
  • A taxable sale taking place
  • Ownership of an asset existing at a specified date

Amounts received before the taxable event occurs are not recognised immediately as revenue. Instead, they are recorded as liabilities until the taxable event takes place.

An asset and related taxation revenue are recognised when the taxable event occurs and the asset recognition criteria are met.

 

Revenue from transactions with binding arrangements

Where a binding arrangement exists and the relevant recognition criteria are met, entities apply a five-step revenue recognition model similar to the model used in IFRS 15, but adapted and expanded for application in the public sector.

Five-step revenue recognition model

Requirement

Confirm that a binding arrangement exists with enforceable rights and obligations.

Requirement

Identify each distinct promise to transfer goods or services to a purchaser or third-party beneficiary, or to use resources internally to deliver them. Assess each obligation separately.

Requirement

Determine the consideration the entity expects to be entitled to for satisfying its compliance obligations, including variable consideration, significant financing components, non-cash consideration and amounts payable to the resource provider.

Requirement

Allocate the transaction consideration to each compliance obligation based on its relative stand-alone value.

Requirement

Revenue is recognised when compliance obligations are satisfied, either over time or at a point in time.

 

Presentation and disclosure requirements

IPSAS 47 requires entities to present or disclose sufficient qualitative and quantitative information for users to understand the nature, amount, timing and uncertainty of revenue and cash flows.

Disclosures cover: 

  • Accounting policies for revenue recognition  
  • The nature of revenue from binding and non-binding arrangements
  • The timing of revenue recognition
  • Significant uncertainties affecting revenue
  • The judgements applied in determining accounting treatments
  • The impact of binding arrangement assets and liabilities

 

Effective date and transition

IPSAS 47 is effective for annual reporting periods beginning on or after 1 January 2026.

Entities may adopt the Standard using either:

  • a full retrospective approach; or
  • a modified retrospective approach.

Under the modified retrospective approach, the cumulative effect of initial application is recognised in opening accumulated surplus or deficit at the date of transition.

 

Priorities before the 2026 year-end close

The first reporting cycle under IPSAS 47 is now underway. 

Finance leaders should focus on several key implementation activities:

Assess accounting policies, revenue streams, processes, systems, controls and disclosures against IPSAS 47. Identify required changes before year-end reporting.

Inventory revenue sources and determine which arise from binding arrangements. This classification determines the applicable accounting model and focuses implementation efforts on material revenue streams.

Revise current revenues accounting policies developed under IPSAS 9, IPSAS 11 and IPSAS 23 to address binding arrangements, compliance obligations, revenue measurement, presentation and disclosure.

Confirm that systems can track compliance obligations, allocate transaction consideration and capture disclosure information. Update internal controls where necessary.

Perform a disclosure gap analysis to identify information not currently captured. IPSAS 47 introduces expanded disclosure requirements.

Ensure relevant stakeholders understand how contractual, legislative and operational arrangements affect revenue recognition and financial reporting.

 

Conclusion

By focusing on enforceability and compliance obligations, IPSAS 47 introduces a new way of analysing revenue transactions and requires entities to apply greater judgement in determining how and when revenue should be recognised.

For many public sector entities, implementation will require reassessment of revenue arrangements, updated accounting policies, system readiness and preparation for expanded disclosures.

Entities that develop a comprehensive implementation plan, including revenue stream mapping, policy updates and system readiness assessments, will be better positioned for a smooth year-end close.

 

How Grant Thornton can help

Grant Thornton’s specialists can support you in assessing the impact of IPSAS 47, developing implementation roadmaps and navigating first-year adoption challenges. From gap assessments and technical accounting reviews to policy development, training, implementation support and financial statement disclosures, our teams can help you achieve a smooth and efficient transition to the new revenue model.