Electronic Arts 2016 Annual Report Download - page 142

Download and view the complete annual report

Please find page 142 of the 2016 Electronic Arts 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 188

  • 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

deliverable using the relative selling prices of each deliverable in the arrangement based on the selling price
hierarchy described below. If the arrangement contains more than one software deliverable, the arrangement
consideration is allocated to the software deliverables as a group and then allocated to each software deliverable.
We determine the selling price for a tangible product deliverable based on the following selling price hierarchy:
VSOE (i.e., the price we charge when the tangible product is sold separately) if available, third-party evidence
(“TPE”) of fair value (i.e., the price charged by others for similar tangible products) if VSOE is not available, or
our best estimate of selling price (“BESP”) if neither VSOE nor TPE is available. Determining the BESP is a
subjective process that is based on multiple factors including, but not limited to, recent selling prices and related
discounts, market conditions, customer classes, sales channels and other factors. Provided the other three revenue
recognition criteria other than delivery have been met, we recognize revenue upon delivery to the customer as we
have no further obligations.
Principal Agent Considerations
We evaluate sales of our interactive software games via third party storefronts, including digital storefronts such
as Microsoft’s Xbox Games Store, Sony PSN, Apple App Store, and Google Play, in order to determine whether
or not we are acting as the primary obligor in the sale to the end consumer, which we consider in determining if
revenue should be reported gross or net of fees retained by the storefront. Key indicators that we evaluate in
determining gross versus net treatment include but are not limited to the following:
The party responsible for delivery/fulfillment of the product or service to the end consumer
The party responsible for the billing, collection of fees and refunds to the consumer
The storefront and Terms of Sale that govern the consumer’s purchase of the product or service
The party that sets the pricing with the consumer and has credit risk
Based on evaluation of the above indicators, we have determined that generally the third party is considered the
primary obligor to end consumers for the sale of our interactive software games. We therefore report revenue
related to these arrangements net of the fees retained by the storefront.
Sales Returns and Allowances and Bad Debt Reserves
We reduce revenue for estimated future returns and price protection which may occur with our distributors and
retailers (“channel partners”). Price protection represents our practice to provide our channel partners with a
credit allowance to lower their wholesale price on a particular product that they have not resold to end
consumers. The amount of the price protection is generally the difference between the old wholesale price and
the new reduced wholesale price. In certain countries for our PC and console packaged goods software products,
we also have a practice of allowing channel partners to return older software products in the channel in exchange
for a credit allowance. As a general practice, we do not give cash refunds.
Taxes Collected from Customers and Remitted to Governmental Authorities
Taxes assessed by a government authority that are both imposed on and concurrent with specific revenue
transactions between us and our customers are presented on a net basis in our Consolidated Statements of
Operations.
Concentration of Credit Risk, Significant Customers, Franchises and Channel Partners
We extend credit to various retailers and channel partners. Collection of trade receivables may be affected by
changes in economic or other industry conditions and may, accordingly, impact our overall credit risk. Although
we generally do not require collateral, we perform ongoing credit evaluations of our customers and maintain
reserves for potential credit losses. Invoices are aged based on contractual terms with our customers. The
provision for doubtful accounts is recorded as a charge to general and administrative expense when a potential
56