UNITED STATES

SECURITIES AND EXCHANGE COMMISSION

Washington, D.C. 20549

 

FORM 10-Q

 

For the Quarterly Period Ended September 30, 2017

OR

For the Transition Period From            to

Commission File Number: 001-37845

 

MICROSOFT CORPORATION

(Exact name of registrant as specified in its charter)

 

 

(425) 882-8080

(Registrant’s telephone number, including area code)

None

(Former name, former address and former fiscal year, if changed since last report)

Indicate by check mark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days. Yes ☒ No ☐

Indicate by check mark whether the registrant has submitted electronically and posted on its corporate Web site, if any, every Interactive Data File required to be submitted and posted pursuant to Rule 405 of Regulation S-T (§232.405 of this chapter) during the preceding 12 months (or for such shorter period that the registrant was required to submit and post such files). Yes ☒ No ☐

Indicate by check mark whether the registrant is a large accelerated filer, an accelerated filer, a non-accelerated filer, a smaller reporting company, or an emerging growth company. See the definitions of “large accelerated filer,” “accelerated filer,” “smaller reporting company,” and “emerging growth company” in Rule 12b-2 of the Exchange Act.

 

If an emerging growth company, indicate by check mark if the registrant has elected not to use the extended transition period for complying with any new or revised financial accounting standards provided pursuant to Section 13(a) of the Exchange Act. ☐

Indicate by check mark whether the registrant is a shell company (as defined in Rule 12b-2 of the Exchange Act). Yes ☐ No ☒

Indicate the number of shares outstanding of each of the issuer’s classes of common stock, as of the latest practicable date.

 

 

 

 

 

---

 

MICROSOFT CORPORATION

FORM 10-Q

For the Quarter Ended September 30, 2017

INDEX

 

 

 

 

2

---

PART I

Item 1

PART I. FINANCIAL INFORMATION

ITEM 1. FINANCIAL STATEMENTS

INCOME STATEMENTS

 

 

Refer to accompanying notes.

 

 

3

---

PART I

Item 1

COMPREHENSIVE INCOME STATEMENTS

 

 

Refer to accompanying notes. Refer to Note 18 – Accumulated Other Comprehensive Income for further information.

 

 

4

---

PART I

Item 1

BALANCE SHEETS

 

 

Refer to accompanying notes.

 

5

---

PART I

Item 1

CASH FLOWS STATEMENTS

 

Refer to accompanying notes.

 

 

6

---

PART I

Item 1

STOCKHOLDERS’ EQUITY STATEMENTS

 

 

Refer to accompanying notes.

 

 

7

---

PART I

Item 1

NOTES TO FINANCIAL STATEMENTS

(Unaudited)

 

NOTE 1 — ACCOUNTING POLICIES

Accounting Principles

Our unaudited interim consolidated financial statements and accompanying notes are prepared 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 2017 Form 10-K filed with the U.S. Securities and Exchange Commission on August 2, 2017.

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 for 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 for 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: for revenue recognition, determining the nature and timing of satisfaction of performance obligations, and determining the standalone selling price (“SSP”) of performance obligations, variable consideration, and other obligations such as product returns and refunds; 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; the market value of, and demand for, our inventory; and stock-based compensation forfeiture rates. Examples of assumptions include: 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.

Revenue  

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; and hardware such as PCs, tablets, gaming and entertainment consoles, other intelligent devices, and related accessories.

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

Revenue Recognition

Revenue is recognized upon transfer of control of promised products or services to customers in an amount that reflects the consideration we expect to receive in exchange for those products or services. We enter into contracts that can include various combinations of products and services, which are generally capable of being distinct and accounted for as separate performance obligations. Revenue is recognized net of allowances for returns and any taxes collected from customers, which are subsequently remitted to governmental authorities.

8

---

PART I

Item 1

Nature of Products and Services

Licenses for on-premises software provide the customer with a right to use the software as it exists when made available to the customer. Customers may purchase perpetual licenses or subscribe to licenses, which provide customers with the same functionality and differ mainly in the duration over which the customer benefits from the software. Revenue from distinct on-premises licenses is recognized upfront at the point in time when the software is made available to the customer. In cases where we allocate revenue to software updates, primarily because the updates are provided at no additional charge, revenue is recognized as the updates are provided, which is generally ratably over the estimated life of the related device or license.

