Oracle 2011 Annual Report Download - page 98

Download and view the complete annual report

Please find page 98 of the 2011 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 140

  • 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

ORACLE CORPORATION
NOTES TO CONSOLIDATED FINANCIAL STATEMENTS—(Continued)
May 31, 2011
We also evaluate arrangements with governmental entities containing “fiscal funding” or “termination for
convenience” provisions, when such provisions are required by law, to determine the probability of possible
cancellation. We consider multiple factors, including the history with the customer in similar transactions, the
“essential use” of the software or hardware systems products and the planning, budgeting and approval processes
undertaken by the governmental entity. If we determine upon execution of these arrangements that the likelihood
of cancellation is remote, we then recognize revenues once all of the criteria described above have been met. If
such a determination cannot be made, revenues are recognized upon the earlier of cash receipt or approval of the
applicable funding provision by the governmental entity.
We assess whether fees are fixed or determinable at the time of sale and recognize revenues if all other revenue
recognition requirements are met. Our standard payment terms are net 30 days. However, payment terms may
vary based on the country in which the agreement is executed. Payments that are due within six months are
generally deemed to be fixed or determinable based on our successful collection history on such arrangements,
and thereby satisfy the required criteria for revenue recognition.
While most of our arrangements for sales within our businesses include short-term payment terms, we have a
standard practice of providing long-term financing to creditworthy customers through our financing division.
Since fiscal 1989, when our financing division was formed, we have established a history of collection, without
concessions, on these receivables with payment terms that generally extend up to five years from the contract
date. Provided all other revenue recognition criteria have been met, we recognize new software license revenues
and hardware systems products revenues for these arrangements upon delivery, net of any payment discounts
from financing transactions. We have generally sold receivables financed through our financing division on a
non-recourse basis to third party financing institutions within 90 days of the contracts’ dates of execution and we
classify the proceeds from these sales as cash flows from operating activities in our consolidated statements of
cash flows. We account for the sales of these receivables as “true sales” as defined in ASC 860, Transfers and
Servicing, as we are considered to have surrendered control of these financing receivables. During fiscal 2011,
$1.5 billion of our financing receivables were sold to financial institutions.
In addition, we enter into arrangements with leasing companies for sale of our hardware systems products. These
leasing companies, in turn, lease our products to end-users. The leasing companies generally have no recourse to
us in the event of default by the end-user and we recognize revenue upon delivery, if all the other revenue
recognition criteria have been met.
Our customers include several of our suppliers and occasionally, we have purchased goods or services for our
operations from these vendors at or about the same time that we have sold our products to these same companies
(Concurrent Transactions). Software license agreements or sales of hardware systems that occur within a three-
month time period from the date we have purchased goods or services from that same customer are reviewed for
appropriate accounting treatment and disclosure. When we acquire goods or services from a customer, we
negotiate the purchase separately from any sales transaction, at terms we consider to be at arm’s length, and settle
the purchase in cash. We recognize new software license revenues or hardware systems product revenues from
Concurrent Transactions if all of our revenue recognition criteria are met and the goods and services acquired are
necessary for our current operations.
Business Combinations
In fiscal 2010, we adopted ASC 805, Business Combinations, which revised the accounting guidance that we
were required to apply for our acquisitions in comparison to prior fiscal years. The underlying principles are
similar to the previous guidance and require that we recognize separately from goodwill the assets acquired and
the liabilities assumed, generally at their acquisition date fair values. Goodwill as of the acquisition date is
measured as the excess of consideration transferred and the net of the acquisition date fair values of the assets
acquired and the liabilities assumed. While we use our best estimates and assumptions as a part of the purchase
96