IFRS in PRACTICE 2020-2021 - IFRS 15 REVENUE from CONTRACTS with CUSTOMERS IFRS in Practice 2020-2021 - IFRS 15 Revenue from Contracts with Customers 2
Total Page:16
File Type:pdf, Size:1020Kb
IFRS IN PRACTICE 2020-2021 - IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS IFRS in Practice 2020-2021 - IFRS 15 Revenue from Contracts with Customers 2 Contents 1. Introduction 3 2. Overview of IFRS 15’s Requirements 5 3. Scope 7 4. The ‘Five Step’ approach 10 4.1. Step One – Identify the contract 10 4.2. Step Two - Identify separate performance obligations in the contract 17 4.3. Step Three - Determine the transaction price of the contract 29 4.4. Step Four - Allocate the transaction price to the performance obligations 45 4.5. Step Five - Recognise revenue when each performance obligation is satisfied 50 5. Other issues 66 5.1 Contract costs 66 5.2. Changes in the transaction price after contract inception 73 5.3. Sale with a right of return 75 5.4. Warranties 77 5.5. Principal vs. agent 80 5.6. Customer options for additional goods or services 83 5.7. Renewal options 86 5.8. Breakage (unexercised rights) 89 5.9. Non-refundable upfront fees 91 5.10. Licencing 92 5.11. Sales-based or usage-based royalties 97 5.12. Repurchase agreements 102 5.13. Consignment arrangements 104 5.14. Bill-and-hold arrangements 105 5.15. Customer acceptance 106 5.16. Treatment of onerous contracts 107 6. Presentation 109 7. Disclosure 111 8. Effective Date and Transition 112 APPENDIX 1 Comparison of IFRS 15 and Topic 606 115 APPENDIX 2 Comparison of IFRS 15 and previous revenue standards 118 IFRS in Practice 2020-2021 - IFRS 15 Revenue from Contracts with Customers 3 1. Introduction Background On 28 May 2014, the International Accounting Standards Board (IASB) published IFRS 15 Revenue from Contracts with Customers. IFRS 15 sets out a single and comprehensive framework for revenue recognition, which supersedes (IAS 18 Revenue and IAS 11 Construction Contracts) and the accompanied Interpretations. In common with other recently issued IFRSs, IFRS 15 includes comprehensive application guidance and illustrative examples, together with a detailed section which sets out how the IASB reached its decisions about the new requirements (the Basis for Conclusions). The new standard also introduces an overall disclosure objective together with significantly enhanced disclosure requirements for revenue recognition. These are accompanied by an explicit statement that immaterial information does not need to be disclosed and that the disclosure requirements should not be used as a checklist. In practice, even if the timing and profile of revenue recognition did not change, new and/or modified processes might have been needed in order to obtain the necessary information. In this publication we update our previous guidance to discuss issues that companies have encountered in implementing IFRS 15 and include a number of new examples to demonstrate how the standard should be applied. Convergence with US GAAP IFRS 15 was developed jointly with the US Financial Accounting Standards Board (FASB) and, to assist implementation, the IASB and the FASB established a joint Transition Resource Group (TRG) as a public forum for preparers, auditors and users to share implementation experience and discuss issues submitted to the TRG. Output from this group resulted in the IASB amending IFRS 15 in April 2016 in the following areas: • Identification of performance obligations: • Principal vs. agent considerations: • Licensing agreements: • Transitional reliefs for completed and modified contracts: When IFRS 15 and Topic 606 were originally issued in May 2014, the Boards achieved their goal of reaching the same conclusions on all significant requirements for accounting for revenue from contracts with customers. Only minor differences existed, in respect of: • collectability threshold; • interim disclosure requirements; • early application and effective date; • impairment loss reversal; and • non-public entity requirements. However, the subsequent changes made in April 2016 by the IASB to IFRS 15 were not the same as subsequent changes that the FASB made to Topic 606. Therefore, the two standards are no longer fully converged, although the differences are still relatively minor. The differences, which are set out in more detail in Appendix 2, deal with the following areas: • Scope: Revenue recognition for contracts with customers that do not meet the Step 1 criteria; • Promised goods or services that are immaterial within the context of the contract; • Shipping and handling activities; • Presentation of sales taxes; • Non-cash consideration; • In – substance sales of intellectual property; IFRS in Practice 2020-2021 - IFRS 15 Revenue from Contracts with Customers 4 • Licensing: – Determining the nature of the entity’s promise in granting a licence of intellectual property; – Contractual restrictions in a licence and the identification of performance obligations; – Renewals of licences of intellectual property; – When to consider the nature of an entity’s promise in granting a licence. • Completed contracts; • Date of application of the contract modifications practical expedient. Effective Date IFRS 15 was originally effective for annual reporting periods beginning on or after 1 January 2017 with earlier application permitted. This was subsequently deferred to annual reporting periods beginning on or after 1 January 2018 following the revisions made to IFRS 15 in April 2016. IFRS in Practice 2020-2021 - IFRS 15 Revenue from Contracts with Customers 5 2. Overview of IFRS 15’s Requirements The IASB’s joint project with the Financial Accounting Standards Board (FASB) to develop a new accounting standard for revenue recognition was a long term project that took over a decade to complete. The international and the US standard setters had noted inconsistencies and weaknesses in each of their respective accounting standards. In IFRS, there was significant diversity in practice because existing standards contained limited guidance for a range of significant topics, such as whether contracts with multiple elements should be accounted for as one overall obligation, or as a series of separate (albeit related) obligations. Under US GAAP, concepts for revenue recognition had been supplemented with a broad range of industry specific guidance, which had resulted in economically similar transactions being accounted for differently. Both the IASB and the FASB also noted that existing disclosure requirements were unsatisfactory, as they often resulted in information being disclosed that was not sufficient for users of financial statements to understand the sources of revenue, and the key judgements and estimates that had been made in its recognition. The information disclosed was also often ‘boilerplate’ and uninformative in nature. IFRS 15 establishes a single and comprehensive framework which sets out how much revenue is to be recognised, and when. The core principle is that a vendor should recognise revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the vendor expects to be entitled in exchange for those goods or services. Revenue is recognised by a vendor when control over the goods or services is transferred to the customer. In contrast, IAS 18 based revenue recognition around an analysis of the transfer of risks and rewards. An assessment of risks and rewards now forms one of a number of criteria that are assessed in determining whether control has been transferred. The application of the core principle in IFRS 15 is carried out in five steps: Step Step Step Step Step ONE TWO THREE FOUR FIVE Identify the Identify separate Determine the Allocate the Recognise revenue contract performance transaction price transaction price as or when each obligations to performance performance obligations obligation is satisfied The first step is to identify the contract(s) with the customer for accounting purposes, which may not be the same as the contract(s) for legal purposes. Whatever the form (written, oral or implied by an entity’s customary business practices), a contract for IFRS 15 purposes must create enforceable rights and obligations between a vendor and its customer. After identifying the contract(s) with the customer for accounting purposes, in step 2 a vendor identifies its separate ‘performance obligations’. A performance obligation is a vendor’s promise to transfer a good or service that is ‘distinct’ from other goods and services identified in the contract. Goods and services (either individually, or in combination with each other) are distinct from one another if the customer can benefit from one or more goods or services on their own (or in combination with resources readily available to the customer). Two or more promises (such as a promise to supply materials (such as bricks and mortar) for the construction of an asset (such as a wall) and a promise to supply labour to construct the asset are combined if they represent one overall performance obligation. IFRS in Practice 2020-2021 - IFRS 15 Revenue from Contracts with Customers 6 In step 3 a vendor determines the transaction price of each contract identified for accounting purposes in step 1, and then in step 4 allocates that transaction price to each of the performance obligations identified in step 2. In step 5, a vendor assesses when it satisfies each performance obligation identified in step 2, which is determined by reference to when the customer obtains control of each good or service. This could be at a point in time or over time, with the revenue allocated to each performance obligation in step 4 recognised accordingly. The five-step model is applied to individual contracts. However, as a practical expedient, IFRS 15 permits an entity to apply the model to a portfolio of contracts (or performance obligations) with similar characteristics if the entity reasonably expects that the effects would not differ materially from applying it to individual contracts. This practical expedient will often be applied to situations involving measurement estimates where an entity may have many contracts which are affected by a particular issue and an estimate is more appropriately made on the population of contracts rather than on each contract individually.