IASB FASB. Paper topic. 1. The. (a) (b) and-if available software. updates. The software is considered to. customer. Page 1 of 5



Similar documents
FASB/IASB Joint Transition Resource Group for Revenue Recognition

Revenue Recognition Measuring progress towards complete satisfaction of a performance obligation

Revenue recognition Application of the model: Credit card reward programs

Meeting. Project Paper topic. nts from. 1. This is the first. (a) (b) (c) plan. 3. The Joanna Yeoh

FASB Agenda. April Project. What is. 1. Policy loans. Izabela Ruta Chris Irwin Jennifer Weiner. Page 1 of 17. IFRSs.

Joint Capital Markets Advisory Committee and Global Preparers Forum meeting 20 June 2012, Agenda paper 4, Appendix D

STAFF PAPER. IASB Agenda ref. FASB Agenda ref 286. June REG FASB IASB Meeting. Purpose

FASB/IASB Joint Transition Resource Group for Revenue Recognition October 2014 Meeting Summary of Issues Discussed and Next Steps

IASB FASB. Paper topic. 3. The as: 4. The. and. Lauren. Alexander. Page 1 of 16

Revenue from contracts with customers The standard is final A comprehensive look at the new revenue model

IFRS 15 Revenue from Contracts with Customers

1. The purpose of this paper is to discuss the assessment of whether a contract contains a lease and does not discuss:

1. The purpose of this paper is to discuss disclosure requirements for a lessor in the final leases standard.

STAFF PAPER. IASB Agenda ref 2A. FASB Agenda ref 89A. 20 September 27 September REG FASB IASB Meeting

Overview of the proposed approaches. Approach 1 Retain proposals from 2013 ED

Financial Instruments: Classification and Measurement Contractual Cash Flow Characteristics: Amortised Cost as a Measurement Basis

Technology Spotlight The Future of Revenue Recognition


Revenue recognition Contracts with customers that contain nonrecourse, seller-based financing

1. The purpose of this paper is to discuss various issues with respect to the accounting for sale and leaseback transactions.

How To Account For Credit Card Fees In The New Revenue Standard

14A. Project. the definition of. (paragraph 16): Paper topic. Joaoo Santos (FI) org. the IASB.

A new global standard on revenue

Constraining the cumulative amount of revenue recognised

Financial Reporting Brief: Roadmap to Understanding the New Revenue Recognition Standards

Understanding the New Revenue Recognition Model. Marion Adams, CPA Swenson Advisors, LLP

IFRS 15 Revenue from Contracts with Customers

Aerospace & Defense Spotlight The Converged Revenue Recognition Model Has Landed

New on the Horizon: Revenue recognition for technology companies

IFRS 15: an overview of the new principles of revenue recognition

CONTACT(S) Kazuhiro Sakaguchi +44 (0)

IASB/FASB Meeting Week commencing September 19, Education session for week commencing September 5, 2011

Presentation in statement of comprehensive income comparison of methods

Revenue from contracts with customers The standard is final A comprehensive look at the new revenue model

Revenue from contracts with customers

Revenue from Contracts with Customers

IFRS 13 Fair Value Measurement Short-term receivables and payables. CONTACT(S) Barbara Jaworek +44 (0)

CONTACTS Kathryn Donkersley Patrina Buchanan

Disclosures Offsetting Financial Assets and Financial Liabilities (Amendments to IFRS 7)

IFRS APPLICATION AROUND THE WORLD JURISDICTIONAL PROFILE: United States of America

IFRS industry insights

How To Classify A Share Based Payment With A Contingent Settlement Feature In Ifrs 2

CONTACT(S) Amy Bannister +44 (0) Kristy Robinson +44 (0)

Snapshot: Offsetting Financial Assets and Financial Liabilities

Revenue recognition The standard is final A comprehensive look at the new revenue model

Accounting & Auditing News IFRS 15 Revenue from Contracts with Customers: Part 2 Differences vs. IAS 11 Construction Contracts

Revenue Recognition (Topic 605)

Narrow-scope amendments to IFRS 2 Share-based Payment Share-based payments settled net of tax withholdings

IASB/FASB Meeting Week commencing 16 May IASB/FASB Education Sessions Week commencing 9 May Lessee accounting other-than-finance lease

Revenue from contracts with customers The standard is final A comprehensive look at the new revenue model

Contact(s) Joanna Yeoh +44 (0) Brian North Unbundling investment components

IFRS INDUSTRY ISSUES SOFTWARE IFRS 15: REVENUE FROM CONTRACTS WITH CUSTOMERS

First Impressions: Revenue from contracts with customers

Leases (Topic 840) Proposed Accounting Standards Update. Issued: August 17, 2010 Comments Due: December 15, 2010

