IFRS IN PRACTICE IFRS 15 Revenue from Contracts with Customers

IFRS IN PRACTICE 2018 IFRS 15 Revenue from Contracts with Customers

2 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 3 TABLE OF CONTENTS 1. Introduction 5 2. Overview of IFRS 15 s Requirements 7 3. Scope 9 4. The Five Step approach 13 4.1. Step One Identify the contract 13 4.2. Step Two Identify separate performance obligations in the contract 21 4.3. Step Three Determine the transaction price of the contract 35 4.4. Step Four Allocate the transaction price to the performance obligations 55 4.5. Step Five Recognise revenue when each performance obligation is satisfied 60 5. Other issues 75 5.1. Contract costs 75 5.2. Changes in the transaction price after contract inception 78 5.3. Sale with a right of return 80 5.4. Warranties 83 5.5. Principal vs. agent 86 5.6. Customer options for additional goods or services 88 5.7. Renewal options 90 5.8. Breakage (unexercised rights) 93 5.9. Non-refundable upfront fees 96 5.10. Licensing 97 5.11. Sales-based or usage-based royalties 103 5.12. Repurchase agreements 110 5.13. Consignment arrangements 112 5.14. Bill-and-hold arrangements 112 5.15. Customer acceptance 113 5.16. Treatment of onerous contracts 114 6. Presentation 116 7. Disclosure 118 8. Effective Date and Transition 121 APPENDIX 1 Illustrative Disclosure Example 124 APPENDIX 2 Comparison of IFRS 15 and Topic 606 140 APPENDIX 3 Comparison of IFRS 15 and current revenue standards 144

4 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 5 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 and, for many entities, the timing and profile of revenue recognition will change. In some areas, the changes will be very significant and will require careful planning. Previous IFRS guidance is set out in two relatively old standards (IAS 18 Revenue and IAS 11 Construction Contracts) which are accompanied by a number of Interpretations. In common with other more 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 does not change, it is possible that new and/or modified processes will be 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 deomstrate 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.

6 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 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; Licensing: Determining the nature of the entity s promise in granting a license of intellectual property; Contractual restrictions in a license and the identification of performance obligations; Renewals of licenses of intellectual property; When to consider the nature of an entity s promise in granting a license; 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 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 7 2. OVERVIEW OF IFRS 15 S REQUIREMENTS The IASB s joint 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 Revenue from Contracts with Customers 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 will now be recognised by a vendor when control over the goods or services is transferred to the customer. In contrast, IAS 18 Revenue 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 ONE STEP TWO STEP THREE STEP FOUR STEP FIVE Identify the contract Identify separate performance obligations Determine the transaction price Allocate transaction price to performance obligations Recognise revenue as or when each performance obligation is satisfied Figure 1: Five-step approach 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.

