Microsoft Revenue Recognition Systems. Our Challenge We are seeking a revenue recognition technology solution to scale with the increasing complexity.

Slides:



Advertisements
Similar presentations
Revenue from Contracts with Customers
Advertisements

IFRS 4 Phase 2 Insurance Contract Model IAA Fund Meeting Kuala Lumpur, October 10, 2011 Darryl Wagner, FSA, MAAA.
Aviation Industry Perspective Future Impact of New Lease Accounting Guidance Bill Solomon Senior Manager – Technical Accounting 1 BOEING CAPITAL CORPORATION.
Accounting and Financial Reporting Trends T.J. Boyle June 20, 2013 Relationships backed by performance.
IFRS 15: Revenue from Contracts with Customers
Revenue Recognition U.S. GAAP vs. IFRS. Adoption vs. Convergence The Securities and Exchange Commission had previously voiced optimism that adoption was.
FASB UPDATE FOR PRIVATE COMPANIES Timothy Pike, CPA, CFE Howard & Co, LLP.
SFRS FOR SMALL ENTITIES
International Financial Reporting Standards The views expressed in this presentation are those of the presenter, not necessarily those of the IASB or IFRS.
Theoretical Structure of Financial Accounting
*connectedthinking  Discussion Paper Preliminary Views on Insurance Contracts Sabine Wuiame.
Chapter 18 Revenue Recognition ACCT Revenue Recognition Basic Concepts Revenue recognition ◦ most difficult issue facing accounting ◦ most prevalent.
Revenue Recognition - Multiple-Element Arrangements
Revenue Recognition Milestone Method ASC Highlights.
6/9/2015Copyright 2015 A. C. Sondhi & Associates, LLC1 ASU , ASC 606 Revenue from Contracts with Customers and Proposed ASU, Deferral of Effective.
Will you be reporting equity in your balance sheet in 2005?
Jeannie J. Harrington MTSU CPE Day December 4, 2014
International Financial Reporting Standards (IFRS)
Consolidation of Financial Information
The views expressed in this presentation are those of the presenter, not necessarily those of the IASB or IFRS Foundation. International Financial Reporting.
Revenue recognition.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 4 International Financial Reporting Standards (IFRSs)
The new revenue recognition standard
IFRS 1 FIRST TIME ADOPTION OF IFRS Asish K Bhattacharyya Slide 1.
Overview - FASB Exposure Draft Leases (Topic 840) February 2, 2011 Douglas Boedeker, CPA, CMA
IFRS 15, Revenue from Contracts with Customers
Accounting for Intangible Assets
1 Derivatives, Contingencies, Business Segments, and Interim Reports.
International Accounting Standards Board ® May 2006 The IASB’s project on Insurance Contracts Peter Clark Senior Project Manager International Accounting.
The views expressed in this presentation are those of the presenter, not necessarily those of the IASB or IFRS Foundation. International Financial Reporting.
0 ISDA ISDA Workshop – The practical implications of the new accounting rules 8 November 2004 ISDA International Swaps and Derivatives Association, Inc.
Experience clarity // CPAs & ADVISORS REVENUE RECOGNITION.
Click to edit Master title style Casualty Loss Reserving Seminar – San Diego, CA September 10 – 11, INSURANCE AND ACTUARIAL.
1 Chapter 6: Revenue Analysis. 2 Revenue Recognition Criteria Both the criteria should be satisfied: Good and service has been delivered Cash is collected.
IAS 18 : Revenue The Institute of Chartered Accountants of India (Set up by an Act of Parliament)
Accounting (Basics) - Lecture 8 Revenue. Contents Measurement of revenue Identification of the revenue transaction Sale of goods Rendering of services.
Revenue Recognition for the AE Industry Presented by: M. Scott Hursh, CPA, CCIFP®, CDA Managing Shareholder AE Industry Group Stambaugh Ness, PC Brian.
New Revenue Recognition Standard – Overview
By Samuel Bediako & Mo Zhang IFRS for Small and Medium Entities(SME)
The views expressed in this presentation are those of the presenter, not necessarily those of the IASB or IFRS Foundation. International Financial Reporting.
Revenue.  Definition of Income: ◦ Income is increases in economic benefits during the accounting period in the form of inflows or enhancements of assets.
Accounting Standards Update for Private and Public Sector NPOs Presented by: Erica Teklits, Partner and National Leader, NPO Sector November 12, 2013.
Accounting (Basics) - Lecture 3 Property, plant and equipment.
Cipfa.org What’s new on the technical accounting scene? Alan Bermingham Principal Consultant, CIPFA.
IFRS Updates 2014 June 6, Agenda  IFRS 10, 11, 12 and IAS 28  IFRS 13  IFRS 15.
FASB and Accounting Standards Update Jay Meglich Trevor Warren.
IFRS 15 – Revenue from contracts with customers
Accounting for Intangible Assets 1 Rangajewa Herath B.Sc. Accountancy and Financial Management(Sp.)(USJ) MBA-PIM(USJ)
IFRS 15 Revenue from Contracts with Customers Presented by CPA Peter Njuguna.
Revenue recognition for health care providers
Revenue from Contracts with Customers
Accounting for Financial Instruments
Revenue from Contracts with Customers (FASB ASC Topic 606)
Chapter 8 Revenue Recognition ACCT-3030.
IFRS 4 Phase 2 Insurance Contract Model
IND AS 18 – REVENUE RECOGNITION
CA Krishanu Bhattacharyya
FASB Targeted Improvements
Ready Set Go! The New Revenue Recognition Rules
International Financial Reporting Standards (IFRSs)
Accounting for Intangible Assets
Revenue Recognition and Profitability Analysis
CONCEPTUAL FRAMEWORK UNDERLYING FINANCIAL ACCOUNTING
Ind AS 115 – Revenue from Contracts with Customers
Revenue from Contracts with Customers (FASB ASC Topic 606)
MFRS 138 – INTANGIBLE ASSETS
Accounting Update 2019 Part II
Income/Revenue Defined as increase in economic benefits during the accounting period in the form of inflows or enhancements of assets or decreases of.
IFRS 15 - Revenue from Contracts with Customers
K-deep Dhaliwal, Partner for Moss Adams LLP
Presentation transcript:

