JAVA » Topics » Revenue Recognition

These excerpts taken from the JAVA 10-K filed Aug 28, 2009.

Revenue Recognition

As discussed in Note 2 to our Consolidated Financial Statements in Item 8, we enter into agreements to sell hardware, software, services and multiple deliverable arrangements that include combinations of products and/or services. Additionally, while the majority of our sales transactions contain standard business terms and conditions, there are some transactions that contain non-standard business terms and conditions. As a result, significant contract interpretation is sometimes required to determine the appropriate accounting including: (1) whether an arrangement exists; (2) how the arrangement consideration should be allocated among the deliverables if there are multiple deliverables; (3) when to recognize revenue on the deliverables; and (4) whether undelivered elements are essential to the functionality of delivered elements. In addition, our revenue recognition policy requires an assessment as to whether collectibility is reasonably assured, which requires us to evaluate the creditworthiness of our customers. Changes in judgments on these assumptions and estimates could materially impact the timing of revenue recognition.

 

42


Table of Contents

We recognize revenue as work progresses on fixed price Professional Services contracts when we can reliably evaluate progress to completion. We perform periodic analysis of these contracts in order to determine if the applicable estimates regarding total revenue, total cost and the extent of progress toward completion require revision. For fixed price Professional Services contracts, when the current estimates of total contract revenue and contract cost indicate a loss, the estimated loss is recognized in the period the loss becomes evident. Changes in assumptions underlying these estimates and costs could materially impact the timing of revenue recognition and loss recognition.

Distributors selling our high-end products generally purchase our products at the time an end-user is identified. Distributors selling our higher-volume products may carry our products as inventory. We recognize revenue when we sell to our distributors only if all applicable revenue recognition criteria are met. These criteria include the price to the buyer being substantially fixed or determinable at the date of sale and the amount of future returns to be reasonably estimated. The revenue we recognize associated with channel sales transactions may require us to make estimates in several areas including: (1) the likelihood of returns; (2) the amount of credits we will give for subsequent changes in our price list (i.e., price protection); (3) the amount of credits we will give for additional discounts in certain competitive transactions (i.e., margin protection); (4) the amount of stock rotation; and (5) the creditworthiness of the distributors. When applicable, we reduce revenue in these areas using assumptions that are based on our historical experience. Changes in these assumptions could require us to make significant revisions to our estimates that could materially impact the amount of net revenue recognized.

Revenue Recognition

We enter into revenue arrangements to sell products (hardware and software) and services in which we are obligated to deliver to our customers multiple products and/or services (multiple deliverables). Revenue arrangements with multiple deliverables are evaluated to determine if the deliverables (items) can be divided into more than one unit of accounting. An item can generally be considered a separate unit of accounting if all of the following criteria are met:

 

 

The delivered item(s) has value to the customer on a standalone basis;

 

 

There is objective and reliable evidence of the fair value of the undelivered item(s); and

 

 

If the arrangement includes a general right of return relative to the delivered item(s), delivery or performance of the undelivered item(s) is considered probable and substantially in our control.

Items that do not meet these criteria are combined into a single unit of accounting. If there is objective and reliable evidence of fair value for all units of accounting, the arrangement consideration is allocated to the separate units of accounting based on their relative fair values. In cases where there is objective and reliable evidence of the fair value of the undelivered item(s) in an arrangement but no such evidence for the delivered item(s), the residual method is used to allocate the arrangement consideration. For units of accounting which include more than one deliverable, we generally defer all revenue for the unit of accounting until the period in which the last undelivered item is delivered. The revenue policies described below are then applied to each unit of accounting.

We recognize revenue when the following criteria are met: 1) persuasive evidence of an arrangement exists; 2) delivery has occurred or services have been rendered; 3) the sales price is fixed or determinable; and 4) collectibility is reasonably assured. Our standard agreements generally do not include customer acceptance provisions. However, if there is a customer acceptance provision or there is uncertainty about customer acceptance, the associated revenue is deferred until we have evidence of customer acceptance.

 

56


Table of Contents

Products Revenue