8 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 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. For example, in a retail sale which gives the customer a right of return, it may be more appropriate to estimate the aggregate level of returns on all such retail transactions, rather than at the contract level (which is each individual retail sale on which a right of return is granted).

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 9 3. SCOPE IFRS 15 Revenue from Contracts with Customers applies to all contracts with customers, except for: Lease contracts within the scope of IAS 17/IFRS 16 Leases; Insurance contracts within the scope of IFRS 4 Insurance Contracts; Financial instruments and other contractual rights and obligations within the scope of IFRS 9 Financial Instruments, IFRS 10 Consolidated Financial Statements, IFRS 11 Joint Arrangements, IAS 27 Separate Financial Statements and IAS 28 Investments in Associates and Joint Ventures. Non-monetary exchanges between entities in the same line of business to facilitate sales to customers or potential customers (such as a contract between two oil customers to exchange oil to fulfil demand from their customers in different specified locations). BDO comment The example in the standard of two oil companies agreeing to exchange oil avoids revenue being accounted for twice in what is essentially a single supply of oil. Each oil company has sold oil to its respective end customer (or potential end customer) and therefore revenue is recognised on that ultimate sale of oil. The scope exclusion prevents both oil companies from also recognising additional revenue (and equivalent cost) from the initial exchange of oil between them. However, barter transactions are in the scope of IFRS 15 for situations in which the two entities concerned are not in the same line of business, or when the exchange is not for the purposes of facilitating sales to customers or potential customers. Therefore, an exchange of oil between a manufacturing company and an oil refiner would potentially be in scope as long as the contract to exchange oil had commercial substance (see Section 4.1 below on identification of a contract). In contrast, a contract between a rail freight company and a road freight company to exchange diesel fuel would not be within the scope of IFRS 15, because those companies sell freight services to their customers, not diesel fuel. IFRS 15 does not give any further guidance on what is meant by a line of business when assessing exchange transactions, and therefore judgement may be needed. For example: Is an entity involved in oil exploration in the same line of business as an entity engaged in mining gold because they both operate in the extractive industry, or are they in different lines of business because they mine very different raw materials? Is an entity involved in mining rubies in the same line of business as an entity mining diamonds because they both operate in the same industry sub-sector (i.e. mining of precious stones), or are they in different lines of business because they both mine different gem stones? Is an entity involved only in mining diamonds in the same industry as an entity engaged in both mining and cutting diamonds? In our view, the scope exception is quite tightly drawn. In each of the above situations, the entities are not in the same line of business. However, it would be necessary to understand what the commercial substance of the transaction is for the exchange in question before concluding that the exchanges give rise to revenue. Further, even if there is commercial substance to the exchanges, each entity might be acting as an agent for the other in the ultimate sale to other entity s the end customer, meaning that they are providing agency services to each other. This would impact the measurement of revenue, which would then be based on the provision of the agency services, not the gross value of the exchanged goods or services.

10 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS As noted above, under IFRS 15, revenue is derived from contracts entered into by a vendor for the sale of goods or services, arising from its ordinary activities, to a customer. Its recognition is linked to changes in a vendor s assets and liabilities. This can be in the form of cash inflows or increases in receivable balances, or decreases in a liability that represents deferred revenue. All changes in those assets and liabilities are recognised in profit or loss, other than those relating to transactions with owners (for example, shareholders) of the vendor if the owners enter into transactions with the vendor in their capacity as such. The existing requirements of other IFRSs for the recognition of a gain or loss on the transfer of some non-financial assets that are not an output of a vendor s ordinary activities (such as property, plant and equipment, investment property and intangible assets) have been amended so that they are consistent with the requirements in IFRS 15. Therefore, sales of such assets should only be recognised by the seller when control has passed to the purchaser. A contract may be partially within the scope of IFRS 15 and partially within the scope of other IFRSs. In this situation a vendor takes the approach summarised in the following diagram: Do other IFRSs specify how to separate and/or initially measure one (or more) parts of the contract? Yes No Apply the requirements of IFRS 15 to the entire contract. Allocate the transaction price relating to parts of the contract dealt with by other IFRSs: (i) Parts of the contract dealt with by other IFRSs: (ii) Parts of the contract not dealt with by other IFRSs: Apply the requirements of other IFRSs to the transaction price allocated to these parts of the contract. Apply the requirements of IFRS 15 to the transaction price allocated to these parts of the contract. Figure 2: Scope of IFRS 15 Therefore, if one or more other IFRSs specify how to separate and/or measure certain parts of a contract, those other IFRSs are applied first. Those other IFRSs take precedence in accounting for the overall contract, with any residual amount of consideration being allocated to those part(s) of the contract that fall within the scope of IFRS 15.

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 11 Example A car manufacturer leases a fleet of cars to a customer for three years. As part of the contract it also deals with various administrative matters for the customer such as arranging insurance, providing breakdown cover and annual servicing. IFRS 16 Leases (periods beginning on or after 1 January 2019 unless adopted earlier) and IAS 17 Leases as interpreted by IFRIC 4 Determining whether an Arrangement Contains a Lease (earlier periods in which IFRS 16 has not been adopted) require contracts to be separated into their lease and non-lease components. A vendor applies IFRS 15 to the amounts received from the customer that relate to the non-lease components of the contract. A vendor is also required to assess whether, instead of a transaction being a sale, the counterparty to a contract shares the risks and benefits that result from an activity or process (such as developing an asset). If so, the counterparty is not a customer, and the transaction falls outside of the scope of IFRS 15. Judgement will be required, as the IASB decided that it would not be feasible to develop application guidance that would apply to all circumstances. This is because the nature of the relationship (supplier-customer or collaborative arrangement) will depend on the specific contractual terms and conditions. Care may also be needed in assessing transactions with related parties, as their relationship with the vendor may be more complex than those with third parties. Example Entity A and Entity B enter into an agreement whereby: A newly formed special purpose entity, Company X, is owned 50:50 by entities A and B, which operate in the real estate sector; Entities A and B have joint control over Company X; Entity A contributes land to Company X; Entity B constructs an office block on the land; The office block will be leased to tenants by Company X. In this fact pattern, Entity A and Entity B might not treat Company X as their customer and, consequently, would not recognise revenue or a receivable from X for their respective land contribution and construction work undertaken. Instead, depending on precise facts and circumstances, appropriate accounting approaches might include the following: If the contractual arrangements give entities A and B rights over Company X s net assets, the arrangement would be classified as a joint venture. Revenue would not be recognised, with entities A and B accounting for their interests in Company X using the equity method; If the contractual arrangements give Entity A and Entity B rights to the assets and obligations for the liabilities of Company X, then the arrangement would be classified as a joint operation. Entity A and Entity B would recognise revenue as Company X earns rental income based on their respective contractual share. However, it would be necessary to consider whether any elements of the arrangement gave rise to a supplier-customer relationship. The IASB also noted that in some collaborative arrangements, an entity might consider applying the principles of IFRS 15 as an accounting policy developed in accordance with IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors.