Classification and measurement: financial liabilities

Defining Issues. Implementing the Forthcoming Revenue Recognition Standard. February 2014, No. 14-9

IFRS industry insights

IFRS 2 Share-based Payment Modification of a share-based payment transaction from cash-settled to equity-settled

3. In this paper, the staff recommend that the exposure draft:

IAS 7 Statement of Cash Flows identification of cash equivalents

CONTACT(S) Rachel Knubley

IFRS APPLICATION AROUND THE WORLD JURISDICTIONAL PROFILE: El Salvador

sets out the next steps of the project (in paragraph 7); and

CONTACT(S) Li Li Lian

Software (Topic 985) No October Certain Revenue Arrangements That Include Software Elements

IASB Meeting Agenda reference 4 Week Date. the objective of a limited scope project to amend IAS 12 Income Taxes and


IFRS 15 Revenue from Contracts with Customers

Implementing IFRS 15 Revenue from Contracts with Customers A practical guide to implementation issues for the travel, hospitality and leisure sector

Agenda (1 of 2) Agenda (2 of 2) Revenue Recognition Update: Implementing EITF and EITF 09-3

Impacts on the construction industry of the new revenue standard

IFRS 2 Share-based Payment Share-based payment awards settled net of tax withholdings

IFRS APPLICATION AROUND THE WORLD JURISDICTIONAL PROFILE: New Zealand

May Leases. Comments to be received by 13 September 2013

Agenda. ref 15. Paper topic. ns where the. Introduction. 1. The. C ) received two. requests to transactions in. 2. The. (a) (b) (c) criteria.

CONTACT(S) Hannah King +44 (0) Kumar Dasgupta +44 (0)

Revenue from contracts with customers The standard is final A comprehensive look at the new revenue model

Allstate Insurance Company

IASB/FASB Board Meeting Week beginning February 14, Financial Instruments: Impairment

Rate used to accrete interest and calculate the present value of cash flows that unlock the contractual service margin

Measuring the fair value of a liability issued with an inseparable third-party credit enhancement

CONTACT(S) Michelle Sansom +44 (0)

Snapshot: Leases. May Exposure Draft

Financial Services Investment Companies (Topic 946)

A TALE OF TWO WARRANTIES

A shifting software revenue recognition landscape

IFRS for Technology Companies: Closing the GAAP? KPMG LLP

Investment Entities (Amendments to IFRS 10, IFRS 12 and IAS 27)

Revenue Recognition: Ten Top Changes to Expect with the New Standard

Software Revenue Recognition A Roadmap to Applying ASC Third Edition December 2011

Revenue Recognition. - A European Contribution -

Revenue Recognition Accounting for Software as a Service (SaaS)

IFRS IN PRACTICE. IFRS 15 Revenue from Contracts with Customers: Transition

2. This paper supplements Agenda Paper 2A Outreach and comment letter analysis for this meeting. This paper does not ask any questions.

Draft Comment Letter

SPECIAL REPORT: Comprehensive Coverage of the New U.S. GAAP Revenue Recognition Requirements

IFRS 13 Fair Value Measurement

Broker-dealers: Prepare for the new revenue recognition standard

following issues: Which, if (a) (Issue 2). contract? (b) Insurance Contracts contract? (Issue 1). Contracts April 2012 Project Paper topic

No May Revenue from Contracts with Customers (Topic 606) An Amendment of the FASB Accounting Standards Codification

Transcription:

IASB Agenda ref 7B STAFF PAPER FASB IASB Meeting FASB Agenda ref 161B 16 20 July 20122 Project Revenue recognition Paper topic Identifying separate performance obligations examples CONTACT(S) Kristin Bauer Buck Bagwell kdbauer@ @fasb.org lbagwell@ @fasb.org +1 203 956 3469 +1 203 956 3471 Glenn Brady gbrady@ifrs.org +44 20 7246 6460 This paper has been prepared by the staff of the IFRS Foundation and the FASB for discussion at a public meeting of the FASB or IASB. It does not purport to represent the views of any individual members of either board. Comments on the application of US GAAP or IFRSs do not purport to set out acceptable or unacceptablee application of U.S. GAAP or IFRSs. The FASB and the IASB report their decisions made at public meetings in FASB Action Alert or in IASB Update. Purpose of the paper 1. The purpose of this paper is to illustrate how the staff s recommendations in Agenda paper 7A apply to several examples. Example 1: Software with postcontract customer support (PCS) A customer enters into a contract with a software provider to purchase a new accounts receivable system. As part of that contract, the software provider will: (a) (b) supply the software and provide postcontract customer support (PCS) for a period of two years, which consists of on-demand helpdesk support and unspecified when- and-if available software updates. The software is considered to be off-the-shelf The entity sells the software separately and delivers the software before PCS is provided. The entity also sells PCS software in that it can be used without significant customization. separately on a yearly renewal basis. Those servicess provide the customer with ongoing helpdesk support and access to unspecified software updates (on a when-and-if available basis). The IASB is the independent standard-setting body of the IFRS Foundation, a not-for-profit corporation promoting the adoption of IFRSs. For more information visit www.ifrs.org The Financial Accounting Standards Board (FASB), is the national standard-setter of the United States, responsible for establishing standards of financial accounting that govern the preparation of financial reports by nongovernmental entities. For more information visit www.fasb.org Page 1 of 5

