Chapter 27
Revenue: introduction and scope

List of examples

Chapter 27
Revenue: introduction and scope

1 INTRODUCTION

Revenue is, arguably, one of most important indicators of an entity's performance. It may be perceived as an indicator of the desirability of an entity's products and services, and the growth or decline over time of a business. However, revenue does not represent all income for an entity. As discussed at 1.1 below, revenue is a subset of income, it is derived from the ordinary activities of an entity and may be referred to by a variety of different names, including sales, fees, interest, dividends, royalties and rent.

Identifying what is revenue and specifying how and when to measure and report it is critical to any accounting framework. Within IFRS, several standards deal with the recognition of revenue, for example IFRS 16 – Leases – covers lease revenue and IFRS 9 – Financial Instruments – covers dividends and interest, which would represent revenue if part of an entity's ordinary activities.

This chapter and Chapters 2832 primarily cover IFRS 15 – Revenue from Contracts with Customers. As discussed further at 1.1 below, IFRS 15 only covers a subset of revenue – specifically, revenue that arises from a contract when the counterparty to that contract is a customer (as defined, see 3.3 below) and the contract is not specifically excluded from the standard (e.g. lease contracts within the scope of IFRS 16 or financial instruments within the scope of IFRS 9, see 3.1 below for a complete list of scope exclusions).

This chapter deals with the core principle in IFRS 15, its definitions and scope. Refer to the following chapters for requirements of IFRS 15 that are not covered in this chapter:

  • Chapter 28 – Identifying the contract and identifying performance obligations.
  • Chapter 29 – Determining the transaction price and allocating the transaction price.
  • Chapter 30 – Recognising revenue.
  • Chapter 31 – Licences, warranties and contract costs.
  • Chapter 32 – Presentation and disclosure requirements.

Other revenue items that are not within the scope of IFRS 15, but arise in the course of the ordinary activities of an entity, as well as the disposal of non-financial assets that are not part of the ordinary activities of the entity, for which IFRS 15's requirements are relevant, are addressed at 4 below.

1.1 The distinction between income, revenue and gains

Income is defined in IFRS 15 as ‘increases in economic benefits during the accounting period in the form of inflows or enhancements of assets or decreases of liabilities that result in increases in equity, other than those relating to contributions from equity participants’. [IFRS 15 Appendix A]. The Conceptual Framework for Financial Reporting similarly defines income. [CF 4.68].

This definition encompasses both, ‘revenue’ and ‘gains’. IFRS 15 defines revenue as income that arises in the course of the ordinary activities of an entity. [IFRS 15 Appendix A]. As discussed at 1 above, according to the International Accounting Standards Board's (IASB or the Board) 2010 Conceptual Framework for Financial Reporting (which applied when IFRS 15 was issued), it can include sales, fees, interest, dividends, royalties and rent. [CF(2010) 4.29]. Gains represent other items that meet the definition of income and may, or may not, arise in the course of the ordinary activities of an entity. Gains include, for example, those arising on the disposal of non-current assets. The definition of income also includes unrealised gains; for example, those arising on the revaluation of marketable securities and those resulting from increases in the carrying amount of long-term assets. [CF(2010) 4.31]. The 2018 Conceptual Framework for Financial Reporting no longer contains a discussion about revenue and gains and losses. However, the definition of revenue in IFRS 15 remains unchanged. The Board does not expect the removal of that discussion to cause any changes in practice. [CF BC4.96].

The rules on offset in IAS 1 – Presentation of Financial Statements – distinguish between revenue and gains. That standard states that an entity undertakes, in the course of its ordinary activities, other transactions that do not generate revenue but are incidental to the main revenue-generating activities. When this presentation reflects the substance of the transaction or other event, the results of such transactions are presented by netting any income with related expenses arising on the same transaction. For example, gains and losses on the disposal of non-current assets, including investments and operating assets, are reported by deducting from the proceeds on disposal the carrying amount of the asset and related selling expenses. [IAS 1.34]. IAS 16 – Property, Plant and Equipment – has a general rule that ‘gains shall not be classified as revenue’. [IAS 16.68]. The only exception to this rule is where an entity routinely sells property, plant and equipment (PP&E) that it has held for rental to others, which is discussed further at 4.3.1 below.

2 IFRS 15 – OBJECTIVE AND OVERVIEW

IFRS 15 provides accounting requirements for all revenue arising from contracts with customers. It affects all entities that enter into contracts to provide goods or services to their customers, unless the contracts are in the scope of other IFRSs, such as the leasing standard. The standard, which is largely converged with the revenue guidance in US GAAP, also specifies the accounting for costs an entity incurs to obtain and fulfil a contract to provide goods or services to customers (see Chapter 31 at 5) and provides a model for the measurement and recognition of gains and losses on the sale of certain non-financial assets, such as property, plant or equipment (see 4.3 below).

As a result, entities that adopted the standard often found implementation to be a significant undertaking. This is because the standard requires entities to make more judgements and estimates and affects entities’ financial statements, business processes and internal controls over financial reporting.

While entities are now more familiar with its requirements, application of IFRS 15 continues to be challenging for them when business practices evolve and operating environments change, raising new implementation questions. For example, during and because of the coronavirus pandemic, areas that may be affected for revenue contracts include, but are not limited to, variable consideration, contract modifications and terminations, collectability and any extended payment terms, customer incentives and changes to selling prices, onerous contracts and capitalised contract costs.

Following the issuance of their revenue standards, the IASB and the US Financial Accounting Standards Board (FASB) (collectively, the Boards) created the Joint Transition Resource Group for Revenue Recognition (TRG) to help them determine whether more application guidance was needed. TRG members included financial statement preparers, auditors and other users from a variety of industries and countries, as well as public and private entities. Members of the joint TRG met six times in 2014 and 2015, and members of the FASB TRG met twice in 2016.TRG members’ views are non-authoritative, but entities should consider them as they implement the standards. In its July 2016 public statement, the European Securities and Markets Authority (ESMA) encouraged issuers to consider the TRG discussions when implementing IFRS 15. Furthermore, the former Chief Accountant of the US Securities and Exchange Commission (SEC) encouraged SEC registrants, including foreign private issuers (that may report under IFRS), to consult with his office if they are considering applying the standard in a manner that differs from the discussions in which TRG members reached general agreement.1

We have incorporated our summaries of topics on which TRG members generally agreed throughout this chapter. Unless otherwise specified, these summaries represent the discussions of the joint TRG. Where possible, we indicate if members of the IASB or its staff commented on the FASB TRG discussions.

This chapter discusses the IASB's standard (including all amendments) and highlights significant differences from the FASB's standard, Accounting Standards Codification (ASC) 606 – Revenue from Contracts with Customers. Throughout this chapter and Chapters 2832, when we refer to the FASB's standard, we mean ASC 606 (including any amendments), unless otherwise noted. It also addresses topics on which the members of the TRG reached general agreement and our views on certain topics.

The views we express in this chapter may evolve as application issues are identified and discussed among stakeholders. The conclusions we describe in our illustrations are also subject to change as views evolve. Conclusions in seemingly similar situations may differ from those reached in the illustrations due to differences in the underlying facts and circumstances.

2.1 Overview of the standard

The revenue standards that the Boards issued in May 2014 were largely converged and superseded virtually all legacy revenue recognition requirements in IFRS and US GAAP, respectively. The Boards’ goal in the joint deliberations was to develop new revenue standards that:

  • remove inconsistencies and weaknesses in the legacy revenue recognition literature;
  • provide a more robust framework for addressing revenue recognition issues;
  • improve comparability of revenue recognition practices across industries, entities within those industries, jurisdictions and capital markets;
  • reduce the complexity of applying revenue recognition requirements by reducing the volume of the relevant standards and interpretations; and
  • provide more useful information to users through expanded disclosure requirements. [IFRS 15(2016).IN5].2

The standards provide accounting requirements for all revenue arising from contracts with customers. They affect all entities that enter into contracts to provide goods or services to their customers, unless the contracts are in the scope of other IFRSs or US GAAP requirements, such as those for leasing. The standards also specify the accounting for costs an entity incurs to obtain and fulfil a contract to provide goods or services to customers (see Chapter 31 at 5) and provide a model for the measurement and recognition of gains and losses on the sale of certain non-financial assets, such as property, plant or equipment (see 4.3 below). IFRS 15 replaced all of the legacy revenue standards and interpretations in IFRS, including IAS 11 – Construction Contracts, IAS 18 – Revenue, IFRIC 13 – Customer Loyalty Programmes, IFRIC 15 – Agreements for the Construction of Real Estate, IFRIC 18 – Transfers of Assets from Customers – and SIC‑31 – Revenue – Barter Transactions Involving Advertising Services (legacy revenue requirements or legacy IFRS). [IFRS 15.C10].

