Oracle 2013 Annual Report Download - page 94

Download and view the complete annual report

Please find page 94 of the 2013 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 151

  • 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

Table of Contents
ORACLE CORPORATION
NOTES TO CONSOLIDATED FINANCIAL STATEMENTS—(Continued)
May 31, 2014
assumptions are made. These estimates, judgments and assumptions can affect the reported amounts of assets and liabilities as of the date of the
financial statements as well as the reported amounts of revenues and expenses during the periods presented. To the extent there are differences
between these estimates, judgments or assumptions and actual results, our consolidated financial statements will be affected. In many cases, the
accounting treatment of a particular transaction is specifically dictated by GAAP and does not require management’
s judgment in its application.
There are also areas in which management’s judgment in selecting among available alternatives would not produce a materially different result.
Revenue Recognition
Our sources of revenues include: (1) software and cloud revenues, including new software licenses revenues earned from granting licenses to use
our software products; cloud SaaS and PaaS revenues generated from fees for granting customers access to a broad range of our software and
related support offerings on a subscription basis in a secure, standards-based cloud computing environment; cloud IaaS revenues generated from
fees for deployment and management offerings for our software and hardware and related IT infrastructure generally on a subscription basis; and
software license updates and product support revenues; (2) hardware systems revenues, which include the sale of hardware systems products
including computer servers, storage products, networking and data center fabric products, and hardware systems support revenues; and
(3) services, which includes software and hardware related services including consulting, advanced customer support and education revenues.
Revenues generally are recognized net of any taxes collected from customers and subsequently remitted to governmental authorities.
Revenue Recognition for Software Products and Software Related Services (Software Elements)
New software licenses revenues primarily represent fees earned from granting customers licenses to use our database, middleware and
application software and exclude cloud SaaS and PaaS revenues and revenues derived from software license updates, which are included in
software license updates and product support revenues. The basis for our new software licenses revenue recognition is substantially governed by
the accounting guidance contained in ASC 985-605, Software-Revenue Recognition
. We exercise judgment and use estimates in connection with
the determination of the amount of software and software related services revenues to be recognized in each accounting period.
For software license arrangements that do not require significant modification or customization of the underlying software, we recognize new
software licenses revenues when: (1) we enter into a legally binding arrangement with a customer for the license of software; (2) we deliver the
products; (3) the sale price is fixed or determinable and free of contingencies or significant uncertainties; and (4) collection is probable.
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.
Substantially all of our software license arrangements do not include acceptance provisions. However, if acceptance provisions exist as part of
public policy, for example, in agreements with government entities where acceptance periods are required by law, or within previously executed
terms and conditions that are referenced in the current agreement and are short-term in nature, we generally recognize revenues upon delivery
provided the 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
90