XML 38 R27.htm IDEA: XBRL DOCUMENT v3.19.1
Revenue Recognition Revenue Recognition (Policies)
6 Months Ended
Mar. 31, 2019
Revenue from Contract with Customer [Abstract]  
Revenue from Contract with Customer [Policy Text Block]
We derive revenue from the following sources: (1) hosting services, (2) software licenses, including royalties, (3) maintenance and support (“M&S”), (4) professional services, and (5) sale of hardware. Revenue is reported net of applicable sales and use tax, value-added tax and other transaction taxes imposed on the related transaction including mandatory government charges that are passed through to our customers. We account for a contract when both parties have approved and committed to the contract, the rights of the parties are identified, payment terms are identified, the contract has commercial substance and collectability of consideration is probable.
The majority of our arrangements with customers typically contain multiple products and services. We account for individual products and services separately if they are distinct--that is, if a product or service is separately identifiable from other items in the contract and if a customer can benefit from it on its own or with other resources that are readily available to the customer.
We recognize revenue after applying the following five steps:
identification of the contract, or contracts, with a customer;
identification of the performance obligations in the contract, including whether they are distinct within the context of the contract;
determination of the transaction price, including the constraint on variable consideration;
allocation of the transaction price to the performance obligations in the contract; and
recognition of revenue when, or as, performance obligations are satisfied.

We allocate the transaction price of the arrangement based on the relative estimated standalone selling price (“SSP”) of each distinct performance obligation. In determining SSP, we maximize observable inputs and consider a number of data points, including:
the pricing of standalone sales (in the instances where available);
the pricing established by management when setting prices for deliverables that are intended to be sold on a standalone basis;
contractually stated prices for deliverables that are intended to be sold on a standalone basis; and
other pricing factors, such as the geographical region in which the products are sold and expected discounts based on the customer size and type.
We only include estimated amounts of variable consideration in the transaction price to the extent it is probable that a significant reversal of cumulative revenue recognized will not occur when the uncertainty associated with the variable consideration is resolved. We reduce transaction prices for estimated returns and other allowances that represent variable consideration under ASC 606, which we estimate based on historical return experience and other relevant factors, and record a corresponding refund liability as a component of accrued expenses and other current liabilities. Other forms of contingent revenue or variable consideration are infrequent.
Revenue is recognized when control of these products and services is transferred to our customers, in an amount that reflects the consideration we expect to be entitled to in exchange for those services.
We assess the timing of the transfer of products or services to the customer as compared to the timing of payments to determine whether a significant financing component exists. In accordance with the practical expedient in ASC 606-10-32-18, we do not assess the existence of a significant financing component when the difference between payment and transfer of deliverables is a year or less. If the difference in timing arises for reasons other than the provision of finance to either the customer or us, no financing component is deemed to exist. The primary purpose of our invoicing terms is to provide customers with simplified and predictable ways of purchasing our services, not to receive or provide financing from or to customers. We do not consider set-up fees nor other upfront fees paid by our customers to represent a financing component.
Certain products are sold through distributors or resellers. Certain distributors and resellers have been granted right of return and selling incentives which are accounted for as variable consideration when estimating the amount of revenue to be recognized. Returns and credits are estimated at the contract inception and updated at the end of each reporting period as additional information becomes available. In accordance with the practical expedient in ASC 606-10-10-4, we apply a portfolio approach to estimate the variable consideration associated with this group of customers.
Reimbursements for out-of-pocket costs generally include, but are not limited to, costs related to transportation, lodging and meals. Revenue from reimbursed out-of-pocket costs is accounted for as variable consideration.
Shipping and handling activities are not considered a contract performance obligation. We record shipping and handling costs billed to customers as revenue with offsetting costs recorded as cost of revenue.
Performance Obligations
Hosting
Hosting services, which allow our customers to use the hosted software over the contract period without taking possession of the software, are provided on a usage basis as consumed or on a fixed fee subscription basis. Our hosting contract terms generally range from one to five years.
As each day of providing services is substantially the same and the customer simultaneously receives and consumes the benefits as access is provided, we have determined that our hosting services arrangements are a single performance obligation comprised of a series of distinct services. These services include variable consideration, typically a function of usage. We recognize revenue as each distinct service period is performed (i.e., recognized as incurred).
Subscription basis revenue represents a single promise to stand-ready to provide access to our hosting services. Revenue is recognized over time on a ratable basis over the hosting contract term, which generally ranges from one to five years.
Software Licenses
On-premise software licenses sold with non-distinct professional services to customize and/or integrate the underlying software are accounted for as a combined performance obligation. Revenue from the combined performance obligation is recognized over time based upon the progress towards completion of the project, which is measured based on the labor hours already incurred to date as compared to the total estimated labor hours.
Revenue from distinct on-premise software licenses, which do not require professional services to customize and/or integrate the software license, is recognized at the point in time when the software is made available to the customer and control is transferred.
Revenue from software license sold on a royalty basis, where the license of intellectual property is the predominant item to which the royalty relates, is recognized in the period the usage occurs in accordance with the practical expedient in ASC 606-10-55-65(A).
Maintenance and Support
Our M&S contracts generally include telephone support and the right to receive unspecified upgrades and updates on a when-and-if available basis. M&S revenue is recognized over time on ratable basis over the contract period because we transfer control evenly by providing a stand-ready service.
Professional Services
Revenue from distinct professional services, including training, is recognized over time based upon the progress towards completion of the project, which is measured based on the labor hours already incurred to date as compared to the total estimated labor hours.
Hardware
Hardware revenue is recognized point in time when control is transferred to the customer, typically delivery.
Significant Judgments
Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment. Our license contracts often include professional services to customize and/or integrate the licenses into the customer’s environment. Judgment is required to determine whether the license is considered distinct and accounted for separately, or not distinct and accounted for together with professional services.
Judgments are required to determine the SSP for each distinct performance obligation. When SSP is directly observable, we estimate SSP based upon the historical transaction prices, adjusted for geographic considerations, customer classes, and customer relationship profiles. In instances where SSP is not directly observable, we determine SSP using information that may include market conditions and other observable inputs. We may have more than one SSP for individual products and services due to the stratification of those products and services by customers and circumstances. In these instances, we may use information such as the size of the customer and geographic region in determining SSP. Determining SSP for performance obligations which we never sell separately also requires significant judgment. In estimating the SSP, we consider the likely price that would have resulted from established pricing practices had the deliverable been offered separately and the prices a customer would likely be willing to pay.
From time to time, we may enter into arrangements with third party suppliers to resell products or services. In such cases, we evaluate whether we are the principal (i.e. report revenues on a gross basis) or agent (i.e. report revenues on a net basis). In doing so, we first evaluate whether we control the good or service before it is transferred to the customer. If we control the good or service before it is transferred to the customer, we are the principal; if not, we are the agent. Generally, we control a promised good or service before transferring that good or service to the customer and act as the principal to the transaction. Determining whether we control the good or service before it is transferred to the customer may require judgment.
Disaggregated Revenue
We disaggregate revenue from contracts with customers by reportable segment and products and services as this presentation depicts the timing, risks and uncertainty of our revenue streams, which is also in line with how we manage our businesses, assess performance, and determine management compensation. Our disaggregated revenue from continuing operations is as follows (dollars in thousands):
 