Products revenue for sales to end-user customers, resellers and distributors (Channel Partners) is recognized upon the passage of title only if all other applicable revenue recognition criteria are met. These criteria include the price to the buyer being substantially fixed or determinable at the date of sale and the amount of future returns being able to be reasonably estimated. When we are not able to meet these criteria at the time of sale to our stocking Channel Partners, we defer revenue until these criteria are met, generally at the time products are sold-out of Channel Partner stocking inventory. Our program offerings to certain of our Channel Partners provide for the limited right to return our product for stock rotation. When applicable, we reduce revenue for rights to return our product based upon our historical experience. End-user customers generally do not have return rights. In accordance with contractual provisions, we offer price protection to certain of our Channel Partners and margin protection on certain transactions. When applicable, we reduce revenue based upon announced price adjustments and historical experience. In accordance with contractual provisions, we may offer cooperative marketing funds based on a fixed dollar percentage of product sales to certain of our Channel Partners. We record such amounts as a reduction to revenue or, if we have evidence of fair value of the advertising benefit received, as marketing expense.

In addition, we sell 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. We had deferred revenue and related deferred costs of $28 million and $11 million at June 30, 2009 and $12 million and $5 million, at June 30, 2008, respectively, related to recourse leases which will be recognized in future periods.

For revenue arrangements with multiple deliverables that include or represent software products and services as well as any non-software deliverables for which a software deliverable is essential to its functionality, we apply the accounting guidance in SOP 97-2, “Software Revenue Recognition” (SOP 97-2), in determining the timing of revenue recognition. The criteria assessed include the following: 1) the functionality of the delivered element(s) is not dependent on the undelivered element; 2) there is Sun-specific objective evidence of fair value of the undelivered element(s) and 3) delivery of the delivered element(s) represents the culmination of the earnings process for those element(s). If these criteria are not met, revenue is deferred until such criteria are met or until the last element is delivered. For arrangements within the scope of SOP 97-2, revenue is recognized ratably only in situations where one of the limited exceptions described in paragraph 12 of SOP 97-2 is met, such as where we agree to deliver unspecified additional software products in the future.

Services Revenue

Maintenance contract revenue is generally recognized ratably over the contractual period. Educational Services revenue is recognized as the services are rendered. Time and material and fixed price Professional Services contract revenue is recognized as the Professional Services are rendered, or upon completion of the services contract. If we can reliably evaluate progress to completion (based on total projected hours to be incurred as compared with hours already incurred), we recognize the revenue as the services are rendered and recognize the related costs as they are incurred. In instances where we cannot reliably estimate the total projected hours, we recognize revenue and the associated costs upon completion of the services contract. For fixed price Professional Services contracts when the current estimates of total contract revenue and contract cost indicate a loss, the estimated loss is recognized in the period the loss becomes evident.

These excerpts taken from the JAVA 10-K filed Aug 29, 2008.

Revenue Recognition

We enter into revenue arrangements to sell products (hardware and software) and services in which we are obligated to deliver to our customers multiple products and/or services (multiple deliverables). Revenue arrangements with multiple deliverables are evaluated to determine if the deliverables (items) can be divided into more than one unit of accounting. An item can generally be considered a separate unit of accounting if all of the following criteria are met:

 

 

The delivered item(s) has value to the customer on a standalone basis;

 

 

There is objective and reliable evidence of the fair value of the undelivered item(s); and

 

 

If the arrangement includes a general right of return relative to the delivered item(s), delivery or performance of the undelivered item(s) is considered probable and substantially in our control.

Items that do not meet these criteria are combined into a single unit of accounting. If there is objective and reliable evidence of fair value for all units of accounting, the arrangement consideration is allocated to the separate units of accounting based on their relative fair values. In cases where there is objective and reliable evidence of the fair value of the undelivered item(s) in an arrangement but no such evidence for the delivered item(s), the residual method is used to allocate the arrangement consideration. For units of accounting which include more than one deliverable, we generally defer all revenue for the unit of accounting until the period over which the last undelivered item is delivered. The revenue policies described below are then applied to each unit of accounting.

We recognize revenue when the following criteria are met: 1) persuasive evidence of an arrangement exists; 2) delivery has occurred or services have been rendered; 3) the sales price is fixed or determinable; and 4) collectibility is reasonably assured. Our standard agreements generally do not include customer acceptance provisions. However, if there is a customer acceptance provision or there is uncertainty about customer acceptance, the associated revenue is deferred until we have evidence of customer acceptance.

Products Revenue