Certain volume licensing programs, including Enterprise Agreements, include on-premises licenses combined with Software Assurance (“SA”). SA conveys rights to new software and upgrades released over the contract period and provides support, tools, and training to help customers deploy and use products more efficiently. On-premises licenses are considered distinct performance obligations when sold with SA. Revenue allocated to SA is generally recognized ratably over the contract period as customers simultaneously consume and receive benefits, given that SA comprises distinct performance obligations that are satisfied over time.  

Cloud services, which allow customers to use hosted software over the contract period without taking possession of the software, are provided on either a subscription or consumption basis. Revenue related to cloud services provided on a subscription basis is recognized ratably over the contract period. Revenue related to cloud services provided on a consumption basis, such as the amount of storage used in a period, is recognized based on the customer utilization of such resources. When cloud services require a significant level of integration and interdependency with software and the individual components are not considered distinct, all revenue is recognized over the period in which the cloud services are provided.

Revenue from search advertising is recognized when the advertisement appears in the search results or when the action necessary to earn the revenue has been completed. Revenue from consulting services is recognized as services are provided.

Our hardware is generally highly dependent on, and interrelated with, the underlying operating system and cannot function without the operating system. In these cases, the hardware and software license are accounted for as a single performance obligation and revenue is recognized at the point in time when ownership is transferred to resellers or directly to end customers through retail stores and online marketplaces.

Refer to Note 19 – Segment Information and Geographic Data for further information, including revenue by significant product and service offering.

Significant Judgments

Our contracts with customers often include promises to transfer multiple products and services to a customer. Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment. Certain cloud services, such as Office 365, depend on a significant level of integration and interdependency between the desktop applications and cloud services. Judgment is required to determine whether the software license is considered distinct and accounted for separately, or not distinct and accounted for together with the cloud service and recognized over time.

Judgment is required to determine the SSP for each distinct performance obligation. We use a single amount to estimate SSP for items that are not sold separately, including on-premises licenses sold with SA or software updates provided at no additional charge. We use a range of amounts to estimate SSP when we sell each of the products and services separately and need to determine whether there is a discount that needs to be allocated based on the relative SSP of the various products and services.

In instances where SSP is not directly observable, such as when we do not sell the product or service separately, we determine the SSP using information that may include market conditions and other observable inputs. We typically have more than one SSP for individual products and services due to the stratification of those products and services by customers and circumstances. In these instances, we may use information such as the size of the customer and geographic region in determining the SSP.  

Due to the various benefits from and the nature of our SA program, judgment is required to assess the pattern of delivery, including the exercise pattern of certain benefits across our portfolio of customers.  

9

---

PART I

Item 1

Our products are generally sold with a right of return and we may provide other credits or incentives, which are accounted for as variable consideration when estimating the amount of revenue to recognize. Returns and credits are estimated at contract inception and updated at the end of each reporting period as additional information becomes available and only to the extent that it is probable that a significant reversal of any incremental revenue will not occur.

Contract Balances  

Timing of revenue recognition may differ from the timing of invoicing to customers. We record a receivable when revenue is recognized prior to invoicing, or unearned revenue when revenue is recognized subsequent to invoicing. For multi-year agreements, we generally invoice customers annually at the beginning of each annual coverage period. We record a receivable related to revenue recognized for multi-year on-premises licenses as we have an unconditional right to invoice and receive payment in the future related to those licenses.

The opening balance of current and long-term accounts receivable, net of allowance for doubtful accounts, was $22.3 billion as of July 1, 2016.

As of September 30, 2017 and June 30, 2017, long-term accounts receivable, net of allowance for doubtful accounts, were $1.6 billion and $1.7 billion, respectively, and are included in other long-term assets on our consolidated balance sheets.

The allowance for doubtful accounts reflects our best estimate of probable losses inherent in the accounts receivable balance. We determine the allowance based on known troubled accounts, historical experience, and other currently available evidence.

Activity in the allowance for doubtful accounts was as follows: 

 

 

Unearned revenue is comprised mainly of unearned revenue related to volume licensing programs, which may include SA and cloud services. Unearned revenue is generally invoiced annually at the beginning of each contract period for multi-year agreements and recognized ratably over the coverage period. Unearned revenue also includes payments for: consulting services to be performed in the future; Office 365 subscriptions; LinkedIn subscriptions; Xbox Live subscriptions; Windows 10 post-delivery support; Dynamics business solutions; Skype prepaid credits and subscriptions; and other offerings for which we have been paid in advance and earn the revenue when we transfer control of the product or service.

Refer to Note 14 – Unearned Revenue for further information, including unearned revenue by segment and changes in unearned revenue during the period.

