How Does Impairment Look Under IFRS 16 Leases?

As we've seen over the last few months, IFRS 16 has brought about a lot of changes to the existing treatment of leases, especially for lessees. Probably everyone, even if not significantly affected by this accounting standard, remembers at least the most important change: in many cases the lessees will now have to recognize their operating lease on balance sheet which means to record a right-of-use (ROU) asset and a lease liability. "What's so difficult about that?" you may ask. But this new accounting treatment has several not-so-obvious impacts that reveal themselves along the way... impairment of the ROU assets following IAS 36 is one of them.

Does it mean I have to test for an impairment?

The ultimate question that comes to mind when we say IFRS 16 and impairment is probably this one: is the newly recognized asset, represented by the ROU asset, tested for impairment? The response is, "YES!" (however, with some exemptions). The impairment of ROU assets recognized by a lessee is fairly similar to the accounting for impairment of a leased asset by a lessor in case of operating leases under IAS 17. In general, since the ROU asset is a non-financial asset, the IAS 36 requirements apply.

There are only two exemptions from the IAS 36 impairment model. Firstly, when a lessee applies a fair value model under IAS 40 for its investment properties, it shall also apply fair value model to the ROU asset. And secondly, if ROU assets relate to a class of PPE to which the lessee applies the revaluation model under IAS 16, then the lessee can elect to apply the revaluation model to all of the ROU assets that relate to that class of PPE.

How does it work in practice?

General IAS 36 provisions apply to the lease asset and lease liabilities in the same way as for all other assets...

To continue reading

Request your trial

VLEX uses login cookies to provide you with a better browsing experience. If you click on 'Accept' or continue browsing this site we consider that you accept our cookie policy. ACCEPT