Autodesk 2015 Annual Report Download - page 128

Download and view the complete annual report

Please find page 128 of the 2015 Autodesk 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 208

  • 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
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208

2015 Form 10-K 36
regarding acquisitions. We currently anticipate that we will continue to acquire products, technology, and businesses as
compelling opportunities become available.
Our strategy depends upon a number of assumptions to successfully make the transition toward new cloud and mobile
platforms, including the related technology and business model shifts; making our technology available to mainstream markets;
leveraging our large global network of distributors, resellers, third-party developers, customers, educational institutions, and
students; improving the performance and functionality of our products; and adequately protecting our intellectual property. If
the outcome of any of these assumptions differs from our expectations, we may not be able to implement our strategy, which
could potentially adversely affect our business. For further discussion regarding these and related risks see Part I, Item 1A,
“Risk Factors.”
Critical Accounting Policies and Estimates
Our Consolidated Financial Statements are prepared in conformity with U.S. generally accepted accounting principles. In
preparing our Consolidated Financial Statements, we make assumptions, judgments, and estimates that can have a significant
impact on amounts reported in our Consolidated Financial Statements. We base our assumptions, judgments, and estimates on
historical experience and various other factors that we believe to be reasonable under the circumstances. Actual results could
differ materially from these estimates under different assumptions or conditions. We regularly reevaluate our assumptions,
judgments, and estimates. Our significant accounting policies are described in Note 1, “Business and Summary of Significant
Accounting Policies,” in the Notes to Consolidated Financial Statements. We believe that of all our significant accounting
policies, the following policies involve a higher degree of judgment and complexity. Accordingly, these are the policies we
believe are the most critical to aid in fully understanding and evaluating our financial condition and results of operations.
Revenue Recognition. We recognize revenue when persuasive evidence of an arrangement exists, delivery has occurred
or services have been rendered, the price is fixed or determinable, and collection is probable. However, determining whether
and when some of these criteria have been satisfied often involves assumptions and judgments that can have a significant
impact on the timing and amount of revenue we report.
For multiple element arrangements containing only software and software-related elements, we allocate the sales price
among each of the deliverables using the residual method, under which revenue is allocated to undelivered elements based on
our vendor-specific objective evidence (“VSOE”) of fair value. VSOE is the price charged when an element is sold separately
or a price set by management with the relevant authority. If we do not have VSOE of an undelivered software license, we defer
revenue recognition on the entire sales arrangement until all elements for which we do not have VSOE are delivered. If we do
not have VSOE for undelivered maintenance or services, the revenue for the arrangement is recognized over the longest
contractual service period in the arrangement. We are required to exercise judgment in determining whether VSOE exists for
each undelivered element based on whether our pricing for these elements is sufficiently consistent.
For multiple elements arrangements involving non-software elements, including cloud subscription services, our revenue
recognition policy is based upon the accounting guidance contained in ASC 605, Revenue Recognition. For these
arrangements, we first allocate the total arrangement consideration based on the relative selling prices of the software group of
elements as a whole and to the non-software elements. We then further allocate consideration within the software group to the
respective elements within that group using the residual method as described above. We exercise judgment and use estimates in
connection with the determination of the amount of revenue to be recognized in each accounting period.
We allocate the total arrangement consideration among the various elements based on a selling price hierarchy. The selling
price for a deliverable is based on its VSOE if available, third-party evidence ("TPE") if VSOE is not available, or the best
estimated selling price ("BESP") if neither VSOE nor TPE is available. BESP represents the price at which Autodesk would
transact for the deliverable if it were sold regularly on a standalone basis. To establish BESP for those elements for which
neither VSOE nor TPE are available, we perform a quantitative analysis of pricing data points for historical standalone
transactions involving such elements for a twelve-month period. As part of this analysis, we monitor and evaluate the BESP
against actual pricing to ensure that it continues to represent a reasonable estimate of the standalone selling price, considering
several other external and internal factors including, but not limited to, pricing and discounting practices, contractually stated
prices, the geographies in which we offer our products and services, and the type of customer (i.e. distributor, value-added
reseller, and direct end user, among others). We analyze BESP at least annually or on a more frequent basis if a significant
change in our business necessitates a more timely analysis or if we experience significant variances in our selling prices.
2015 Annual Report