12 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS TRG discussions Credit card fees (Agenda Paper 36; July 2015) The TRG discussed whether arrangements between financial institutions and credit cardholders are within the scope of the new revenue standard. Although contracts within the scope of IFRS 9 Financial Instruments mean that some income streams, such as interest charges on late payments, are not within the scope of IFRS 15, questions had been raised in respect of periodic or annual fees which are not dependent on the amount of credit available or the level of use of a credit card. Ancillary services such as access to airport lounges and rewards programmes are also often included. While US GAAP includes specific guidance on credit card fees, IFRS does not have specific guidance on this topic. The TRG members observed that IFRS 15 did not change the requirements for determining whether fees received by a card issuing bank are within the scope of IFRS 9 Financial Instruments or IFRS 15. The card issuing bank would first determine whether any fees (or part of the fees) are within the scope of IFRS 9. If the bank concludes that the fees are not within the scope of IFRS 9 then they would be accounted for in accordance with IFRS 15. This could include cardholder reward programmes because IFRS 15 does not explicitly exclude them from its scope. Most of the TRG agreed with the IASB and FASB staff (hereinafter, the staff) view that under US GAAP these types of arrangements are outside the scope of the new revenue standard to the extent that they fall within the scope of Topic 310 Receivables (for which there is no equivalent specific guidance under IFRS). As there is no specific guidance under IFRS, some TRG members noted that preparers might come to a different conclusion under US GAAP and IFRS.

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 13 4. THE FIVE STEP APPROACH 4.1. Step One Identify the contract IFRS 15 Revenue from Contracts with Customers is applied to contracts with customers that meet all of the following five criteria: The contract has been approved in writing, orally, or in accordance with other customary business practices and the parties are committed to perform their obligations in the contract; Each party s rights regarding the goods or services to be transferred can be identified; The payment terms for the goods or services to be transferred can be identified; The contract has commercial substance (i.e. the risk, timing or amount of the vendor s future cash flows is expected to change as a result of the contract); It is probable that the consideration for the exchange of the goods or services that the vendor is entitled to will be collected. For the purposes of this criterion, only the customer s ability and intention to pay amounts when they become due are considered. The last point above introduces a collectability threshold for revenue recognition, which goes beyond the contractual terms of an arrangement with a customer. This introduces a higher threshold than IAS 18 Revenue which required that in order for a vendor to recognise revenue, it was necessary for it to be probable that the economic benefits associated with the transaction would flow to the vendor. However, IAS 18 did not explicitly mention any of the other four criteria. The focus will often be on the price included in the contract between a vendor and its customer. However, it is possible that the amount of consideration that the vendor ultimately expects to be entitled to will be less, because it may offer a price concession or discount. In these cases, the assessment of the customer s ability and intention to pay is made against the lower amount, which will be determined in accordance with the guidance in IFRS 15 for variable consideration. In some cases, an entity may consider it probable that it will receive only some of the stated consideration in an otherwise fixed price contract. In these cases, although it can be concluded the probability of collection condition is met, it is also necessary to apply the guidance in IFRS 15 on variable consideration. The accounting for variable consideration is discussed in more detail in Section 4.3 below. Example A vendor sells a product to a customer in return for a contractually agreed amount of CU 1 million. This is the vendor s first sale to a customer in the geographic region, and the region is experiencing significant economic difficulty. The vendor therefore expects that it will not be able to collect the full amount of the contract price. Despite the fact that it may not collect the full amount, the vendor believes that economic conditions in the region will improve in future. It also considers that establishing a trading relationship with this customer could help it to open up a new market with other potential customers in the region. This means that instead of the contract price being fixed at CU 1 million, the amount of promised consideration is variable. The vendor assesses the customer s intention and ability to pay and, based on the facts and circumstances and taking into account the poor economic conditions, it is concluded that it is probable that it will be entitled to an estimated amount of CU 500,000 and that the customer will pay this amount. Assuming that the other four criteria set out above are met, the vendor concludes that it has entered into a contract for the sale of the product in return for variable consideration of CU 500,000.