Products revenue for sales to end-user customers, resellers and distributors (Channel Partners) is recognized upon the passage of title only if all other applicable revenue recognition criteria are met. These criteria include the price to the buyer being substantially fixed or determinable at the date of sale and the amount of future returns to be reasonably estimated. Our program offerings to certain of our Channel Partners provide for the limited right to return our product for stock rotation. When applicable, we reduce revenue for rights to return our product based upon our historical experience. End-user customers generally do not have return rights. In accordance with contractual provisions, we offer price protection to certain of our Channel Partners and margin protection on certain transactions. When applicable under these contractual provisions, we reduce revenue based upon announced price adjustments and historical experience. In accordance with contractual provisions we may offer cooperative marketing funds based on a fixed dollar percentage of product sales to certain of our Channel Partners. We record such amounts as a reduction to revenue or, if we have evidence of fair value of the advertising benefit received, as marketing expense.

In addition, we sell 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 full 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. We had deferred revenue and related deferred costs of $12 million and $5 million at June 30, 2008 and $10 million and $4 million, at June 30, 2007, respectively, related to recourse leases which will be recognized in future periods.

For revenue arrangements with multiple deliverables that include or represent software products and services as well as any non-software deliverables for which a software deliverable is essential to its functionality, we apply the accounting guidance in SOP 97-2, “Software Revenue Recognition” in determining the timing of revenue recognition. The criteria assessed include the following: 1) the functionality of the delivered element(s) is not dependent on the undelivered element; 2) there is Sun-specific objective evidence of fair value of the undelivered element(s) and 3) delivery of the delivered element(s) represents the culmination of the earnings process for those element(s). If these criteria are not met, revenue is deferred until such criteria are met or until the last element is delivered. For arrangements within the scope of SOP 97-2, revenue is recognized ratably only in situations where one of the limited exceptions described in paragraph 12 of SOP 97-2 is met, such as where we agree to deliver unspecified additional software products in the future.

 

57


Table of Contents

Beginning in the second quarter of fiscal 2008, we introduced programs in certain geographic markets entitling our distributors to a reduced price on hardware when sold to the end customer with a support services contract. Accordingly, in these cases, we are no longer able to meet the criteria for revenue recognition under U.S. generally accepted accounting principles at the time of sale to our distributors. We have deferred revenue on these sales until our distributors sell the hardware to the end customer.

Services Revenue

Maintenance contract revenue is generally recognized ratably over the contractual period. Educational Services revenue is recognized as the services are rendered. Time and material and fixed price Professional Services contract revenue is recognized as the Professional Services are rendered, or upon completion of the services contract. If we can reliably evaluate progress to completion (based on total projected hours to be incurred as compared with hours already incurred), we recognize the revenue as the services are rendered and recognize the related costs as they are incurred. In instances where we cannot reliably estimate the total projected hours, we recognize revenue and the associated costs upon completion of the services contract. For fixed price Professional Services contracts when the current estimates of total contract revenue and contract cost indicate a loss, the estimated loss is recognized in the period the loss becomes evident.

Revenue Recognition

SIZE="2">We enter into revenue arrangements to sell products (hardware and software) and services in which we are obligated to deliver to our customers multiple products and/or services (multiple deliverables). Revenue arrangements with multiple
deliverables are evaluated to determine if the deliverables (items) can be divided into more than one unit of accounting. An item can generally be considered a separate unit of accounting if all of the following criteria are met:

STYLE="font-size:6px;margin-top:0px;margin-bottom:0px"> 






 

The delivered item(s) has value to the customer on a standalone basis;

STYLE="font-size:6px;margin-top:0px;margin-bottom:0px"> 






 

There is objective and reliable evidence of the fair value of the undelivered item(s); and

STYLE="font-size:6px;margin-top:0px;margin-bottom:0px"> 






 

If the arrangement includes a general right of return relative to the delivered item(s), delivery or performance of the undelivered item(s) is considered probable
and substantially in our control.

Items that do not meet these criteria are combined into a single unit of accounting. If there is
objective and reliable evidence of fair value for all units of accounting, the arrangement consideration is allocated to the separate units of accounting based on their relative fair values. In cases where there is objective and reliable evidence of
the fair value of the undelivered item(s) in an arrangement but no such evidence for the delivered item(s), the residual method is used to allocate the arrangement consideration. For units of accounting which include more than one deliverable, we
generally defer all revenue for the unit of accounting until the period over which the last undelivered item is delivered. The revenue policies described below are then applied to each unit of accounting.

