AASB clarifies what is meant by ‘class of ROU asset’ for concessionary (peppercorn) leases

In order to comply with AASB 1049 Whole of Government and General Government Sector Financial Reporting, subsequent to initial recognition, public sector entities are required to measure right-of-use (ROU) assets at fair value, even though AASB 16 Leases permits ROU assets arising from peppercorn lease arrangements to be measured at ‘cost’.

Public sector entities therefore requested clarification from the Australian Accounting Standards Board (AASB) as to whether ROU assets arising under concessionary leases (peppercorn leases) are part of the same class of ROU assets arising from market-related leases.

In December 2019, the AASB issued AASB 2019-8 Amendments to Australian Accounting Standards – Class of Right-of-Use Assets arising under Concessionary Leases to clarify that right-of-use (ROU) assets arising under concessionary leases (peppercorn leases) can be treated as a separate class of ROU assets to ROU assets arising under other leases for the purposes of AASB 16 Leases.

These amendments are effective for annual periods beginning on or after 1 January 2019.

Subscribe to Corporate Reporting Insights


This publication has been carefully prepared, but is general commentary only. This publication is not legal or financial advice and should not be relied upon as such. The information in this publication is subject to change at any time and therefore we give no assurance or warranty that the information is current when read. The publication cannot be relied upon to cover any specific situation and you should not act, or refrain from acting, upon the information contained therein without obtaining specific professional advice. Please contact the BDO member firms in Australia to discuss these matters in the context of your particular circumstances.

BDO Australia Ltd and each BDO member firm in Australia, their partners and/or directors, employees and agents do not give any warranty as to the accuracy, reliability or completeness of information contained in this article nor do they accept or assume any liability or duty of care for any loss arising from any action taken or not taken by anyone in reliance on the information in this publication or for any decision based on it, except in so far as any liability under statute cannot be excluded. Read full Disclaimer.