14 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS TRG discussions Collectability criteria (Agenda Paper 13; January 2015) The TRG discussed several questions arising from the collectability criteria. It was agreed that if an entity considers collectability of the transaction price to be probable for a portfolio of contracts, then the entity should recognise the transaction price as revenue when (or as) each of the separate performance obligations are satisfied. Example An entity has a large volume of homogenous revenue generating customer contracts for which invoices are sent in arrears on a monthly basis. Before accepting a customer, the entity performs procedures designed to ensure that it is probable that the customer will pay the amounts owed. If these procedures result in the entity concluding that it is not probable that the customer will pay the amounts owed, the entity does not accept them as a customer. Because these procedures are only designed to determine whether collection is probable (and thus not a certainty), the entity anticipates that it will have some customers that will not pay all amounts. While the entity collects the entire amount due from the vast majority of its customers, on average, the entity s historical evidence (which is representative of its expectations for the future) indicates that the entity will only collect 98% of the amounts billed. The issue could be viewed as being whether a contract exists for 100% of the amounts invoiced, or for 98%. Based on the TRG discussions, 100% would be recorded as revenue, as the criterion is that it is probable that the entity will collect the consideration for each of the sales on an individual contract basis (which is the unit of account for the purposes of IFRS 15). This is because the entity concluded that, as a result of its customer acceptance procedures, it is probable that each customer will pay the amount owed. The fact that only 98% of amounts invoiced are expected to be collected will instead be relevant to the expected credit loss (bad debt) provision recognised for the purposes of IFRS 9 Financial Instruments. In addition to determining whether collectability of the transaction price is probable at contract inception, collectability also needs to be reassessed when there is an indication of a significant change in facts and circumstances. Therefore, if a contract is initially assessed as meeting the probability of collection criterion and the customer s ability to pay the consideration subsequently deteriorates, there might no longer be a contract for accounting purposes. For this to happen, the change in the customer s financial condition would need to be so significant that it indicates that the contract is no longer valid. Changes of a more minor nature that might reasonably occur (particularly during a long term contract) would not result in that conclusion. If it is concluded that a contract is no longer valid, although any revenue recognised to date would not be reversed (instead the receivable or contract asset would be subject to the impairment provisions of IFRS 9), no further revenue is recognised until the vendor could once again conclude that the probability of receipt criterion is met, or when one of the following applies: The vendor has no remaining contractual obligations to transfer goods or services and all, or substantially all, of the consideration has been received and is non-refundable; or The contract has been terminated and the consideration received is non-refundable. The above two bullet points would also apply if an entity receives payment before all of the five criteria set out above are met.

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 15 Example (continued) A linked point is that the criteria above mean that when collectability for a contract as a whole is not probable, recognising revenue on the basis of cash collected is prohibited by IFRS 15. This is the case even if some non-refundable consideration has been received from the customer, with any such non-refundable consideration instead giving rise to a liability. This may result in a significant chance in practice for some entities. Some members of the TRG considered that the accounting might not reflect the economics in some circumstances because the vendor may be unable to terminate a contract and be required to continue to provide goods or services. It was also considered possible that, for a contract such as a three year contract with a customer with a poor credit rating, under which services are carried out monthly and non-refundable cash is collected monthly, IFRS 15 could be interpreted to require full deferral of revenue until either the contract is terminated (the end of three years, or earlier depending on the termination provisions), or until collection of the entire transaction price becomes probable. Some TRG members felt that a prohibition on the recognition of revenue when a distinct good or service has been provided and payment has been received would not reflect economic substance. However, Board members at the TRG meeting noted that the inclusion of the collectability criterion in Step 1 was deliberate, because revenue recognition of prohibited when a valid contract does not exist. Combination of contracts Two or more contracts that are entered into at (or near) the same time, and with the same customer or related parties of the customer, are accounted for as if they were a single contract for accounting purposes, if one of the following criteria are met: The contracts are negotiated as a package with a single commercial objective; The amount of consideration in one contract depends on the price or performance of the other contract(s); or The goods or services that are promised in the contracts (or some of the goods or services) represent a single performance obligation (see discussion on Step 2 in Section 4.2 below). BDO comment The requirement to consider contracts which are entered into with two or more separate parties that are related to each other has been included because there may be interdependencies between or among those contracts. The term related parties has the same meaning as the definition in IAS 24 Related Party Disclosures, which encompasses a wide range of entities and individuals, and careful analysis may be required to ensure that all of these are considered.