IFRS 15 became effective for annual reporting periods beginning on or after 1 January 2018. Early adoption was permitted, provided that fact was disclosed. [IFRS 15.C1].

IFRS 15 required retrospective application. However, it allowed either a ‘full retrospective’ adoption (in which the standard was applied retrospectively to all of the periods presented in accordance with IAS 8 – Accounting Policies, Changes in Accounting Estimates and Errors) or a ‘modified retrospective’ adoption (in which the standard was applied retrospectively to only the most current period presented in the financial statements). Under both transition methods, the IASB granted transition practical expedients to provide relief.

Depending on the manner in which an entity elected to transition to IFRS 15, it may not have needed to apply the standard to contracts if they had completed performance before the date of initial application or the beginning of the earliest period presented (depending on the practical expedient and the transition method), even if they had not yet received the consideration and that consideration was still subject to variability. Applying a completed contract practical expedient might also have affected an entity's revenue recognition in subsequent reporting periods. That is, if an entity applied a practical expedient for completed contracts, it continued to apply its legacy revenue policy to its completed contracts, instead of IFRS 15. In some cases, even though an entity will have fully transferred its identified goods or services, there may still be revenue to recognise in accordance with its legacy revenue policy in reporting periods after adoption of IFRS 15.

The FASB's standard became effective for public entities, as defined,3 for annual reporting periods beginning after 15 December 2017 and interim periods therein. Non-public entities (i.e. an entity that does not meet the definition of a public entity in the FASB's standard) were required to adopt the standard for annual reporting periods beginning after 15 December 2018 and for interim periods within annual reporting periods beginning after 15 December 2019. That is, non-public entities were not required to apply the standard in interim periods in the year of adoption.

However, in June 2020, the FASB deferred by one year the effective date for entities that had not yet issued financial statements or made financial statements available for issuance that reflected the standard as of 3 June 2020 (i.e. certain non-public and not-for-profit entities). These entities are now required to adopt the standard for annual reporting periods beginning after 15 December 2019, and interim periods within annual reporting periods beginning after 15 December 2020. Early adoption is permitted.

After issuing the standards, the Boards issued converged amendments on certain topics (e.g. principal versus agent considerations) and different amendments on other topics (e.g. licences of intellectual property). The FASB also issued several amendments that the IASB has not issued (e.g. non-cash consideration). See 2.1.2 below for a discussion of the changes to the standards since issuance. While we address the significant differences between the IASB's final standard and the FASB's final standard throughout this chapter and in Chapters 2832, the primary purpose of this chapter, and Chapters 2832, is to describe the IASB's standard, including all amendments to date, and focus on the effects for IFRS preparers. As such, we generally refer to the ‘standard’ in the singular in this chapter and in Chapters 2832.

2.1.1 Core principle of the standard

The standard describes the principles an entity must apply to measure and recognise revenue and the related cash flows. [IFRS 15.1]. The core principle is that an entity recognises revenue at an amount that reflects the consideration to which the entity expects to be entitled in exchange for transferring goods or services to a customer. [IFRS 15.2].

The principles in IFRS 15 are applied using the following five steps:

  1. Identify the contract(s) with a customer.
  2. Identify the performance obligations in the contract.
  3. Determine the transaction price.
  4. Allocate the transaction price to the performance obligations in the contract.
  5. Recognise revenue when (or as) the entity satisfies a performance obligation.

Entities need to exercise judgement when considering the terms of the contract(s) and all of the facts and circumstances, including implied contract terms. Entities also have to apply the requirements of the standard consistently to contracts with similar characteristics and in similar circumstances. [IFRS 15.3]. To assist entities, IFRS 15 includes detailed application guidance. The IASB also published more than 60 illustrative examples that accompany IFRS 15.

2.1.2 Changes to the standard since issuance

Since the issuance of the standards, the Boards have issued various amendments to their respective standards, as summarised below. The Boards did not agree on the nature and breadth of all of the changes to their respective revenue standards. However, the Boards have said they expect the amendments to result in similar outcomes in many circumstances. No further changes to the standard are currently expected.

In September 2015, the IASB deferred the effective date of IFRS 15 by one year to give entities more time to implement it.4 In addition, in April 2016, the IASB issued Clarifications to IFRS 15 – Revenue from Contracts with Customers (the IASB's amendments) that addressed several implementation issues (many of which were discussed by the TRG) on key aspects of the standard.

The IASB's amendments:

  • clarified when a promised good or service is separately identifiable from other promises in a contract (i.e. distinct within the context of the contract), which is part of an entity's assessment of whether a promised good or service is a performance obligation (see Chapter 28 at 3.2);
  • clarified how to apply the principal versus agent application guidance to determine whether the nature of an entity's promise is to provide a promised good or service itself (i.e. the entity is a principal) or to arrange for goods or services to be provided by another party (i.e. the entity is an agent) (see Chapter 28 at 3.4);
  • clarified for a licence of intellectual property when an entity's activities significantly affect the intellectual property to which the customer has rights, which is a factor in determining whether the entity recognises revenue over time or at a point in time (see Chapter 31 at 2);
  • clarified the scope of the exception for sales-based and usage-based royalties related to licences of intellectual property (the royalty recognition constraint) when there are other promised goods or services in the contract (see Chapter 31 at 2.5); and
  • added two practical expedients to the transition requirements of IFRS 15 for: (a) completed contracts under the full retrospective transition method; and (b) contract modifications at transition.

The FASB also deferred the effective date of its standard by one year for US GAAP public and non-public entities, as defined, which kept the standards’ effective dates converged under IFRS and US GAAP. However, as discussed at 2.1 above, in June 2020, the FASB deferred by one year the effective date for entities that had not yet issued financial statements or made financial statements available for issuance that reflected the standard as of 3 June 2020 (i.e. certain non-public and not-for-profit entities).

Like the IASB, the FASB also amended its revenue standard to address principal versus agent considerations, identifying performance obligations, licences of intellectual property and certain practical expedients on transition.5 The FASB's amendments for principal versus agent considerations and clarifying when a promised good or service is separately identifiable when identifying performance obligations were converged with those of the IASB discussed above. However, the FASB's other amendments were not the same as those of the IASB. The FASB also issued amendments, which the IASB did not, relating to immaterial goods or services in a contract, accounting for shipping and handling, collectability, non-cash consideration, consideration payable to a customer, the presentation of sales and other similar taxes, the measurement and recognition of gains and losses on the sale of non-financial assets (e.g. PP&E) and other technical corrections. We describe the significant differences between the IASB's final standard and the FASB's final standard throughout this chapter and in Chapters 2832.

2.2 Definitions

The following table summarises the terms that are defined in IFRS 15. [IFRS 15 Appendix A].

Term Definition
Contract An agreement between two or more parties that creates enforceable rights and obligations.
Contract asset An entity's right to consideration in exchange for goods or services that the entity has transferred to a customer when that right is conditioned on something other than the passage of time (for example, the entity's future performance).
Contract liability An entity's obligation to transfer goods or services to a customer for which the entity has received consideration (or the amount is due) from the customer.
Customer A party that has contracted with an entity to obtain goods or services that are an output of the entity's ordinary activities in exchange for consideration.
Income Increases in economic benefits during the accounting period in the form of inflows or enhancements of assets or decreases of liabilities that result in an increase in equity, other than those relating to contributions from equity participants.
Performance obligation A promise in a contract with a customer to transfer to the customer either:
  1. a good or service (or a bundle of goods or services) that is distinct; or
  2. a series of distinct goods or services that are substantially the same and that have the same pattern of transfer to the customer.
Revenue Income arising in the course of an entity's ordinary activities.
Stand-alone selling price
(of a good or service)
The price at which an entity would sell a promised good or service separately to a customer.
Transaction price
(for a contract with a customer)
The amount of consideration to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer, excluding amounts collected on behalf of third parties.

Figure 27.1: IFRS 15 Definitions

3 IFRS 15 – SCOPE

3.1 Scope of IFRS 15