For the Three Months Ended March 31, 2019
 
Hosting and professional services
 
Product and licensing
 
Maintenance and support
 
Total
Healthcare
$
125,867

 
$
41,708

 
$
36,829

 
$
204,404

Enterprise
76,674

 
14,774

 
23,994

 
115,442

Automotive
33,584

 
39,317

 
98

 
72,999

Other
14,986

 
1,744

 
8

 
16,738

Total revenues
$
251,111

 
$
97,543

 
$
60,929

 
$
409,583

 
For the Six Months Ended March 31, 2019
 
Hosting and professional services
 
Product and licensing
 
Maintenance and support
 
Total
Healthcare
$
259,382

 
$
134,737

 
$
82,150

 
$
476,269

Enterprise
155,216

 
35,053

 
54,625

 
244,894

Automotive
65,455

 
81,425

 
98

 
146,978

Other
30,646

 
4,325

 
125

 
35,096

Total revenues
$
510,699

 
$
255,540

 
$
136,998

 
$
903,237


Hardware comprised approximately $7.1 million of total product and license revenue for the three months ended March 31, 2019 and $17.2 million for the six months ended March 31, 2019.
Contract Acquisition Costs
In conjunction with the adoption of ASC 606, we are required to capitalize certain contract acquisition costs. The capitalized costs primarily relate to paid commissions and other direct, incremental cost to acquire customer contracts. In accordance with the practical expedient in ASC 606-10-10-4, we apply a portfolio approach to estimate contract acquisition costs for groups of customer contracts. We elect to apply the practical expedient in ASC 340-40-25-4 and will expense contract acquisition costs as incurred where the expected period of benefit is one year or less. Sales commissions paid on renewal maintenance and support are not commensurate with sales commissions paid on the initial maintenance and support contract. Contract acquisition costs are deferred and amortized on a straight-line basis over the period of benefit, which we have estimated to be between one and five years. The period of benefit was determined based on an average customer contract term, expected contract renewals, changes in technology and our ability to retain customers including canceled contracts. Contract acquisition costs are classified as current or noncurrent assets based on when the expense will be recognized. The current and noncurrent portions of contract acquisition costs are included in Prepaid expenses and other current assets, and Other assets, respectively. As of March 31, 2019, we had $17.7 million of current contract acquisition costs and $27.8 million of noncurrent contract acquisition costs. Commission expense is primarily included in Sales and marketing expense on the condensed consolidated statements of operations. We had amortization expense of $3.7 million related to contract acquisition costs for the three months ended March 31, 2019 and $7.2 million for the six months ended March 31, 2019. There was no impairment related to commission costs capitalized.
Contract Fulfillment Costs
We capitalize the setup costs incurred to satisfy our stand-ready obligation to provide access to our hosting service. Contract fulfillment costs are expensed to cost of revenue as we satisfy our stand-ready obligation over the contract term which we estimate to be between one and five years. The contract term was determined based on an average customer contract term, expected contract renewals, changes in technology, and our ability to retain customers including canceled contracts. We classify contract fulfillment costs as current or noncurrent based on the timing of when we expect to recognize the expense. The current and noncurrent portions of capitalized contract fulfillment costs are included in Prepaid expenses and other current assets, and Other assets, respectively. At March 31, 2019, we had $13.4 million of short-term contract fulfillment costs included with Prepaid expenses and other current assets and $96.2 million of long-term costs included within Other assets.
Trade Accounts Receivable and Contract Balances
We classify our right to consideration in exchange for deliverables as either a receivable or a contract asset. A receivable is a right to consideration that is unconditional (i.e. only the passage of time is required before payment is due). We present such receivables in Accounts receivable, net in our condensed consolidated balance sheets at their net estimated realizable value. We maintain an allowance for doubtful accounts to provide for the estimated amount of receivables that may not be collected. The allowance is based upon an assessment of customer creditworthiness, historical payment experience, the age of outstanding receivables and other applicable factors.
Our contract assets and liabilities are reported in a net position on a contract-by-contract basis at the end of each reporting period.
Contract assets include unbilled amounts from long-term contracts when revenue recognized exceeds the amount billed to the customer, and right to payment is not solely subject to the passage of time. The current and noncurrent portions of contract assets are included in Prepaid expenses and other current assets and Other assets. As of March 31, 2019, we had $59.8 million of current contract assets and $100.8 million of noncurrent contract assets. The table below shows significant changes in contract assets of continuing operations (dollars in thousands):
 
Contract assets
Balance as of October 1, 2018
$
168,595

    Revenues recognized but not billed
156,541

    Amounts reclassified to accounts receivable
(164,483
)
Balance at March 31, 2019
$
160,653


Our contract liabilities, or deferred revenue, consist of advance payments and billings in excess of revenues recognized. We classify deferred revenue as current or noncurrent based on when we expect to recognize the revenues. At March 31, 2019, we had $715.2 million of deferred revenue. The table below shows significant changes in deferred revenue of continuing operations (dollars in thousands):
 
Deferred revenue
Balance as of October 1, 2018
$
693,272

    Amounts bill but not recognized
506,225

    Revenue recognized
(484,314
)
Balance at March 31, 2019
$
715,183


Remaining Performance Obligations
The following table includes estimated revenue expected to be recognized in the future related to performance obligations that are unsatisfied or partially unsatisfied at March 31, 2019 (dollars in thousands):
 
Within One Year
 
Two to Five Years
 
Greater than Five years
 
Total
Total revenue
$
748,526

 
$
1,138,447

 
$
112,907

 
$
1,999,880

The table above includes fixed backlogs and does not include variable backlog derived from continent usage-based activities, such as royalties and usage-based hosting revenue.