|The Committee discussed the following matters and tentatively decided not to add standard-setting projects to the work plan. The Committee will reconsider these tentative decisions, including the reasons for not adding standard-setting projects, at a future meeting. The Committee invites comments on the tentative agenda decisions. Interested parties may submit comments on the open for comment page. All comments will be on the public record and posted on our website unless a respondent requests confidentiality and we grant that request. We do not normally grant such requests unless they are supported by a good reason, for example, commercial confidence. The Committee will consider all comments received in writing up to and including the closing date; comments received after that date will not be analysed in agenda papers considered by the Committee.
The Committee received a request about how to assess whether a contract contains a lease. The request asked about:
The definition of a lease
Paragraph 9 of IFRS 16 states that ‘a contract is, or contains, a lease if the contract conveys the right to control the use of an identified asset for a period of time in exchange for consideration’. Applying paragraph B9 of IFRS 16, to meet the definition of a lease the customer must have both:
The period of use is ‘the total period of time that an asset is used to fulfil a contract with a customer (including any non-consecutive periods of time)’. (Appendix A to IFRS 16)
Paragraph B12 of IFRS 16 states that ‘an entity shall assess whether a contract contains a lease for each potential separate lease component’ and directs an entity to paragraph B32 of IFRS 16 for application guidance on separate lease components. Paragraph B32 specifies that the right to use an underlying asset is a separate lease component if both:
The first requirement for a contract to meet the definition of a lease is that a customer controls the use of an identified asset. Paragraphs B13–B20 of IFRS 16 provide application guidance on an identified asset.
Paragraph B13 states that ‘an asset is typically identified by being explicitly specified in a contract. However, an asset can also be identified by being implicitly specified at the time that the asset is made available for use by the customer’.
But ‘even if an asset is specified, a customer does not have the right to use an identified asset if the supplier has the substantive right to substitute the asset throughout the period of use’ (paragraph B14). In that case, the supplier—rather than the customer—controls the use of the asset. As a consequence, there is no identified asset; the contract does not contain a lease.
For a substitution right to be substantive, paragraph B14 states that both of the following conditions must exist:
Paragraph B16 states that ‘an entity’s evaluation of whether a supplier’s substitution right is substantive excludes consideration of future events that, at inception of the contract, are not considered likely to occur.’
Paragraphs B15–B18 specify requirements that mean, in each of the following situations, a supplier’s substitution right is not substantive (or the customer is not precluded from having the right to use an identified asset):
Paragraph B17 notes that the costs of substitution are more likely to exceed the associated benefits when the asset is located at the customer’s premises or elsewhere. Paragraph B19 requires the customer to presume that a supplier’s substitution right is not substantive if the customer cannot readily determine whether the supplier has a substantive substitution right.
Paragraph BC113 of the Basis for Conclusions on IFRS 16 explains the IASB’s rationale in developing the requirements on substitution rights and states that ‘the IASB’s intention in including [these requirements] is to differentiate between:
Paragraph BC113 goes on to explain that, at the time of developing IFRS 16, the IASB was of the view ‘that, in many cases, it will be clear that the supplier would not benefit from the exercise of a substitution right because of the costs associated with substituting an asset’. ‘If substitution rights are substantive, then the IASB thinks that this would be relatively clear from the facts and circumstances’ (paragraph BC115).
Consequently, the Committee observed that the requirements in paragraphs B13–B19 set a high hurdle for a customer to conclude that there is no identified asset when an asset is explicitly or implicitly specified. The Committee also observed that determining whether a supplier’s right to substitute an asset is substantive throughout the period of use requires judgement.
Application of the requirements in IFRS 16 to the fact pattern described in the request
In the fact pattern described in the request:
The level at which to evaluate whether a contract contains a lease
In the fact pattern described in the request, the customer is able to benefit from use of each asset (a battery) together with other resources (a bus) available to it and each battery is neither highly dependent on, nor highly interrelated with, the other batteries in the contract.
Therefore, the Committee concluded that, in the fact pattern described in the request, applying paragraph B12, the customer assesses whether the contract contains a lease—including evaluating whether the supplier’s substitution right is substantive—for each potential separate lease component, ie for each battery.
In the fact pattern described in the request, each battery is specified. Even if not explicitly specified in the contract, a battery would be implicitly specified at the time it is made available for the customer’s use. Therefore, the Committee observed that, unless the supplier has the substantive right to substitute the battery throughout the period of use, each battery is an identified asset.
In the fact pattern described in the request, the condition in paragraph B14(a)—the supplier has the practical ability to substitute alternative assets throughout the period of use—is assumed to exist. The Committee observed, however, that the condition in paragraph B14(b) does not exist throughout the period of use because the supplier is not expected to benefit economically from exercising its right to substitute a battery for at least the first three years of the contract. Those years are part of the period of use. Consequently, the supplier’s substitution right is not substantive throughout the period of use.
Therefore, the Committee concluded that, in the fact pattern described in the request, each battery is an identified asset. To assess whether the contract contains a lease, the customer would then apply the requirements in paragraphs B21–B30 of IFRS 16 to determine whether, throughout the period of use, it has the right to obtain substantially all the economic benefits from use, and direct the use, of each battery.
The Committee concluded that the principles and requirements in IFRS 16 provide an adequate basis for an entity to evaluate the level at which to assess whether the contract contains a lease and whether there is an identified asset in the fact pattern described in the request. Consequently, the Committee [decided] not to add a standard-setting project to the work plan.
|Some proposed amendments to IFRS Accounting Standards that are sufficiently minor or narrow in scope can be packaged together and exposed in one document even though the amendments are unrelated—these are called ‘annual improvements’. Such amendments are limited to changes that either clarify the wording in an IFRS Accounting Standard or correct relatively minor unintended consequences, oversights or conflicts between existing requirements in the Standards. Annual improvements follow the same due process as other amendments to IFRS Accounting Standards, except that annual improvements consist of unrelated amendments that are exposed together, rather than separately.
The Committee discussed matters that have been raised as possible amendments in the next annual improvements cycle, and provided advice to be presented to the IASB together with the recommendations for proposed amendments.
The Committee was informed of potential confusion arising from an inconsistency in wording between paragraph B6 of IFRS 1 and requirements for hedge accounting in IFRS 9 Financial Instruments.
The Committee provided advice on the recommendation to amend:
The Committee was informed of potential confusion arising from an inconsistency between paragraphs B73 and B74 of IFRS 10 related to an investor determining whether another party is acting on its behalf.
The Committee provided advice on the recommendation to amend particular wording in paragraph B74 of IFRS 10 that has created the inconsistency with paragraph B73.
The Committee was informed of potential confusion arising from a reference in Appendix A to IFRS 9 to the definition of ‘transaction price’ in IFRS 15 Revenue from Contracts with Customers. The term ‘transaction price’ is used in particular paragraphs of IFRS 9 with a meaning that is not necessarily consistent with the definition of that term in IFRS 15.
The Committee provided advice on the recommendation to delete the reference to ‘transaction price’ and the associated references to IFRS 15 in Appendix A to IFRS 9.
The Committee was informed of potential confusion in paragraph 37 of IAS 7 Statement of Cash Flows arising from the use of the term ‘cost method’ that is no longer defined in IFRS Accounting Standards.
The Committee provided advice on the recommendation to amend paragraph 37 of IAS 7 by replacing the term ‘cost method’ with ‘at cost’.
The Committee was informed of potential confusion in paragraph B38 of IFRS 7 arising from the reference to a paragraph that has been deleted from the Accounting Standard (paragraph 27A).
The Committee provided advice on the recommendation to amend paragraph B38 of IFRS 7 by replacing the reference to paragraph 27A of IFRS 7 with a reference to paragraphs 72–73 of IFRS 13 Fair Value Measurement.
The Committee was informed of potential confusion in paragraph IG20C accompanying IFRS 7 because that paragraph fails to state that the example does not illustrate all the requirements in paragraph 35M of IFRS 7.
The Committee provided advice on the recommendation to amend paragraph IG20C accompanying IFRS 7 to add a statement that the example does not illustrate all the requirements in paragraph 35M of IFRS 7.
The Committee discussed the IASB’s Post-implementation Review (PIR) of IFRS 15. Committee members provided their views on the implementation and ongoing application of IFRS 15, and suggested matters that the IASB should consider in the PIR.
The IASB will consider this feedback and feedback from other stakeholders in identifying matters to include in the request for information.
The Committee received an update on the status of open matters not discussed at its November 2022 meeting.