Payment terms and conditions vary by contract type, although terms generally include a requirement of payment within 30 to 60 days. In instances where the timing of revenue recognition differs from the timing of invoicing, we have determined our contracts generally do not include a significant financing component. The primary purpose of our invoicing terms is to provide customers with simplified and predictable ways of purchasing our products and services, not to receive financing from our customers, such as invoicing at the beginning of a subscription term with revenue recognized ratably over the contract period, or to provide customers with financing, such as multi-year on-premises licenses that are invoiced annually with revenue recognized upfront.

10

---

PART I

Item 1

Assets Recognized from the Costs to Obtain a Contract with a Customer

We recognize an asset for the incremental costs of obtaining a contract with a customer if we expect the benefit of those costs to be longer than one year. We have determined that certain sales incentive programs meet the requirements to be capitalized. Total capitalized costs to obtain a contract were immaterial during the periods presented and are included in other current and long-term assets on our consolidated balance sheets.

We apply a practical expedient to expense costs as incurred for costs to obtain a contract when the amortization period would have been one year or less. These costs include our internal sales force compensation program and certain partner sales incentive programs as we have determined annual compensation is commensurate with annual sales activities.

Leases

We determine if an arrangement is a lease at inception. Operating leases are included in operating lease right-of-use (“ROU”) assets, other current liabilities, and operating lease liabilities on our consolidated balance sheets. Finance leases are included in property and equipment, other current liabilities, and other long-term liabilities on our consolidated balance sheets.  

Operating lease ROU assets and operating lease liabilities are recognized based on the present value of the future minimum lease payments over the lease term at commencement date. As most of our leases do not provide an implicit rate, we use our incremental borrowing rate based on the information available at commencement date in determining the present value of future payments. The operating lease ROU asset also includes any lease payments made and excludes lease incentives and initial direct costs incurred. Our lease terms may include options to extend or terminate the lease when it is reasonably certain that we will exercise that option. Lease expense for minimum lease payments is recognized on a straight-line basis over the lease term.

We have lease agreements with lease and non-lease components, which are generally accounted for separately. For certain equipment leases, such as vehicles, we account for the lease and non-lease components as a single lease component. Additionally, for certain equipment leases, we apply a portfolio approach to effectively account for the operating lease ROU assets and liabilities.

Recent Accounting Guidance

Recently Adopted Accounting Guidance

Leases

In February 2016, the Financial Accounting Standards Board (“FASB”) issued a new standard related to leases to increase transparency and comparability among organizations by requiring the recognition of ROU assets and lease liabilities on the balance sheet. Most prominent among the changes in the standard is the recognition of ROU assets and lease liabilities by lessees for those leases classified as operating leases. Under the 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 are also required to recognize and measure leases existing at, or entered into after, the beginning of the earliest comparative period presented using a modified retrospective approach, with certain practical expedients available.

We elected to early adopt the standard effective July 1, 2017 concurrent with our adoption of the new standard related to revenue recognition. We elected the available practical expedients and implemented internal controls and key system functionality to enable the preparation of financial information on adoption.

The standard had a material impact on our consolidated balance sheets, but did not have an impact on our consolidated income statements. The most significant impact was the recognition of ROU assets and lease liabilities for operating leases, while our accounting for finance leases remained substantially unchanged. Adoption of the standard required us to restate certain previously reported results, including the recognition of additional ROU assets and lease liabilities for operating leases. Refer to Impacts to Previously Reported Results below for the impact of adoption of the standard on our consolidated financial statements.

11

---

PART I

Item 1

Revenue from Contracts with Customers

In May 2014, the FASB issued a new standard related to revenue recognition. Under the standard, revenue is recognized when a customer obtains control of promised goods or services in an amount that reflects the consideration 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.

We elected to early adopt the standard effective July 1, 2017, using the full retrospective method, which required us to restate each prior reporting period presented. We implemented internal controls and key system functionality to enable the preparation of financial information on adoption.

The most significant impact of the standard relates to our accounting for software license revenue. Specifically, for Windows 10, we recognize revenue predominantly at the time of billing and delivery rather than ratably over the life of the related device. For certain multi-year commercial software subscriptions that include both distinct software licenses and SA, we recognize license revenue at the time of contract execution rather than over the subscription period. Due to the complexity of certain of our commercial license subscription contracts, the actual revenue recognition treatment required under the standard depends on contract-specific terms and in some instances may vary from recognition at the time of billing. Revenue recognition related to our hardware, cloud offerings (such as Office 365), LinkedIn, and professional services remains substantially unchanged.

