Microsoft 2013 Annual Report Download - page 47

Download and view the complete annual report

Please find page 47 of the 2013 Microsoft annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 87

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87

NOTES TO FINANCIAL STATEMENTS
NOTE 1 — ACCOUNTING POLICIES
Accounting Principles
The financial statements and accompanying notes are prepared in accordance with accounting principles generally
accepted in the United States of America (“U.S. GAAP”).
Principles of Consolidation
The financial statements include the accounts of Microsoft Corporation and its subsidiaries. Intercompany transactions
and balances have been eliminated. Equity investments through which we 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 goodwill impairment 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
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 in our 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.
Foreign Currencies
Assets and liabilities recorded in foreign currencies are translated at the exchange rate on the balance sheet date.
Revenue and expenses are translated at average rates of exchange prevailing during the year. Translation adjustments
resulting from this process are recorded to other comprehensive income (“OCI”).
Revenue Recognition
Revenue is recognized when persuasive evidence of an arrangement exists, delivery has occurred, the fee is fixed or
determinable, and collectibility is probable. Revenue generally is recognized net of allowances for returns and any taxes
collected from customers and subsequently remitted to governmental authorities.
Revenue for retail packaged products, products licensed to original equipment manufacturers (“OEMs”), and perpetual
licenses under certain volume licensing programs generally is recognized as products are shipped or made available.
Technology guarantee programs are accounted for as multiple element arrangements as customers receive free or
significantly discounted rights to use upcoming new versions of a software product if they license existing versions of the
product during the eligibility period. Revenue is allocated between the existing product and the new product, and revenue
allocated to the new product is deferred until that version is delivered. The revenue allocation is based on the vendor-
specific objective evidence (“VSOE”) of fair value of the products. The VSOE of fair value for upcoming new products are
based on the price determined by management having the relevant authority when the element is not yet sold separately,
but is expected to be sold in the near future at the price set by management.