IFRS 15 applies to all entities and all contracts with customers to provide goods or services in the ordinary course of business, except for the following contracts, which are specifically excluded: [IFRS 15.5]

  • lease contracts within the scope of IFRS 16;
  • insurance contracts within the scope of IFRS 4 – Insurance Contracts (or, when effective, contracts within the scope of IFRS 17 – Insurance Contracts – except when an entity elects to apply IFRS 15 to certain service contracts in accordance with paragraph 8 of IFRS 17);
  • financial instruments and other contractual rights or obligations within the scope of IFRS 9, IFRS 10 – Consolidated Financial Statements, IFRS 11 – Joint Arrangements, IAS 27 – Separate Financial Statements – and IAS 28 – Investments in Associates and Joint Ventures; and
  • non-monetary exchanges between entities in the same line of business to facilitate sales to customers or potential customers.

Arrangements must meet the criteria set out in paragraph 9 of IFRS 15, which are discussed in Chapter 28 at 2.1, to be accounted for as a revenue contract under the standard.

For certain arrangements, entities have to evaluate their relationship with the counterparty to the contract in order to determine whether a vendor-customer relationship exists. Some collaboration arrangements, for example, are more akin to a partnership, while others have a vendor-customer relationship. Only transactions that are determined to be with a customer are within the scope of IFRS 15. The definition of a customer is discussed at 3.3 below. See 3.4 below for a discussion on collaborative arrangements.

