XML 23 R13.htm IDEA: XBRL DOCUMENT v3.3.1.900
DEFERRED REVENUES
9 Months Ended
Feb. 29, 2016
Deferred Revenues [Abstract]  
DEFERRED REVENUES

7. DEFERRED REVENUES

 

Deferred revenues consisted of the following:

 

 

(in millions)

 

 

February 29,

2016

 

May 31,

2015

Software license updates and product support

 

$

5,239

 

$

5,635

Cloud SaaS, PaaS and IaaS

 

 

642

 

 

404

Hardware support and other

 

 

618

 

 

703

Services

 

 

322

 

 

379

New software licenses

 

 

91

 

 

124

Deferred revenues, current

 

 

6,912

 

 

7,245

Deferred revenues, non-current (in other non-current liabilities)

 

 

485

 

 

393

Total deferred revenues

 

$

7,397

 

$

7,638

 

Deferred software license updates and product support revenues and deferred hardware support revenues represent customer payments made in advance for support contracts that are typically billed on a per annum basis in advance with corresponding revenues being recognized ratably over the support periods. Deferred cloud software as a service (SaaS), platform as a service (PaaS) and infrastructure as a service (IaaS) revenues generally result from customer payments made in advance for our cloud-based offerings that are recognized over the corresponding contractual term. Deferred services revenues include prepayments for our services business and revenues for these services are generally recognized as the services are performed. Deferred new software licenses revenues typically result from undelivered products or specified enhancements, customer specific acceptance provisions, customer payments made in advance for time-based license arrangements and software license transactions that cannot be separated from undelivered consulting or other services.

 

In connection with our acquisitions, we have estimated the fair values of the cloud SaaS and PaaS, software license updates and product support, and hardware support obligations, among others, assumed from our acquired companies. We generally have estimated the fair values of these obligations assumed using a cost build-up approach. The cost build-up approach determines fair value by estimating the costs related to fulfilling the obligations plus a normal profit margin. The sum of the costs and operating profit approximates, in theory, the amount that we would be required to pay a third party to assume these acquired obligations. These aforementioned fair value adjustments recorded for obligations assumed from our acquisitions reduced the cloud SaaS and PaaS, software license updates and product support and hardware support deferred revenues balances that we recorded as liabilities from these acquisitions and also reduced the resulting revenues that we recognized or will recognize over the terms of the acquired obligations during the post-combination periods.