Oracle 2014 Annual Report Download - page 97

Download and view the complete annual report

Please find page 97 of the 2014 Oracle 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 165

  • 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

Table of Contents
ORACLE CORPORATION
NOTES TO CONSOLIDATED FINANCIAL STATEMENTS—(Continued)
May 31, 2015
acceptance terms are perfunctory and all other revenue recognition criteria have been met. If acceptance provisions are not perfunctory (for
example, acceptance provisions that are long-term in nature or are not included as standard terms of an arrangement), revenues are recognized
upon the earlier of receipt of written customer acceptance or expiration of the acceptance period.
The vast majority of our software license arrangements include software license updates and product support contracts, which are entered into at
the customer’s option and are recognized ratably over the term of the arrangement, typically one year. Software license updates provide
customers with rights to unspecified software product upgrades, maintenance releases and patches released during the term of the support period.
Product support includes internet access to technical content, as well as internet and telephone access to technical support personnel. Software
license updates and product support contracts are generally priced as a percentage of the net new software licenses fees. Substantially all of our
customers renew their software license updates and product support contracts annually.
Revenue Recognition for Multiple-Element Arrangements—Software Products and Software Related Services (Software Arrangements)
We often enter into arrangements with customers that purchase both software related products and software related services from us at the same
time, or within close proximity of one another (referred to as software related multiple-element arrangements). Such software related multiple-
element arrangements include the sale of our software products, software license updates and product support contracts and other software
related services whereby software license delivery is followed by the subsequent or contemporaneous delivery of the other elements. For those
software related multiple-element arrangements, we have applied the residual method to determine the amount of new software license revenues
to be recognized pursuant to ASC 985-605. Under the residual method, if fair value exists for undelivered elements in a multiple-element
arrangement, such fair value of the undelivered elements is deferred with the remaining portion of the arrangement consideration generally
recognized upon delivery of the software license. We allocate the fair value of each element of a software related multiple-element arrangement
based upon its fair value as determined by our vendor specific objective evidence (VSOE—
described further below), with any remaining amount
allocated to the software license.
Revenue Recognition for Cloud SaaS, PaaS and IaaS Offerings, Hardware Systems Products, Hardware Systems Support and Related
Services (Nonsoftware Elements)
Our revenue recognition policy for nonsoftware deliverables including cloud SaaS, PaaS and IaaS offerings, hardware systems products, support
and related services is based upon the accounting guidance contained in ASC 605-25, Revenue Recognition , Multiple-Element Arrangements,
and we exercise judgment and use estimates in connection with the determination of the amount of cloud SaaS, PaaS and IaaS revenues,
hardware systems products revenues, support and related services revenues to be recognized in each accounting period.
Revenues from the sales of our nonsoftware elements are recognized when: (1) persuasive evidence of an arrangement exists; (2) we deliver the
products and passage of the title to the buyer occurs; (3) the sale price is fixed or determinable; and (4) collection is reasonably assured.
Revenues that are not recognized at the time of sale because the foregoing conditions are not met are recognized when those conditions are
subsequently met. When applicable, we reduce revenues for estimated returns or certain other incentive programs where we have the ability to
sufficiently estimate the effects of these items. Where an arrangement is subject to acceptance criteria and the acceptance provisions are not
perfunctory (for example, acceptance provisions that are long-term in nature or are not included as standard terms of an arrangement), revenues
are recognized upon the earlier of receipt of written customer acceptance or expiration of the acceptance period.
Our cloud SaaS and PaaS offerings generally provide customers access to certain of our software within a cloud-based IT environment that we
manage, host and support and offer to customers on a subscription basis. Revenues for our cloud SaaS and PaaS offerings are generally
recognized ratably over the contract term commencing with the date the service is made available to customers and all other revenue recognition
criteria have been satisfied.
93