Electronic Arts 2016 Annual Report Download - page 119

Download and view the complete annual report

Please find page 119 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

Annual Report
addresses simplifications related to statement of cash flows classification, accounting for forfeitures, and
minimum statutory tax withholding requirements. The pronouncement is effective for annual periods (and for
interim periods within those annual periods) beginning after December 15, 2016. We are currently evaluating the
timing and the impact of this new standard on our Consolidated Financial Statements and related disclosures.
In January 2016, the FASB issued ASU 2016-01, Financial Instruments (Topic 825-10), which requires that most
equity investments be measured at fair value, with subsequent changes in fair value recognized in net income.
The ASU also impacts financial liabilities under the fair value option and the presentation and disclosure
requirements for financial instruments. The requirements will be effective for annual periods (and interim periods
within those annual periods) beginning after December 15, 2017. We are currently evaluating the impact of this
new standard on our Consolidated Financial Statements and related disclosures.
In March 2016, the FASB issued ASU 2016-04, Liabilities — Extinguishments of Liabilities (Subtopic 405-20):
Recognition of Breakage for Certain Prepaid Stored-Value Products. The amendments in the ASU are designed
to provide guidance and eliminate diversity in the accounting for derecognition of prepaid stored-value product
liabilities. Typically, a prepaid stored-value product liability is to be derecognized when it is probable that a
significant reversal of the recognized breakage amount will not subsequently occur. This is when the likelihood
of the product holder exercising its remaining rights becomes remote. This estimate shall be updated at the end of
each period. The amendments in this ASU are effective for annual periods (and interim periods within those
annual periods) beginning after December 15, 2017. Early adoption is permitted. We are currently evaluating the
timing of adoption and impact of this new standard on our Consolidated Financial Statements and related
disclosures.
In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers (Topic 606), which
requires an entity to recognize the amount of revenue to which it expects to be entitled for the transfer of
promised goods or services to customers. The ASU will replace most existing revenue recognition guidance in
U.S. GAAP when it becomes effective. The standard permits the use of either the retrospective or cumulative
effect transition method. This new revenue standard, as amended by ASU 2015-14, is effective in the first quarter
of fiscal year 2019. In March 2016, the FASB issued ASU 2016-08, Revenue from Contracts with Customers:
Principal versus Agent Considerations (Reporting Revenue Gross versus Net), which clarifies the guidance in the
new revenue standard on assessing whether an entity is a principal or agent in a revenue transaction. This
conclusion impacts whether an entity reports revenue on a gross or net basis. In April 2016, the FASB issued
ASU 2016-10, Revenue from Contracts with Customers: Identifying Performance Obligations and Licensing,
which clarifies the guidance in the new revenue standard regarding an entity’s identification of its performance
obligations in a contract, as well as an entity’s evaluation of the nature of its promise to grant a license of
intellectual property and whether or not that revenue is recognized over time or at a point in time. In May 2016,
the FASB issued ASU 2016-12, Revenue from Contracts with Customers:Narrow- Scope Improvements and
Practical Expedients, which amends the guidance in the new revenue standard on collectibility, noncash
consideration, presentation of sales tax, and transition. The amendments are intended to address implementation
issues that were raised by stakeholders and provide additional practical expedients to reduce the cost and
complexity of applying the new revenue standard. These pronouncements have the same effective date as the
new revenue standard. While we are currently evaluating the method of adoption and the impact of the new
revenue standard, as amended, on our Consolidated Financial Statements and related disclosures, we believe the
adoption of the new standard may have a significant impact on the accounting for certain transactions with
multiple elements or “bundled” arrangements (for example, sales of online-enabled games for which we do not
have VSOE for unspecified future updates) because the requirement to have VSOE for undelivered elements
under current accounting standards is eliminated under the new standard. Accordingly, we may be required to
recognize as revenue a portion of the sales price upon delivery of the software, as compared to the current
requirement of recognizing the entire sales price ratably over an estimated offering period. While we are still
evaluating the total impact of the new revenue standard, as amended, we believe adoption of this new standard
will have a material impact on our Consolidated Financial Statements and related disclosures.
In February 2016, the FASB issued ASU 2016-02, Leases (Topic 842). The FASB issued this update to increase
transparency and comparability among organizations by recognizing lease assets and lease liabilities on the
33