16 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS Contract modifications A contract modification is a change in the scope and/or price of a contract that is approved by the parties to that contract. This might be referred to as change order, variation, and/or an amendment. Consistent with the provisions of IFRS 15, adjustments are only made for a contract modification when either new enforceable rights and obligations are created, or existing ones are changed. A vendor accounts for a contract modification as a separate contract to the original one, such that the accounting for the original contract remains unchanged, only if: The scope of the contract changes due to the addition of promised goods or services that are distinct for the purposes of Step 2 of the five-step model (see Section 4.2 below); and The price of the contract increases by an amount of consideration that reflects the vendor s stand-alone selling price of the additional promised goods or services and any appropriate adjustments to that price to reflect the circumstances of the particular contract (e.g. a discount to reflect that the vendor did not incur the same costs as it would do for a new customer). If both of these criteria are met, then the contract modification is, for accounting purposes, a separate contract which is subject to the same five-step model as any other contract. When a contract modification is not accounted for as a separate contract (i.e. neither of the above two criteria are met), the vendor identifies the total goods or services that have not yet been transferred. This will be comprised of the remaining goods or services from the original contract, and any new goods or services arising from the contract modification. The approach which is then followed is illustrated by the following diagram: Are the remaining goods and services to be transferred under the original contract distinct? Yes No Mixture Is there only a single performance obligation? Yes No (iii) Mixed Approach will be a mixture of (i) and (ii) (i) Termination Replace the original contract with a new contract. (No adjustment to revenue recognised to date. Consider treatment of any remaining performance obligations) (ii) Continuation Treat modification as part of the original contract. (There will be an adjustment to revenue recognised to date) (Consider the effects on any unsatisfied performance obligations) Figure 3: Accounting for contract modifications

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 17 If the modification results in the original contract being accounted for as if it were terminated, then no adjustment is made on modification date to the cumulative revenue previously recognised on the original contract. Instead, the remaining goods and services and the remaining contractual consideration (i.e. the total consideration as modified less revenue recognised prior to modification) form the new contract for accounting purposes. If, in contrast, the modification results in the original contract continuing, then the amount of revenue recognised prior to the modification will need to be adjusted to reflect the extent to which the performance obligation affected in the modified contract has been completed. This might apply to a construction contract for a building where revenue is being recognised over time, and there is a change to the building specification which increases the scope of work and affects the stage of completion. In some cases, the remaining goods and services to be delivered under the modified contract are not distinct from those that have already been delivered, and may be comprised of more than one performance obligation. In those cases, the entity will need to apply judgement to determine which elements of the original contract are being terminated and which elements are being continued. Example sale of a product A vendor enters into a contract with a customer to sell 200 units of a product for CU 16,000 (CU 80 per unit). These are to be supplied evenly to the customer over a four month period (50 units per month) and control over each unit passes to the customer on delivery. After 150 units have been delivered, the contract is modified to require the delivery of an additional 50 units (i.e. at the point of contract modification, the vendor is now required to supply at total of 100 units, being the 50 units not delivered under the original contract plus a further 50 units). At the point at which the contract is modified, the stand-alone selling price of one unit of the product has declined to CU 75. Assuming the additional units to be delivered are distinct (considered under Step 2 in Section 4.2 below), the accounting for the contract modification will depend on whether the sales price for the additional units reflects the stand-alone selling price at the date of contract modification (CU 75).

