Revenues

General

We recognize revenue when control of the promised goods or services is transferred to our customers, in an amount that reflects the consideration we expect to be entitled to in exchange for the goods or services. Revenue is recognized net of allowances for returns, discounts, distributor incentives, and end-user rebates, and any taxes collected from customers and subsequently remitted to governmental authorities.

For arrangements with multiple performance obligations, which may include hardware, software licenses, cloud services, support and maintenance, and professional services, we allocate revenue to each performance obligation on a relative fair value basis based on management’s estimate of stand-alone selling price (SSP). Judgment is required to determine the SSP for each performance obligation. The determination of SSP is made by taking into consideration observable prices in historical transactions. When observable prices in historical transactions are not available or are inconsistent, we estimate SSP based on observable prices in historical transactions of similar products, pricing discount practices, product margins, and other factors that may vary over time depending upon the unique facts and circumstances related to each performance obligation.

Enterprise Security

Revenue for our Enterprise Security products is earned from arrangements that can include various combinations of software licenses, cloud services, hardware, support and maintenance, and professional services, which are sold directly to end-users or through a multi-tiered distribution channel. Performance periods generally range from one to three years, and payment terms are generally between thirty and sixty days. Contracts generally do not contain significant financing components or variable consideration.

We generally do not offer rights of return for Enterprise Security products, and the distribution channel does not hold inventory. As a result, historical returns and related reserves have been insignificant. We offer channel rebates and marketing programs for our Enterprise Security products. Our estimated reserves for channel volume incentive rebates are based on distributors’ and resellers’ performance compared to the terms and conditions of volume incentive rebate programs, which are typically entered into quarterly. We had reserves for Enterprise Security rebates and marketing programs of $6 million recorded in Other current liabilities as of March 29, 2019 and $6 million recorded against Accounts receivable, net as of March 30, 2018.

Consumer Cyber Safety

We sell consumer products and services directly to end-users and consumer packaged software products through a multi-tiered distribution channel. Performance periods are generally one year or less, and payments are generally collected up front.

We offer various channel and end-user rebates for our Consumer Cyber Safety products. Our estimated reserves for channel volume incentive rebates are based on distributors’ and resellers’ performance compared to the terms and conditions of volume incentive rebate programs, which are typically entered into quarterly. Our reserves for end-user rebates are estimated based on the terms and conditions of the promotional program, actual sales during the promotion, the amount of redemptions received, historical redemption trends by product and by type of promotional program, and the value of the rebate. We record estimated reserves for channel and end-user rebates as an offset to revenue or contract liabilities. We had reserves for Consumer Cyber Safety rebates of $11 million recorded in Other current liabilities as of March 29, 2019 and $21 million recorded against Accounts receivable, net as of March 30, 2018. For consumer products that include content updates, rebates are recognized as a ratable offset to revenue or contract liabilities over the term of the subscription.

Performance obligations

At contract inception, we assess the products and services promised in the contract to identify each performance obligation and evaluate whether the performance obligations are capable of being distinct and are distinct within the context of the contract. Performance obligations that are not both capable of being distinct and distinct within the context of the contract are combined and treated as a single performance obligation in determining the allocation and recognition of revenue. Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment. In determining whether products and services are considered distinct performance obligations, we assess whether the customer can benefit from the products and services on their own or together with other readily available resources and whether our promise to transfer the product or service to the customer is separately identifiable from other promises in the contract.

Our typical performance obligations include the following:



Performance Obligation		When Performance Obligations are Typically Satisfied
Products and services transferred at a point in time:
License with distinct deliverables		When software activation keys have been made available for download
Hardware with distinct deliverables		When control of the product passes to the customer, typically upon shipment
Products and services transferred over time:
License with interrelated deliverables		Primarily term-based license subscriptions recognized over the expected performance term, beginning on the date that software activation keys are made available to the customer
Cloud hosted solutions		Over the contract term, beginning on the date that service is made available to the customer
Support and maintenance		Ratably over the course of the service term
Professional services		As the services are provided

Timing of revenue recognition

As a result of the adoption of the new revenue recognition guidance, the timing of recognition of certain of our performance obligations has changed. For example, certain term-based licenses with distinct performance obligations have a portion of revenue recognized up front when the software activation keys have been made available for download, whereas these arrangements were previously recognized over time. In addition, allocating the transaction price for perpetual software licenses and support on a relative standalone selling price basis under the new guidance has generally resulted in more revenue allocated to the upfront license compared to the residual method of allocation under the previous guidance. Conversely, certain of our perpetual licenses are not distinct from their accompanying support and maintenance under the new guidance and are now recognized over time.

The following table provides our revenue disaggregated by the timing of recognition under both the new guidance and the legacy guidance during our fiscal 2019:



(In millions)	As Reported		Amounts Without Adoption of New Standard		Effect of Change
Enterprise Security:
Products and services transferred at a point in time	$	462	$	266	$	196
Products and services transferred over time	$	1,861	$	2,010	$	(149	)
Consumer Cyber Safety:
Products and services transferred at a point in time	$	49	$	48	$	1
Products and services transferred over time	$	2,359	$	2,360	$	(1	)
Total
Products and services transferred at a point in time	$	511	$	314	$	197
Products and services transferred over time	$	4,220	$	4,370	$	(150	)

Contract liabilities

Contract liabilities by segment were as follows:



(In millions)	March 29, 2019		March 30, 2018
Enterprise Security	$	2,002	$	2,010
Consumer Cyber Safety	1,054		1,093
Total	$	3,056	$	3,103

During fiscal 2019, we recognized $2,211 million of revenue from our beginning fiscal 2019 contract liabilities balance.

Contract acquisition costs

During fiscal 2019, 2018, and 2017, we recognized $100 million, $102 million, and $85 million, respectively, of amortization expense of capitalized contract acquisition costs. There were no impairment losses recognized during fiscal 2019.

Remaining performance obligations

Remaining performance obligations represent contracted revenue that has not been recognized, which include contract liabilities and amounts that will be billed and recognized as revenue in future periods. As of March 29, 2019, we had $2,608 million of remaining performance obligations, which does not include customer deposit liabilities of approximately $505 million, and the approximate percentages expected to be recognized as revenue in the future are as follows:



	Total Remaining Performance Obligations		Percent Expected to be Recognized as Revenue
(In millions, except percentages)	Total Remaining Performance Obligations		0 - 12 Months		13 - 24 Months		25 - 36 Months		Over 36 Months
Enterprise Security	$	2,059	65	%	24	%	10	%	2	%
Consumer Cyber Safety	549		95	%	4	%	1	%	—	%
Total	$	2,608	71	%	19	%	8	%	1	%

Percentages may not add to 100% due to rounding.