The interaction between IFRS 15 and other standards can be challenging and may require significant judgement. Such interactions with IFRS 15 include when:

  • an entity needs to apply other standards’ requirements to assets and liabilities arising from a revenue contract (e.g. applying certain requirements in IFRS 9 to contract assets, determining an entity's right to consideration becomes unconditional (i.e. a receivable) such that IFRS 9 applies to that asset instead of IFRS 15, discussed in Chapter 32 at 2.1);
  • other standards refer to guidance in IFRS 15 (e.g. the accounting for disposals of certain non-financial assets (as discussed at 4.3 below), applying requirements in IFRS 15 to service concession arrangements that are within the scope of IFRIC 12 – Service Concession Arrangements – See Chapter 25);
  • two or more contracts need to be assessed together to determine the appropriate standard(s) to apply (e.g. sales with repurchase agreements (discussed in Chapter 30 at 5), sale and leaseback arrangements within the scope of IFRS 16) or the legal form of the arrangement is not consistent with the substance. When developing IFRS 16, the IASB noted that constituents had questions about how to distinguish between a lease and a sale or purchase when legal title to the underlying asset is not transferred. [IFRS 15.BC79]. If an arrangement does not meet the definition of a lease because the ‘lessor’ has a substantive right to substitute the underlying asset throughout the period of use and hence is out of scope of IFRS 16 (see Chapter 23 at 2.2), that entity may be providing a service within the scope of IFRS 15. The IASB decided not to provide requirements in this area and noted that the accounting for such leases would be similar to the sale or purchase of the respective asset and that the accounting also depends on the substance of the transaction and not its legal form. [IFRS 15.BC138-BC139]. Refer to Chapter 23, for more information on IFRS 16; and
  • a contract falls within the scope of more than one standard (e.g. lease with a non-lease revenue component, a contract that includes the issuance of a financial instrument and a revenue component within the scope of IFRS 15). When entities enter into transactions that are partially within the scope of IFRS 15 and partially within the scope of other standards, the standard requires an entity to apply any separation and/or measurement requirements in the other standard first, before applying the requirements in IFRS 15. See 3.5 below for further discussion.

As noted above, when effective, IFRS 17 could change the applicable standard for certain service contracts, specifically fixed-fee service contracts, which are contracts in which the level of service depends on an uncertain event. Examples include roadside assistance programmes and maintenance contracts in which the service provider agrees to repair specified equipment after a malfunction for a fixed fee. IFRS 17 indicates that these are insurance contracts and, therefore, when it is effective, that standard would apply. However, if their primary purpose is the provision of services for a fixed fee, IFRS 17 permits entities the choice of applying IFRS 15 instead of IFRS 17 to such contracts if, and only if, all of the following conditions are met: [IFRS 17.8]

  • the entity does not reflect an assessment of the risk associated with an individual customer in setting the price of the contract with that customer;
  • the contract compensates the customer by providing services, rather than by making cash payments to the customer; and
  • the insurance risk transferred by the contract arises primarily from the customer's use of services rather than from uncertainty over the cost of those services.

The entity may make that choice on a contract by contract basis, but the choice for each contract is irrevocable. IFRS 17 is effective for annual periods beginning on or after 1 January 2023. See Chapter 56 at 2.3.2 for further discussion.

IFRS 9 became effective for annual periods beginning on or after 1 January 2018, superseding IAS 39 – Financial Instruments: Recognition and Measurement. However, entities that are applying IFRS 4, have an optional temporary exemption that permits an insurance company whose activities are predominantly connected with insurance to defer adoption of IFRS 9. If an entity uses this optional exemption, it continues to apply IAS 39 until it first applies IFRS 17. References to IFRS 9 in this chapter, and Chapters 2832, are generally also relevant for IAS 39.

3.1.1 Non-monetary exchanges

IFRS 15 does not apply to non-monetary exchanges between entities in the same line of business to facilitate sales to (potential) customers. For example, the standard does not apply to a contract between two oil companies that swap oil to fulfil demand from their respective customers in different locations on a timely basis and to reduce transportation costs. This scope exclusion applies even though the party exchanging goods or services with the entity might meet the definition of a customer on the basis that it has contracted with the entity to obtain an output of the entity's ordinary activities. As discussed in the Basis for Conclusions, this type of scenario may be common in industries with homogeneous products. [IFRS 15.BC58]. Not all non-monetary exchanges between entities are outside the scope of IFRS 15 and the standard does provide requirements for contracts involving non-cash consideration in exchange for goods or services (see Chapter 29 at 2.6 on non-cash consideration and at 2.6.2 on barter transactions). Therefore, determining whether an exchange is to facilitate a sale to a customer may require judgement. Judgement may also be needed to determine whether entities are in the same line of business.

The following examples illustrate some of these considerations:

3.2 Other scope considerations

Certain arrangements executed by entities include repurchase provisions, either as a component of a sales contract or as a separate contract that relates to the same or similar goods in the original agreement. The form of the repurchase agreement and whether the customer obtains control of the asset will determine whether the agreement is within the scope of the standard. See Chapter 30 at 5 for a discussion on repurchase agreements.

IFRS 15 also specifies the accounting for certain costs, such as the incremental costs of obtaining a contract and the costs of fulfilling a contract. However, the standard is clear that these requirements only apply if there are no other applicable requirements in IFRS for those costs. [IFRS 15.8]. See Chapter 31 at 5 for further discussion on the requirements relating to contract costs in the standard.

Certain requirements in IFRS 15 are also relevant for the recognition and measurement of a gain or loss on the disposal of a non-financial asset not in the ordinary course of business. See 4.3 below for further discussion.

3.3 Definition of a customer

The standard defines a customer as ‘a party that has contracted with an entity to obtain goods or services that are an output of the entity's ordinary activities in exchange for consideration’. [IFRS 15 Appendix A]. IFRS 15 does not define the term ‘ordinary activities’ because it was derived from the definitions of revenue in the respective conceptual frameworks of the IASB and the FASB in effect when the standards were developed. In particular, the description of revenue in the IASB's Conceptual Framework for Financial Reporting at that time referred specifically to the ‘ordinary activities’ of an entity – [CF(2010) 4.29, IFRS 15 Appendix A] – and the definition of revenue in the FASB's Statement of Financial Accounting Concepts No. 6 refers to the notion of an entity's ‘ongoing major or central operations’.6 In many transactions, a customer is easily identifiable. However, in transactions involving multiple parties, it may be less clear which counterparties are customers of the entity. For some arrangements, multiple parties could all be considered customers of the entity. However, for other arrangements, only some of the parties involved are considered customers.

During the coronavirus pandemic, governments often granted additional and wide-ranging assistance, particularly during periods involving restrictions on business activities. Any entity will need to evaluate whether there is a vendor-customer relationship even when the counterparty is a government or similar body. To determine the appropriate standard to apply, an entity needs to consider all relevant facts and circumstances to understand whether there is an exchange transaction arising from a vendor-customer relationship (to which IFRS 15 applies) or if, for example, the entity is receiving government assistance or a grant (as defined in IAS 20 – Accounting for Government Grants and Disclosure of Government Assistance – see Chapter 24). Factors to consider would include, but not be limited to, whether the government (or similar body) is providing assistance to the entity or to its customer (e.g. by paying the entity on a customer's behalf), and whether the government (or similar body) is providing assistance in their capacity as the government (or similar body) or as the entity's customer. An entity with an existing vendor-customer relationship with a government or similar body also needs to evaluate whether any additional assistance is a modification of a customer contract under IFRS 15. See Chapter 28 at 2.4 for contract modifications.

Example 27.3 below shows how the party considered to be the customer may differ, depending on the specific facts and circumstances.

In addition, the identification of the performance obligations in a contract (discussed further in Chapter 28 at 3) can have a significant effect on the determination of which party is the entity's customer. Also see the discussion of the identification of an entity's customer when applying the application guidance on consideration paid or payable to a customer in Chapter 29 at 2.7.

3.4 Collaborative arrangements

Entities often enter into collaborative arrangements to, for example, jointly develop and commercialise intellectual property (such as a drug candidate in the life sciences industry or a motion picture in the entertainment industry). In such arrangements, a counterparty may not always be a ‘customer’ of the entity. Instead, the counterparty may be a collaborator or partner that shares in the risks and benefits of developing a product to be marketed. [IFRS 15.6]. This is common in the pharmaceutical, bio-technology, oil and gas, and health care industries. However, depending on the facts and circumstances, these arrangements may also contain a vendor-customer relationship component. Such contracts could still be within the scope of IFRS 15, at least partially, if the collaborator or partner meets the definition of a customer for some, or all, aspects of the arrangement. If the collaborator or partner is not a customer, the transaction is not within the scope of IFRS 15. An example of transactions between collaborators or partners not being within the scope of IFRS 15 was discussed by the IFRS Interpretations Committee in March 2019; it related to the output to which an entity is entitled from a joint operation, but which the entity has not yet received and sold to its customers (see 3.5.1.K below).

The IASB decided not to provide additional application guidance for determining whether certain revenue-generating collaborative arrangements are within the scope of IFRS 15. In the Basis for Conclusions, the IASB explained that it would not be possible to provide application guidance that applies to all collaborative arrangements. [IFRS 15.BC54]. Therefore, the parties to such arrangements need to consider all facts and circumstances to determine whether a vendor-customer relationship exists that is subject to the standard.

However, the IASB did determine that, in some circumstances, it may be appropriate for an entity to apply the principles in IFRS 15 to collaborations or partnerships (e.g. when there are no applicable or more relevant requirements that could be applied). [IFRS 15.BC56].

Identifying the customer can be difficult, especially when multiple parties are involved in a transaction. This evaluation may require significant judgement and IFRS 15 does not provide many factors to consider.

Furthermore, transactions among partners in collaboration arrangements are not within the scope of IFRS 15. Therefore, entities need to use judgement to determine whether transactions are between partners acting in their capacity as collaborators or reflect a vendor-customer relationship.

3.5 Interaction with other standards

The standard provides requirements for arrangements partially within the scope of IFRS 15 and partially within the scope of other standards. IFRS 15 states that if the other standards specify how to separate and/or initially measure one or more parts of the contract, then an entity shall first apply the separation and/or measurement requirements in those standards. An entity shall exclude from the transaction price (as discussed in Chapter 29 at 2) the amount of the part (or parts) of the contract that are initially measured in accordance with other standards and shall apply the allocation requirements in IFRS 15 (as discussed in Chapter 29 at 3) to allocate the amount of the transaction price that remains (if any) to each performance obligation within the scope of IFRS 15. If the other standards do not specify how to separate and/or initially measure one or more parts of the contract, then the entity shall apply IFRS 15 to separate and/or initially measure the part (or parts) of the contract. [IFRS 15.7]. Figure 27.2 illustrates these requirements.

image

Figure 27.2: Interactions with other standards

If a component of the arrangement is covered by another standard or interpretation that specifies how to separate and/or initially measure that component, the entity needs to apply IFRS 15 to the remaining components of the arrangement. Some examples of where separation and/or initial measurement are addressed in other IFRS include the following:

  • IFRS 9 generally requires that a financial instrument be recognised at fair value at initial recognition. For contracts that include the issuance of a financial instrument and revenue components within the scope of IFRS 15 and the financial instrument is required to be initially recognised at fair value, the fair value of the financial instrument is first measured and the remainder of the estimated contract consideration is allocated among the other components in the contract in accordance with IFRS 15.
  • A contract may contain a lease coupled with an agreement to sell other goods or services (e.g. subject to IFRS 15). IFRS 16 requires that a lessor accounts separately for the lease component (in accordance with IFRS 16) and any non-lease components (in accordance with other standards) and provides application guidance on separating the components of such a contract. [IFRS 16.12, B32, B33]. A lessor allocates the consideration in a contract that contains a lease component and one or more additional lease or non-lease components by applying the requirements in IFRS 15 for allocating the transaction price to performance obligations and changes in the transaction price after contract inception (see Chapter 29). [IFRS 16.17]. Care may be needed in such an allocation if the lease term (under IFRS 16) and the contract duration (under IFRS 15) differ. Refer to Chapter 23 for more information on IFRS 16.

Conversely, if a component of the arrangement is covered by another standard or interpretation, but that standard or interpretation does not specify how to separate and/or initially measure that component, the entity needs to apply IFRS 15 to separate and/or initially measure each component. For example, specific requirements do not exist for the separation and measurement of the different parts of an arrangement when an entity sells a business and also enters into a long-term supply agreement with the other party. See Chapter 29 at 3.6 for further discussion on the effect on the allocation of arrangement consideration when an arrangement includes both revenue and non-revenue components.

3.5.1 Application questions on scope

3.5.1.A Islamic financing transactions

Islamic financial institutions (IFIs) enter into Sharia-compliant instruments and transactions that do not result in IFIs earning interest on loans. Instead, these transactions involve purchases and sales of real assets (e.g. vehicles) on which IFIs can earn a premium to compensate them for deferred payment terms. Typically, an IFI makes a cash purchase of the underlying asset, takes legal possession, even if only for a short time, and immediately sells the asset on deferred payment terms. The financial instruments created by these transactions are within the scope of the financial instruments standards.7

At the January 2015 TRG meeting, the IASB TRG members discussed whether (before applying the financial instruments standards) deferred-payment transactions that are part of Sharia-compliant instruments and transactions are within the scope of IFRS 15. The IASB TRG members generally agreed that Sharia-compliant instruments and transactions may be outside the scope of the standard. However, the analysis depends on the specific facts and circumstances. This may require significant judgement as contracts often differ within and between jurisdictions. The FASB TRG members did not discuss this issue.8

3.5.1.B Certain fee-generating activities of financial institutions

The TRG considered an issue raised by US GAAP stakeholders whether certain fee-generating activities of financial institutions are in the scope of the revenue standard (i.e. servicing and sub-servicing financial assets, providing financial guarantees and providing deposit-related services).9

The FASB TRG members generally agreed that the standard provides a framework for determining whether certain contracts are in the scope of the FASB's standard, ASC 606, or other standards. As discussed above, the standard's scope includes all contracts with customers to provide goods or services in the ordinary course of business, except for contracts with customers that are within the scope of certain other ASC topics that are listed as scope exclusions. If another standard specifies the accounting for the consideration (e.g. a fee) received in the arrangement, the consideration is outside the scope of ASC 606. If other standards do not specify the accounting for the consideration and there is a separate good or service provided, the consideration is in (or at least partially in) the scope of ASC 606. The FASB staff applied this framework in the TRG agenda paper to arrangements to service financial assets, provide financial guarantees and provide deposit-related services.

The FASB TRG members generally agreed that income from servicing financial assets (e.g. loans) is not within the scope of ASC 606. An asset servicer performs various services, such as communication with the borrower and payment collection, in exchange for a fee. The FASB TRG members generally agreed that an entity should look to ASC 860 – Transfers and Servicing – to determine the appropriate accounting for these fees. This is because ASC 606 contains a scope exception for contracts that fall under ASC 860, which provides requirements on the recognition of the fees (despite not providing explicit requirements on revenue accounting).

The FASB TRG members generally agreed that fees from providing financial guarantees are not within the scope of ASC 606. A financial institution may receive a fee for providing a guarantee of a loan. These types of financial guarantees are generally within the scope of ASC 460 – Guarantees – or ASC 815 – Derivatives and Hedging. The FASB TRG members generally agreed that an entity should look to ASC 460 or ASC 815 to determine the appropriate accounting for these fees. This is because ASC 606 contains a scope exception for contracts that fall within those topics, which provide principles an entity can follow to determine the appropriate accounting to reflect the financial guarantor's release from risk (and credit to earnings).

The FASB TRG members also generally agreed that fees from deposit-related services are within the scope of ASC 606. In contrast to the decisions for servicing income and financial guarantees, the guidance in ASC 405 – Liabilities – that financial institutions apply to determine the appropriate liability accounting for customer deposits, does not provide a model for recognising fees related to customer deposits (e.g. ATM fees, account maintenance or dormancy fees). Accordingly, the FASB TRG members generally agreed that deposit fees and charges are within the scope of ASC 606, even though ASC 405 is listed as a scope exception in ASC 606, because of the lack of guidance on the accounting for these fees in ASC 405.

It should be noted that, while this was not specifically discussed by the IASB TRG, IFRS preparers may find the FASB TRG's discussions helpful in assessing whether certain contracts are within the scope of IFRS 15 or other standards.

3.5.1.C Credit card arrangements

A bank that issues credit cards can have various income streams (e.g. annual fees) from a cardholder under various credit card arrangements. Some of these fees may entitle cardholders to ancillary services (e.g. concierge services, airport lounge access). The card issuer may also provide rewards to cardholders based on their purchases. At the July 2015 TRG meeting, the TRG members discussed a question raised by US GAAP stakeholders regarding whether such fees and programmes are within the scope of the revenue standard, particularly when a good or service is provided to a cardholder.10

While this question was only raised by US GAAP stakeholders, IASB TRG members generally agreed that an IFRS preparer first needs to determine whether the credit card fees are within the scope of IFRS 9. IFRS 9 requires that any fees that are an integral part of the effective interest rate for a financial instrument be treated as an adjustment to the effective interest rate. Conversely, any fees that are not an integral part of the effective interest rate of the financial instrument are generally accounted for under IFRS 15.

The FASB TRG members generally agreed that credit card fees that are accounted for under ASC 310 – Receivables – are not in the scope of ASC 606. This includes annual fees that may entitle cardholders to ancillary services. The FASB TRG members noted that this conclusion is consistent with legacy US GAAP requirements for credit card fees. However, the observer from the US SEC noted that the nature of the arrangement must truly be that of a credit card lending arrangement in order to be in the scope of ASC 310. As such, entities need to continue evaluating their arrangements as new programmes develop. Credit card fees could, therefore, be treated differently under IFRS and US GAAP.

3.5.1.D Credit card-holder rewards programmes

The FASB TRG members also discussed whether cardholder rewards programmes are within the scope of ASC 606. The FASB TRG members generally agreed that if all consideration (i.e. credit card fees discussed at 3.5.1.C above) related to the rewards programme is determined to be within the scope of ASC 310, the rewards programme is not in the scope of ASC 606. However, this determination has to be made based on the facts and circumstances due to the wide variety of credit card reward programmes offered. The IASB TRG members did not discuss this issue because the question was only raised in relation to US GAAP.11

3.5.1.E Contributions

The FASB amended ASC 606 to clarify that an entity needs to consider the requirements in ASC 958‑605 – Not-for-Profit Entities – Revenue Recognition – when determining whether a transaction is a contribution (as defined in the ASC Master Glossary) within the scope of ASC 958‑605 or a transaction within the scope of ASC 606.12 The requirements for contributions received in ASC 958‑605 generally apply to all entities that receive contributions (i.e. not just not-for-profit entities), unless otherwise indicated.

Before the amendment, FASB TRG members discussed this issue in March 2015 and generally agreed that contributions are not within the scope of ASC 606 because they are non-reciprocal transfers. That is, contributions generally do not represent consideration given in exchange for goods or services that are an output of the entity's ordinary activities. The IASB TRG members did not discuss this issue because the question was only raised in the context of US GAAP.13

3.5.1.F Fixed-odds wagering contracts

In fixed-odds wagering contracts, the payout for wagers placed on gambling activities (e.g. table games, slot machines, sports betting) is known at the time the wager is placed.

Under IFRS, consistent with a July 2007 IFRS Interpretations Committee agenda decision, wagers that meet the definition of a derivative are within the scope of IFRS 9. Those that do not meet the definition of a derivative are within the scope of IFRS 15.

Under US GAAP, the FASB added scope exceptions in ASC 815 and ASC 924 – Entertainment – Casinos – in December 2016 to clarify that fixed-odds wagering arrangements are within the scope of ASC 606.

3.5.1.G Pre-production activities related to long-term supply arrangements

In some long-term supply arrangements, entities perform upfront engineering and design activities to create new technology or adapt existing technology according to the needs of the customer. These pre-production activities are often a prerequisite to delivering any units under a production contract.

Entities need to evaluate whether the pre-production activities are promises in a contract with a customer (and potentially performance obligations) under IFRS 15. When making this evaluation, entities need to determine whether the activities transfer a good or service to a customer. Refer to Chapter 28 at 3.1.1.A for further discussion on determining whether pre-production activities are promised goods or services under IFRS 15. If an entity determines that these activities are promised goods or services, it will apply the requirements in IFRS 15 to those goods or services.

3.5.1.H Sales of by-products or scrap materials

Consider an example in which a consumer products entity sells by-products or accumulated scrap materials that are produced as a result of its manufacturing process. In determining whether the sale of by-products or scrap materials to third parties is in the scope of IFRS 15, an entity first determines whether the sale of such items is an output of the entity's ordinary activities. This is because IFRS 15 defines revenue as ‘income arising in the course of an entity's ordinary activities’. [IFRS 15 Appendix A]. If an entity determines the sale of such items represents revenue from a contract with a customer, it would generally recognise the sale under IFRS 15.

If an entity determines that such sales are not in the course of its ordinary activities, the entity would recognise those sales separately from revenue from contracts with customers because they represent sales to non-customers.

We do not believe that it would be appropriate for an entity to recognise the sale of by-products or scrap materials as a reduction of cost of goods sold. This is because recognising the sale of by-products or scrap materials as a reduction of cost of goods sold may inappropriately reflect the cost of raw materials used in manufacturing the main product. However, this interpretation would not apply if other accounting standards allow for recognition as a reduction of costs.

IAS 2 – Inventories – requires that the costs of conversion of the main product and the by-product be allocated between the products on a rational and consistent basis. However, IAS 2 mentions that most by-products, by their nature, are immaterial. When this is the case, they are often measured at net realisable value and this value is deducted from the cost of the main product. As a result, the carrying amount of the main product is not materially different from its cost. We believe that the language in IAS 2 only relates to the allocation of the costs of conversion between the main product and by-product and does not allow the proceeds from the sale of by-products to be presented as a reduction of cost of goods sold.

3.5.1.I Prepaid gift cards

Entities may sell prepaid gift cards in their normal course of business in exchange for cash. The prepaid gift cards typically provide the customer with the right to redeem those cards in the future for goods or services of the entity and/or third parties. For any unused balance of the prepaid gift cards, entities need to recognise a liability that will be released upon redemption of that unused balance. However, the features of each prepaid gift card may vary and the nature of the liability depends on the assessment of these features. Entities may need to use judgement in order to determine whether the prepaid gift card is within the scope of IFRS 15 or another standard.

Prepaid gift cards that give rise to financial liabilities are within the scope of IFRS 9. If a prepaid gift card does not give rise to a financial liability it is likely to be within the scope of IFRS 15. For further information on applying IFRS 15 to prepaid gift cards within its scope refer to Chapter 30 at 11.

An example of a prepaid gift card that is within the scope of IFRS 9 was discussed by the IFRS Interpretations Committee at its March 2016 meeting. The issue related to the accounting treatment of any unused balance on a prepaid card issued by an entity in exchange for cash as well as the classification of the relevant liability that arises. The discussion was limited to prepaid cards that have the specific features described in the request to the IFRS Interpretations Committee.14 In particular, the prepaid card:

  1. has no expiry date and no back-end fees. That is, any unspent balance does not reduce unless it is spent by the cardholder;
  2. is non-refundable, non-redeemable and non-exchangeable for cash;
  3. can be redeemed only for goods or services to a specified monetary amount; and
  4. can be redeemed only at specified third-party merchants (the range of merchants accepting the specific card could vary depending on the card programme) and, upon redemption, the entity delivers cash to the merchant(s).

The IFRS Interpretations Committee observed that when an entity issues a prepaid card with the above features, it is contractually obliged to deliver cash to the merchants on behalf of the cardholder. Although this obligation is conditional upon the cardholder redeeming the card by purchasing goods or services, the entity's right to avoid delivering cash to settle this contractual obligation is not unconditional. On this basis, the IFRS Interpretations Committee concluded that the entity's liability for such a prepaid card meets the definition of a financial liability and would fall within the scope of IFRS 9 and IAS 32 – Financial Instruments: Presentation. Entities need to apply judgement to determine which standard applies depending upon the specific facts and circumstances for scenarios other than the one discussed by the IFRS Interpretations Committee in its March 2016 meeting. The IFRS Interpretations Committee also noted in its agenda decision that its discussion on this issue did not include customer loyalty programmes.15

3.5.1.J Determining whether IFRS 10 or IFRS 15 applies to the sale of a corporate wrapper to a customer

As part of their ordinary activities, entities may enter into contracts with customers to sell an asset by selling their equity interest in a separate entity (commonly referred to as a ‘corporate wrapper’ or ‘single-asset entity’) holding that asset (e.g. real estate), rather than by selling the asset itself. Entities may sell assets via a sale of equity interest in a corporate wrapper for tax or legal reasons or because of local regulation or business practice. Facts and circumstances may differ, for example, in relation to:

  • when the corporate wrapper is created and the asset transferred into it;
  • when the entity enters into a contract with a customer;
  • if the asset is constructed by the entity, when construction starts; and
  • when the equity interest in the corporate wrapper is legally transferred to the customer.

In addition, a corporate wrapper could include only one asset (plus a related deferred tax asset or liability) or one or more other assets or liabilities, such as a financing liability.

Whether an entity needs to apply IFRS 10 or IFRS 15 to the sale of a corporate wrapper to a customer depends on facts and circumstances and may require significant judgement, including consideration of the following:

  • IFRS 10 requires an entity that controls one or more entities (i.e. the parent) to present consolidated financial statements, with some limited exceptions, and sets out the requirements to determine whether, as an investor, it controls (and, therefore, must consolidate) an investee. A parent consolidates an entity that it controls (i.e. the subsidiary) from the date on which it first obtains control. It ceases consolidating that subsidiary on the date on which it loses control. [IFRS 10.2, 4‑4B, 20, Appendix A]. IFRS 10 also specifies how a parent accounts for the full or partial sale of a subsidiary. See Chapters 6 and 7 for further discussion.
  • IFRS 15 excludes from its scope ‘… financial instruments and other contractual rights or obligations within the scope of … IFRS 10’ (see 3.1 above). [IFRS 15.5(c)].

In practice, some entities apply IFRS 15 to all such contracts with customers because the transactions are part of the entity's ordinary activities and they believe doing so would better reflect the ‘substance’ of each transaction (e.g. the entity is ‘in substance’ selling the asset and not the equity interest; the structure is for legal, tax or risk reasons and they believe it should not affect the recognition of revenue).16

Judgement may also be needed in determining whether an investor controls the corporate wrapper. For example, the (selling) entity may act as an agent (in accordance with IFRS 10) in relation to the corporate wrapper based on the terms and conditions in the customer contract. IFRS 10 would not apply to the sale, if the entity does not control the corporate wrapper prior to sale.

In June 2019, the IFRS Interpretations Committee discussed a request about the accounting for a transaction in which an entity, as part of its ordinary activities, enters into a contract with a customer to sell real estate by selling its equity interest in a subsidiary. The entity established the subsidiary some time before it enters into the contract with the customer; the subsidiary has one asset (real estate inventory) and a related tax asset or liability. The entity has applied IFRS 10 in consolidating the subsidiary before it loses control of the subsidiary as a result of the transaction with the customer. The IFRS Interpretations Committee discussed this issue, but did not reach any decisions, at its June 2019 meeting.17 At the time of writing, the IFRS Committee had not issued an agenda decision on this matter. Instead, the issue was referred to the IASB.

In October 2019, the IASB directed its staff to research the feasibility of narrow-scope standard setting. In June 2020, the IASB discussed a possible narrow-scope amendment that would have required an entity to apply IFRS 15, instead of IFRS 10, to sales of subsidiaries where all of the following apply:

  • the entity contracts with a customer for goods or services that are the output of its ordinary activities in exchange for consideration;
  • the subsidiary contains only inventory and any related income tax asset or liability; and
  • the entity retains no interest in the inventory transferred to the customer.

the Board decided against proposing this amendment.18

During the discussions held by both the IFRS Interpretations Committee and the IASB, a number of members of the Committee and the Board considered that, absent an amendment, IFRS 10 (rather than IFRS 15) would apply to the transaction considered. During the June 2020 discussion, some Board members thought there was merit in a narrow-scope amendment. However, concerns were raised about potential unintended consequences of proposing a narrow-scope amendment without a more comprehensive discussion. Any narrow-scope amendment would affect the scope of both IFRS 10 and IFRS 15 and, as such, Board members wanted to learn more from stakeholders about the need for, and the consequences of, such a project.19 However, these considerations were not noted in the relevant IFRIC Update and IASB Update that were issued as summaries of the meetings. At the time of writing, this matter was expected to be considered as part of phase 2 of the post-implementation review (PIR) of IFRS 10, which was scheduled to commence in Q4 of 2020.20

Until the deliberation process on this question is completed, there may continue to be some diversity in practice. However, in the meantime, entities may need to consider the discussions on this matter as they determine the appropriate standard to apply to transactions with customers involving the loss of control of a single asset entity.

It should be noted that the applicable standard (i.e. IFRS 10 or IFRS 15) is not just a matter of presentation. That is, it may also affect, for example, the timing of recognition (i.e. point in time versus over time and, if point in time, the specific point in time) and the measurement of consideration (e.g. IFRS 10 does not constrain variable consideration). Furthermore, IFRS 10 provides specific requirements for the derecognition of all assets and liabilities of the former subsidiary on loss of control, which would not apply if the contract with the customer is within the scope of IFRS 15.

Under US GAAP, the sale of a corporate wrapper to a customer generally will be in the scope of ASC 606. ASC 810 – Consolidation – indicates that its deconsolidation and derecognition guidance does not apply to a loss of control of a subsidiary that is a business if that transaction is within the scope of ASC 606. Loss of control of a subsidiary that is not a business is equally excluded from the scope of ASC 810 if the substance of the transaction is within the scope of another standard (e.g. ASC 606, ASC 610‑20 – Other Income – Gains and Losses from Derecognition of Nonfinancial Assets). Therefore, the sale of a corporate wrapper to a counterparty that is not a customer may be in the scope of ASC 610‑20, which applies to the recognition of gains or losses on transfers of non-financial assets and in-substance non-financial assets, including transfers of these assets when included in a consolidated subsidiary, that are not businesses to counterparties that are not customers.

3.5.1.K Revenue arising from an interest in a joint operation

Revenue recognised in accordance with IFRS 15 must reflect an entity's performance in transferring a good or service to a customer.

Under IFRS 11, a joint operator is required to account for revenue relating to its interest in the joint operation (as defined in IFRS 11; see Chapter 12) by applying the standards that are applicable to the particular revenue. [IFRS 11.21]. Therefore, while contracts with joint operators are excluded from the scope of IFRS 15, if revenue relating to an interest in a joint operation under IFRS 11 arises from a contract with a customer, it is recognised in accordance with IFRS 15.

As discussed at 3.1 above, IFRS 15 applies only to contracts with customers. In addition, IFRS 11 requires a joint operator to recognise ‘its revenue from the sale of its share of the output arising from the joint operation’. [IFRS 11.20]. Therefore, revenue recognised by a joint operator must depict the output it has received from the joint operation and sold to customers, rather than the production of output or entitlement to output, as shown in Example 27.3 below.

This is consistent with the conclusion reached by the IFRS Interpretations Committee in March 2019. The IFRS Interpretations Committee discussed this issue using the following example:21

3.5.1.L Are equity instruments issued by an entity to a customer in connection with a revenue arrangement within the scope of the revenue standard?

Whether or not an entity needs to apply IFRS 15 to a transaction in which equity instruments (e.g. shares) are issued to a customer in connection with a revenue arrangement depends on the substance and purpose of the transaction.

Many entities make payments to their customers. In some cases, the consideration paid or payable represents purchases by the entity of goods or services offered by the customer that satisfy a business need of the entity. In other cases, the consideration paid or payable represents incentives given by the entity to entice the customer to purchase, or continue purchasing, its goods or services.

According to paragraph 7 of IFRS 15, a contract with a customer may be partially within the scope of IFRS 15 and partially within the scope of other standards. IFRS 15 does not specify whether equity instruments issued by an entity to a customer are a type of consideration paid or payable to customer. Nor does IFRS 2 – Share-based Payment – specifically address such transactions. Depending on the facts and circumstances, several standards (or a combination of standards) may be applicable (e.g. IFRS 2, IFRS 15, IAS 32). To determine the substance of the transaction and which standard(s) apply, entities will need to consider all relevant facts and circumstances, including the purpose of the transaction. Such determinations may require significant judgement.

In 2018, the FASB amended ASC 606 to clarify that equity instruments granted to customers in conjunction with the sale of goods or services (e.g. shares, options) are within the scope of the requirements for consideration payable to customers.22 The IASB has not proposed any similar amendments to IFRS 15. Therefore, entities applying IFRS could reach a different accounting conclusion from those applying US GAAP.

4 OTHER INCOME AND OTHER REVENUE

As income and revenue are defined broadly, not all income-generating transactions are in the scope of IFRS 15. As discussed at 3.1 above, an entity applies IFRS 15 only to a contract in which the counterparty to the contract meets the definition of a customer (unless the contract is specifically excluded from the scope of IFRS 15 (see 3.1 above for a list of scope exclusions)).

Below, we highlight some other items of income that are not within the scope of IFRS 15 and note whether they are covered by another standard. Some of these items of income may represent other revenue (i.e. non-IFRS 15 revenue) if part of the entity's ordinary activities.

4.1 Income and distributable profits

In general, IFRS does not address the issue of the distribution of profit. Whether or not revenue and gains recognised in accordance with IFRS are distributable to shareholders of an entity will depend entirely on the national laws and regulations with which the entity needs to comply. Thus, income reported in accordance with IFRS does not necessarily imply that such income would either be realised or distributable under a reporting entity's applicable national legislation.

4.2 Interest and dividends

Entities (e.g. financial institutions) may earn interest or dividends in the course of their ordinary activities and, therefore, present these transactions as revenue. The relevant recognition and measurement requirements are included in IFRS 9. These transactions are recognised as follows:

  • Interest: calculated by using the effective interest method [IFRS 9 Appendix A, IFRS 9.5.4.1, B5.4.1-B5.4.7] as discussed in Chapter 50 at 3;
  • Dividends: when the shareholder's right to receive payment is established, it is probable that the economic benefits associated with the dividend will flow to the entity and the amount of the dividend can be measured reliably. [IFRS 9.5.7.1A]. See Chapter 50 at 2.

4.3 Disposal of non-financial assets not in the ordinary course of business

When an entity disposes of an asset that is within the scope of IAS 16, IAS 38 – Intangible Assets – and IAS 40 – Investment Property – and that disposal is not part of the entity's ordinary activities, the transaction is within the scope of those standards, not IFRS 15. However, IAS 16, IAS 38 and IAS 40 require entities to use certain of the requirements of IFRS 15 when recognising and measuring gains or losses arising from the sale or disposal of non-financial assets.

IAS 16, IAS 38 and IAS 40 require that the gain or loss arising from the disposal of a non-financial asset be included in profit or loss when the item is derecognised, unless IFRS 16 requires otherwise on a sale and leaseback. IAS 16 and IAS 38 specifically prohibit classification of any such gain as revenue. [IAS 16.68, IAS 38.113, IAS 40.69]. This was reiterated by the IFRS Interpretations Committee in June 2020 in relation to the presentation of player transfer payments resulting from the sale of an intangible asset within the scope of IAS 38.23 However, IAS 16 mentions an exception in the case of entities that are in the business of renting and subsequently selling the same assets (discussed at 4.3.1 below). [IAS 16.68A]. IFRS 16 applies to disposal via a sale and leaseback. [IAS 16.69, IAS 38.113, IAS 40.67].

The gain or loss on disposal of a non-financial asset is the difference between the net disposal proceeds, if any, and the carrying amount of the item. [IAS 16.71, IAS 38.113, IAS 40.69]. Under IAS 16 or IAS 38, if an entity applies the revaluation model for measurement after initial recognition, any revaluation surplus relating to the asset disposed of is transferred within equity to retained earnings when the asset is derecognised and not reflected in profit or loss. [IAS 16.41, IAS 38.87].

As noted above, IAS 16, IAS 38 and IAS 40 provide a consistent model for the measurement and recognition of gains or losses on the sale or disposal of non-financial assets to non-customers (i.e. not in the ordinary course of business) by referring to the requirements in IFRS 15. For sales of non-financial assets to non-customers, IAS 16, IAS 38 and IAS 40 require entities to:

  • determine the date of disposal (and, therefore, derecognition of the asset) using the requirements in IFRS 15 for determining when a performance obligation is satisfied (i.e. Step 5 requirements, see Chapter 30); [IAS 16.69, IAS 38.114, IAS 40.67] and
  • measure the consideration that is included in the calculation of the gain or loss on disposal in accordance with the requirements for determining the transaction price (i.e. Step 3 requirements, see Chapter 29 at 2). Any subsequent changes to the estimate of the consideration (e.g. updates of variable consideration estimates, including reassessment of the constraint) are recognised in accordance with the requirements for changes in the transaction price. [IAS 16.72, IAS 38.116, IAS 40.70]. For example, if variable consideration is constrained at the time of disposal, it would not be recognised in profit or loss until it is no longer constrained, which could be in a subsequent period.

IFRS 5 – Non-current Assets Held for Sale and Discontinued Operations – provides additional requirements for assets that meet that standard's criteria to be classified as held for sale. These requirements include measurement provisions, which may affect the measurement of the amount of the subsequent gain or loss on disposal. These are discussed in Chapter 4 at 2.2.

IFRS 10 specifies how a parent accounts for the full or partial disposal of a subsidiary (see Chapter 7 for further discussion).24 The accounting treatment may, therefore, differ depending on whether a non-financial asset is sold on its own (in which case, IAS 16, IAS 38 or IAS 40 would apply) or included within a full or partial disposal of a subsidiary (in which case IFRS 10 would apply). Where there is a retained interest in a former subsidiary, other IFRSs (such as IAS 28, IFRS 11 or IFRS 9) may also apply in accounting for the transaction.

Similar considerations may apply to disposals of non-financial assets held in a corporate wrapper that are in the ordinary course of business, since IFRS 15 excludes transactions within the scope of IFRS 10. See 3.5.1.J above for further discussion.

The FASB's ASC 610‑20 provides guidance on how to account for any gain or loss resulting from the sale of non-financial assets or in-substance non-financial assets that are not an output of an entity's ordinary activities and are not a business. This includes the sale of intangible assets and PP&E, including real estate, as well as materials and supplies. ASC 610‑20 requires entities to apply certain recognition and measurement principles of ASC 606. Thus, under US GAAP, the accounting for a contract that includes the sale of a non-financial asset to a non-customer will generally be consistent with a contract to sell a non-financial asset to a customer, except for financial statement presentation and disclosure. Sales or transfers of businesses or subsidiaries that do not contain solely non-financial assets and in-substance non-financial assets to non-customers are accounted for using the deconsolidation guidance in ASC 810.

As discussed above, IAS 16, IAS 38 and IAS 40 require entities to use certain of the requirements of IFRS 15 when recognising and measuring gains or losses arising from the sale or disposal of non-financial assets when it is not in the ordinary course of business. Changes in a parent's ownership interest in a subsidiary (including loss of control through sale or disposal) are generally accounted for under IFRS 10 (see 3.5.1.J above). Unlike US GAAP, IFRS does not contain specific requirements regarding the sale of in-substance non-financial assets.

4.3.1 Sale of assets held for rental

In general, IAS 16 prohibits the classification of gains arising from the derecognition of PP&E as revenue. [IAS 16.68A]. However, for entities that are in the business of renting and subsequently selling the same asset, the IASB has agreed that the presentation of revenue, rather than a net gain or loss on the sale of the assets, would better reflect the ordinary activities of such entities. [IAS 16.BC35C]. See Chapter 18 at 7.2 for further discussion.

Therefore, where an entity, in the course of its ordinary activities, routinely sells items of PP&E that it has held for rental to others, it is required to transfer the assets to inventories at their carrying amount when they cease to be rented and become held for sale. The proceeds from the sale of such assets are recognised as revenue in accordance with IFRS 15 on a gross basis. IFRS 5 does not apply when assets that are held for sale in the ordinary course of business are transferred to inventories. [IAS 16.68A].

IAS 7 – Statement of Cash Flows – requires presentation within operating activities of cash payments to manufacture or acquire such assets and cash receipts from rents and sales of such assets. [IAS 7.14]. The requirements of IAS 7 are discussed further in Chapter 40.

4.4 Regulatory assets and liabilities

In many countries, the provision of utilities (e.g. water, natural gas or electricity) to consumers is regulated by a government agency (regulators). The objective of this rate regulation is to ensure ‘quality, quantity and availability of supply’, as well as ‘stability, predictability and affordability of pricing’ for ‘goods or services that governments consider essential for a reasonable quality of life for their citizens and for which there are significant barriers to effective competition for supply’. Regulations differ between countries, but regulators may operate a cost-plus system under which a utility is allowed to make a fixed return on investment. Consequently, there is rate-adjustment mechanism to adjust the future price that a utility is allowed to charge its customers for variances between estimated and actual inputs to the rate calculation. Hence, this adjustment creates timing differences as the future price may be influenced by past cost levels and investment levels.

Under some national GAAPs (including US GAAP) accounting practices have been developed that allow an entity to account for the effects of regulation by recognising a ‘regulatory liability’ or ‘regulatory asset’ that reflects the decrease in future prices required by the regulator to compensate for an excessive return on investment, and vice versa where an increase would be permitted.

In September 2012, the Board decided to restart its rate-regulated activities project and issued a discussion paper in September 2014 aiming to develop an accounting model so that investors can compare the effects of rate regulation on the financial position, performance and cash flows of any entity with significant rate-regulated revenue.25 As an interim measure, the IASB issued IFRS 14 – Regulatory Deferral Accounts – to help entities who currently recognise rate-regulated assets and liabilities under their national GAAP adopt IFRS. That standard permits a first-time adopter of IFRS to continue to use its previous accounting policies for rate-regulated assets and liabilities, with specific disclosure requirements (see Chapter 5 for discussion on first-time adoption).

The Board is currently undertaking a standard-setting project to develop a new accounting model to provide users of financial statements with useful information about an entity's rights and obligations arising from a defined rate regulation that are not captured by existing IFRS requirements.

The possible accounting model being discussed by the IASB provides explanations for the term ‘defined rate regulation’ and proposes a ‘supplementary approach’. Under this approach, an entity would continue to apply existing IFRS standards, including IFRS 15, without modification (i.e. customer contracts perspective). The model would then be applied to provide information about the effects of the timing differences between when a transaction or event takes place and when some of the effects of that transaction or event are reflected in the rate (i.e. regulatory agreement perspective). The rights and obligations reflecting these timing differences that are incremental to those reported using existing IFRS standards (e.g. IFRS 15) would then be recognised in the statement of financial position as an asset or liability.26

At its July 2019 meeting, the Board decided to publish its proposal for a new accounting model as an exposure draft of a new standard that would replace IFRS 14.27 In its September 2019 meeting, the Board discussed application guidance to include in the exposure draft to assist entities when determining the boundary of a regulatory agreement. It also discussed transition considerations.28 In March 2020, the Board discussed its planned proposals for the elements of ‘target profit’ (i.e. the profit an entity is entitled to include in the regulated rate) and the composition of the total allowed compensation for the goods or services supplied.29 At the time of writing, the Board was expected to issue the exposure draft in Q4 of 2020.30 Until any new standard is issued and becomes effective, regulatory assets and liabilities are not eligible for recognition under IFRS, unless the entity is a first-time adopter that can apply IFRS 14. For further details see Chapter 17 at 11.1.

References

  1. 1   Speech by Wesley R. Bricker, 5 May 2016. Refer to SEC website at https://www.sec.gov/news/speech/speech-bricker-05‑05‑16.html (accessed 10 September 2018).
  2. 2   Paragraph IN5 was part of the Introduction that accompanied IFRS 15 when the standard was issued in May 2014. This Introduction was last included in the 2016 edition of the IFRS Red Book, which contained all IFRSs issued (but not necessarily effective) at 1 January 2016.
  3. 3   The FASB's standard defines a public entity as one of the following: A public business entity (as defined); A not-for-profit entity that has issued, or is a conduit bond obligor for, securities that are traded, listed or quoted on an exchange or an over-the-counter market; An employee benefit plan that files or furnishes financial statements with the US SEC. An entity may meet the definition of a public business entity solely because its financial statements or financial information is included in another entity's filing with the SEC. The SEC staff said it would not object if these entities adopt the new revenue standard using the effective date for non-public entities rather than the effective date for public entities.
  4. 4   Effective Date of IFRS 15, September 2015.
  5. 5   The FASB's amendments to its standard were effected through the following: ASU 2015‑14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date; ASU 2016‑08, Revenue from Contracts with Customers (Topic 606): Principal versus Agent Considerations (Reporting Revenue Gross versus Net); ASU 2016‑10, Revenue from Contracts with Customers (Topic 606): Identifying Performance Obligations and Licensing (April 2016); ASU 2016‑12, Revenue from Contracts with Customer (Topic 606): Narrow-Scope Improvements and Practical Expedients (May 2016); and ASU 2016‑20, Technical Corrections and Improvements to Topic 606, Revenue From Contracts With Customers (December 2016).
  6. 6   US GAAP, Statement of Financial Accounting Concepts No. 6, para. 78.
  7. 7   TRG Agenda paper 17, Application of IFRS 15 to permitted Islamic Finance Transactions, dated 26 January 2015.
  8. 8   TRG Agenda paper 25, January 2015 Meeting – Summary of Issues Discussed and Next Steps, dated 30 March 2015.
  9. 9   FASB TRG Agenda paper 52, Scoping Considerations for Financial Institutions, dated 18 April 2016.
  10. 10 TRG Agenda paper 36, Scope: Credit Cards, dated 13 July 2015.
  11. 11 TRG Agenda paper 36, Scope: Credit Cards, dated 13 July 2015.
  12. 12 ASU 2018‑08, Accounting Standards Update 2018‑08 – Not-For-Profit Entities (Topic 958): Clarifying The Scope And Accounting Guidance For Contributions Received And Contributions Made.
  13. 13 TRG Agenda paper 26, Whether Contributions are Included or Excluded from the Scope, dated 30 March 2015 and TRG Agenda paper 34, March 2015 Meeting – Summary of Issues Discussed and Next Steps, dated 13 July 2015.
  14. 14 IFRIC Update, March 2016.
  15. 15 IFRIC Update, March 2016.
  16. 16 Agenda paper 6, Sale of a single asset entity containing real estate (IFRS 10), paras 15‑16, dated June 2019.
  17. 17 IFRIC Update, June 2019.
  18. 18 IASB Update, June 2020 and IASB agenda paper 12A, Maintenance and Consistent Application: Sale of a Subsidiary to a Customer, dated June 2020.
  19. 19 Project summary: Sales of Subsidiary to a customer, website of the IFRS Foundation and IASB, https:// www.ifrs.org/projects/2020/sale-of-a-single-asset-entity-containing-real-estate-ifrs-10/ (accessed 17 August 2020).
  20. 20 IASB work plan, website of the IFRS Foundation and IASB, https:// www.ifrs.org/projects/2020/sale-of-a-single-asset-entity-containing-real-estate-ifrs-10/ (accessed 17 August 2020).
  21. 21 IFRIC Update, March 2019 and Agenda Paper 2, Output received by a joint operator (IFRS 11), dated November 2018.
  22. 22 ASU 2018‑07 Compensation – Stock Compensation (718): Improvements to Nonemployee Share-Based Payment accounting.
  23. 23 IFRIC Update, June 2020.
  24. 24 Para. 25 of IFRS 10 applies if a parent loses control of a subsidiary. Para. 23 of IFRS 10 applies if a parent's ownership interest in a subsidiary changes without the parent losing control of that subsidiary.
  25. 25 Discussion Paper DP/2014/2, Reporting the Financial Effects of Rate Regulation.
  26. 26 IASB Agenda paper 9A Rate-regulated Activities, July 2018.
  27. 27 IASB Update, July 2019.
  28. 28 IASB Update, September 2019.
  29. 29 IASB Update, March 2020.
  30. 30 Website of the IFRS Foundation and IASB, https://www.ifrs.org/projects/work-plan/ (accessed 20 August 2020).
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.117.107.90