XML 21 R9.htm IDEA: XBRL DOCUMENT v3.6.0.2
ACCOUNTING POLICIES
6 Months Ended
Dec. 31, 2016
ACCOUNTING POLICIES

NOTE 1  ACCOUNTING POLICIES

Accounting Principles

We prepare our unaudited interim consolidated financial statements in accordance with accounting principles generally accepted in the United States of America (“U.S. GAAP”). In the opinion of management, the unaudited interim consolidated financial statements reflect all adjustments of a normal recurring nature that are necessary for a fair presentation of the results for the interim periods presented. Interim results are not necessarily indicative of results for a full year. The information included in this Form 10-Q should be read in conjunction with information included in the Microsoft Corporation 2016 Form 10-K filed with the U.S. Securities and Exchange Commission on July 28, 2016.

We have recast certain prior period amounts to conform to the current period presentation, with no impact on consolidated net income or cash flows.

Principles of Consolidation

The consolidated financial statements include the accounts of Microsoft Corporation and its subsidiaries. Intercompany transactions and balances have been eliminated. Equity investments through which we are able to exercise significant influence over but do not control the investee and are not the primary beneficiary of the investee’s activities are accounted for using the equity method. Investments through which we are not able to exercise significant influence over the investee and which do not have readily determinable fair values are accounted for under the cost method.

Estimates and Assumptions

Preparing financial statements requires management to make estimates and assumptions that affect the reported amounts of assets, liabilities, revenue, and expenses. Examples of estimates include: loss contingencies; product warranties; the fair value of, and/or potential impairment of goodwill and intangible assets, for our reporting units; product life cycles; useful lives of our tangible and intangible assets; allowances for doubtful accounts; allowances for product returns; the market value of and volume of demand for our inventory; and stock-based compensation forfeiture rates. Examples of assumptions include: the elements comprising a software arrangement, including the distinction between upgrades or enhancements and new products; when technological feasibility is achieved for our products; the potential outcome of future tax consequences of events that have been recognized on our consolidated financial statements or tax returns; and determining when investment impairments are other-than-temporary. Actual results and outcomes may differ from management’s estimates and assumptions.

Product Revenue and Service and Other Revenue

Product revenue includes sales from operating systems; cross-device productivity applications; server applications; business solution applications; desktop and server management tools; software development tools; video games; hardware such as PCs, tablets, gaming and entertainment consoles, phones, other intelligent devices, and related accessories; and training and certification of computer system integrators and developers.

Service and other revenue includes sales from cloud-based solutions that provide customers with software, services, platforms, and content such as Office 365, Microsoft Azure (“Azure”), Microsoft Dynamics 365 (“Dynamics 365”), and Xbox Live; solution support; and consulting services. Service and other revenue also includes sales from online advertising and LinkedIn.

Recent Accounting Guidance Not Yet Adopted

Financial Instruments – Credit Losses

In June 2016, the Financial Accounting Standards Board (“FASB”) issued a new standard to replace the incurred loss impairment methodology in current U.S. GAAP with a methodology that reflects expected credit losses and requires consideration of a broader range of reasonable and supportable information to inform credit loss estimates. For trade and other receivables, loans, and other financial instruments, we will be required to use a forward-looking expected loss model rather than the incurred loss model for recognizing credit losses which reflects losses that are probable. Credit losses relating to available-for-sale debt securities will also be recorded through an allowance for credit losses rather than as a reduction in the amortized cost basis of the securities. The new standard will be effective for us beginning July 1, 2020, with early adoption permitted beginning July 1, 2019. Application of the amendments is through a cumulative-effect adjustment to retained earnings as of the effective date. We are currently evaluating the impact of this standard on our consolidated financial statements.

Leases

In February 2016, the FASB issued a new standard related to leases to increase transparency and comparability among organizations by requiring the recognition of lease assets and lease liabilities on the balance sheet. Most prominent among the amendments is the recognition of assets and liabilities by lessees for those leases classified as operating leases under previous U.S. GAAP. Under the new standard, disclosures are required to meet the objective of enabling users of financial statements to assess the amount, timing, and uncertainty of cash flows arising from leases. We will be required to recognize and measure leases at the beginning of the earliest period presented using a modified retrospective approach.

