UNITED STATES
SECURITIES AND EXCHANGE COMMISSION
Washington, D.C. 20549
FORM 10-Q
QUARTERLY REPORT PURSUANT TO SECTION 13 OR 15(d) OF
THE SECURITIES EXCHANGE ACT OF 1934
For the quarterly period ended February 28, 2010
or
TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF
THE SECURITIES EXCHANGE ACT OF 1934
For the transition period from
to .
Commission File Number: 000-51788
Oracle
Corporation
(Exact name of registrant as specified in its charter)
Delaware
54-2185193
(State or other jurisdiction of
incorporation or organization)
(I.R.S. Employer
Identification No.)
500 Oracle Parkway
Redwood City, California
94065
(Zip Code)
(Address of principal executive offices)
(650) 506-7000
(Registrant s telephone number, including area code)
Indicate by check mark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for
such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days. Yes No
Indicate by check mark whether the registrant has submitted electronically and posted to its corporate Web site, if any, every Interactive Data File required to be submitted and posted pursuant to Rule
405 of Regulation S-T ( 232.405 of this chapter) during the preceding 12 months (or for such shorter period that the registrant was required to submit and post such files). Yes No
Indicate by check mark whether the registrant is a large accelerated filer, an accelerated filer, a non-accelerated filer, or a smaller reporting company. See the definitions of large accelerated
filer , accelerated filer and smaller reporting company in Rule 12b-2 of the Exchange Act.
Large accelerated filer
Accelerated filer
Non-accelerated filer
Smaller reporting company
(Do not check if a smaller reporting company)
Indicate by check mark whether the registrant is a shell company (as defined in Rule 12b-2 of the Exchange
Act). Yes No
The number of shares of registrant s common stock outstanding as of March 23, 2010 was: 5,019,091,000.
Table of Contents
ORACLE CORPORATION
FORM 10-Q QUARTERLY REPORT
TABLE OF CONTENTS
Page
PART I.
FINANCIAL INFORMATION
Item 1.
Financial Statements (Unaudited)
Condensed Consolidated Balance Sheets as of February 28, 2010 and May 31, 2009
Condensed Consolidated Statements of Operations for the Three and Nine Months Ended February 28, 2010 and 2009
Condensed Consolidated Statements of Cash Flows for the Nine Months Ended February 28, 2010 and 2009
Notes to Condensed Consolidated Financial Statements
Item 2.
Management s Discussion and Analysis of Financial Condition and Results of
Operations
34
Item 3.
Quantitative and Qualitative Disclosures About Market Risk
67
Item 4.
Controls and Procedures
67
PART II.
OTHER INFORMATION
Item 1.
Legal Proceedings
69
Item 1A.
Risk Factors
69
Item 2.
Unregistered Sales of Equity Securities and Use of Proceeds
72
Item 6.
Exhibits
74
Signatures
75
Table of Contents
PART I. FINANCIAL INFORMATION
Item 1. Financial Statements (Unaudited)
ORACLE CORPORATION
CONDENSED CONSOLIDATED BALANCE SHEETS
As of February 28, 2010 and May 31, 2009
(Unaudited)
(in millions, except per share data)
February 28,
2010
May 31,
2009
ASSETS
Current assets:
Cash and cash equivalents
9,331
8,995
Marketable securities
8,158
3,629
Trade receivables, net of allowances for doubtful accounts of $273 and $270 as of February 28, 2010 and May 31, 2009,
respectively
3,898
4,430
Inventories
315
Deferred tax assets
978
661
Prepaid expenses and other current assets
1,299
866
Total current assets
23,979
18,581
Non-current assets:
Property, plant and equipment, net
2,869
1,922
Intangible assets: software support agreements and related relationships, net
3,038
3,411
Intangible assets: other, net
6,830
3,858
Goodwill
20,415
18,842
Other assets
2,255
802
Total non-current assets
35,407
28,835
Total assets
59,386
47,416
LIABILITIES AND EQUITY
Current liabilities:
Notes payable, current and other current borrowings
4,220
1,001
Accounts payable
616
271
Accrued compensation and related benefits
1,452
1,409
Deferred revenues
5,389
4,592
Other current liabilities
2,574
1,876
Total current liabilities
14,251
9,149
Non-current liabilities:
Notes payable and other non-current borrowings
11,498
9,237
Income taxes payable
3,275
2,423
Deferred tax liabilities
339
480
Other non-current liabilities
1,172
682
Total non-current liabilities
16,284
12,822
Commitments and contingencies
Oracle Corporation stockholders equity:
Preferred stock, $0.01 par value authorized: 1.0 shares; outstanding: none
Common stock, $0.01 par value and additional paid in capital authorized: 11,000 shares; outstanding: 5,015 shares as of
February 28, 2010 and 5,005 shares as of May 31, 2009
13,973
12,980
Retained earnings
14,257
11,894
Accumulated other comprehensive income
246
216
Total Oracle Corporation stockholders equity
28,476
25,090
Noncontrolling interests
375
355
Total equity
28,851
25,445
Total liabilities and equity
59,386
47,416
See notes to condensed consolidated financial statements.
Table of Contents
ORACLE CORPORATION
CONDENSED CONSOLIDATED STATEMENTS OF OPERATIONS
For the Three and Nine Months Ended February 28, 2010 and 2009
(Unaudited)
Three Months Ended
February 28,
Nine Months Ended
February 28,
(in millions, except per share data)
2010
2009
2010
2009
Revenues:
New software licenses
1,718
1,516
4,399
4,379
Software license updates and product support
3,297
2,917
9,661
8,702
Software revenues
5,015
4,433
14,060
13,081
Hardware systems products
273
273
Hardware systems support
185
185
Hardware systems revenues
458
458
Services
931
1,020
2,797
3,310
Total revenues
6,404
5,453
17,315
16,391
Operating expenses:
Sales and marketing
1,241
1,054
3,335
3,312
Software license updates and product support
281
256
771
795
Hardware systems products
206
206
Hardware systems support
116
116
Services
816
855
2,429
2,820
Research and development
823
677
2,191
2,037
General and administrative
236
192
619
571
Amortization of intangible assets
502
437
1,369
1,276
Acquisition related and other
34
27
50
98
Restructuring
306
15
467
46
Total operating expenses
4,561
3,513
11,553
10,955
Operating income
1,843
1,940
5,762
5,436
Interest expense
(186
(154
(553
(471
Non-operating income (expense), net
(75
24
(41
114
Income before provision for income taxes
1,582
1,810
5,168
5,079
Provision for income taxes
393
481
1,396
1,377
Net income
1,189
1,329
3,772
3,702
Earnings per share:
Basic
0.24
0.27
0.75
0.73
Diluted
0.23
0.26
0.74
0.72
Weighted average common shares outstanding:
Basic
5,015
5,005
5,012
5,095
Diluted
5,076
5,056
5,067
5,159
Dividends declared per common share
0.05
0.15
See notes to condensed consolidated financial statements.
Table of Contents
ORACLE CORPORATION
CONDENSED CONSOLIDATED STATEMENTS OF CASH FLOWS
For the Nine Months Ended February 28, 2010 and 2009
(Unaudited)
Nine Months Ended
February 28,
(in millions)
2010
2009
Cash Flows From Operating Activities:
Net income
3,772
3,702
Adjustments to reconcile net income to net cash provided by operating activities:
Depreciation
196
198
Amortization of intangible assets
1,369
1,276
Deferred income taxes
(362
(302
Stock-based compensation
310
274
Tax benefits on the exercise of stock options and vesting of restricted stock-based awards
117
141
Excess tax benefits on the exercise of stock options and vesting of restricted stock-based awards
(71
(92
Other, net
79
68
Changes in operating assets and liabilities, net of effects from acquisitions:
Decrease in trade receivables, net
1,614
1,848
Decrease in inventories
18
Decrease in prepaid expenses and other assets
375
336
Decrease in accounts payable and other liabilities
(842
(1,097
Decrease in income taxes payable
(269
(51
Decrease in deferred revenues
(136
(54
Net cash provided by operating activities
6,170
6,247
Cash Flows From Investing Activities:
Purchases of marketable securities and other investments
(11,162
(6,906
Proceeds from maturities and sales of marketable securities and other investments
7,121
6,397
Acquisitions, net of cash acquired
(5,567
(1,165
Capital expenditures
(161
(491
Net cash used for investing activities
(9,769
(2,165
Cash Flows From Financing Activities:
Payments for repurchases of common stock
(738
(3,704
Proceeds from issuances of common stock
602
448
Payment of dividends to stockholders
(753
Proceeds from borrowings, net of issuance costs
6,420
Repayments of borrowings
(1,708
(4
Excess tax benefits on the exercise of stock options and vesting of restricted stock-based awards
71
92
Distributions to noncontrolling interests
(59
(53
Net cash provided by (used for) financing activities
3,835
(3,221
Effect of exchange rate changes on cash and cash equivalents
100
(912
Net increase (decrease) in cash and cash equivalents
336
(51
Cash and cash equivalents at beginning of period
8,995
8,262
Cash and cash equivalents at end of period
9,331
8,211
Non-cash investing and financing transactions:
Fair value of stock options and restricted stock-based awards assumed in connection with acquisitions
91
Increase in unsettled repurchases of common stock
See notes to condensed consolidated
financial statements.
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS
February 28, 2010
(Unaudited)
1.
BASIS OF PRESENTATION AND RECENT ACCOUNTING PRONOUNCEMENTS
Basis of Presentation
We have prepared the condensed consolidated financial statements
included herein, without audit, pursuant to the rules and regulations of the U.S. Securities and Exchange Commission (SEC). Certain information and footnote disclosures normally included in financial statements prepared in accordance with U.S.
generally accepted accounting principles have been condensed or omitted pursuant to such rules and regulations. However, we believe that the disclosures are adequate to ensure the information presented is not misleading. These unaudited condensed
consolidated financial statements should be read in conjunction with the audited financial statements and the notes thereto included in our Annual Report on Form 10-K for the fiscal year ended May 31, 2009.
On January 26, 2010, we completed our acquisition of Sun Microsystems, Inc. (Sun), a provider of hardware systems, software and services, by means of a
merger of one of our wholly owned subsidiaries with and into Sun such that Sun became a wholly owned subsidiary of Oracle. As a result of our acquisition of Sun, we entered into a new hardware systems business. Our hardware systems business consists
of two operating segments: hardware systems products and hardware systems support. In addition, we enhanced our existing software and services businesses with additional offerings. The condensed consolidated financial statements included in this
Quarterly Report include the financial results of Sun prospectively from the date of acquisition. Upon completion of our acquisition of Sun, we adopted certain new significant accounting policies as noted below. Refer to Note 2 below for additional
details of our acquisition of Sun.
We believe that all necessary adjustments, which consisted only of normal recurring items, have been
included in the accompanying financial statements to present fairly the results of the interim periods. The results of operations for the interim periods presented are not necessarily indicative of the operating results to be expected for any
subsequent interim period or for our fiscal year ending May 31, 2010.
In July 2009, the Financial Accounting Standards Board (FASB)
issued the FASB Accounting Standards Codification (Codification), which we adopted in our second quarter of fiscal 2010. There were no changes to our consolidated financial statements and related disclosures contained in this Quarterly Report
due to the implementation of the Codification, other than changes in reference in this Quarterly Report to the various authoritative accounting pronouncements contained within the Codification.
During fiscal 2010, we adopted certain new accounting pronouncements that affected our significant accounting policies, including FASB Accounting Standards
Codification (ASC) 805, Business Combinations, Accounting Standards Update No. 2009-13, Revenue Recognition (Topic 605) Multiple-Deliverable Revenue Arrangements (ASU 2009-13) and Accounting Standards Update No. 2009-14,
Software (Topic 985) Certain Revenue Arrangements That Include Software Elements (ASU 2009-14). As a result of our recent acquisition of Sun and our adoption of ASU 2009-13 and ASU 2009-14, we have included our updated accounting
policies for revenue recognition, inventories and shipping costs below. We disclosed our accounting policies for ASC 805 and all of our other significant accounting policies in Note 1 of Notes to Consolidated Financial Statements in our Annual
Report on Form 10-K for the fiscal year ended May 31, 2009. There have been no other changes to our significant accounting policies that were disclosed in our Annual Report on Form 10-K for the fiscal year ended May 31, 2009 other than the
aforementioned policy changes and standards reference changes resulting from the Codification.
As a result of our adoption of the FASB s
new accounting guidance for noncontrolling interests as contained in ASC 810, Consolidation, as of the beginning of fiscal 2010, we retrospectively classified noncontrolling interest positions of certain of our consolidated entities as a
separate component of consolidated equity from the equity attributable to Oracle s stockholders for all periods presented. The noncontrolling interests in our net income were not significant to our consolidated results for the periods presented
and therefore have been included as a
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
component of non-operating income (expense), net in our condensed consolidated statements of operations. Certain other prior year balances have been reclassified to conform to the current
year s presentation. Such reclassifications did not affect our total revenues, operating income or net income.
Revenue Recognition
Our sources of revenues prior to our acquisition of Sun were: (1) software, which includes new software license and software
license updates and product support revenues, and (2) services, which include consulting, On Demand and education revenues. As a result of our acquisition of Sun on January 26, 2010, our sources of revenues have been expanded to include
hardware systems products, which primarily include revenues from the sale of computer servers and storage products, and hardware systems support revenues.
Revenue Recognition for Software Products and Software Related Services (Software Elements)
New software license revenues represent fees earned from granting customers licenses to use our database, middleware and applications software, and exclude revenues derived from software license updates, which are included in software
license updates and product support revenues. While the basis for software license 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 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 license revenues when: (1) we enter into a legally binding arrangement with a customer for the
license of software; (2) we deliver the products; (3) customer payment is deemed fixed or determinable and free of contingencies or significant uncertainties; and (4) collection is probable. Substantially all of our new software
license revenues are recognized in this manner.
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 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 license 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 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
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
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 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 recognized upon delivery of the software license or services arrangement. We allocate the fair values 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 Hardware Systems Products and Hardware Systems Related Services (Nonsoftware Elements)
Revenues from the sale of hardware systems products represent amounts earned primarily from the sale of computer servers and storage products. Our revenue recognition policy for these nonsoftware
deliverables is based upon the accounting guidance contained in ASC 605, Revenue Recognition, and we exercise judgment and use estimates in connection with the determination of the amount of hardware systems products and hardware systems
related services revenues to be recognized in each accounting period.
Revenues from the sales of hardware systems products 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 hardware systems support offerings generally provide customers with software updates for the software components that are essential to the functionality of our hardware systems and storage products
and can include product repairs, maintenance services, and technical support services. Hardware systems support contracts are entered into at the customer s option and are recognized ratably over the contractual term of the arrangement.
Revenue Recognition for Multiple-Element Arrangements Hardware Systems Products and Hardware Systems Related Services (Nonsoftware
Arrangements)
In the third quarter of fiscal 2010, we early adopted the provisions of ASU 2009-13 and ASU 2009-14. ASU 2009-13 amended
existing accounting guidance for revenue recognition for multiple-element arrangements. To the extent a deliverable within a multiple-element arrangement is not accounted for pursuant to other accounting standards, including ASC 985-605,
Software-Revenue Recognition, ASU 2009-13 establishes a selling price hierarchy that allows for the use of an estimated selling price (ESP) to determine the allocation of arrangement consideration to a deliverable in a multiple element
arrangement where neither VSOE nor third-party evidence (TPE) is available for that deliverable. ASU 2009-14 modifies the scope of ASC 985-605 to exclude tangible products containing software components and nonsoftware components that function
together to deliver the product s essential functionality. In addition, ASU 2009-14 provides guidance on how a vendor should allocate arrangement consideration to nonsoftware and software deliverables in an arrangement where the vendor sells
tangible products containing software components that are essential in delivering the tangible product s functionality.
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
As a result of our early adoption of ASU 2009-13 and ASU 2009-14, we applied the provisions of these
accounting standards updates as of the beginning of our fiscal year 2010. The retrospective application of ASU 2009-13 and 2009-14 as of the beginning of our fiscal year 2010 had no impact to our previously reported results of operations.
We enter into arrangements with customers that purchase both nonsoftware related products and services from us at the same time, or within
close proximity of one another (referred to as nonsoftware multiple-element arrangements). Each element within a nonsoftware multiple-element arrangement is accounted for as a separate unit of accounting provided the following criteria are met: the
delivered products or services have value to the customer on a standalone basis; and for an arrangement that includes a general right of return relative to the delivered products or services, delivery or performance of the undelivered product or
service is considered probable and is substantially controlled by us. We consider a deliverable to have standalone value if the product or service is sold separately by us or another vendor or could be resold by the customer. Further, our revenue
arrangements generally do not include a general right of return relative to the delivered products. Where the aforementioned criteria for a separate unit of accounting are not met, the deliverable is combined with the undelivered element(s) and
treated as a single unit of accounting for the purposes of allocation of the arrangement consideration and revenue recognition. For those units of accounting which include more than one deliverable but are treated as a single unit of accounting, we
generally recognize revenues over the delivery period. For the purposes of revenue classification of the elements that are accounted for as a single unit of accounting, we allocate revenue to hardware system and services based on a rational and
consistent methodology utilizing our best estimate of fair value of such elements.
For our nonsoftware multiple-element arrangements, we
allocate revenue to each element based on a selling price hierarchy at the arrangement inception. The selling price for each element is based upon the following selling price hierarchy: VSOE if available, TPE if VSOE is not available, or ESP if
neither VSOE nor TPE is available (a description as to how we determine VSOE, TPE and ESP is provided below). If a tangible hardware systems product includes software, we determine whether the tangible hardware systems product and the software work
together to deliver the product s essential functionality and, if so, the entire product is treated as a nonsoftware deliverable. The total arrangement consideration is allocated to each separate unit of accounting for each of the nonsoftware
deliverables using the relative selling prices of each based on the aforementioned selling price hierarchy. We limit the amount of revenue recognized for delivered elements to an amount that is not contingent upon future delivery of additional
products or services or meeting of any specified performance conditions.
To determine the selling price in multiple-element arrangements, we
establish VSOE of selling price using the price charged for a deliverable when sold separately and for software license updates and product support and hardware systems support, based on the renewal rates offered to customers. For nonsoftware
multiple element arrangements, TPE is established by evaluating similar and interchangeable competitor products or services in standalone arrangements with similarly situated customers. If we are unable to determine the selling price because VSOE or
TPE doesn t exist, we determine ESP for the purposes of allocating the arrangement by considering several external and internal factors including, but not limited to, pricing practices, margin objectives, competition, geographies in which we
offer our products and services, internal costs and stage of the product lifecycle. The determination of ESP is made through consultation with and approval by our management, taking into consideration our go-to-market strategy. As our, or our
competitors , pricing and go-to-market strategies evolve, we may modify our pricing practices in the future, which could result in changes to our determination of VSOE, TPE and ESP. As a result, our future revenue recognition for
multiple-element arrangements could differ materially from our results in the current period. Selling prices are analyzed on an annual basis or more frequently if we experience significant changes in our selling prices.
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
Revenue Recognition Policies Applicable to both Software and Nonsoftware Elements
Revenue Recognition for Multiple-Element Arrangements Arrangements with Software and Nonsoftware Elements
We also enter into multiple-element arrangements that may include a combination of our various software related and nonsoftware related products and services
offerings including hardware systems products, hardware systems support, new software licenses, software license updates and product support, consulting, On Demand and education. In such arrangements, we first allocate the total arrangement
consideration based on the relative selling prices of the software group of elements as a whole and to the nonsoftware elements. We then further allocate consideration within the software group to the respective elements within that group following
the guidance in ASC 985-605 and our policies described above. After the arrangement consideration has been allocated to the elements, we account for each respective element in the arrangement as described above.
Other Revenue Recognition Policies Applicable to Software and Nonsoftware Elements
Many of our software arrangements include consulting implementation services sold separately under consulting engagement contracts and are included as a part of our services business. Consulting revenues
from these arrangements are generally accounted for separately from new software license revenues because the arrangements qualify as services transactions as defined in ASC 985-605. The more significant factors considered in determining whether the
revenues should be accounted for separately include the nature of services (i.e., consideration of whether the services are essential to the functionality of the licensed product), degree of risk, availability of services from other vendors, timing
of payments and impact of milestones or acceptance criteria on the realizability of the software license fee. Revenues for consulting services are generally recognized as the services are performed. If there is a significant uncertainty about the
project completion or receipt of payment for the consulting services, revenues are deferred until the uncertainty is sufficiently resolved. We estimate the proportional performance on contracts with fixed or not to exceed fees on a
monthly basis utilizing hours incurred to date as a percentage of total estimated hours to complete the project. If we do not have a sufficient basis to measure progress towards completion, revenues are recognized when we receive final acceptance
from the customer. When total cost estimates exceed revenues, we accrue for the estimated losses immediately using cost estimates that are based upon an average fully burdened daily rate applicable to the consulting organization delivering the
services. The complexity of the estimation process and factors relating to the assumptions, risks and uncertainties inherent with the application of the proportional performance method of accounting affects the amounts of revenues and related
expenses reported in our consolidated financial statements. A number of internal and external factors can affect our estimates, including labor rates, utilization and efficiency variances and specification and testing requirement changes.
On Demand is comprised of Oracle On Demand and Advanced Customer Services and is a part of our services business. Oracle On Demand services
are offered as standalone arrangements or as a part of arrangements to customers buying new software licenses or hardware systems products and services. Our On Demand services provide multi-featured software and hardware management and maintenance
services for our software and hardware systems products delivered at our data center facilities, select partner data centers or customer facilities. Advanced Customer Services provide customers with services to architect, implement and manage
customer IT environments including software and hardware systems product management services, industry-specific solution support centers and remote and on-site expert services. Depending upon the nature of the arrangement, revenues from On Demand
services are recognized as services are performed or ratably over the term of the service period, which is generally one year or less.
Education revenues are a part of our services business and include instructor-led, media-based and internet-based training in the use of our software and hardware systems products. Education revenues are recognized as the classes or other
education offerings are delivered.
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
If an arrangement contains multiple elements and does not qualify for separate accounting for the
product and service transactions, then new software license revenues and/or hardware systems products revenues, including the costs of hardware systems products, are generally recognized together with the services based on contract accounting using
either the percentage-of-completion or completed-contract method. Contract accounting is applied to any bundled software, hardware systems and services arrangements: (1) that include milestones or customer specific acceptance criteria that may
affect collection of the software license or hardware systems product fees; (2) where consulting services include significant modification or customization of the software or hardware systems product; (3) where significant consulting
services are provided for in the software license contract or hardware systems product contract without additional charge or are substantially discounted; or (4) where the software license or hardware systems product payment is tied to the
performance of consulting services. For the purposes of revenue classification of the elements that are accounted for as a single unit of accounting, we allocate revenues to software and nonsoftware elements based on a rational and consistent
methodology utilizing our best estimate of fair value of such elements.
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 software and hardware systems businesses include short-term payment terms, we have a standard practice of providing long-term financing to credit worthy
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 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.
In addition, we sell hardware systems products to leasing companies that, in turn, lease these products to end-users. In transactions where the leasing companies have no recourse to us in the event of
default by the end-user, we recognize revenue at point of shipment or point of delivery, depending on the shipping terms and if all the other revenue recognition criteria have been met. In arrangements where the leasing companies have more than
insignificant recourse to us in the event of default by the end-user (defined as recourse leasing), we recognize both the product revenue and the related cost of the product as the payments are made to the leasing company by the end-user, generally
ratably over the lease term.
Our customers include several of our suppliers and on rare occasion, 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
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
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 products
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.
Inventories
Inventories are stated at the lower of cost (first in, first out) or
market value. We evaluate our ending inventories for estimated excess quantities and obsolescence. This evaluation includes analysis of sales levels by product and projections of future demand within specific time horizons (generally six months or
less). Inventories in excess of future demand are written down. In addition, we assess the impact of changing technology to our inventory and we write-off inventories that are considered obsolete.
Shipping Costs
Our shipping and
handling costs for hardware systems products sales are included in expenses for hardware systems products for all periods presented.
Acquisition Related and Other Expenses
Acquisition related and other expenses consist of personnel related costs for
transitional and certain other employees, stock-based compensation expenses, integration related professional services, certain business combination adjustments after the measurement period or purchase price allocation period has ended, and certain
other operating expenses, net. Stock-based compensation included in acquisition related and other expenses resulted from unvested options or restricted stock-based awards (primarily consisting of restricted stock units) assumed from acquisitions
whereby vesting was accelerated upon termination of the employees pursuant to the original terms of those options or restricted stock-based awards. As a result of our adoption of the FASB s revised accounting guidance for business combinations
as of the beginning of fiscal 2010, certain acquisition related and other expenses are now recorded as expenses in our statements of operations that would previously have been included as a part of the consideration transferred and capitalized as a
part of the accounting for our acquisitions pursuant to previous accounting rules, primarily direct transaction costs such as professional services fees.
Three Months Ended
February 28,
Nine Months Ended
February 28,
(in millions)
2010
2009
2010
2009
Transitional and other employee related costs
10
39
Stock-based compensation
10
10
14
Professional fees and other, net
18
16
25
34
Business combination adjustments, net
11
Total acquisition related and other expenses
34
27
50
98
10
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
Non-Operating Income (Expense), net
Non-operating income (expense), net consists primarily of interest income, net foreign currency exchange gains (losses), the noncontrolling interests in the net profits of our majority-owned subsidiaries
(Oracle Financial Services Software Limited and Oracle Japan), and net other income (losses), including net realized gains and losses related to all of our investments and net unrealized gains and losses related to the small portion of our
investment portfolio that we classify as trading.
Three Months Ended
February 28,
Nine Months Ended
February 28,
(in millions)
2010
2009
2010
2009
Interest income
27
58
91
243
Foreign currency losses, net
(88
(9
(109
(22
Noncontrolling interests in income
(24
(23
(63
(58
Other income (losses), net
10
(2
40
(49
Total non-operating income (expense), net
(75
24
(41
114
Included in our non-operating income (expense), net are net foreign currency losses for the three and nine months ended
February 28, 2010 that included a foreign currency loss relating to our Venezuelan subsidiary s operations. Effective December 1, 2009, we designated our Venezuelan subsidiary as highly inflationary in accordance with ASC
830, Foreign Currency Matters, and began using the U.S. Dollar as the subsidiary s new functional currency. During our third quarter of fiscal 2010, the Venezuelan government devalued its currency and we recognized a $70 million
foreign currency loss as a result of the remeasurement of certain assets and liabilities of our Venezuelan subsidiary. As a large portion of our consolidated operations are international, we could experience additional foreign currency volatility in
the future, the amounts and timing of which are variable.
Comprehensive Income
Comprehensive income consists of the following, net of income tax effects: net income, net foreign currency translation gains and losses, net gains and
losses related to certain of our derivative financial instruments that are reflected in Oracle Corporation stockholders equity and net unrealized gains and losses on marketable debt and equity securities that we classify as available-for-sale.
The following table sets forth the calculation of comprehensive income:
Three Months Ended
February 28,
Nine Months Ended
February 28,
(in millions)
2010
2009
2010
2009
Net income
1,189
1,329
3,772
3,702
Foreign currency translation (losses) gains, net
(233
(56
43
(739
Unrealized gains (losses) on derivative financial instruments, net
18
10
(13
(34
Unrealized (losses) gains on marketable securities, net
(4
Comprehensive income
974
1,279
3,802
2,935
Recent Accounting Pronouncements
Disclosure requirements related to Fair Value Measurements: In January 2010, the FASB issued Accounting Standards Update No. 2010-06, Improving
Disclosures about Fair Value Measurements (Topic 820) Fair Value Measurements and Disclosures (ASU 2010-06) to add additional disclosures about the different classes of assets
11
Table of Contents
ORACLE CORPORATION
NOTES TO CONDENSED CONSOLIDATED FINANCIAL STATEMENTS (Continued)
February 28, 2010
(Unaudited)
and liabilities measured at fair value, the valuation techniques and inputs used, the activity in Level 3 fair value measurements, and the transfers between Levels 1, 2, and 3. Levels 1, 2 and 3
of fair value measurements are defined in Note 3 below. We will adopt this new accounting standards update in our fourth quarter of fiscal 2010 except for the provisions of this update that will be effective in our fiscal 2012. We
are currently evaluating the impact of its pending adoption on our consolidated financial statements.
Transfers of
Financial Assets: In June 2009, the FASB issued and subsequently codified Accounting Standards Update No. 2009-16, Transfers and Servicing (Topic 860) Accounting for
Transfers of Financial Assets (ASU 2009-16). ASU 2009-16 eliminates the concept of a qualifying special-purpose entity with regards to transfer of financial assets and changes the requirements for derecognizing financial
assets. We will adopt this new accounting standards update in fiscal 2011 and are currently evaluating the impact of its pending adoption on our consolidated financial statements.