XML 32 R18.htm IDEA: XBRL DOCUMENT v3.7.0.1
DEFERRED REVENUES
12 Months Ended
May 31, 2017
Deferred Revenue Disclosure [Abstract]  
DEFERRED REVENUES

10.

DEFERRED REVENUES

Deferred revenues consisted of the following:

 

 

 

May 31,

 

(in millions)

 

2017

 

 

2016

 

Software license updates and product support

 

$

5,952

 

 

$

5,864

 

Cloud SaaS, PaaS and IaaS

 

 

1,192

 

 

 

705

 

Hardware

 

 

640

 

 

 

675

 

Services

 

 

382

 

 

 

339

 

New software licenses

 

 

67

 

 

 

72

 

Deferred revenues, current

 

 

8,233

 

 

 

7,655

 

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

 

 

602

 

 

 

536

 

Total deferred revenues

 

$

8,835

 

 

$

8,191

 

 

Deferred software license updates and product support revenues and deferred hardware revenues substantially 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 SaaS, PaaS and IaaS revenues generally resulted 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 resulted from customer payments that relate to undelivered products or specified enhancements, customer-specific acceptance provisions, 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, PaaS and IaaS, 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, PaaS and IaaS, software license updates and product support and hardware 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.