The new standard will be effective for us beginning July 1, 2019, with early adoption permitted. We currently anticipate early adoption of the new standard effective July 1, 2017 in conjunction with our adoption of the new revenue standard. Our ability to early adopt is dependent on system readiness, including software procured from third-party providers, and the completion of our analysis of information necessary to restate prior period financial statements. We remain on schedule and have implemented specific system functionality to enable the accounting transition.

We anticipate this standard will have a material impact on our consolidated balance sheets. However, we do not believe adoption will have a material impact on our consolidated income statements. Due to the recent acquisition of LinkedIn Corporation (“LinkedIn”), we are still assessing the qualitative and quantitative impacts of the leases assumed on our consolidated balance sheets. While we are continuing to assess all potential impacts of the standard, we currently believe the most significant impact relates to our accounting for office space, retail space, and datacenter operating leases. We expect our accounting for capital leases related to office space and datacenters will remain substantially unchanged under the new standard.

Financial Instruments – Recognition, Measurement, Presentation, and Disclosure

In January 2016, the FASB issued a new standard to amend certain aspects of recognition, measurement, presentation, and disclosure of financial instruments. Most prominent among the amendments is the requirement for changes in the fair value of our equity investments, with certain exceptions, to be recognized through net income rather than other comprehensive income (“OCI”). The new standard will be effective for us beginning July 1, 2018. The application of the amendments will result in a cumulative-effect adjustment to our consolidated balance sheets as of the effective date. We are currently evaluating the impact of this standard on our consolidated financial statements.

Revenue from Contracts with Customers

In May 2014, the FASB issued a new standard related to revenue recognition. Under the new standard, revenue is recognized when a customer obtains control of promised goods or services and is recognized in an amount that reflects the consideration which the entity expects to receive in exchange for those goods or services. In addition, the standard requires disclosure of the nature, amount, timing, and uncertainty of revenue and cash flows arising from contracts with customers. The FASB recently issued several amendments to the standard, including clarifications on disclosure of prior-period performance obligations and remaining performance obligations.

The guidance permits two methods of adoption: retrospectively to each prior reporting period presented (full retrospective method), or retrospectively with the cumulative effect of initially applying the guidance recognized at the date of initial application (the cumulative catch-up transition method). We currently anticipate adopting the standard using the full retrospective method to restate each prior reporting period presented.

The new standard will be effective for us beginning July 1, 2018, and adoption as of the original effective date of July 1, 2017 is permitted. We currently anticipate early adoption of the new standard effective July 1, 2017. While our ability to early adopt using the full retrospective method is dependent on system readiness, including software procured from third-party providers, and the completion of our analysis of information necessary to restate prior period financial statements, we remain on schedule and have implemented key system functionality to enable restated financial information. Our progress includes nearing completion of retrospectively adjusted financial information for fiscal year 2016.

We anticipate this standard will have a material impact on our consolidated financial statements, and continue to make progress in assessing all potential impacts of the standard, including any impacts from recently issued amendments. We have reached conclusions on all key accounting assessments related to the new standard. However, we are still assessing impacts from guidance issued by the FASB Transition Resource Group as part of their November 2016 meeting. We will continue to monitor and assess the impact of changes to the standard and interpretations as they become available. We have also started our assessment to determine the revenue recognition impact of our recent acquisition of LinkedIn. The most significant impact of the standard relates to our accounting for software license revenue. Specifically, under the new standard we expect to recognize Windows 10 revenue predominantly at the time of billing rather than ratably over the life of the related device. We expect to recognize license revenue at the time of contract execution rather than over the subscription period from certain multi-year commercial software subscriptions that include both software licenses and Software Assurance. Due to the complexity of certain of our commercial license subscription contracts, the actual revenue recognition treatment required under the standard will be dependent on contract-specific terms, and may vary in some instances from recognition at the time of billing. We expect revenue recognition related to our hardware, cloud offerings including Office 365, and professional services to remain substantially unchanged.

We continue to believe that the net change in Windows 10 revenue from period to period is indicative of the net change in revenue we expect from the adoption of the new standard.