STYLE="margin-top:6px;margin-bottom:0px">We recognize revenue when the following criteria are met: 1) persuasive evidence of an arrangement exists; 2) delivery has occurred or services have been rendered; 3) the
sales price is fixed or determinable; and 4) collectibility is reasonably assured. Our standard agreements generally do not include customer acceptance provisions. However, if there is a customer acceptance provision or there is uncertainty about
customer acceptance, the associated revenue is deferred until we have evidence of customer acceptance.

Products Revenue

STYLE="margin-top:6px;margin-bottom:0px">Products revenue for sales to end-user customers, resellers and distributors (Channel Partners) is recognized upon the passage of title only if all other applicable
revenue recognition criteria are met. These criteria include the price to the buyer being substantially fixed or determinable at the date of sale and the amount of future returns to be reasonably estimated. Our program offerings to certain of our
Channel Partners provide for the limited right to return our product for stock rotation. When applicable, we reduce revenue for rights to return our product based upon our historical experience. End-user customers generally do not have return
rights. In accordance with contractual provisions, we offer price protection to certain of our Channel Partners and margin protection on certain transactions. When applicable under these contractual provisions, we reduce revenue based upon announced
price adjustments and historical experience. In accordance with contractual provisions we may offer cooperative marketing funds based on a fixed dollar percentage of product sales to certain of our Channel Partners. We record such amounts as a
reduction to revenue or, if we have evidence of fair value of the advertising benefit received, as marketing expense.

In addition, we sell 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 full 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. We had deferred revenue and related deferred costs of $12 million and $5 million at
June 30, 2008 and $10 million and $4 million, at June 30, 2007, respectively, related to recourse leases which will be recognized in future periods.

SIZE="2">For revenue arrangements with multiple deliverables that include or represent software products and services as well as any non-software deliverables for which a software deliverable is essential to its functionality, we apply the
accounting guidance in SOP 97-2, “Software Revenue Recognition” in determining the timing of revenue recognition. The criteria assessed include the following: 1) the functionality of the delivered element(s) is not dependent on the
undelivered element; 2) there is Sun-specific objective evidence of fair value of the undelivered element(s) and 3) delivery of the delivered element(s) represents the culmination of the earnings process for those element(s). If these criteria are
not met, revenue is deferred until such criteria are met or until the last element is delivered. For arrangements within the scope of SOP 97-2, revenue is recognized ratably only in situations where one of the limited exceptions described in
paragraph 12 of SOP 97-2 is met, such as where we agree to deliver unspecified additional software products in the future.

 


57







Table of Contents


Beginning in the second quarter of fiscal 2008, we introduced programs in certain geographic markets entitling our
distributors to a reduced price on hardware when sold to the end customer with a support services contract. Accordingly, in these cases, we are no longer able to meet the criteria for revenue recognition under U.S. generally accepted accounting
principles at the time of sale to our distributors. We have deferred revenue on these sales until our distributors sell the hardware to the end customer.

SIZE="2">Services Revenue

Maintenance contract revenue is generally recognized ratably over the contractual period. Educational Services revenue is
recognized as the services are rendered. Time and material and fixed price Professional Services contract revenue is recognized as the Professional Services are rendered, or upon completion of the services contract. If we can reliably evaluate
progress to completion (based on total projected hours to be incurred as compared with hours already incurred), we recognize the revenue as the services are rendered and recognize the related costs as they are incurred. In instances where we cannot
reliably estimate the total projected hours, we recognize revenue and the associated costs upon completion of the services contract. For fixed price Professional Services contracts when the current estimates of total contract revenue and contract
cost indicate a loss, the estimated loss is recognized in the period the loss becomes evident.

This excerpt taken from the JAVA 10-K filed Aug 29, 2007.

Revenue Recognition

We enter into revenue arrangements to sell products (hardware and software) and services in which we are obligated to deliver to our customers multiple products and/or services (multiple deliverables). Revenue arrangements with multiple deliverables are evaluated to determine if the deliverables (items) can be divided into more than one unit of accounting. An item can generally be considered a separate unit of accounting if all of the following criteria are met:

 

 

The delivered item(s) has value to the customer on a standalone basis;

 

 

There is objective and reliable evidence of the fair value of the undelivered item(s); and

 

 

If the arrangement includes a general right of return relative to the delivered item(s), delivery or performance of the undelivered item(s) is considered probable and substantially in our control.