18 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS Scenario A the price of each of the additional units is CU 75 The selling price of the additional units is the stand-alone price at the date of contract modification. Consequently, the additional units are accounted for as being sold under a new and separate contract from the units to be delivered under the terms of the original contract. The vendor recognises revenue of CU 80 per unit for the remaining 50 units specified in the original contract, and CU 75 per unit for the 50 units that are added as a result of the contract modification. BDO comment In our view, if the units are fungible, revenue should be recognised on a FIFO basis. That is, the first 50 units delivered to the customer after the modification satisfy the remainder of the original promise to deliver 200 units in the original contract, and which will result in revenue of CU 80 being recognised as each of the first 50 units of the remaining 100 units are delivered. The second tranche of 50 units delivered relate to the contract modification (which, for accounting purposes, is a separate contract) on which revenue of CU 75 is recognised as each unit is delivered. To permit a different approach could result in structuring of the amount of revenue to be recognised, by specifying whether deliveries of the remaining 100 units following the contract modification relate to the original contract or the contract modification. The FIFO approach is consistent with the approach which is implied in IFRS 15, Example 5A, with the obligations in the original contract being satisfied first, before the additional items arising from the contract modification. Scenario B the price of each of the additional units is CU 65, reflecting a CU 10 discount as compensation for past poor service When the contract modification for the additional 50 units was being negotiated, the vendor agreed to a price reduction of CU 10 for each of the additional units, to compensate the customer for poor service. Some of the first 50 units that had been delivered were faulty and the vendor had been slow in rectifying the position. At the point of contract modification, the vendor recognises the CU 10 per unit discount as an immediate reduction in revenue of CU 500. This is because the discount relates to units that have already been delivered to the customer; the allocation of the discount to the price charged for units that are to be sold in future does not mean that the discount is attributed to them. The selling price of the additional units is therefore the stand-alone selling price (CU 75) at the date of contract modification. Consequently, the additional units are accounted for as being sold under a new and separate contract from the units to be delivered under the terms of the original contract. This means that, as in scenario A, the vendor recognises revenue of CU 80 per unit for the remaining 50 units specified in the original contract, and then CU 75 per unit for the 50 units that are delivered as a result of the contract modification. Scenario C the price of each of the additional units is CU 60, solely reflecting a special discount given to the customer The selling price of the additional units is not the stand-alone price at the date of contract modification. The 100 units still to be delivered after the contract modification are distinct from the 150 already delivered. Consequently, for accounting purposes, the original contract is considered to be terminated at the point of contract modification. The remaining units to be sold that were covered by the original contract, together with the additional units from the contract modification, are accounted for together as being sold under a new contract. The amount of revenue recognised for each of the units is a weighted average price of CU 70. This is calculated as ((50* CU 80) + (50* CU 60)) / 100.

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 19 BDO comment Care will be needed when determining the appropriate accounting approach in circumstances in which a contract is modified, and the selling price of remaining performance obligations reflects both compensation for poor past performance, and a revised price that does not represent the stand-alone selling price at the date of contract modification. This is to ensure that the adjustment to revenue previously recognised on contract modification (reflecting compensation payable to the customer for poor past performance) and the revenue to be reflected for the remaining goods to be delivered is appropriate. Contract enforceability and termination clauses Under IFRS 15, a contract does not exist if each party to the contract has the unilateral enforceable right to terminate a wholly unperformed contract without compensating the other party (or parties). A contract is wholly unperformed if: The entity has not yet transferred any promised goods or services to the customer; and The entity has not yet received, and is not yet entitled to receive, any consideration in exchange for promised goods or services. An entity only applies IFRS 15 to the term of the contract in which the parties to the contract have enforceable rights and obligations.

