IFRIC Update is a summary of the decisions reached by the IFRS Interpretations Committee (Committee) in its public meetings. Past Updates can be found in the IFRIC Update archive.
The Committee met on 14-15 March 2023, and discussed:
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 whether, in applying IFRS 9, an entity accounts for a guarantee written over a derivative contract as a financial guarantee contract or a derivative.
The request described a guarantee written over a derivative contract between two third parties. Such a guarantee would reimburse the holder of the guarantee for the actual loss incurred—up to the close-out amount—in the event of default by the other party. The close-out amount is determined based on a valuation of the remaining contractual cash flows of the derivative prior to default.
Findings
Evidence gathered by the Committee [to date] indicated that the matters described in the request are not widespread, and that when the matters do arise, the amounts involved are not material.
Conclusion
Based on its findings, the Committee concluded that the matter described in the request does not have widespread effects and it does not have (and nor is it expected to have) a material effect on those affected. Consequently, the Committee [decided] not to add a standard-setting project to the work plan.
The Committee received requests about how an entity that issues insurance contracts (insurer) applies the requirements in IFRS 17 and IFRS 9 to premiums receivable from an intermediary.
In the fact pattern described in the request, an intermediary acts as a link between an insurer and a policyholder to arrange an insurance contract between them. The policyholder has paid in cash the premiums to the intermediary, but the insurer has not yet received in cash the premiums from the intermediary. The agreement between the insurer and the intermediary allows the intermediary to collect the premiums to the insurer at a later date.
When the policyholder paid the premiums to the intermediary, the policyholder discharged its obligation under the insurance contract and the insurer is obliged to provide insurance contract services to the policyholder. If the intermediary fails to pay the premiums to the insurer, the insurer does not have the right to recover the premiums from the policyholder, or to cancel the insurance contract.
The requests asked whether, in the submitted fact pattern, the premiums receivable from the intermediary are future cash flows within the boundary of an insurance contract and included in the measurement of the group of insurance contracts applying IFRS 17 or are a separate financial asset applying IFRS 9. The requests set out two views.
Under the first view (View 1), the insurer determines that the premiums receivable from the intermediary are future cash flows within the boundary of an insurance contract. Applying View 1, when the policyholder pays the premiums to the intermediary:
Under the second view (View 2), because the payment by the policyholder discharges its obligation under the insurance contract, the insurer considers the right to receive premiums from the policyholder to be settled by the right to receive premiums from the intermediary. The insurer therefore determines that the premiums receivable from the intermediary are not future cash flows within the boundary of an insurance contract but, instead, a separate financial asset. Applying View 2, when the policyholder pays the premiums to the intermediary:
Applying the requirements in IFRS Accounting Standards
The Committee observed that IFRS 17 is the starting point for an insurer to consider how to account for its right to receive premiums under an insurance contract. The Committee considered:
Cash flows within the boundary of an insurance contract applying IFRS 17
Paragraph 33 of IFRS 17 requires an insurer to include in the measurement of a group of insurance contracts an estimate of all the future cash flows within the boundary of each contract in the group. Paragraph B65 explains that cash flows within the boundary of an insurance contract are those that relate directly to the fulfilment of the contract, including premiums from a policyholder.
The Committee observed that paragraph B65 of IFRS 17 does not distinguish between premiums to be collected directly from a policyholder and premiums to be collected through an intermediary. In applying IFRS 17, premiums from a policyholder collected through an intermediary is therefore included in the measurement of a group of insurance contracts.
The Committee next considered when the premiums that are already included in the measurement of a group of insurance contracts are removed from that measurement.
Removing cash flows from the measurement of a group of insurance contracts
Paragraph 34 of IFRS 17 specifies that cash flows are within the boundary of an insurance contract if they arise from substantive rights and obligations that exist during the reporting period in which the entity can compel the policyholder to pay the premiums or in which the entity has a substantive obligation to provide the policyholder with insurance contract services.
In the fact pattern described in the requests, the insurer has not recovered the premiums in cash. The Committee observed that IFRS 17 is silent on whether future cash flows within the boundary of an insurance contract are removed from the measurement of a group of insurance contracts only when these cash flows are recovered or settled in cash.
Therefore, the Committee observed that, in accounting for premiums receivable from an intermediary when payment by the policyholder discharges the policyholder’s obligation under the insurance contract, an insurer can apply either View 1 or View 2. Given this, the Committee next considered the implications of both views for information about credit risk.
Information about credit risk
IFRS 17 and IFRS 9 deal differently with the measurement, presentation and disclosure of expected credit losses from an intermediary. The Committee considered that, depending on which view (View 1 or View 2) an insurer applies, it is required to apply all the measurement and disclosure requirements in the applicable IFRS Accounting Standards. Therefore, an insurer applies either IFRS 17 (including paragraph 131 that requires disclosure of information about the credit risk that arises from contracts within the scope of IFRS 17) or IFRS 9 (and the requirements in IFRS 7 Financial Instruments: Disclosures) to the premiums receivable from an intermediary.
Conclusion
The Committee concluded that, because IFRS 17 is silent on when future cash flows within the boundary of an insurance contract are removed from the measurement of a group of insurance contracts, in the fact pattern described in the requests, an insurer could account for premiums paid by a policyholder and receivable from an intermediary applying either IFRS 17 or IFRS 9.
In light of its analysis, the Committee considered whether to add a standard-setting project on the interaction between IFRS 17 and IFRS 9 to the work plan. The Committee noted that any such project would involve assessing whether changes to the Standards would have unintended consequences. This assessment may take considerable time and effort to complete because it would involve, among other steps, analysing a broad range of contracts (not only those set out in the fact pattern described in the requests). The Committee observed that the application of either View 1 or View 2 when accounting for premiums paid by a policyholder and receivable from an intermediary would provide users of financial statements with useful information based on the requirements in IFRS 17 or IFRS 9.
Consequently, the Committee concluded that a project would not result in an improvement in financial reporting that would be sufficient to outweigh the costs. The Committee therefore [decided] not to add a standard-setting project to the work plan.
The Committee received a request about how an entity accounts for employee home ownership plans and employee home loans.
Fact pattern 1: employee home ownership plans
An entity provides its employee with a house that the entity constructed and owns. In return, the employee has a proportion of his or her base salary deducted every month until the agreed price of the house has been fully repaid.
If the employee leaves employment within the first five years of the arrangement, the employee forfeits his or her rights to the house and recovers the salary deductions to date. If the employee leaves employment after that five-year period, the employee may choose either:
Legal title to the house transfers to the employee only when he or she has paid in full the agreed price for the house.
The request asked how the entity should account for this arrangement—in particular, when it should recognise the transfer of the house to the employee, and the accounting before and after the transfer.
Fact pattern 2: employee home loans
An entity provides its employee with a loan to buy a house, which the employee chooses and purchases and the entity does not own. The entity provides the loan at a below-market rate of interest; the loan is typically interest-free. The employee repays the loan through salary deductions. If the employee leaves employment for any reason at any point, the outstanding balance of the loan becomes repayable.
The request asked how the entity should account for this arrangement—in particular, whether the loan is:
Findings
Evidence gathered by the Committee [to date] indicated that the matters described in the request are not widespread, and that when the matters do arise, the amounts involved are not material.
Conclusion
Based on its findings, the Committee concluded that the matters described in the request do not have widespread effect and they do not have (and nor are they expected to have) a material effect on those affected. Consequently, the Committee [decided] not to add a standard-setting project to the work plan.
The Committee considered feedback on the tentative agenda decision published in the November 2022 IFRIC Update about how to assess whether a contract contains a lease.
The Committee concluded its discussions on that agenda decision. In accordance with paragraph 8.7 of the IFRS Foundation’s Due Process Handbook, the International Accounting Standards Board (IASB) will consider this agenda decision at its April 2023 meeting. If the IASB does not object to the agenda decision, it will be published in April 2023 in an addendum to this IFRIC Update.
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.
In March 2022 the Committee discussed a request about the application of IFRS 9 and IFRS 16 in accounting for a rent concession in which the only change to a lease contract is the lessor’s forgiveness of lease payments due from the lessee under that contract.
The Committee recommended that the IASB consider undertaking a narrow-scope standard-setting project—potentially as an annual improvement—to address a lessee’s accounting for such a rent concession.
At this meeting, the Committee provided advice on the recommendation:
The Committee was informed of potential confusion arising from an inconsistency between paragraph 28 of IFRS 7 and paragraph IG14 of its accompanying illustrative guidance in the Guidance on implementing IFRS 7.
The Committee provided advice on the recommendation to amend paragraph IG14 of IFRS 7 to improve its consistency with paragraph 28 of IFRS 7.
The Committee discussed the IASB’s Business Combinations—Disclosures, Goodwill and Impairment project. Committee members provided their views on possible changes to the requirements in IAS 36 Impairment of Assets relating to the impairment test for cash-generating units containing goodwill.
The IASB will consider this feedback, along with feedback from other stakeholders, when discussing the possible changes to the requirements in IAS 36.
The Committee received an update on the status of open matters not discussed at its March 2023 meeting.
Agenda decisions, in many cases, include explanatory material. Explanatory material may provide additional insights that might change an entity's understanding of the principles and requirements in IFRS Accounting Standards. Because of this, an entity might determine that it needs to change an accounting policy as a result of an agenda decision. It is expected that an entity would be entitled to sufficient time to make that determination and implement any necessary accounting policy change (for example, an entity may need to obtain new information or adapt its systems to implement a change). Determining how much time is sufficient to make an accounting policy change is a matter of judgement that depends on an entity's particular facts and circumstances. Nonetheless an entity would be expected to implement any change on a timely basis and, if material, consider whether disclosure related to the change is required by IFRS Accounting Standards. The Committee discussed the following matters and decided not to add standard-setting projects to the work plan. |
Published in April 20231
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, for a contract 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:
Identified asset
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. Consequently, 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 […] shall exclude 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.
Paragraphs BC112–BC115 of the Basis for Conclusions on IFRS 16 explain the IASB’s rationale in developing the requirements on substitution rights. Paragraph BC113 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’.
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 BC115 notes:
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, as required by paragraph B14, requires judgement. Paragraph B14(a) specifies that a supplier has the practical ability to substitute alternative assets throughout the period of use even if the supplier does not already have alternative assets but could source those assets within a reasonable period of time. This illustrates that the term ‘throughout the period of use’ does not mean at all times within that period.
Applying 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:
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.
Identified asset
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 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, the condition in paragraph B14(b) does not exist throughout the period of use. Therefore, the supplier does not have the substantive right to substitute a battery throughout the period of use. While determining whether a supplier’s substitution right is substantive throughout the period of use can require judgement, the Committee observed that the facts and circumstances in this fact pattern are such that it is clear that the supplier’s right is not substantive throughout that period.
The Committee’s conclusion
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 assess 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. If the customer concludes that the contract contains a lease, it would apply the requirements in paragraphs 18–21 of IFRS 16 to determine the lease term.
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.