Items that do not meet these criteria are combined into a single unit of accounting. If there is objective and reliable evidence of fair value for all units of accounting, the arrangement consideration is allocated to the separate units of accounting based on their relative fair values. In cases where there is objective and reliable evidence of the fair value of the undelivered item(s) in an arrangement but no such evidence for the delivered item(s), the residual method is used to allocate the arrangement consideration. For units of accounting which include more than one deliverable, we generally defer all revenue for the unit of accounting until the period over which the last undelivered item is delivered. The revenue policies described below are then applied to each unit of accounting.

We recognize revenue when the following criteria are met: 1) persuasive evidence of an arrangement exists; 2) delivery has occurred or services have been rendered; 3) the sales price is fixed or determinable; and 4) collectibility is reasonably assured. Our standard agreements generally do not include customer acceptance provisions. However, if there is a customer acceptance provision or there is uncertainty about customer acceptance, the associated revenue is deferred until we have evidence of customer acceptance.

Products Revenue

Products revenue for sales to end-user customers, resellers and distributors (Channel Partners) is recognized upon the passage of title only if all other applicable revenue recognition criteria are met. These criteria include the price to the buyer being substantially fixed or determinable at the date of sale and the amount of future returns to be reasonably estimated. Our program offerings to certain of our Channel Partners provide for the limited right to return our product for stock rotation. When applicable, we reduce revenue for rights to return our product based upon our historical experience. End-user customers generally do not have return rights. In accordance with contractual provisions, we offer price protection to certain of our Channel Partners and margin protection on certain transactions. When applicable under these contractual provisions, we reduce revenue based upon announced price adjustments and historical experience. In accordance with contractual provisions we may offer co-operative marketing funds based on a fixed dollar percentage of product sales to certain of our Channel Partners. We record such amounts as a reduction to revenue or, if we have evidence of fair value of the advertising benefit received, as marketing expense.

In addition, we sell products to leasing companies that, in turn, lease these products to end-users. In transactions where the leasing companies have no recourse to Sun 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 full recourse to Sun 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. We had deferred revenue and related deferred costs of $20 million and $11 million at June 30, 2007, and $22 million and $12 million, at June 30, 2006, respectively, related to recourse leases which will be recognized in future periods.

For revenue arrangements with multiple deliverables that include or represent software products and services as well as any non-software deliverables for which a software deliverable is essential to its functionality, we apply the accounting guidance in SOP 97-2, “Software Revenue Recognition” in determining the timing of revenue recognition. The criteria assessed include the following: 1) the functionality of the delivered element(s) is not dependent on the undelivered element; 2) there is Sun-specific objective evidence of fair value of the undelivered element(s), and 3) delivery of the delivered element(s) represents the culmination of the earnings process for those element(s). If these criteria are not met, revenue is deferred until such criteria are met or until the last element is delivered. For arrangements within the scope of SOP 97-2, revenue is recognized ratably only in situations where one of the limited exceptions described in paragraph 12 of SOP 97-2 is met, such as where we agree to deliver unspecified additional software products in the future.

 

53


Table of Contents

Services Revenue

Maintenance contract revenue is generally recognized ratably over the contractual period. Educational Services revenue is recognized as the services are rendered. Time and material, and fixed price Professional Services contract revenue is recognized as the Professional Services are rendered, or upon completion of the services contract. If we can reliably evaluate progress to completion (based on total projected hours to be incurred as compared with hours already incurred), we recognize the revenue as the services are rendered and recognize the related costs as they are incurred. In instances where we cannot reliably estimate the total projected hours, we recognize revenue and the associated costs upon completion of the services contract. For fixed price Professional Services contracts when the current estimates of total contract revenue and contract cost indicate a loss, the estimated loss is recognized in the period the loss becomes evident.

This excerpt taken from the JAVA 10-K filed Sep 8, 2006.

Revenue Recognition

Sun enters into revenue arrangements to sell products (hardware and software) and services in which we are obligated to deliver to our customers multiple products and/or services (multiple deliverables). Revenue arrangements with multiple deliverables are evaluated to determine if the deliverables (items) can be divided into more than one unit of accounting. An item can generally be considered a separate unit of accounting if all of the following criteria are met:

 

  The delivered item(s) has value to the customer on a standalone basis;

 

  There is objective and reliable evidence of the fair value of the undelivered item(s); and

 

  If the arrangement includes a general right of return relative to the delivered item(s), delivery or performance of the undelivered item(s) is considered probable and substantially in the control of Sun.