20 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS TRG discussions Contract enforceability and termination clauses (Agenda Paper 10; October 2014) Although IFRS 15 contains guidance on when a contract exists, questions were raised about how to assess whether a contract exists for accounting purposes (and, if so, the contract duration) if the contract between a vendor and its customer contains termination clauses. The TRG considered the following examples in deliberating how such clauses should be taken into account by a vendor and generally agreed with the staffs conclusions: Example 1 An entity enters into a service contract with a customer under which the entity continues to provide services until the contract is terminated. Each party can terminate the contract without compensating the other party for the termination (that is, there is no termination penalty). The duration of the contract does not extend beyond the services already provided. Example 2 An entity enters into a contract with a customer to supply services for two years. Each party can terminate the contract at any time after fifteen months from the start of the contract without compensating the other party for the termination. The duration of the contract is fifteen months. Example 3 An entity enters into a contract with a customer to provide services for two years. Either party can terminate the contract by compensating the other party. The duration of the contract is the specified contractual period of two years. Example 4 An entity enters into a contract to provide services for 24 months. Either party can terminate the contract by compensating the other party. The entity has a past practice of allowing customers to terminate the contract at the end of 12 months without enforcing collection of the termination penalty. In this case, whether the contractual period is 24 months or 12 months depends on whether the past practice is considered by law (which may vary by jurisdiction) to restrict the parties enforceable rights and obligations. The entity s past practice of allowing customers to terminate the contract at the end of month 12 without enforcing collection of the termination penalty affects the contract term only if that practice changes the parties legally enforceable rights and obligations. If that past practice does not change the parties legally enforceable rights and obligations, then the contract term is the stated period of 24 months.

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 21 4.2. Step Two Identify separate performance obligations in the contract Having identified the contract for accounting purposes in Step one, a vendor is then required to identify the performance obligations(s) contained in that contract. A performance obligation is a promise to a customer to transfer: A good or service (or a bundle of goods or services) that is distinct; or A series of distinct goods or services that are substantially the same and that have the same pattern of transfer to the customer. A single contract can have more than one performance obligation. For example, the purchase of a mobile handset and connection to a mobile network for two years, in return for 24 monthly fixed payments, is likely to be set out in a single contract. However, the contract will typically be analysed as containing two performance obligations for accounting purposes the sale of the mobile handset on credit, and the provision of network services for two years. Further, although two contracts between a vendor and its customer may be identified as a single contract for accounting purposes in Step 1 (because, for example, they were negotiated at or near the same time, with interdependency in the amount of consideration allocated to each), the good(s) or service(s) specified in each of the two legal contracts could be separate performance obligations for accounting purposes. As a result, an entity is not able to obtain a particular accounting result by structuring obligations in different contracts with its customer. Continuing the example of a mobile handset and provision of network services above, a vendor might structure this as a contract for the purchase of a mobile phone and a separate contract for the connection of that phone to a mobile network rather than as a single contract. However, the two contracts would still have the same two performance obligations for accounting purposes as the more typical situation of both deliverables being set out in a single legal contract. This has important consequences for the consistency of revenue recognition for similar arrangements that are structured differently. If the two separate contracts were priced on the basis of the relative fair values of the mobile handset and the network services, there would be no difference in the accounting compared to a single contract for both performance obligations. However, if the vendor structured the arrangement as being a contract (at overvalue) for the mobile handset and a contract (at undervalue) for the network services, the two contracts would be combined into one contract for accounting purposes in Step 1, with the total consideration allocated to each performance obligation (the mobile handset and the network services) on the basis of their relative fair values. BDO comment The identification of each of the distinct goods or services in contracts may require a detailed analysis of contractual terms, and linkage to IFRS 15 s requirements on whether a promise in a contract is a distinct good or service (and hence constitutes a performance obligation), or needs to be combined ( bundled ) with other promises in the contract to create a single performance obligation. Subtle differences in contractual terms and conditions, as well as individual and facts and circumstances, can impact the analysis. The importance of appropriately identifying the performance obligations in a contract cannot be underestimated as they each form a separate unit of account for the purposes of determining how much revenue should be recognised and when revenue should be recognised. The conclusions reached in Step 2 could also bring substantial changes to the amount and timing of revenue recognition in comparison with current standards.