Adoption of the standard using the full retrospective method required us to restate certain previously reported results, including the recognition of additional revenue and an increase in the provision for income taxes, primarily due to the net change in Windows 10 revenue recognition. In addition, adoption of the standard resulted in an increase in accounts receivable and other current and long-term assets, driven by unbilled receivables from upfront recognition of revenue for certain multi-year commercial software subscriptions that include both distinct software licenses and Software Assurance; a reduction of unearned revenue, driven by the upfront recognition of license revenue from Windows 10 and certain multi-year commercial software subscriptions; and an increase in deferred income taxes, driven by the upfront recognition of revenue. Refer to Impacts to Previously Reported Results below for the impact of adoption of the standard on our consolidated financial statements.

Impacts to Previously Reported Results

Adoption of the standards related to revenue recognition and leases impacted our previously reported results as follows:

 

 

12

---

PART I

Item 1

Adoption of the standards related to revenue recognition and leases had no impact to cash from or used in operating, financing, or investing on our consolidated cash flows statements.

Recent Accounting Guidance Not Yet Adopted

Financial Instruments – Targeted Improvements to Accounting for Hedging Activities

In August 2017, the FASB issued new guidance related to accounting for hedging activities. This guidance expands strategies that qualify for hedge accounting, changes how many hedging relationships are presented in the financial statements, and simplifies the application of hedge accounting in certain situations. The standard will be effective for us beginning July 1, 2019, with early adoption permitted for any interim or annual period before the effective date. Adoption of the standard will be applied using a modified retrospective approach 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, including accounting policies, processes, and systems.

Accounting for Income Taxes – Intra-Entity Asset Transfers

In October 2016, the FASB issued new guidance requiring an entity to recognize the income tax consequences of an intra-entity transfer of an asset other than inventory when the transfer occurs, rather than when the asset has been sold to an outside party. This guidance is effective for us beginning July 1, 2018, with early adoption permitted beginning July 1, 2017. We plan to adopt the guidance effective July 1, 2018. Adoption of the guidance will be applied using a modified retrospective approach through a cumulative-effect adjustment to retained earnings as of the effective date. A cumulative-effect adjustment will capture the write-off of income tax consequences deferred from past intra-entity transfers involving assets other than inventory and new deferred tax assets for amounts not recognized under current U.S. GAAP. We anticipate this guidance will have a material impact on our consolidated balance sheets upon adoption, and continue to evaluate any impacts to our accounting policies, processes, and systems.

Financial Instruments – Credit Losses

In June 2016, the FASB issued a new standard to replace the incurred loss impairment methodology under 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. We will be required to use a forward-looking expected credit loss model for accounts receivables, loans, and other financial instruments. 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 standard will be effective for us beginning July 1, 2020, with early adoption permitted beginning July 1, 2019. Adoption of the standard will be applied using a modified retrospective approach through a cumulative-effect adjustment to retained earnings as of the effective date to align our credit loss methodology with the new standard. We are currently evaluating the impact of this standard on our consolidated financial statements, including accounting policies, processes, and systems.

13

---

PART I

Item 1

Financial Instruments – Recognition, Measurement, Presentation, and Disclosure

In January 2016, the FASB issued a new standard related to certain aspects of recognition, measurement, presentation, and disclosure of financial instruments. Most prominent among the changes in the standard 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 standard will be effective for us beginning July 1, 2018. Adoption of the standard will be applied using a modified retrospective approach through a cumulative-effect adjustment to retained earnings as of the effective date. A cumulative-effect adjustment will capture any previously held unrealized gains and losses related to our equity investments carried at fair value and the impact of recording the fair value of certain equity investments that were carried at cost. We are currently evaluating the impact of this standard on our consolidated financial statements, including accounting policies, processes, and systems.

 

 

NOTE 2 — EARNINGS PER SHARE

Basic earnings per share (“EPS”) is computed based on the weighted average number of shares of common stock outstanding during the period. Diluted EPS is computed based on the weighted average number of shares of common stock plus the effect of dilutive potential common shares outstanding during the period using the treasury stock method. Dilutive potential common shares include outstanding stock options and stock awards.

The components of basic and diluted EPS were as follows:

 

Anti-dilutive stock-based awards excluded from the calculations of diluted EPS were immaterial during the periods presented.

 

 

14

---

PART I

Item 1

NOTE 3 — OTHER INCOME (EXPENSE), NET

The components of other income (expense), net were as follows:

 

Following are details of net recognized gains (losses) on investments during the periods reported:

 

 

 

NOTE 4 — INVESTMENTS

Investment Components

The components of investments, including associated derivatives, were as follows:

 

 

15

---

PART I

Item 1