Items which do not meet these criteria are combined into a single unit of accounting. If there is objective and reliable evidence of fair value for all units of accounting, the arrangement consideration is allocated to the separate units of accounting based on their relative fair values. In cases where there is objective and reliable evidence of the fair value of the undelivered item(s) in an arrangement but no such evidence for the delivered item(s), the residual method is used to allocate the arrangement consideration. For units of accounting which include more than one deliverable, we generally defer all revenue for the unit of accounting until the period over which the last undelivered item is delivered. The revenue policies described below are then applied to each unit of accounting.

We recognize revenue when the following criteria are met: 1) persuasive evidence of an arrangement exists; 2) delivery has occurred or services have been rendered; 3) the sales price is fixed or determinable; and 4) collectibility is reasonably assured. Our standard agreements generally do not include customer acceptance provisions. However, if there is a customer acceptance provision or there is uncertainty about customer acceptance, the associated revenue is deferred until we have evidence of customer acceptance.

Products Revenue

Products revenue for sales to both end-user customers and resellers is generally recognized upon the passage of title if all other revenue recognition criteria have been met. End-user customers generally do not have return rights. Our program offerings to certain of our resellers and distributors (Channel Partners) provide for the limited right to return our product for stock rotation. We reduce revenue for rights to return our product based upon our historical experience with the Channel Partners. In accordance with contractual provisions, we offer price protection to certain of our Channel Partners. We also offer margin protection to our Channel Partners on certain transactions. For our price protection and margin protection programs, we reduce revenue based upon our historical experience or specific announced price adjustments. In accordance with contractual provisions, to certain of our Channel Partners we also offer co-operative marketing funds based on a fixed dollar percentage of product sales. We record the amount as a reduction to revenue or, if we have evidence of fair value of the advertising benefit received, as marketing expense.

In addition, we sell products to leasing companies that, in turn, lease these products to end-users. In transactions where the leasing companies have no recourse to Sun 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 full recourse to Sun 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. We had deferred revenue and related deferred costs of $22 million and $12 million, respectively, at June 30, 2006 and $37 million and $16 million, respectively, at June 30, 2005, related to recourse leases which will be recognized in future periods.

 

58


Table of Contents

For revenue arrangements with multiple deliverables that include or represent software products and services as well as any non-software deliverables for which a software deliverable is essential to its functionality, we apply the accounting guidance in SOP 97-2, “Software Revenue Recognition” in determining the timing of revenue recognition. The criteria assessed include the following: 1) the functionality of the delivered element(s) is not dependent on the undelivered element; 2) there is Sun-specific objective evidence of fair value of the undelivered element(s), and 3) delivery of the delivered element(s) represents the culmination of the earnings process for those element(s). If these criteria are not met, revenue is deferred until such criteria are met or until the last element is delivered. For arrangements within the scope of SOP 97-2, revenue is recognized ratably only in situations where one of the limited exceptions described in paragraph 12 of SOP 97-2 is met, such as where we agree to deliver unspecified additional software products in the future.

Services Revenue

Maintenance contract revenue is generally recognized ratably over the contractual period. Educational services revenue is recognized as the services are rendered. Time and material, and fixed price Client solutions contract revenue is recognized as the professional services are rendered, or upon completion of the services contract. If we can reliably evaluate progress to completion (based on total projected hours to be incurred as compared with hours already incurred), we recognize the revenue as the services are rendered and recognize the related costs as they are incurred. In instances where we cannot reliably estimate the total projected hours, we recognize revenue and the associated costs upon completion of the services contract. For fixed price Client solutions contracts when the current estimates of total contract revenue and contract cost indicate a loss, the estimated loss is recognized in the period the loss becomes evident.

This excerpt taken from the JAVA 10-K filed Sep 13, 2005.

Revenue Recognition

 

Multiple Deliverable Arrangements

 

Sun enters into revenue arrangements to sell products (hardware and software) and services in which we are obligated to deliver to our customers multiple products and/or services (multiple deliverables). Revenue arrangements with multiple deliverables are evaluated to determine if the deliverables (items) can be divided into more than one unit of accounting. An item can generally be considered a separate unit of accounting if all of the following criteria are met:

 

  The delivered item(s) has value to the customer on a standalone basis;

 

72


Table of Contents
  There is objective and reliable evidence of the fair value of the undelivered item(s); and

 

  If the arrangement includes a general right of return relative to the delivered item(s), delivery or performance of the undelivered item(s) is considered probable and substantially in the control of Sun.

 