22 IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS The following diagram illustrates the approach to determine whether a promise to in a contract (i.e. a contract for accounting purposes determined in Step 1) is a distinct good or service, and hence a performance obligation: Can the customer benefit from the good or service, either on its own, or with other readily available resources, i.e. it is capable of being distinct? ( Readily available resources are those that the customer possesses or is able to obtain from the entity or another third party) Yes No The good or service is not distinct Is the promise to transfer a good or service separate from the other promised goods or services in the contract, i.e. it is distinct within the context of the contract? Indicators a promise is NOT distinct include: The entity provides a significant service of integrating the good or service with other goods or services promised in the contract The good or service significantly modifies or customises the other goods or services promised in the contract The good or service is highly dependent or interrelated with one or more of the other goods or services promised in the contract No (These are then grouped into bundles of goods and services that together are distinct ) Yes The good or service is distinct Figure 4: Distinct goods or services

IFRS IN PRACTICE 2018 IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 23 The two criteria that need to be met in order for a good or service to be distinct are set out in more detail below: CRITERION 1 The customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer (i.e. the good or service is capable of being distinct). A customer can benefit from a good or service if the good or service can be used, consumed, or sold (other than for scrap value), or it can be held in a way that generates economic benefits. A customer may benefit from some goods or services on their own, while for others a customer may only be able to obtain benefits from them in conjunction with other readily available resources. A readily available resource is either a good or service that is sold separately (either by the vendor or another vendor), or a resource that the customer has already obtained from the vendor (this includes goods or services that the vendor has already transferred to the customer under the contract) or from other transactions or events. If the vendor regularly sells a good or service separately, this indicates that a customer can benefit from it (either on its own, or in conjunction with other resources). CRITERION 2 The entity s promise to transfer the good or service to the customer is separately identifiable from other promises in the contract (i.e. the good or service is distinct within the context of the contract). To assist in making this assessment, Paragraph 29 of IFRS 15 includes indicators that a vendor s promise to transfer two or more goods or services to the customer are not distinct within the context of the contract. The guidance is explicit that these are not the only circumstances in which two or more promised goods or services are not distinct: The vendor provides a significant service of integrating one good or service with other goods or services promised in the contract into a bundle, which represents a combined output for which the customer has contracted (i.e. the vendor is using one good or service as an input to produce the combined output specified by the customer); One good or service significantly modifies or customises other goods or services promised in the contract; One good or service is highly dependent on (or highly interrelated with) other promised goods or services. That is, if the customer decides not to purchase the good or service it would not significantly affect any of the other promised goods or services in the contract. To determine whether the vendor s promise to transfer a good or service is separately identifiable from other promised goods or services in the contract (i.e. distinct within the context of the contract) requires judgement in light of all relevant facts and circumstances. This is evident from the Basis for Conclusions to IFRS 15, which explains that the notion of two or more promises being separately identifiable (i.e. distinct within the context of the contract) is in turn based on the notion that the risks assumed in one promise are separable from the risks assumed in another. The three factors included in Paragraph 29 are therefore intended to assist entities in making that judgement. Further, the three factors are not mutually exclusive, because they are based on the same underlying principle of inseparable risks.