Write an original paper thatsummarizes the main points of the current IFRS exposure drafts attached.

Additionally, compare/contrast with current theory/standards.

Each section must be a minimum of two pages. Additionally, use one or two peer reviewed journal articles.

May 2015 Exposure Draft ED/2015/2 Effective Date of IFRS 15 Proposed amendments to IFRS 15 Comments to be received by 3 July 2015 Effective Date of IFRS 15 (Proposed amendments to IFRS 15) Comments to be received by 3 July 2015 Exposure Draft ED/2015/2 Effective Date of IFRS 15 (Proposed amendments to IFRS 15) is published by the International Accounting Standards Board (IASB) for comment only. The proposals may be modified in the light of the comments received before being issued in final form. Comments need to be received by 3 July 2015 and should be submitted in writing to the address below, by email to commentletters@ifrs.org or electronically using our 'Comment on a proposal' page. All comments will be on the public record and posted on our website unless the respondent requests confidentiality. Such requests will not normally be granted unless supported by good reason, for example, commercial confidence. Please see our website for details on this and how we use your personal data. Disclaimer: the IASB, the IFRS Foundation, the authors and the publishers do not accept responsibility for any loss caused by acting or refraining from acting in reliance on the material in this publication, whether such loss is caused by negligence or otherwise. International Financial Reporting Standards (including International Accounting Standards and SIC and IFRIC Interpretations), Exposure Drafts and other IASB and/or IFRS Foundation publications are copyright of the IFRS Foundation. Copyright 2015 IFRS Foundation ISBN: 978-1-909704-88-6 All rights reserved. Copies of the Exposure Draft may only be made for the purpose of preparing comments to the IASB provided that such copies are for personal or internal use, are not sold or otherwise disseminated, acknowledge the IFRS Foundation's copyright and set out the IASB's address in full. Except as permitted above no part of this publication may be translated, reprinted, reproduced or used in any form either in whole or in part or by any electronic, mechanical or other means, now known or hereafter invented, including photocopying and recording, or in any information storage and retrieval system, without prior permission in writing from the IFRS Foundation. The approved text of International Financial Reporting Standards and other IASB publications is that published by the IASB in the English language. Copies may be obtained from the IFRS Foundation. Please address publications and copyright matters to: IFRS Foundation Publications Department 30 Cannon Street, London EC4M 6XH, United Kingdom Tel: +44 (0)20 7332 2730 Fax: +44 (0)20 7332 2749 Email: publications@ifrs.org Web: www.ifrs.org The IFRS Foundation logo/the IASB logo/the IFRS for SMEs logo/'Hexagon Device', 'IFRS Foundation', 'IFRS Taxonomy', 'eIFRS', 'IASB', 'IFRS for SMEs', 'IAS', 'IASs', 'IFRIC', 'IFRS', 'IFRSs', 'SIC', 'International Accounting Standards' and 'International Financial Reporting Standards' are Trade Marks of the IFRS Foundation. Further details of the Trade Marks, including details of countries where the Trade Marks are registered or applied for, are available from the IFRS Foundation on request. The IFRS Foundation is a not-for-profit corporation under the General Corporation Law of the State of Delaware, USA and operates in England and Wales as an overseas company (Company number: FC023235) with its principal office as above. EFFECTIVE DATE OF IFRS 15 (PROPOSED AMENDMENTS TO IFRS 15) CONTENTS from page EFFECTIVE DATE OF IFRS 15 (PROPOSED AMENDMENTS TO IFRS 15) INTRODUCTION 4 INVITATION TO COMMENT 5 [DRAFT] AMENDMENTS TO IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS 6 APPROVAL BY THE BOARD OF EFFECTIVE DATE OF IFRS 15 (PROPOSED AMENDMENTS TO IFRS 15) PUBLISHED IN MAY 2015 7 BASIS FOR CONCLUSIONS ON THE EXPOSURE DRAFT EFFECTIVE DATE OF IFRS 15 (PROPOSED AMENDMENTS TO IFRS 15) 8 3 IFRS Foundation EXPOSURE DRAFTMAY 2015 Introduction The International Accounting Standards Board (IASB) has published this Exposure Draft of proposed amendments to IFRS 15 Revenue from Contracts with Customers to propose changing the effective date of IFRS 15. Accordingly, entities would be required to apply IFRS 15 for annual reporting periods beginning on or after 1 January 2018 rather than being required to apply IFRS 15 for annual reporting periods beginning on or after 1 January 2017. Earlier application of IFRS 15 would continue to be permitted. Entities would also continue to be permitted to choose between applying the Standard either retrospectively to each prior reporting period presented or retrospectively with the cumulative effect of initially applying the Standard recognised at the date of initial application. The IASB also plans to propose targeted amendments to IFRS 15 to clarify aspects of the requirements. Those proposed amendments will be included in a further Exposure Draft to be published later in 2015. Next steps The IASB will consider the comments it receives on the proposal and plans to decide whether to proceed with an amendment to IFRS 15 regarding the effective date at its July 2015 meeting. IFRS Foundation 4 EFFECTIVE DATE OF IFRS 15 (PROPOSED AMENDMENTS TO IFRS 15) Invitation to comment The IASB invites comments on the proposal in this Exposure Draft, particularly on the question set out below. Comments are most helpful if they: (a) comment on the question as stated; (b) indicate the specific paragraph or group of paragraphs to which they relate; (c) contain a clear rationale; and (d) include any alternative that the IASB should consider, if applicable. The IASB is not requesting comments on matters in IFRS 15 that are not addressed in this Exposure Draft. Comments should be submitted in writing so as to be received no later than 3 July 2015. Question on the effective date Question The IASB proposes to amend IFRS 15 so that entities would be required to apply IFRS 15 for annual reporting periods beginning on or after 1 January 2018. Earlier application would continue to be permitted. Do you agree? Why or why not? 5 IFRS Foundation EXPOSURE DRAFTMAY 2015 [Draft] Amendments to IFRS 15 Revenue from Contracts with Customers In Appendix C, paragraphs C1 and C7 are amended. Deleted text is struck through and new text is underlined. Effective date C1 An entity shall apply this Standard for annual reporting periods beginning on or after 1 January 2017 2018. Earlier application is permitted. If an entity applies this Standard earlier, it shall disclose that fact. Transition ... C7 If an entity elects to apply this Standard retrospectively in accordance with paragraph C3(b), the entity shall recognise the cumulative effect of initially applying this Standard as an adjustment to the opening balance of retained earnings (or other component of equity, as appropriate) of the annual reporting period that includes the date of initial application. Under this transition method, an entity shall apply this Standard retrospectively only to contracts that are not completed contracts at the date of initial application (for example, 1 January 2017 2018 for an entity with a 31 December year-end). IFRS Foundation 6 EFFECTIVE DATE OF IFRS 15 (PROPOSED AMENDMENTS TO IFRS 15) Approval by the Board of Effective Date of IFRS 15 (Proposed amendments to IFRS 15) published in May 2015 The Exposure Draft Effective Date of IFRS 15 was approved for publication by the fourteen members of the International Accounting Standards Board. Hans Hoogervorst Chairman Ian Mackintosh Vice-Chairman Stephen Cooper Philippe Danjou Amaro Luiz De Oliveira Gomes Martin Edelmann Patrick Finnegan Gary Kabureck Suzanne Lloyd Takatsugu Ochi Darrel Scott Chungwoo Suh Mary Tokar Wei-Guo Zhang 7 IFRS Foundation EXPOSURE DRAFTMAY 2015 Basis for Conclusions on the Exposure Draft Effective Date of IFRS 15 (Proposed amendments to IFRS 15) This Basis for Conclusions accompanies, but is not part of, the draft amendments. Effective date (paragraph C1) BC1 In May 2014, the IASB issued IFRS 15 Revenue from Contracts with Customers with an effective date of 1 January 2017; earlier application is permitted. At the same time, the US national standard-setter, the Financial Accounting Standards Board (FASB), issued Accounting Standards Update No. 2014-09 Revenue from Contracts with Customers (Topic 606) with an effective date of 15 December 2016. IFRS 15 and Topic 606 include requirements that are substantially the same. BC2 After issuing IFRS 15 and Topic 606, the IASB and the FASB formed a joint Transition Resource Group (TRG) for Revenue Recognition to support the implementation of the Standard. The substantial majority of the issues discussed by the TRG have been resolved without the need for standard-setting activity. However, at the date of publication of this Exposure Draft, the IASB had tentatively decided to propose targeted amendments to IFRS 15, which include clarifying the guidance on licences and adding examples illustrating the guidance on identifying performance obligations. The IASB also plans to discuss possible clarifications to the guidance on principal versus agent considerations. BC3 In the light of those proposed amendments, the IASB discussed whether it should propose to defer the effective date of IFRS 15. At the time of the IASB's discussion, the FASB had already decided to propose to defer the effective date of Topic 606 for public entities by one year to 15 December 2017, with earlier application permitted for annual reporting periods beginning after the original effective date of 15 December 2016. The IASB had also received a number of unsolicited comment letters from stakeholders supporting a deferral of the effective date of IFRS 15. Those stakeholders indicated that, in their view, a one-year deferral would improve the quality of implementation, particularly in the light of the availability (or lack thereof) of information technology systems. BC4 Changing the effective date of a Standard shortly after its issuance creates uncertainty for stakeholders and has the potential to set a bad precedent. The effective date is set after careful consideration of information obtained in the exposure process about the time needed to implement the requirements. Accordingly, the IASB would consider doing so only in exceptional circumstances. The IASB noted that it had already provided a considerable amount of time between issuing IFRS 15 and the effective date, anticipating that some entities would be required to change information technology systems and processes when adopting the Standard. The IASB has also provided substantive relief on transition to IFRS 15 by giving entities a choice of transition methods, one of which does not involve the restatement of comparative financial information. In addition, the IASB observed that the proposed targeted amendments to IFRS 15 are expected to clarify, instead of change, the requirements of the Standard. IFRS Foundation 8 EFFECTIVE DATE OF IFRS 15 (PROPOSED AMENDMENTS TO IFRS 15) BC5 Some stakeholders had requested a deferral of the effective date because the time required to implement the Standard is longer than they had initially anticipated. However, the IASB observed that deferring the effective date for this reason could potentially penalise those who start the implementation process early and reward those who delay, which the IASB does not view as appropriate. In addition, although retaining an aligned effective date between IFRS 15 and Topic 606 is desirable, the IASB observed that it is not the only factor that it should consider. BC6 Nonetheless, despite those concerns, the IASB decided to propose a one-year deferral of the effective date of IFRS 15 to 1 January 2018 because of the combination of the following factors that result in the current situation regarding IFRS 15 being exceptional: (a) the IASB acknowledged that, although intended to provide clarity, the proposed amendments to IFRS 15 noted in paragraph BC2 may affect some entities that would wish to apply the amendments at the same time as they first apply IFRS 15those entities are likely to wish to avoid reporting changes to revenue when first implementing the Standard and then, within a year or two, potentially reporting further changes to revenue as a result of applying any amendments to the Standard. For those entities, a deferral of the effective date by one year would provide additional time to implement any amendments to the Standard. (b) IFRS 15 was issued later than had been anticipated when the IASB set the effective date of the Standard, which absorbed some of the implementation time that entities were expecting to have. (c) IFRS 15 is a converged Standard with Topic 606although not the only consideration, the IASB thinks that there are benefits for a broad range of stakeholders of retaining an effective date that is aligned with the effective date of Topic 606. BC7 In reaching this decision, the IASB concluded that a one-year deferral is sufficient in terms of providing additional time to implement IFRS 15. IASB members noted that a number of stakeholders had indicated that a deferral of the effective date of IFRS 15 is not needed while those supporting a deferral had requested only a one-year deferral. IASB members also observed that the issuance of IFRS 15 in May 2014 had been later than anticipated by some months, not years. Accordingly, a deferral of the effective date of IFRS 15 for anything longer than one year would unnecessarily prolong the period of uncertainty regarding the Standard, which would not be beneficial for stakeholders. It would also delay transition by many entities to a new Standard that the IASB views as a substantial improvement to financial reporting. BC8 At the date of publication of this Exposure Draft, the IASB had not yet decided upon the effective date of the proposed amendments to IFRS 15 noted in paragraph BC2, which it plans to consider at a future IASB meeting. 9 IFRS Foundation International Accounting Standards Board (IASB ) The IASB is the independent standard-setting body of the IFRS Foundation 30 Cannon Street | London EC4M 6XH | United Kingdom Telephone: +44 (0)20 7246 6410 | Fax: +44 (0)20 7246 6411 Email: info@ifrs.org | Web: www.ifrs.org Publications Department Telephone: +44 (0)20 7332 2730 | Fax: +44 (0)20 7332 2749 Email: publications@ifrs.org IFRS 15 International Financial Reporting Standard 15 Revenue from Contracts with Customers In April 2001 the International Accounting Standards Board (IASB) adopted IAS 11 Construction Contracts and IAS 18 Revenue, both of which had originally been issued by the International Accounting Standards Committee (IASC) in December 1993. IAS 18 replaced a previous version: Revenue Recognition (issued in December 1982). IAS 11 replaced parts of IAS 11 Accounting for Construction Contracts (issued in March 1979). In December 2001 the IASB issued SIC-31 RevenueBarter Transactions Involving Advertising Services. The Interpretation was originally developed by the Standards Interpretations Committee of the IASC to determine the circumstances in which a seller of advertising services can reliably measure revenue at the fair value of advertising services provided in a barter transaction. In June 2007 the IASB issued IFRIC 13 Customer Loyalty Programmes. The Interpretation was developed by the IFRS Interpretations Committee (the 'Interpretations Committee') to address the accounting by the entity that grants award credits to its customers. In July 2008 the IASB issued IFRIC 15 Agreements for the Construction of Real Estate. The Interpretation was developed by the Interpretations Committee to apply to the accounting for revenue and associated expenses by entities that undertake the construction of real estate directly or through subcontractors. In January 2009 the IASB issued IFRIC 18 Transfers of Assets from Customers. The Interpretation was developed by the Interpretations Committee to apply to the accounting for transfers of items of property, plant and equipment by entities that receive such transfers from their customers. In May 2014 the IASB issued IFRS 15 Revenue from Contracts with Customers, together with the introduction of Topic 606 into the Financial Accounting Standards Board's Accounting Standards Codification. IFRS 15 replaces IAS 11, IAS 18, IFRIC 13, IFRIC 15, IFRIC 18 and SIC-31. IFRS 15 provides a comprehensive framework for recognising revenue from contracts with customers. IFRS Foundation A675 IFRS 15 CONTENTS from paragraph INTRODUCTION IN1 INTERNATIONAL FINANCIAL REPORTING STANDARD 15 REVENUE FROM CONTRACTS WITH CUSTOMERS OBJECTIVE 1 Meeting the objective 2 SCOPE 5 RECOGNITION 9 Identifying the contract 9 Combination of contracts 17 Contract modifications 18 Identifying performance obligations 22 Satisfaction of performance obligations 31 MEASUREMENT 46 Determining the transaction price 47 Allocating the transaction price to performance obligations 73 Changes in the transaction price 87 CONTRACT COSTS 91 Incremental costs of obtaining a contract 91 Costs to fulfil a contract 95 Amortisation and impairment 99 PRESENTATION 105 DISCLOSURE 110 Contracts with customers 113 Significant judgements in the application of this Standard 123 Assets recognised from the costs to obtain or fulfil a contract with a customer 127 Practical expedients 129 APPENDICES A Defined terms B Application Guidance C Effective date and transition D Amendments to other Standards FOR THE ACCOMPANYING DOCUMENTS LISTED BELOW, SEE PART B OF THIS EDITION APPROVAL BY THE BOARD OF IFRS 15 REVENUE FROM CONTRACTS WITH CUSTOMERS ISSUED IN MAY 2014 BASIS FOR CONCLUSIONS A676 IFRS Foundation IFRS 15 APPENDICES A Comparison of IFRS 15 and Topic 606 B Amendments to the Basis for Conclusions on other Standards ILLUSTRATIVE EXAMPLES APPENDIX Amendments to the guidance on other Standards IFRS Foundation A677 IFRS 15 International Financial Reporting Standard 15 Revenue from Contracts with Customers (IFRS 15) is set out in paragraphs 1-129 and Appendices A-D. All the paragraphs have equal authority. Paragraphs in bold type state the main principles. Terms defined in Appendix A are in italics the first time that they appear in the Standard. Definitions of other terms are given in the Glossary for International Financial Reporting Standards. The Standard should be read in the context of its objective and the Basis for Conclusions, the Preface to International Financial Reporting Standards and the Conceptual Framework for Financial Reporting. IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors provides a basis for selecting and applying accounting policies in the absence of explicit guidance. A678 IFRS Foundation IFRS 15 Introduction Overview IN1 International Financial Reporting Standard 15 Revenue from Contracts with Customers (IFRS 15) establishes principles for reporting useful information to users of financial statements about the nature, amount, timing and uncertainty of revenue and cash flows arising from an entity's contracts with customers. IN2 IFRS 15 is effective for annual periods beginning on or after 1 January 2017. Earlier application is permitted. IN3 IFRS 15 supersedes: (a) IAS 11 Construction Contracts; (b) IAS 18 Revenue; (c) IFRIC 13 Customer Loyalty Programmes; (d) IFRIC 15 Agreements for the Construction of Real Estate; (e) IFRIC 18 Transfers of Assets from Customers; and (f) SIC-31 RevenueBarter Transactions Involving Advertising Services. Reasons for issuing the IFRS IN4 Revenue is an important number to users of financial statements in assessing an entity's financial performance and position. However, previous revenue recognition requirements in International Financial Reporting Standards (IFRS) differed from those in US Generally Accepted Accounting Principles (US GAAP) and both sets of requirements were in need of improvement. Previous revenue recognition requirements in IFRS provided limited guidance and, consequently, the two main revenue recognition Standards, IAS 18 and IAS 11, could be difficult to apply to complex transactions. In addition, IAS 18 provided limited guidance on many important revenue topics such as accounting for multiple-element arrangements. In contrast, US GAAP comprised broad revenue recognition concepts together with numerous revenue requirements for particular industries or transactions, which sometimes resulted in different accounting for economically similar transactions. IN5 Accordingly, the International Accounting Standards Board (IASB) and the US national standard-setter, the Financial Accounting Standards Board (FASB), initiated a joint project to clarify the principles for recognising revenue and to develop a common revenue standard for IFRS and US GAAP that would: (a) remove inconsistencies requirements; and weaknesses (b) provide a more robust framework for addressing revenue issues; (c) improve comparability of revenue recognition practices across entities, industries, jurisdictions and capital markets; IFRS Foundation in previous revenue A679 IFRS 15 (d) (e) IN6 provide more useful information to users of financial statements through improved disclosure requirements; and simplify the preparation of financial statements by reducing the number of requirements to which an entity must refer. IFRS 15, together with Topic 606 that was introduced into the FASB Accounting Standards Codification by Accounting Standards Update 2014-09 Revenue from Contracts with Customers (Topic 606), completes the joint effort by the IASB and the FASB to meet those objectives and improve financial reporting by creating a common revenue recognition standard for IFRS and US GAAP. Main features IN7 The core principle of IFRS 15 is that an entity recognises revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. An entity recognises revenue in accordance with that core principle by applying the following steps: (a) (b) Step 2: Identify the performance obligations in the contracta contract includes promises to transfer goods or services to a customer. If those goods or services are distinct, the promises are performance obligations and are accounted for separately. A good or service is distinct if the customer can benefit from the good or service on its own or together with other resources that are readily available to the customer and the entity's promise to transfer the good or service to the customer is separately identifiable from other promises in the contract. (c) A680 Step 1: Identify the contract(s) with a customera contract is an agreement between two or more parties that creates enforceable rights and obligations. The requirements of IFRS 15 apply to each contract that has been agreed upon with a customer and meets specified criteria. In some cases, IFRS 15 requires an entity to combine contracts and account for them as one contract. IFRS 15 also provides requirements for the accounting for contract modifications. Step 3: Determine the transaction pricethe transaction price is the amount of consideration in a contract to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer. The transaction price can be a fixed amount of customer consideration, but it may sometimes include variable consideration or consideration in a form other than cash. The transaction price is also adjusted for the effects of the time value of money if the contract includes a significant financing component and for any consideration payable to the customer. If the consideration is variable, an entity estimates the amount of consideration to which it will be entitled in exchange for the promised goods or services. The estimated amount of variable consideration will be included in the transaction price only to the extent that it is highly probable that a significant reversal in the IFRS Foundation IFRS 15 amount of cumulative revenue recognised will not occur when the uncertainty associated with the variable consideration is subsequently resolved. (d) (e) IN8 Step 4: Allocate the transaction price to the performance obligations in the contractan entity typically allocates the transaction price to each performance obligation on the basis of the relative stand-alone selling prices of each distinct good or service promised in the contract. If a stand-alone selling price is not observable, an entity estimates it. Sometimes, the transaction price includes a discount or a variable amount of consideration that relates entirely to a part of the contract. The requirements specify when an entity allocates the discount or variable consideration to one or more, but not all, performance obligations (or distinct goods or services) in the contract. Step 5: Recognise revenue when (or as) the entity satisfies a performance obligationan entity recognises revenue when (or as) it satisfies a performance obligation by transferring a promised good or service to a customer (which is when the customer obtains control of that good or service). The amount of revenue recognised is the amount allocated to the satisfied performance obligation. A performance obligation may be satisfied at a point in time (typically for promises to transfer goods to a customer) or over time (typically for promises to transfer services to a customer). For performance obligations satisfied over time, an entity recognises revenue over time by selecting an appropriate method for measuring the entity's progress towards complete satisfaction of that performance obligation. IFRS 15 also includes a cohesive set of disclosure requirements that would result in an entity providing users of financial statements with comprehensive information about the nature, amount, timing and uncertainty of revenue and cash flows arising from the entity's contracts with customers. Specifically, IFRS 15 requires an entity to provide information about: (a) (b) contract balances, including the opening and closing balances of receivables, contract assets and contract liabilities; (c) performance obligations, including when the entity typically satisfies its performance obligations and the transaction price that is allocated to the remaining performance obligations in a contract; (d) significant judgements, and changes in judgements, made in applying the requirements to those contracts; and (e) IN9 revenue recognised from contracts with customers, including the disaggregation of revenue into appropriate categories; assets recognised from the costs to obtain or fulfil a contract with a customer. The IASB and the FASB achieved their goal of reaching the same conclusions on all requirements for the accounting for revenue from contracts with customers. IFRS Foundation A681 IFRS 15 As a result, IFRS 15 and Topic 606 are substantially the same. However, there are some minor differences which are outlined in the appendix to the Basis for Conclusions. A682 IFRS Foundation IFRS 15 International Financial Reporting Standard 15 Revenue from Contracts with Customers Objective 1 The objective of this Standard is to establish the principles that an entity shall apply to report useful information to users of financial statements about the nature, amount, timing and uncertainty of revenue and cash flows arising from a contract with a customer. Meeting the objective 2 To meet the objective in paragraph 1, the core principle of this Standard is that an entity shall recognise revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. 3 An entity shall consider the terms of the contract and all relevant facts and circumstances when applying this Standard. An entity shall apply this Standard, including the use of any practical expedients, consistently to contracts with similar characteristics and in similar circumstances. 4 This Standard specifies the accounting for an individual contract with a customer. However, as a practical expedient, an entity may apply this Standard to a portfolio of contracts (or performance obligations) with similar characteristics if the entity reasonably expects that the effects on the financial statements of applying this Standard to the portfolio would not differ materially from applying this Standard to the individual contracts (or performance obligations) within that portfolio. When accounting for a portfolio, an entity shall use estimates and assumptions that reflect the size and composition of the portfolio. Scope 5 An entity shall apply this Standard to all contracts with customers, except the following: (a) lease contracts within the scope of IAS 17 Leases; (b) insurance contracts within the scope of IFRS 4 Insurance Contracts; (c) financial instruments and other contractual rights or 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; and (d) non-monetary exchanges between entities in the same line of business to facilitate sales to customers or potential customers. For example, this Standard would not apply to a contract between two oil companies that agree to an exchange of oil to fulfil demand from their customers in different specified locations on a timely basis. IFRS Foundation A683 IFRS 15 6 An entity shall apply this Standard to a contract (other than a contract listed in paragraph 5) only if the counterparty to the contract is a customer. A customer is 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. A counterparty to the contract would not be a customer if, for example, the counterparty has contracted with the entity to participate in an activity or process in which the parties to the contract share in the risks and benefits that result from the activity or process (such as developing an asset in a collaboration arrangement) rather than to obtain the output of the entity's ordinary activities. 7 A contract with a customer may be partially within the scope of this Standard and partially within the scope of other Standards listed in paragraph 5. (a) (b) 8 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 the amount of the part (or parts) of the contract that are initially measured in accordance with other Standards and shall apply paragraphs 73-86 to allocate the amount of the transaction price that remains (if any) to each performance obligation within the scope of this Standard and to any other parts of the contract identified by paragraph 7(b). 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 this Standard to separate and/or initially measure the part (or parts) of the contract. This Standard specifies the accounting for the incremental costs of obtaining a contract with a customer and for the costs incurred to fulfil a contract with a customer if those costs are not within the scope of another Standard (see paragraphs 91-104). An entity shall apply those paragraphs only to the costs incurred that relate to a contract with a customer (or part of that contract) that is within the scope of this Standard. Recognition Identifying the contract 9 An entity shall account for a contract with a customer that is within the scope of this Standard only when all of the following criteria are met: (a) (b) the entity can identify each party's rights regarding the goods or services to be transferred; (c) A684 the parties to the contract have approved the contract (in writing, orally or in accordance with other customary business practices) and are committed to perform their respective obligations; the entity can identify the payment terms for the goods or services to be transferred; IFRS Foundation IFRS 15 (d) the contract has commercial substance (ie the risk, timing or amount of the entity's future cash flows is expected to change as a result of the contract); and (e) it is probable that the entity will collect the consideration to which it will be entitled in exchange for the goods or services that will be transferred to the customer. In evaluating whether collectability of an amount of consideration is probable, an entity shall consider only the customer's ability and intention to pay that amount of consideration when it is due. The amount of consideration to which the entity will be entitled may be less than the price stated in the contract if the consideration is variable because the entity may offer the customer a price concession (see paragraph 52). 10 A contract is an agreement between two or more parties that creates enforceable rights and obligations. Enforceability of the rights and obligations in a contract is a matter of law. Contracts can be written, oral or implied by an entity's customary business practices. The practices and processes for establishing contracts with customers vary across legal jurisdictions, industries and entities. In addition, they may vary within an entity (for example, they may depend on the class of customer or the nature of the promised goods or services). An entity shall consider those practices and processes in determining whether and when an agreement with a customer creates enforceable rights and obligations. 11 Some contracts with customers may have no fixed duration and can be terminated or modified by either party at any time. Other contracts may automatically renew on a periodic basis that is specified in the contract. An entity shall apply this Standard to the duration of the contract (ie the contractual period) in which the parties to the contract have present enforceable rights and obligations. 12 For the purpose of applying this Standard, 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 both of the following criteria are met: (a) the entity has not yet transferred any promised goods or services to the customer; and (b) the entity has not yet received, and is not yet entitled to receive, any consideration in exchange for promised goods or services. 13 If a contract with a customer meets the criteria in paragraph 9 at contract inception, an entity shall not reassess those criteria unless there is an indication of a significant change in facts and circumstances. For example, if a customer's ability to pay the consideration deteriorates significantly, an entity would reassess whether it is probable that the entity will collect the consideration to which the entity will be entitled in exchange for the remaining goods or services that will be transferred to the customer. 14 If a contract with a customer does not meet the criteria in paragraph 9, an entity shall continue to assess the contract to determine whether the criteria in paragraph 9 are subsequently met. IFRS Foundation A685 IFRS 15 15 When a contract with a customer does not meet the criteria in paragraph 9 and an entity receives consideration from the customer, the entity shall recognise the consideration received as revenue only when either of the following events has occurred: (a) (b) 16 the entity has no remaining obligations to transfer goods or services to the customer and all, or substantially all, of the consideration promised by the customer has been received by the entity and is non-refundable; or the contract has been terminated and the consideration received from the customer is non-refundable. An entity shall recognise the consideration received from a customer as a liability until one of the events in paragraph 15 occurs or until the criteria in paragraph 9 are subsequently met (see paragraph 14). Depending on the facts and circumstances relating to the contract, the liability recognised represents the entity's obligation to either transfer goods or services in the future or refund the consideration received. In either case, the liability shall be measured at the amount of consideration received from the customer. Combination of contracts 17 An entity shall combine two or more contracts entered into at or near the same time with the same customer (or related parties of the customer) and account for the contracts as a single contract if one or more of the following criteria are met: (a) the contracts are negotiated as a package with a single commercial objective; (b) the amount of consideration to be paid in one contract depends on the price or performance of the other contract; or (c) the goods or services promised in the contracts (or some goods or services promised in each of the contracts) are a single performance obligation in accordance with paragraphs 22-30. Contract modifications 18 A contract modification is a change in the scope or price (or both) of a contract that is approved by the parties to the contract. In some industries and jurisdictions, a contract modification may be described as a change order, a variation or an amendment. A contract modification exists when the parties to a contract approve a modification that either creates new or changes existing enforceable rights and obligations of the parties to the contract. A contract modification could be approved in writing, by oral agreement or implied by customary business practices. If the parties to the contract have not approved a contract modification, an entity shall continue to apply this Standard to the existing contract until the contract modification is approved. 19 A contract modification may exist even though the parties to the contract have a dispute about the scope or price (or both) of the modification or the parties have approved a change in the scope of the contract but have not yet determined the corresponding change in price. In determining whether the rights and obligations that are created or changed by a modification are enforceable, an entity shall consider all relevant facts and circumstances including the terms of A686 IFRS Foundation IFRS 15 the contract and other evidence. If the parties to a contract have approved a change in the scope of the contract but have not yet determined the corresponding change in price, an entity shall estimate the change to the transaction price arising from the modification in accordance with paragraphs 50-54 on estimating variable consideration and paragraphs 56-58 on constraining estimates of variable consideration. 20 An entity shall account for a contract modification as a separate contract if both of the following conditions are present: (a) (b) 21 the scope of the contract increases because of the addition of promised goods or services that are distinct (in accordance with paragraphs 26-30); and the price of the contract increases by an amount of consideration that reflects the entity's stand-alone selling prices of the additional promised goods or services and any appropriate adjustments to that price to reflect the circumstances of the particular contract. For example, an entity may adjust the stand-alone selling price of an additional good or service for a discount that the customer receives, because it is not necessary for the entity to incur the selling-related costs that it would incur when selling a similar good or service to a new customer. If a contract modification is not accounted for as a separate contract in accordance with paragraph 20, an entity shall account for the promised goods or services not yet transferred at the date of the contract modification (ie the remaining promised goods or services) in whichever of the following ways is applicable: (a) An entity shall account for the contract modification as if it were a termination of the existing contract and the creation of a new contract, if the remaining goods or services are distinct from the goods or services transferred on or before the date of the contract modification. The amount of consideration to be allocated to the remaining performance obligations (or to the remaining distinct goods or services in a single performance obligation identified in accordance with paragraph 22(b)) is the sum of: (i) (ii) (b) the consideration promised by the customer (including amounts already received from the customer) that was included in the estimate of the transaction price and that had not been recognised as revenue; and the consideration promised as part of the contract modification. An entity shall account for the contract modification as if it were a part of the existing contract if the remaining goods or services are not distinct and, therefore, form part of a single performance obligation that is partially satisfied at the date of the contract modification. The effect that the contract modification has on the transaction price, and on the entity's measure of progress towards complete satisfaction of the performance obligation, is recognised as an adjustment to revenue IFRS Foundation A687 IFRS 15 (either as an increase in or a reduction of revenue) at the date of the contract modification (ie the adjustment to revenue is made on a cumulative catch-up basis). (c) If the remaining goods or services are a combination of items (a) and (b), then the entity shall account for the effects of the modification on the unsatisfied (including partially unsatisfied) performance obligations in the modified contract in a manner that is consistent with the objectives of this paragraph. Identifying performance obligations 22 At contract inception, an entity shall assess the goods or services promised in a contract with a customer and shall identify as a performance obligation each promise to transfer to the customer either: (a) (b) 23 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 (see paragraph 23). A series of distinct goods or services has the same pattern of transfer to the customer if both of the following criteria are met: (a) each distinct good or service in the series that the entity promises to transfer to the customer would meet the criteria in paragraph 35 to be a performance obligation satisfied over time; and (b) in accordance with paragraphs 39-40, the same method would be used to measure the entity's progress towards complete satisfaction of the performance obligation to transfer each distinct good or service in the series to the customer. Promises in contracts with customers 24 A contract with a customer generally explicitly states the goods or services that an entity promises to transfer to a customer. However, the performance obligations identified in a contract with a customer may not be limited to the goods or services that are explicitly stated in that contract. This is because a contract with a customer may also include promises that are implied by an entity's customary business practices, published policies or specific statements if, at the time of entering into the contract, those promises create a valid expectation of the customer that the entity will transfer a good or service to the customer. 25 Performance obligations do not include activities that an entity must undertake to fulfil a contract unless those activities transfer a good or service to a customer. For example, a services provider may need to perform various administrative tasks to set up a contract. The performance of those tasks does not transfer a service to the customer as the tasks are performed. Therefore, those setup activities are not a performance obligation. A688 IFRS Foundation IFRS 15 Distinct goods or services 26 Depending on the contract, promised goods or services may include, but are not limited to, the following: (a) (b) resale of goods purchased by an entity (for example, merchandise of a retailer); (c) resale of rights to goods or services purchased by an entity (for example, a ticket resold by an entity acting as a principal, as described in paragraphs B34-B38); (d) performing a contractually agreed-upon task (or tasks) for a customer; (e) providing a service of standing ready to provide goods or services (for example, unspecified updates to software that are provided on a when-and-if-available basis) or of making goods or services available for a customer to use as and when the customer decides; (f) providing a service of arranging for another party to transfer goods or services to a customer (for example, acting as an agent of another party, as described in paragraphs B34-B38); (g) granting rights to goods or services to be provided in the future that a customer can resell or provide to its customer (for example, an entity selling a product to a retailer promises to transfer an additional good or service to an individual who purchases the product from the retailer); (h) constructing, manufacturing or developing an asset on behalf of a customer; (i) granting licences (see paragraphs B52-B63); and (j) 27 sale of goods produced by an entity (for example, inventory of a manufacturer); granting options to purchase additional goods or services (when those options provide a customer with a material right, as described in paragraphs B39-B43). A good or service that is promised to a customer is distinct if both of the following criteria are met: (a) (b) 28 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 (ie the good or service is capable of being distinct); and the entity's promise to transfer the good or service to the customer is separately identifiable from other promises in the contract (ie the good or service is distinct within the context of the contract). A customer can benefit from a good or service in accordance with paragraph 27(a) if the good or service could be used, consumed, sold for an amount that is greater than scrap value or otherwise held in a way that generates economic benefits. For some goods or services, a customer may be able to benefit from a good or service on its own. For other goods or services, a customer may be able to benefit from the good or service only in conjunction with other readily available resources. A readily available resource is a good or IFRS Foundation A689 IFRS 15 service that is sold separately (by the entity or another entity) or a resource that the customer has already obtained from the entity (including goods or services that the entity will have already transferred to the customer under the contract) or from other transactions or events. Various factors may provide evidence that the customer can benefit from a good or service either on its own or in conjunction with other readily available resources. For example, the fact that the entity regularly sells a good or service separately would indicate that a customer can benefit from the good or service on its own or with other readily available resources. 29 Factors that indicate that an entity's promise to transfer a good or service to a customer is separately identifiable (in accordance with paragraph 27(b)) include, but are not limited to, the following: (a) (b) the good or service does not significantly modify or customise another good or service promised in the contract. (c) 30 the entity does not provide a significant service of integrating the good or service with other goods or services promised in the contract into a bundle of goods or services that represent the combined output for which the customer has contracted. In other words, the entity is not using the good or service as an input to produce or deliver the combined output specified by the customer. the good or service is not highly dependent on, or highly interrelated with, other goods or services promised in the contract. For example, the fact that a customer could decide to not purchase the good or service without significantly affecting the other promised goods or services in the contract might indicate that the good or service is not highly dependent on, or highly interrelated with, those other promised goods or services. If a promised good or service is not distinct, an entity shall combine that good or service with other promised goods or services until it identifies a bundle of goods or services that is distinct. In some cases, that would result in the entity accounting for all the goods or services promised in a contract as a single performance obligation. Satisfaction of performance obligations 31 An entity shall recognise revenue when (or as) the entity satisfies a performance obligation by transferring a promised good or service (ie an asset) to a customer. An asset is transferred when (or as) the customer obtains control of that asset. 32 For each performance obligation identified in accordance with paragraphs 22-30, an entity shall determine at contract inception whether it satisfies the performance obligation over time (in accordance with paragraphs 35-37) or satisfies the performance obligation at a point in time (in accordance with paragraph 38). If an entity does not satisfy a performance obligation over time, the performance obligation is satisfied at a point in time. 33 Goods and services are assets, even if only momentarily, when they are received and used (as in the case of many services). Control of an asset refers to the ability A690 IFRS Foundation IFRS 15 to direct the use of, and obtain substantially all of the remaining benefits from, the asset[G]. Control includes the ability to prevent other entities from directing the use of, and obtaining the benefits from, an asset. The benefits of an asset are the potential cash flows (inflows or savings in outflows) that can be obtained directly or indirectly in many ways, such as by: (a) (b) using the asset to enhance the value of other assets; (c) using the asset to settle liabilities or reduce expenses; (d) selling or exchanging the asset; (e) pledging the asset to secure a loan; and (f) 34 using the asset to produce goods or provide services (including public services); holding the asset. When evaluating whether a customer obtains control of an asset, an entity shall consider any agreement to repurchase the asset (see paragraphs B64-B76). Performance obligations satisfied over time 35 An entity transfers control of a good or service over time and, therefore, satisfies a performance obligation and recognises revenue over time, if one of the following criteria is met: (a) the customer simultaneously receives and consumes the benefits provided by the entity's performance as the entity performs (see paragraphs B3-B4); (b) the entity's performance creates or enhances an asset (for example, work in progress) that the customer controls as the asset is created or enhanced (see paragraph B5); or (c) the entity's performance does not create an asset with an alternative use to the entity (see paragraph 36) and the entity has an enforceable right to payment for performance completed to date (see paragraph 37). 36 An asset created by an entity's performance does not have an alternative use to an entity if the entity is either restricted contractually from readily directing the asset for another use during the creation or enhancement of that asset or limited practically from readily directing the asset in its completed state for another use. The assessment of whether an asset has an alternative use to the entity is made at contract inception. After contract inception, an entity shall not update the assessment of the alternative use of an asset unless the parties to the contract approve a contract modification that substantively changes the performance obligation. Paragraphs B6-B8 provide guidance for assessing whether an asset has an alternative use to an entity. 37 An entity shall consider the terms of the contract, as well as any laws that apply to the contract, when evaluating whether it has an enforceable right to payment for performance completed to date in accordance with paragraph 35(c). The right to payment for performance completed to date does not need to be for a fixed amount. However, at all times throughout the duration of the contract, the entity must be entitled to an amount that at least compensates the entity for IFRS Foundation A691 IFRS 15 performance completed to date if the contract is terminated by the customer or another party for reasons other than the entity's failure to perform as promised. Paragraphs B9-B13 provide guidance for assessing the existence and enforceability of a right to payment and whether an entity's right to payment would entitle the entity to be paid for its performance completed to date. Performance obligations satisfied at a point in time 38 If a performance obligation is not satisfied over time in accordance with paragraphs 35-37, an entity satisfies the performance obligation at a point in time. To determine the point in time at which a customer obtains control of a promised asset and the entity satisfies a performance obligation, the entity shall consider the requirements for control in paragraphs 31-34. In addition, an entity shall consider indicators of the transfer of control, which include, but are not limited to, the following: (a) (b) The customer has legal title to the assetlegal title may indicate which party to a contract has the ability to direct the use of, and obtain substantially all of the remaining benefits from, an asset or to restrict the access of other entities to those benefits. Therefore, the transfer of legal title of an asset may indicate that the customer has obtained control of the asset. If an entity retains legal title solely as protection against the customer's failure to pay, those rights of the entity would not preclude the customer from obtaining control of an asset. (c) The entity has transferred physical possession of the assetthe customer's physical possession of an asset may indicate that the customer has the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset or to restrict the access of other entities to those benefits. However, physical possession may not coincide with control of an asset. For example, in some repurchase agreements and in some consignment arrangements, a customer or consignee may have physical possession of an asset that the entity controls. Conversely, in some bill-and-hold arrangements, the entity may have physical possession of an asset that the customer controls. Paragraphs B64-B76, B77-B78 and B79-B82 provide guidance on accounting for repurchase agreements, consignment arrangements and bill-and-hold arrangements, respectively. (d) A692 The entity has a present right to payment for the assetif a customer is presently obliged to pay for an asset, then that may indicate that the customer has obtained the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset in exchange. The customer has the significant risks and rewards of ownership of the assetthe transfer of the significant risks and rewards of ownership of an asset to the customer may indicate that the customer has obtained the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset. However, when evaluating the risks and rewards of ownership of a promised asset, an entity shall exclude any risks that give rise to a separate performance obligation in addition to the performance obligation to transfer the asset. For example, an entity IFRS Foundation IFRS 15 may have transferred control of an asset to a customer but not yet satisfied an additional performance obligation to provide maintenance services related to the transferred asset. (e) The customer has accepted the assetthe customer's acceptance of an asset may indicate that it has obtained the ability to direct the use of, and obtain substantially all of the remaining benefits from, the asset. To evaluate the effect of a contractual customer acceptance clause on when control of an asset is transferred, an entity shall consider the guidance in paragraphs B83-B86. Measuring progress towards complete satisfaction of a performance obligation 39 For each performance obligation satisfied over time in accordance with paragraphs 35-37, an entity shall recognise revenue over time by measuring the progress towards complete satisfaction of that performance obligation. The objective when measuring progress is to depict an entity's performance in transferring control of goods or services promised to a customer (ie the satisfaction of an entity's performance obligation). 40 An entity shall apply a single method of measuring progress for each performance obligation satisfied over time and the entity shall apply that method consistently to similar performance obligations and in similar circumstances. At the end of each reporting period, an entity shall remeasure its progress towards complete satisfaction of a performance obligation satisfied over time. Methods for measuring progress 41 Appropriate methods of measuring progress include output methods and input methods. Paragraphs B14-B19 provide guidance for using output methods and input methods to measure an entity's progress towards complete satisfaction of a performance obligation. In determining the appropriate method for measuring progress, an entity shall consider the nature of the good or service that the entity promised to transfer to the customer. 42 When applying a method for measuring progress, an entity shall exclude from the measure of progress any goods or services for which the entity does not transfer control to a customer. Conversely, an entity shall include in the measure of progress any goods or services for which the entity does transfer control to a customer when satisfying that performance obligation. 43 As circumstances change over time, an entity shall update its measure of progress to reflect any changes in the outcome of the performance obligation. Such changes to an entity's measure of progress shall be accounted for as a change in accounting estimate in accordance with IAS 8 Accounting Policies, Changes in Accounting Estimates and Errors. Reasonable measures of progress 44 An entity shall recognise revenue for a performance obligation satisfied over time only if the entity can reasonably measure its progress towards complete satisfaction of the performance obligation. An entity would not be able to IFRS Foundation A693 IFRS 15 reasonably measure its progress towards complete satisfaction of a performance obligation if it lacks reliable information that would be required to apply an appropriate method of measuring progress. 45 In some circumstances (for example, in the early stages of a contract), an entity may not be able to reasonably measure the outcome of a performance obligation, but the entity expects to recover the costs incurred in satisfying the performance obligation. In those circumstances, the entity shall recognise revenue only to the extent of the costs incurred until such time that it can reasonably measure the outcome of the performance obligation. Measurement 46 When (or as) a performance obligation is satisfied, an entity shall recognise as revenue the amount of the transaction price (which excludes estimates of variable consideration that are constrained in accordance with paragraphs 56-58) that is allocated to that performance obligation. Determining the transaction price 47 An entity shall consider the terms of the contract and its customary business practices to determine the transaction price. The transaction price is 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 (for example, some sales taxes). The consideration promised in a contract with a customer may include fixed amounts, variable amounts, or both. 48 The nature, timing and amount of consideration promised by a customer affect the estimate of the transaction price. When determining the transaction price, an entity shall consider the effects of all of the following: (a) (b) constraining estimates of variable consideration (see paragraphs 56-58); (c) the existence of a significant financing component in the contract (see paragraphs 60-65); (d) non-cash consideration (see paragraphs 66-69); and (e) 49 variable consideration (see paragraphs 50-55 and 59); consideration payable to a customer (see paragraphs 70-72). For the purpose of determining the transaction price, an entity shall assume that the goods or services will be transferred to the customer as promised in accordance with the existing contract and that the contract will not be cancelled, renewed or modified. Variable consideration 50 If the consideration promised in a contract includes a variable amount, an entity shall estimate the amount of consideration to which the entity will be entitled in exchange for transferring the promised goods or services to a customer. 51 An amount of consideration can vary because of discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties or other A694 IFRS Foundation IFRS 15 similar items. The promised consideration can also vary if an entity's entitlement to the consideration is contingent on the occurrence or non-occurrence of a future event. For example, an amount of consideration would be variable if either a product was sold with a right of return or a fixed amount is promised as a performance bonus on achievement of a specified milestone. 52 The variability relating to the consideration promised by a customer may be explicitly stated in the contract. In addition to the terms of the contract, the promised consideration is variable if either of the following circumstances exists: (a) (b) 53 the customer has a valid expectation arising from an entity's customary business practices, published policies or specific statements that the entity will accept an amount of consideration that is less than the price stated in the contract. That is, it is expected that the entity will offer a price concession. Depending on the jurisdiction, industry or customer this offer may be referred to as a discount, rebate, refund or credit. other facts and circumstances indicate that the entity's intention, when entering into the contract with the customer, is to offer a price concession to the customer. An entity shall estimate an amount of variable consideration by using either of the following methods, depending on which method the entity expects to better predict the amount of consideration to which it will be entitled: (a) (b) 54 The expected valuethe expected value is the sum of probability-weighted amounts in a range of possible consideration amounts. An expected value may be an appropriate estimate of the amount of variable consideration if an entity has a large number of contracts with similar characteristics. The most likely amountthe most likely amount is the single most likely amount in a range of possible consideration amounts (ie the single most likely outcome of the contract). The most likely amount may be an appropriate estimate of the amount of variable consideration if the contract has only two possible outcomes (for example, an entity either achieves a performance bonus or does not). An entity shall apply one method consistently throughout the contract when estimating the effect of an uncertainty on an amount of variable consideration to which the entity will be entitled. In addition, an entity shall consider all the information (historical, current and forecast) that is reasonably available to the entity and shall identify a reasonable number of possible consideration amounts. The information that an entity uses to estimate the amount of variable consideration would typically be similar to the information that the entity's management uses during the bid-and-proposal process and in establishing prices for promised goods or services. Refund liabilities 55 An entity shall recognise a refund liability if the entity receives consideration from a customer and expects to refund some or all of that consideration to the IFRS Foundation A695 IFRS 15 customer. A refund liability is measured at the amount of consideration received (or receivable) for which the entity does not expect to be entitled (ie amounts not included in the transaction price). The refund liability (and corresponding change in the transaction price