Microsoft Revenue Recognition Systems

Our Challenge We are seeking a revenue recognition technology solution to scale with the increasing complexity of existing and future business models and address the new standard Some of the opportunities:  New business models (new revenue types, more MEA)  Multiple provisioning, order processing, invoicing systems (revenue infrastructure)  Data mastering, models and flows (increased data needs)  Impact of new proposed standard: Contract modifications Tracking new performance obligations (namely license and possibly others) Fair value calculations and allocations of transaction price, creating contractual assets and liabilities System impact: Common subledger needed, new data and integration

Revenue Recognition Joint Project Objective of project: Develop a standard based on a single model to deal with all types of contracts and business sectors Would replace most of existing U.S. GAAP and IFRS revenue recognition standards Final Standard in Summer 2013 Effective Date (U.S. GAAP): Public entities: fiscal years and interim periods within those years, beginning after December 15, 2016 – early adoption prohibited Transition Approaches: Retrospective, or Cumulative effect at the date of adoption

Transition, Early Application, and Effective date – Tentative Decisions Transition MethodFY16 and FY17FY18 Date of Cumulative Effect Adjustment 1 Full RetrospectiveRestate for all contractsApply new revenue standard to all contracts July 1, 2015 Cumulative Effect at the Date of Adoption These periods not restated for any contracts Apply new revenue standard to new and existing contracts; disclose effect of applying new standard July 1, 2017

Main Steps To Apply the Model Identify the contract with a customer 1 Identify the separate performance obligations in the contract 2 Determine the transaction price 3 Allocate the transaction price to the separate performance obligations 4 Recognize revenue when (or as) the entity satisfies a performance obligation 5

Step 2: Identify the Separate Performance Obligations in the Contract Separate performance obligations Single performance obligation YesNo Are promised goods and services distinct from other goods and services in the contract? Can the customer benefit from the good or service either on its own or together with other resources that are readily available to the customer? The good or service is not highly dependent on, or highly interrelated with, other promised goods or services in the contract AND Yes No

