Revenue from Contracts with Customers | Revenue from Contracts with Customers Adoption of ASC 606, Revenue from Contracts with Customers The Company adopted ASC 606 on January 1, 2018 using the modified retrospective approach for all contracts not completed as of the date of adoption. Results for reporting periods beginning after January 1, 2018 are presented under ASC 606, while prior period amounts are not adjusted and continue to be reported in accordance with ASC 605, Revenue Recognition (ASC 605). The adoption of ASC 606 represents a change in accounting principle that will more closely align revenue recognition with the delivery of the Company’s software licenses, maintenance and services. ASC 606 requires an entity to evaluate revenue recognition by identifying a contract with a customer, identifying the performance obligations in the contract, determining the transaction price, allocating the transaction price to the performance obligations in the contract, and recognizing revenue when (or as) the entity satisfies a performance obligation. The Company recorded an increase to retained earnings of $242.4 million , or $183.1 million net of tax, on January 1, 2018 due to the cumulative effect of the ASC 606 adoption, with the impact primarily derived from revenue related to time-based software lease licenses. Revenue Recognition Revenue is derived principally from the licensing of computer software products and from related maintenance contracts. The Company enters into contracts that include combinations of products, maintenance and services, which are accounted for as separate performance obligations with differing revenue recognition patterns. Revenue from perpetual licenses is classified as software license revenue. Software license revenue is recognized up front upon delivery of the licensed product and the utility that enables the customer to access authorization keys, provided that a signed contract has been received. Typically, the Company’s perpetual licenses are sold with post-contract support (PCS), which includes unspecified technical enhancements and customer support. The Company allocates value in bundled perpetual and PCS arrangements based on the standalone selling prices of the perpetual license and PCS. Revenue from PCS is classified as maintenance revenue and is recognized ratably over the term of the contract, as the Company satisfies the PCS performance obligation over time. In addition to perpetual licenses, the Company sells time-based lease licenses. Lease licenses are sold only as a bundled arrangement that includes the rights to a term software license and PCS. Maximizing the use of observable inputs, the Company determined that 50% of the estimated standalone selling price of the lease license is attributable to the term license and 50% is attributable to the PCS. Consistent with the perpetual sales, the license component is classified as software license revenue and recognized as revenue up front at the commencement of the lease. The PCS is classified as maintenance revenue and is recognized ratably over the term of the contract, as the Company provides the PCS benefit over time. Revenue from training, support and other services is recognized as the services are performed. For contracts in which the service consists of a single performance obligation, such as providing a training class to a customer, the Company recognizes revenue upon completion of the performance obligation. For service contracts that are longer in duration and often include multiple performance obligations (for example, both training and consulting), the Company measures the progress toward completion of the obligations and recognizes revenue accordingly. In measuring the progress towards completion of performance obligations, the Company typically utilizes output-based estimates for services with contractual billing arrangements that are not based on time and materials, and estimates output based on the total tasks completed as compared to the total tasks required for each work contract. Input-based estimates are utilized for services that involve general consultations with contractual billing arrangements based on time and materials, utilizing direct labor as the input measure. The Company also executes arrangements through independent channel partners in which the channel partners are authorized to market and distribute the Company's software products to end users of the Company's products and services in specified territories. In sales facilitated by channel partners, the channel partner bears the risk of collection from the end-user customer. The Company recognizes revenue from transactions with channel partners when the channel partner submits a purchase commitment, collectability from the channel partner is probable, a license agreement signed by the end-user customer is received and the performance obligation was met, at a point in time or over time as appropriate, provided that all other revenue recognition criteria are satisfied. Revenue from channel partner transactions is the amount remitted to the Company by the channel partners. This amount includes a fee for PCS that is compensation for providing technical enhancements and the second level of technical support to the end user, which is recognized over the period that PCS is to be provided. The Company does not offer right of return, product rotation or price protection to any of its channel partners. Non-income related taxes collected from customers and remitted to governmental authorities are recorded on the condensed consolidated balance sheet as accounts receivable and accrued expenses. The collection and payment of these amounts are reported on a net basis in the condensed consolidated statements of income and do not impact reported revenues or expenses. The Company warrants to its customers that its software will substantially perform as specified in the Company's current user manuals. The Company has not experienced significant claims related to software warranties beyond the scope of maintenance support, which the Company is already obligated to provide. The warranty is not sold, and cannot be purchased, separately. The warranty does not provide any type of additional service to the customer or performance obligation for the Company. Significant Judgments The Company’s contracts with customers typically include promises to transfer licenses and services to a customer. Judgment is required to determine if the promises are separate performance obligations, and if so, the allocation of the transaction price to each performance obligation. The Company uses the estimated standalone selling price method to allocate the transaction price for items that are not sold separately, particularly lease licenses sold with PCS. The estimated standalone selling price is determined using all information reasonably available to the Company, including market conditions and other observable inputs. The corresponding revenues are recognized as the related performance obligations are satisfied. The Company applies a practical expedient to expense sales commissions as incurred when the amortization period would have been one year or less. Certain sales commissions associated with multi-year contracts are subject to an employee service requirement. As an action other than each party approving the contract is required to trigger these sales commissions, they are not considered incremental costs to obtain a contract and are expensed as incurred. The Company is required to adjust promised amounts of consideration for the effects of the time value of money if the timing of the payments provides the customer or the Company with a significant financing benefit. The Company considers various factors in assessing whether a financing component exists, including the duration of the contract, market interest rates and the timing of payments. The Company’s contracts do not include a significant financing component requiring adjustment to the transaction price. Impact of ASC 606 on Condensed Consolidated Financial Statement Line Items The following tables compare the reported condensed consolidated balance sheet and statement of income, as of and for the three months ended March 31, 2018, to the amounts had ASC 605 been in effect: Condensed Consolidated Balance Sheet As of March 31, 2018 (in thousands) As Reported (ASC 606) ASC 605 Change Accounts receivable, less allowance for doubtful accounts of $6,800 $ 256,560 $ 113,585 $ 142,975 Other receivables and current assets 181,001 269,175 (88,174 ) Deferred income tax assets 15,446 38,641 (23,195 ) Accrued income taxes 4,870 3,681 1,189 Other accrued expenses and liabilities 95,053 101,165 (6,112 ) Deferred revenue - current 311,718 471,676 (159,958 ) Deferred income tax liabilities 28,849 4,878 23,971 Other long-term liabilities 80,865 94,060 (13,195 ) Stockholders' equity 2,407,360 2,221,649 185,711 The Company recorded $244.1 million of deferred revenue to retained earnings upon the adoption of ASC 606 on January 1, 2018. The pattern of software lease license revenue recognition has changed under ASC 606. Software lease license revenue was recognized ratably over the term of the contract under the previous guidance; however, 50% of the contract is recognized up front at the commencement of the lease under ASC 606. This change in the pattern of revenue recognition, coupled with the recording of deferred revenue to retained earnings at the adoption date, resulted in the changes to the condensed consolidated balance sheet line items as noted in the table above. Condensed Consolidated Statement of Income Three Months Ended March 31, 2018 (in thousands, except per share data) As Reported (ASC 606) ASC 605 Change Revenue: Software licenses $ 110,046 $ 154,857 $ (44,811 ) Maintenance and service 172,827 129,712 43,115 Cost of sales: Software licenses 3,911 8,146 (4,235 ) Maintenance and service 26,341 22,106 4,235 Income tax provision 12,758 12,981 (223 ) Earnings per share: Basic $ 1.00 $ 1.02 $ (0.02 ) Diluted $ 0.98 $ 1.00 $ (0.02 ) The impacts to reported software licenses revenue and maintenance and service revenue were primarily due to the PCS portion of lease license contracts now being allocated to maintenance and service revenue under ASC 606. Under the previous guidance, this revenue was reported as software licenses revenue. The decrease to software licenses revenue was partially offset by the upfront recognition of lease license revenue, which would have been recognized ratably over the contract under prior guidance. Consistent with the change in revenue, there was a corresponding reclassification within cost of sales. Costs incurred related to the PCS portion of lease license contracts were reflected in cost of maintenance and service. Under the previous guidance, such costs were reflected within cost of software licenses. The adoption of ASC 606 had no impact on the Company’s cash flows from operations. However, with the adoption of ASC 606, there will be an acceleration of income tax payments associated with deferred revenue and backlog credited to retained earnings and never recognized as revenue in the financial statements. The 2018 tax payments related to the adoption of ASC 606 are expected to be $12.0 million - $15.0 million . Disaggregation of Revenue The following table summarizes revenue: Three Months Ended March 31, (in thousands) 2018 (ASC 606) 2018 (ASC 605) 2017 (ASC 605) Revenue: Lease licenses $ 48,772 $ 101,789 $ 93,634 Perpetual licenses 61,274 53,068 48,274 Software licenses 110,046 154,857 141,908 Maintenance 163,896 120,762 104,406 Service 8,931 8,950 7,091 Maintenance and service 172,827 129,712 111,497 Total revenue $ 282,873 $ 284,569 $ 253,405 The Company’s software licenses revenue is recognized up front, while maintenance and service revenue is generally recognized over the term of the contract. Under ASC 606, the Company derived 23.5% of its total revenue through the indirect sales channel for the three months ended March 31, 2018. Under ASC 605, the Company derived 22.9% and 24.4% of its total revenue through the indirect sales channel for the three months ended March 31, 2018 and 2017, respectively. Deferred Revenue Deferred revenue consists of billings made or payments received in advance of revenue recognition from software license and maintenance agreements. The timing of revenue recognition may differ from the timing of billings to customers. Payment terms vary by the type and location of customer and the products or services offered. The term between invoicing and when payment is due is not significant. The changes in deferred revenue, inclusive of both current and long-term, are as follows: (in thousands) Three Months Ended March 31, 2018 Beginning balance – January 1 $ 299,730 Recognition of deferred revenue (282,873 ) Deferral of revenue 307,978 Currency translation 4,559 Ending balance – March 31 $ 329,394 Revenue recognized during the three months ended March 31, 2018 from amounts included in deferred revenue at the beginning of the period was $145.8 million . Revenue allocated to remaining performance obligations represents contracted revenue that has not yet been recognized, which includes deferred revenue and backlog. The Company's backlog represents installment billings for periods beyond the current quarterly billing cycle and customer orders received but not processed. Total revenue allocated to remaining performance obligations was $595.0 million as of March 31, 2018 and will be recognized as revenue as follows: (in thousands) Next 12 months $ 438,650 Months 13-24 112,580 Months 25-36 40,016 Thereafter 3,763 Total revenue allocated to remaining performance obligations $ 595,009 |