Question What are the promised goods or services in the contract? Staff response and consideration points The entity has promised to provide 3 goods and services: (i) software, (ii) helpdesk support (a component of the PCS) and (iii) software updates (a component of the PCS). The helpdesk support and the unspecified when-and-if available software updates are assessed as being stand ready obligations. capable of being distinct? (i) Software Yes, because the customer can benefit from the software on its own. This is evidenced by the fact that the entity also sells the software separately. (ii) Helpdesk support Yes, because the customer can benefit from each increment of (standing ready to provide) helpdesk service in conjunction with the software already received (ie the software is a resource that is readily available to the customer). (iii) Software updates Yes, because the customer can benefit from each increment of the service to (stand ready to) provide updates in conjunction with the software already received. distinct in the context of the contract? (An entity would make this assessment by considering the bundling principle and the related indicators) Software Yes, because none of the specified indicators suggest that the software is highly dependent or interrelated with either of the PCS services. In particular, any software updates would maintain or enhance functionality of the software rather than significant modify or customise the software. Helpdesk support Each increment of helpdesk support service is not individually distinct in the context of the contract because they have the same pattern of transfer as Page 2 of 5

every other increment of promised helpdesk service, which indicates that those services are highly interrelated. Consequently, only the bundle of helpdesk support services is distinct in the context of the contract. Each increment of helpdesk support has the same pattern of transfer because they form a series of services that: (a) transfer to the customer over time, and (b) an entity would use a single method to measure progress for each increment of the service transferred delivered to the customer (in this case, the measure of progress would be time-based measure because the service is a stand ready obligation). Software updates Only the bundle of software update services is distinct in the context of the contract. (The same analysis applies for both software updates and helpdesk support services.) How many separate performance obligations are in the contract? What promises are included in each separate performance obligation? There are three separate performance obligations: (i) software, (ii) the helpdesk support services, and (iii) the software updates. In practice, an entity could account for the two components of the PCS (the helpdesk support and the updates) as if they were a single performance obligation because both are services that are provided concurrently and use the same measure of progress. Consequently, the timing and amount of revenue recognition would be the same regardless of whether the entity accounted for each bundle of services as a two performance obligations or one performance obligation. Page 3 of 5

Example 2: Sale of off the shelf software with customization services An entity has a contract to supply customer relationship software and provide software customization services to a customer. The software is considered to be off-the-shelf software in that it can be used without significant customization. The software is sold separately. Scenario A customization services only provided by the entity The customization services specified in the contract require the entity to significantly modify the features and the functionality of the software code to meet precise, customised, specifications. In addition the entity will be building complex interfaces between the software and the customer s existing IT environment. Scenario B customization services provided by other entities In addition to the software license, the customer has issued a request for proposal on customization services on the software. In this case, the services involve modification to the existing code of the software but such modification is not extensive or specifically customised. The software vendor routinely provides these services and is highly qualified to perform them; however, these services are also available from other vendors who are equally qualified to provide the services. As these services do not carry a significant degree of difficulty, the customer, in this case, is looking to find the vendor who will provide these services at the lowest cost. The entity wins the bid on providing the services. Question Staff response and consideration points Scenario A Scenario B What are the promised goods or services in the contract? (2) Software, modification service and integration service. Same Page 4 of 5

capable of being distinct? Modification and integration service Yes. The customer can benefit from these services with readily available resources. Software Yes. The customer can benefit from the software on its own. Same distinct in the context of the contract (without including the pattern of transfer indicator in the analysis)? No (should be combined). The software is highly dependent and interrelated with the services, which significantly modify and customize the software. Therefore, individually, the software and the services are inputs to produce a separate output and should be bundled. Yes (services should be separated from the software). While like Scenario A the services are interrelated with the purchased software, the degree of dependency is significantly less. Additionally, the customer could choose to purchase, or not purchase, the services. How many separate performance obligations are in the contract? What promises are included in each separate performance obligation? 1: the software and customization services together. 2: the software separate from the customization services. Page 5 of 5