Revenue from Contracts with Customers | 7. Revenue from Contracts with Customers Our two primary revenue streams are (i) software delivery, support and maintenance and (ii) client services. Software delivery revenue consists of all of our proprietary software sales (either as a perpetual or term license delivery model), transaction-related revenue and the resale of hardware and third-party software. Support and maintenance revenue consists of revenue from post contract client support and maintenance services, which includes telephone support services, maintaining and upgrading software and ongoing enhanced maintenance. Client services revenue consists of revenue from managed services solutions, such as private cloud hosting, outsourcing and revenue cycle management, as well as other client services or project-based revenue from implementation, training and consulting services. In addition, for some clients, we host the software applications licensed from us using our own or third-party servers. For other clients, we offer an outsourced service in which we assume partial to total responsibility for a healthcare organization’s IT operations using our employees. Adoption of New Revenue Standard In May 2014, the FASB issued ASC 606 to supersede nearly all existing revenue recognition guidance under GAAP. The core principle of ASC 606 is to recognize revenue when promised goods or services are transferred to customers in an amount that reflects the consideration that is expected to be received for those goods or services. ASC 606 defines a five-step process to achieve this principle and, in doing so, it is possible more judgment and estimates may be required within the revenue recognition process than required under the previous ASC 605, Revenue Recognition The new revenue recognition guidance permits two methods of adoption: retrospectively to each prior reporting period presented (full retrospective method), or retrospectively with the cumulative effect of initially applying the guidance recognized at the date of initial application (modified retrospective method). We have adopted the standard effective on January 1, 2018 using the modified retrospective method. We also implemented internal controls and updated our processes and key systems to allow us to comply with the new requirements. The reported results for the three months ended March 31, 2018 reflect the adoption of ASC 606. The comparative information for the three months ended March 31, 2017 has not been restated and will continue to be reported under the previous guidance of ASC 605, which was in effect during that period. The following adjustments were made to balances previously reported on the condensed consolidated balance sheet as of December 31, 2017: As Reported Adjustments Adjusted (In thousands, except per share amounts) December 31, 2017 due to ASC 606 January 1, 2018 Accounts receivable, net $ 567,873 $ (32,529 ) $ 535,344 Contract assets 0 76,509 76,509 Prepaid expenses and other current assets 115,463 11,646 127,109 Deferred revenue, current 546,830 (7,453 ) 539,377 Deferred revenue, long-term 24,047 0 24,047 Deferred taxes, net 93,643 16,478 110,121 Accumulated deficit (338,150 ) 46,601 (291,549 ) The adoption of ASC 606 had no impact on cash from or used in operating, financing or investing activities reported in our consolidated statement of cash flows for the year ended December 31, 2017. The following tables compare the reported consolidated balance sheet and statement of operations as of and for the three months ended March 31, 2018, to the pro-forma amounts assuming the previous guidance of ASC 605 had been in effect: March 31, 2018 (In thousands, except per share amounts) As reported under ASC 606 Adjustments due to ASC 606 Pro forma under ASC 605 Accounts receivable, net $ 495,695 $ 78,302 $ 573,997 Contract assets 45,068 (45,068 ) 0 Prepaid expenses and other current assets 130,051 33 130,084 Contract assets - long-term 40,486 (40,486 ) 0 Deferred revenue, current 540,289 (972 ) 539,317 Deferred taxes, net 117,061 (1,629 ) 115,432 Accumulated deficit (319,271 ) (4,618 ) (323,889 ) Three Months Ended March 31, 2018 (In thousands, except per share amounts) As reported under ASC 606 Adjustments due to ASC 606 Pro forma under ASC 605 Software delivery, support and maintenance $ 329,766 $ (5,028 ) $ 324,738 Client services 184,160 (1,066 ) 183,094 Gross profit 220,975 (6,279 ) 214,696 Selling, general and administrative expenses 143,070 (218 ) 142,852 Loss from operations (4,320 ) (6,061 ) (10,381 ) Loss from continuing operations before income taxes (35,844 ) (6,247 ) (42,091 ) Income tax benefit 2,914 1,629 4,543 Net loss (28,515 ) (4,618 ) (33,133 ) Net loss attributable to Allscripts Healthcare Solutions, Inc. stockholders $ (39,874 ) (4,618 ) $ (44,492 ) Loss per share - basic attributable to Allscripts Healthcare Solutions, Inc. stockholders $ (0.22 ) (0.03 ) $ (0.25 ) Loss per share - diluted attributable to Allscripts Healthcare Solutions, Inc. stockholders $ (0.22 ) (0.03 ) $ (0.25 ) The recognition of revenue related to hardware sales, software-as-a-service-based offerings, client services, electronic data interchange services, and managed services remained substantially unchanged under ASC 606. The adoption of ASC 606 resulted in an increase in contract assets driven by upfront recognition of revenue, rather than over the subscription period, from certain multi-year software subscription contracts that include both software licenses and software support and maintenance. Costs to Obtain or Fulfill a Contract Under ASC 605, we only capitalized direct sales commissions that were specifically associated with new or renewal contracts. The new revenue recognition guidance under ASC 606 requires the capitalization of all incremental costs of obtaining a contract with a customer that an entity expects to recover. As part of our implementation efforts, we identified certain indirect commissions and other payments that would be eligible for capitalization under ASC 606 as they are incremental costs solely associated with new or renewal contracts that we expect to recover. Certain costs related to the fulfillment of contracts will also be capitalized. As a result, we recorded a deferral for such costs of $8.6 million, net of tax, upon adoption of the new guidance on January 1, 2018, which was included in the cumulative effect of initially applying ASC 606. Capitalized costs to obtain or fulfill a contract are amortized over periods ranging from two to nine years which represent the contract term or a longer period, if renewals are expected and the renewal commission, if any, is not commensurate with the initial commission. We classify such capitalized costs as current or non-current based on the expected timing of expense recognition. The current and non-current portion are included in prepaid expenses and other current assets, and other assets, respectively, in our consolidated balance sheets. At March 31, 2018, we had $27.4 million of capitalized costs to obtain or fulfill a contract. During the three months ended March 31, 2018, we recognized $8.2 million of amortization expense related to such capitalized costs, of which $8.1 million is included in selling, general and administrative expenses and $0.1 million is included in cost of revenue, in our consolidated statements of operations. Contract Balances The timing of revenue recognition, billings and cash collections results in billed and unbilled accounts receivables, contract assets and customer advances and deposits. Accounts receivable, net includes both billed and unbilled amounts where the right to receive payment is unconditional and only subject to the passage of time. Contract assets include amounts where revenue recognized exceeds the amount billed to the customer and the right to payment is not solely subject to the passage of time. Deferred revenue includes advanced payments and billings in excess of revenue recognized. Our contract assets and deferred revenue are reported in a net position on an individual contract basis at the end of each reporting period. Contract assets are classified as current or long-term based on the timing of when we expect to complete the related performance obligations and bill the customer. Deferred revenue is classified as current or long-term based on the timing of when we expect to recognize revenue. In general, with the exception of fixed fee project-based client service offerings (such as implementation services), we sell our software solutions on date-based milestone events where control transfers and use of the software occurs on the delivery date but the associated payments for the software license occur on future milestone dates. In such instances, unbilled amounts are included in contract assets since our right to receive payment is conditional upon the continued functionality of the software and the provision of ongoing support and maintenance. Our fixed fee project-based client service offerings typically require us to provide the services with either a significant portion or all amounts due prior to service completion. Since our right to payment is not unconditional, amounts associated with work prior to the completion date are also deemed to be contract assets. Performance Obligations A performance obligation is a promise in a contract to transfer a distinct product or service to a customer and is the unit of account in ASC 606. A performance obligation is considered distinct when both (i) a customer can benefit from the product or service either on its own or together with other resources that are readily available to the customer and (ii) the promised product or service is separately identifiable from other promises in the contract. Activities related to the fulfillment of a contract that do not transfer products or services to a customer, such as contract preparation or legal review of contract terms, are not deemed to be performance obligations. Based on the similarities in the definitions of a “deliverable” under ASC 605 and “performance obligation” under ASC 606, our identification of performance obligations did not result in a significant divergence from our existing identification approach. We generally sell our solutions through multi-element arrangements where we provide the customer with (1) software license, (2) support and maintenance, (3) embedded content such as third-party software and (4) client services. Incremental solutions, such as hardware and managed services are also provided based upon a customer’s preferences and requirements. We deem that a customer is typically able to benefit from a product or service on its own or together with readily available resources when we sell such product or service on a standalone basis. We have historically sold the majority of our performance obligations with the exception of software licenses, on a standalone basis. Incremental solutions, such as hardware, client services and managed services, are often negotiated and fulfilled on an independent sales order basis as customer needs and requirements grow over the course of a relationship period. In addition, support and maintenance and embedded content are provided on a stand-alone basis through the renewal process. One of the product offerings under our CareInMotion TM Additionally, our support and maintenance obligations include multiple discrete performance obligations, with the two largest being unspecified product upgrades or enhancements, and technical support, which can be offered at various points during a contract period. We believe that the multiple discrete performance obligations within our overall support and maintenance obligations can be viewed as a single performance obligation since both the unspecified upgrades and technical support are activities to fulfill the maintenance performance obligation and are rendered concurrently. Generally, we do not provide additional warranties to clients above and beyond warranties that the solutions purchased will perform in accordance with the agreed-upon specifications. On rare occasions, when additional warranties are granted, we evaluate on a case-by-case basis whether the additional warranty represents a separate performance obligation. The breakdown of revenue recognized related to various performance obligations and elected accounting expedients is presented in the table below: (In thousands) Three Months Ended March 31, 2018 Revenue related to deferred revenue balance at beginning of period $ 204,297 Revenue related to new performance obligations satisfied during the period 257,222 Revenue recognized under "right-to-invoice" expedient 49,638 Reimbursed travel expenses, shipping and other revenue 2,769 Total revenue $ 513,926 The aggregate amount of contract transaction price related to remaining unsatisfied performance obligations (commonly referred to as “backlog”) represents contracted revenue that has not yet been recognized and includes both deferred revenue and amounts that will be invoiced and recognized as revenue in future periods. Total backlog equaled $4.7 billion as of March 31, 2018, of which we expect to recognize approximately 36% over the next 12 months, and the remaining 64% thereafter. Accounting Policy Elections and Practical Expedients The majority of our contracts contain provisions that require customer payment no later than one year from the transfer of control of the related performance obligation. Perpetual software license contracts in which payments range from 2 to 10 years contain a financing component. Interest income is recognized in these circumstances and totaled $0.2 million during the three months ended March 31, 2018. We have elected to exclude from the measurement of the transaction price all taxes (e.g. sales, use, value-added, etc.) assessed by government authorities and collected from a customer. Therefore, revenue is recognized net of such taxes. Within the normal course of business, we contract with customers to deliver and ship tangible products such as computer hardware or licensed software disks. In these situations, the control of the products transfers to the customer when the product reaches the shipper based on free on board (FOB) shipping clauses. We have elected to use the practical expedient allowed under ASC 606 to account for shipping and handling activities that occur after the customer has obtained control of a promised good as fulfillment costs rather than as an additional promised service and, therefore, we do not allocate a portion of the transaction price to a shipping service obligation. Instead, we record as revenue any amounts billed to customers for shipping and handling costs and record as cost of revenue the actual shipping costs incurred. Additionally, our standard contract terms allow for the reimbursement by the customer for certain travel expenses necessary to provide on-site services to customer, such as implementation and training. Such reimbursed travel expenses are reported on a gross basis. Since such reimbursed travel expenses do not represent a distinct good or service nor represent incremental value provided to the customer, a performance obligation is deemed not to exist. In certain situations, however, when the allowable reimbursable expenses amount is capped, we believe that such cap represents the most likely amount of variable consideration and the capped amount is included in the total contract transaction price. In accordance with ASC 606, if an entity has a right to consideration from a customer in an amount that corresponds directly with the value to the customer of the entity’s performance completed to date, the entity may recognize revenue in the amount to which the entity has a right to invoice (“right-to-invoice” practical expedient). We have elected to utilize this expedient as it relates to transaction-based services (such as revenue cycle management) and electronic data interchange transactions. Revenue Recognition We recognize revenue only when we satisfy an identified performance obligation (or bundle of obligations) by transferring control of a promised product or service to a customer. We consider a product or service to be transferred when a customer obtains control because a customer has sole possession of the right to use (or the right to direct the use of) the product or service for the remainder of its economic life or to consume the product or service in its own operations. We evaluate the transfer of control primarily from the customer’s perspective as this reduces the risk that revenue is recognized for activities that do not transfer control to the customer. The majority of our revenue is recognized over time because a customer continuously and simultaneously receives and consumes the benefits of our performance. The exceptions to this pattern are our sales of perpetual and term software licenses, and hardware where we determined that a customer obtains control of the asset upon delivery, shipment or granting of access. The following table summarizes the pattern of revenue recognition for our most significant performance obligations: Performance Obligation Revenue Recognition Pattern Measure of progress Support and maintenance (SMA) Over time Output method (time elapsed) – revenue is recognized ratably over the contract term Software as a service (SaaS) Over time Output method (time elapsed) – revenue is recognized ratably over the contract term Private Cloud Hosting Over time Output method (time elapsed) – revenue is recognized ratably over the contract term Client/Education Services Over time Input method (cost to cost) – revenue is recognized proportionally over the service implementation based on hours Outsourcing services Over time Input method (cost to cost) – revenue is recognized proportionally over the outsourcing period Payerpath (transaction volume) Over time Output method ("right-to-invoice" practical expedient) – value transferred to the customer is reflected on invoicing. Software Licenses Point in time Upon shipment or electronically delivered, as applicable Hardware Point in time Upon shipment When evaluating our SMA, SaaS and private cloud hosting performance obligations, we noted that these obligations are fulfilled as stand-ready obligations to perform and, therefore, we deem the obligations to be satisfied evenly over time. Client services, such as those relating to implementation, consulting, training or education, are generally not fulfilled evenly over the contract period but rather over a shorter timeline where work effort can rise, or decline based upon stages of the project work effort. These client services are typically quoted to a customer as a fixed fee amount that covers the implementation effort. Delivery progress for these services is measured by establishing an approved cost budget with labor hour inputs utilized to gauge percentage of completion of the work effort. Therefore, revenue for our client, education and outsourcing services is recognized proportionally with the progress of the implementation work effort. Payerpath transaction volume and other transaction-based service obligations, such as revenue cycle management services, are fulfilled over time but are not provided evenly over the contract period and reliable inputs are not available to track progress of completion. We determined that value is provided to the customer throughout the contract period and the pricing charged to the customer varies on a monthly basis, based upon the volume of the customer’s transactions processed in that respective period. The invoiced amount to the customer represents this value and accordingly the practical expedient to recognize revenue based upon invoicing is most appropriate. We considered the specific implementation guidance for accounting for licenses of intellectual property (“IP”) to determine if point in time or over time recognition was more appropriate. The first step in the licensing framework is to determine whether the license is distinct or combined with other goods and services. For most of our software licensing products, the licenses are distinct, with the exception of one of our product offerings under our CareInMotion TM Disaggregation of Revenue We disaggregate our revenue from contracts with customers based on the type of revenue and nature of revenue stream, as we believe those categories best depict how the nature, amount, timing and uncertainty of our revenue and cash flows are affected by economic factors. The below tables summarize revenue by type and nature of revenue stream as well as by our reportable segments: Three Months Ended March 31, (In thousands) 2018 2017 Revenue: Software delivery, support and maintenance Recurring revenue $ 294,455 $ 227,450 Non-recurring revenue 35,311 40,738 Total software delivery, support and maintenance 329,766 268,188 Client services Recurring revenue $ 122,474 $ 101,779 Non-recurring revenue 61,686 43,508 Total client services 184,160 145,287 Total revenue $ 513,926 $ 413,475 Three Months Ended March 31, 2018 (In thousands) Clinical and Financial Solutions Population Health Netsmart Unallocated Discontinued Operations Total Software delivery, support and maintenance $ 230,557 $ 61,198 $ 49,245 $ 1,165 $ (12,399 ) $ 329,766 Client services 143,422 8,507 33,241 (3,113 ) 2,103 184,160 Total revenue $ 373,979 $ 69,705 $ 82,486 $ (1,948 ) $ (10,296 ) $ 513,926 Three Months Ended March 31, 2017 (In thousands) Clinical and Financial Solutions Population Health Netsmart Unallocated Discontinued Operations Total Software delivery, support and maintenance $ 178,330 $ 39,689 $ 46,496 $ 3,673 $ 0 $ 268,188 Client services 117,850 3,741 26,511 (2,815 ) 0 145,287 Total revenue $ 296,180 $ 43,430 $ 73,007 $ 858 $ 0 $ 413,475 |