NVIDIA 2016 Annual Report Download - page 177

Download and view the complete annual report

Please find page 177 of the 2016 NVIDIA 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 250

  • 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
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

31
Revenue Recognition
Product Revenue
We recognize revenue from product sales when persuasive evidence of an arrangement exists, the product has been
delivered, the price is fixed or determinable and collection of the related receivable is reasonably assured.
For sales to certain distributors with rights of return for which the level of returns cannot be reasonably estimated, our
policy is to defer recognition of revenue and related cost of revenue until the distributors resell the product and, in some
cases, when customer return rights lapse.
Our customer programs primarily involve rebates, which are designed to serve as sales incentives to resellers of our
products in various target markets. We account for rebates as a reduction of revenue and accrue for 100% of the potential
rebates and do not apply a breakage factor. While we have a long history of rebate arrangements with OEMs, we believe
we are unable to apply our historical experience to reliably estimate the amount of rebates that will eventually be claimed
by individual OEMs. In such cases, the OEMs may not be our direct customers and therefore the quantity and mix of demand
they place on their CEMs/ODMs may shift as we introduce new generations and iterations of products and as we experience
changes in new competitor offerings. In addition, we typically find that approximately 95% of the rebates we accrue each
year are eventually claimed, which is substantially close to 100%, and that this percentage varies by program and by customer.
We recognize a liability for these rebates at the later of the date at which we record the related revenue or the date at which
we offer the rebate. Rebates typically expire six months from the date of the original sale, unless we reasonably believe that
the customer intends to claim the rebate. Unclaimed rebates are reversed to revenue, the amount of which typically represents
less than 0.5% of total revenue.
Our customer programs also include marketing development funds, or MDFs. MDFs represent monies paid to retailers,
system builders, OEMs, distributors, add-in card partners and other channel partners that are earmarked for market segment
development and expansion and typically are designed to support our partners’ activities while also promoting NVIDIA
products. Depending on market conditions, we may take actions to increase amounts offered under customer programs,
possibly resulting in an incremental reduction of revenue at the time such programs are offered. We account for MDFs as
a reduction of revenue and apply a breakage factor to certain types of MDF program accruals for which we believe we can
make a reasonable and reliable estimate of the amount that will ultimately be unclaimed.
We also record a reduction to revenue by establishing a sales return allowance for estimated product returns at the time
revenue is recognized, based primarily on historical return rates. However, if product returns for a particular fiscal period
exceed historical return rates we may determine that additional sales return allowances are required to properly reflect our
estimated exposure for product returns.
License and Development Revenue
For license arrangements that require significant customization of our intellectual property components, we generally
recognize the related revenue over the period that services are performed. For most license and service arrangements, we
determine progress to completion based on actual cost incurred to date as a percentage of the estimated total cost required
to complete the project. We periodically evaluate the actual status of each project to ensure that the estimates to complete
each contract remain accurate. Revenue recognized in any period is dependent on our progress toward completion of projects
in progress. Significant management judgment and discretion are used to estimate total cost. Any changes in or deviations
from these estimates could have a material effect on the amount of revenue we recognize in any period.
For license arrangements that do not require significant customization but where we are obligated to provide further
deliverables over the term of the license agreement, we record revenue over the life of the license term, with consideration
received in advance of the performance period classified as deferred revenue.