Step 3: Determine the Transaction Price Transaction price = Total amount of consideration entity expects to be entitled to under the contract in exchange for transferring goods or services (excluding amounts collected on behalf of third parties) Variable consideration and constraint on variable consideration Noncash consideration Consideration payable to a customer Time value of money Collectibility Variable Consideration - may be a result of discounts, rebates, refunds, credits, incentives, performance bonuses/penalties, royalties, price concessions, or other similar items. At contract inception, entities would estimate variable consideration using probability-weighted or most-likely approach Revenue Constraint – Transaction price limited to fixed consideration plus portion of estimated variable consideration the inclusion of which does not create the risk of a significant revenue reversal. Need to have a high level of confidence in variable amounts before including them in transaction price Ongoing Reassessment – Entities will continually update their estimates of variable consideration and amounts thereof subject to the constraint

Step 4: Allocate the Transaction Price to the Performance Obligations Transaction price allocated based on relative stand alone selling prices ABC Performance obligations Observable price Estimated price How to estimate the stand alone selling price? Best evidence If not available Adjusted market assessment approach Expected cost plus a margin approach Residual approach if price is highly variable or uncertain

Disclosure Requirements  High level objective Intended to assist users to understand nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers  Disclosures about contracts with customers Disaggregation of revenue Changes in contract assets, liabilities, and costs Remaining performance obligations Qualitative disclosures Interim requirements

Examples of some key challenges  BUNDLES  One product has multiple performance obligations  One contract has multiple products/services  Multiple contracts need to be combined and accounted for together  Multiple products/services need to be accounted for as one performance obligation  Increased Disclosure Requirements  Two sets of books likely needed during transition

11 Solution Approach and Key Findings Revenue Recognition Pillars Exposure Draft Analysis Revenue Solution Analysis Governance Systems (Tools) Systems (Tools) Systems (Data) Systems (Data) Policy & Process Current State Analysis Peer Company Analysis Findings Governance Enterprise data management is a key success factor Rev Rec is always part of a larger program Policy & Process Pro-active Exposure Draft analysis Policies can significantly affect the complexity (and cost) of system solution Revenue Systems - Data New business models and GAAP guidance change the type of data necessary to process Rev Rec Revenue Systems - Tools Excel is most common toolset for FV among peers No enterprise ready solutions are available today Due Diligence Activities

Custom built.Net based solution Enhance LOB solution; Leverage 3 rd party as needed (e.g., FV calculation/allocation) Customized implementation of standard SAP solution Standard RevPro solution (+) Allows most flexibility (–) Complicated bottom-up build Note: Potential to co- develop solution as a commercial grade asset (+) Leverages existing logic for data integration and Rev Rec (+) Alignment with reporting/analysis roadmap (+) Lead Time (-) Requires significant effort to enhance our existing infrastructure (+) Leverages our ERP system for accounting (–) Dependency on SAP development timelines (–) High costs and extended timelines for customization (+) Out of the box solution addressing core revenue recognition needs (–) Scalability concerns (e.g., complexity and volume) (–) Unable to handle complex upstream data integration needs and requires external reporting infrastructure Removed from consideration Short term solution in process Continued engagement with SAP product development for both input and evaluation Oh site pilot completed for limited scenarios. Currently investigating implementation options Rev Rec System Solution Options 12 Solution Considerations Custom New SAPRevPro Custom existing Disposition

High Level Rev. Rec. System Attributes Accounting:  Ability to handle accounting requirements  Ease and flexibility of rules configuration for multiples of SKUs  Ability to support revenue accounting/operational reporting, such as earn-out schedules Operational:  Adequate controls over access, and workflow/reporting/audit capabilities  Ability to make manual adjustments, with adequate logging and approval System:  Ability to handle the complexity and volume of Microsoft, and yet ability to scale  Ability to integrate various feeds from upstream systems  Ability to “accept” revenue recognition from upstream systems, and then calculate the GAAP adjusting entries  Ability to support significant and complex management reporting and compensation programs, including ability to maintain revenue recognition and GAAP/FV entries separately