Items which do not meet these criteria are combined into a single unit of accounting. If there is objective and reliable evidence of fair value for all units of accounting, the arrangement consideration is allocated to the separate units of accounting based on their relative fair values. In cases where there is objective and reliable evidence of the fair value of the undelivered item(s) in an arrangement but no such evidence for the delivered item(s), the residual method is used to allocate the arrangement consideration. For units of accounting which include more than one deliverable, we generally defer all revenue for the unit of accounting until the period over which the last undelivered item is delivered. The revenue policies described below are then applied to each unit of accounting.

 

We recognize revenue when the following criteria are met: 1) persuasive evidence of an arrangement exists; 2) delivery has occurred or services have been rendered; 3) the sales price is fixed or determinable; and 4) collectibility is probable. Our standard agreements generally do not include customer acceptance provisions. However, if there is a customer acceptance provision or there is uncertainty about customer acceptance, the associated revenue is deferred until we have evidence of customer acceptance.

 

Products Revenue

 

Products revenue for sales to both end-user customers and resellers is generally recognized upon the passage of title if all other revenue recognition criteria have been met. End-user customers generally do not have return rights. Our program offerings to certain of our resellers and distributors (Channel Partners) provide for the limited right to return our product for stock rotation. We reduce revenue for rights to return our product based upon our historical experience with the Channel Partners. In accordance with contractual provisions, we offer price protection to certain of our Channel Partners. We also offer margin protection to our Channel Partners on certain transactions. For our price protection and margin protection programs, we reduce revenue based upon our historical experience. In accordance with contractual provisions, to certain of our Channel Partners we also offer co-operative marketing funds based on a fixed dollar percentage of product sales. We record the amount as a reduction to revenue or, if we have evidence of fair value of the advertising benefit received as marketing expense.

 

In addition, we sell products to leasing companies that, in turn, lease these products to end-users. In transactions where the leasing companies have no recourse to Sun 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 full recourse to Sun 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. We had deferred revenue and related deferred costs of $37 million and $16 million, respectively, at June 30, 2005 and $16 million and $7 million, respectively, at June 30, 2004, related to recourse leases which will be recognized in future periods.

 

For revenue arrangements with multiple deliverables that include software products and services as well as any non-software deliverables for which a software deliverable is essential to its functionality, we apply the accounting guidance in SOP 97-2, “Software Revenue Recognition” in determining the timing of revenue recognition. The criteria assessed include the following: 1) the functionality of the delivered element(s) is not dependent on the undelivered element; 2) there is Sun-specific objective evidence of fair value of the undelivered element(s), and 3) delivery of the delivered element(s) represents the culmination of the earnings process for those element(s). If these criteria are not met, revenue is deferred until such criteria are met or until the last element is delivered.

 

Services Revenue

 

Maintenance contract revenue is recognized ratably over the contractual period. Educational services revenue is recognized as the services are rendered. Time and material, and fixed price Client solutions contract revenue is recognized as the professional services are rendered, or upon completion of the services contract. If we can reliably evaluate progress to completion (based on total projected hours to be incurred as compared with hours already incurred), we recognize the revenue as the services are rendered and recognize the related costs as they are incurred. In instances where we cannot reliably estimate the total projected hours, we recognize revenue and the associated costs

 

73


Table of Contents

upon completion of the services contract. For fixed price Client solutions contracts when the current estimates of total contract revenue and contract cost indicate a loss, the estimated loss is recognized in the period the loss becomes evident.

 

Wikinvest © 2006, 2007, 2008, 2009, 2010, 2011, 2012. Use of this site is subject to express Terms of Service, Privacy Policy, and Disclaimer. By continuing past this page, you agree to abide by these terms. Any information provided by Wikinvest, including but not limited to company data, competitors, business analysis, market share, sales revenues and other operating metrics, earnings call analysis, conference call transcripts, industry information, or price targets should not be construed as research, trading tips or recommendations, or investment advice and is provided with no warrants as to its accuracy. Stock market data, including US and International equity symbols, stock quotes, share prices, earnings ratios, and other fundamental data is provided by data partners. Stock market quotes delayed at least 15 minutes for NASDAQ, 20 mins for NYSE and AMEX. Market data by Xignite. See data providers for more details. Company names, products, services and branding cited herein may be trademarks or registered trademarks of their respective owners. The use of trademarks or service marks of another is not a representation that the other is affiliated with, sponsors, is sponsored by, endorses, or is endorsed by Wikinvest.
Powered by MediaWiki