UNITED STATES

SECURITIES AND EXCHANGE COMMISSION

Washington, D.C. 20549

 

FORM 10-Q

 

For the quarterly period ended June 30, 2018

OR

Commission file number 001-35547

 

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

(Exact Name of Registrant as Specified in Its Charter)

 

 

222 Merchandise Mart, Suite 2024

Chicago, IL 60654

(Address of Principal Executive Offices, Zip Code)

(312) 506-1200

(Registrant's Telephone Number, Including Area Code)

 

Indicate by check mark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days.     Yes   ☒     No   ☐

Indicate by check mark whether the registrant has submitted electronically and posted on its corporate Web site, if any, every Interactive Data File required to be submitted and posted pursuant to Rule 405 of Regulation S-T (§232.405 of this chapter) during the preceding 12 months (or for such shorter period that the registrant was required to submit and post such files).      Yes   ☒     No   ☐

Indicate by check mark whether the registrant is a large accelerated filer, an accelerated filer, a non-accelerated filer, smaller reporting company or an emerging growth company. See the definitions of “large accelerated filer,” “accelerated filer,” “smaller reporting company,” and “emerging growth company” in Rule 12b-2 of the Exchange Act. (Check one):

 

If an emerging growth company, indicate by check mark if the registrant has elected not to use the extended transition period for complying with any new or revised financial accounting standards provided pursuant to Section 13(a) of the Exchange Act.     ☐ 

Indicate by check mark whether the registrant is a shell company (as defined in Rule 12b-2 of the Exchange Act).      Yes   ☐     No   ☒

As of August 3, 2018, there were 174,609,840 shares of the registrant's $0.01 par value common stock outstanding.

 

 

---

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

FORM 10-Q

For the Fiscal Quarter Ended June 30, 2018

TABLE OF CONTENTS

 

 

2

---

PART I. FINANCIAL INFORMATION

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

CONSOLIDATED BALANCE SHEETS

(Unaudited)

 

 

3

---

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

CONSOLIDATED BALANCE SHEETS (CONTINUED)

(Unaudited)

 

 

The accompanying notes are an integral part of these consolidated financial statements.

4

---

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

CONSOLIDATED STATEMENTS OF OPERATIONS

(Unaudited)

 

 

The accompanying notes are an integral part of these consolidated financial statements.

5

---

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

CONSOLIDATED STATEMENTS OF COMPREHENSIVE INCOME (LOSS)

(Unaudited)

 

 

 

The accompanying notes are an integral part of these consolidated financial statements.

6

---

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

CONSOLIDATED STATEMENTS OF CASH FLOWS

(Unaudited)

 

 

The accompanying notes are an integral part of these consolidated financial statements.

7

---

ALLSCRIPTS HEALTHCARE SOLUTIONS, INC.

NOTES TO CONSOLIDATED FINANCIAL STATEMENTS

(Unaudited)

 

 

1. Basis of Presentation and Significant Accounting Policies

Principles of Consolidation

The consolidated financial statements include the accounts of Allscripts Healthcare Solutions, Inc. (“Allscripts”) and its wholly-owned subsidiaries and controlled affiliates. All significant intercompany balances and transactions have been eliminated. Each of the terms “we,” “us,” “our” or the “Company” as used herein refers collectively to Allscripts Healthcare Solutions, Inc. and its wholly-owned subsidiaries and controlled affiliates, unless otherwise stated.

Unaudited Interim Financial Information

The unaudited interim consolidated financial statements as of and for the three and six months ended June 30, 2018 and 2017 have been prepared in accordance with the rules and regulations of the Securities and Exchange Commission (the “SEC”) for interim financial reporting. These interim consolidated financial statements are unaudited and, in the opinion of our management, include all adjustments, consisting of normal recurring adjustments and accruals, necessary to present fairly the consolidated financial statements for the periods presented in accordance with generally accepted accounting principles in the United States of America (“GAAP”). The consolidated results of operations for the three and six months ended June 30, 2018 are not necessarily indicative of the results to be expected for the full year ending December 31, 2018.

Certain information and footnote disclosures normally included in annual financial statements prepared in accordance with GAAP have been condensed or omitted in accordance with the SEC's rules and regulations for interim reporting, although the Company believes that the disclosures made are adequate to make that information not misleading. These unaudited interim consolidated financial statements should be read in conjunction with the consolidated financial statements and related notes included in our Annual Report on Form 10-K for the year ended December 31, 2017 (our “Form 10-K”).

Use of Estimates

The preparation of consolidated financial statements in accordance with GAAP requires us to make estimates and assumptions that affect the amounts reported and disclosed in the consolidated financial statements and the accompanying notes. Actual results could differ materially from these estimates.

Change in Presentation

During the first quarter of 2018, we changed the presentation of certain bundled revenue streams.  Such revenue was previously included as part of software delivery, support and maintenance revenue.  Under the new presentation, such revenue is included as part of client services revenue.  The revenues previously reported for the three and six months ended June 30, 2017 have been recast to match the new presentation by reducing software delivery, support and maintenance and increasing client services by $4.2 million and $8.5 million, respectively.

Significant Accounting Policies

We adopted Financial Accounting Standards Board (“FASB”) Accounting Standards Update No. 2014-09, Revenue from Contracts with Customers: Topic 606 (“ASC 606”) effective on January 1, 2018 using the modified retrospective method for all contracts not completed as of the date of adoption. There have been no other significant changes to our significant accounting policies from those disclosed in our Form 10-K.

8

---

Recently Adopted Accounting Pronouncements

In January 2016, the FASB issued Accounting Standards Update No. 2016-01, “Recognition and Measurement of Financial Assets and Financial Liabilities” (“ASU 2016-01”). The amendments in ASU 2016-01 modify the requirements related to the measurement of certain financial instruments in the statement of financial condition and results of operation. Equity investments (except those accounted for under the equity method of accounting or those that result in consolidation of the investee) are required to be measured at fair value with changes in fair value recognized in net income. An entity may continue to elect to measure equity investments which do not have a readily determinable fair value at cost with adjustments for impairment, if any, and observable changes in price. In addition, for a liability (other than a derivative liability) that an entity measures at fair value, any change in fair value related to the instrument-specific credit risk (i.e., the entity’s own credit risk), should be presented separately in other comprehensive income and not as a component of net income. ASU 2016-01 also clarifies that an entity should evaluate the need for a valuation allowance on a deferred tax asset related to available-for sale securities in combination with the entity’s other deferred tax assets. ASU 2016-01 is effective for interim and annual periods beginning after December 15, 2017 with early adoption permitted   solely for the instrument-instrument specific credit risk for liabilities measured at fair value. The amendments should be applied by means of a cumulative-effect adjustment to the balance sheet as of the beginning of the fiscal year of adoption. The amendments related to equity securities without readily determinable fair values (including disclosure requirements) should be applied prospectively to equity investments that exist as of the date of adoption. We adopted ASU 2016-01 effective January 1, 2018 and there was no immediate impact upon adoption. Refer to Note 4, “Fair Value Measurements and Long-term Investments,” for additional information regarding our unconsolidated equity investments.

In January 2017, the FASB issued Accounting Standards Update No. 2017-01, Business Combinations (Topic 805): Clarifying the Definition of a Business (“ASU 2017-01”). ASU 2017-01 provides new accounting guidance to assist an entity in evaluating when a set of transferred assets and activities is a business.  The guidance is effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2017, and should be applied prospectively to any transactions occurring within the period of adoption. We adopted ASU 2017-01 effective January 1, 2018 and there was no immediate impact upon adoption.

Accounting Pronouncements Not Yet Adopted

In June 2018, the FASB issued Accounting Standards Update No. 2018-07, “Compensation-Stock Compensation (Topic 718): Improvements to Nonemployee Share-Based Payment Accounting” (“ASU 2018-07”), which expands the scope of Topic 718 to include share-based payment transactions for acquiring goods and services from nonemployees. ASU 2018-07 specifies that Topic 718 applies to all share-based payment transactions in which a grantor acquires goods or services to be used or consumed in its own operations by issuing share-based payment awards. ASU 2018-07 also clarifies that Topic 718 does not apply to share-based payments used to effectively provide (1) financing to the issuer or (2) awards granted in conjunction with selling goods or services to customers as part of a contract accounted for under ASC 606. ASU 2018-07 is effective for interim and annual periods beginning after December 15, 2018. We are currently evaluating the impact of this accounting guidance, including the timing of adoption.

In February 2016, the FASB issued Accounting Standards Update No. 2016-02, “Leases (Topic 842)” (“ASU 2016-02”), intended to improve financial reporting about leasing transactions. The new guidance will require entities that lease assets to recognize on their balance sheets the assets and liabilities for the rights and obligations created by those leases and to disclose key information about the leasing arrangements. ASU 2016-02 is effective for interim and annual periods beginning after December 15, 2018 with early adoption permitted. We are currently gathering lease data and have selected specific software to assist us in recording and maintaining an inventory of leases. We will adopt ASU 2016-02 on January 1, 2019 and we are currently evaluating its financial statement impact.

In January 2017, the FASB issued Accounting Standards Update No. 2017-04, Intangibles—Goodwill and Other (Topic 350): Simplifying the Test for Goodwill Impairment (“ASU 2017-04”), which provides new accounting guidance to simplify the accounting for goodwill impairment. ASU 2017-04 removes Step Two of the goodwill impairment test, which requires a hypothetical purchase price allocation. Under the new guidance, a goodwill impairment will equal the amount by which a reporting unit’s carrying value exceeds its fair value, not to exceed the carrying amount of goodwill assigned to the reporting unit. All other goodwill impairment guidance will remain largely unchanged. Entities will continue to have the option to perform a qualitative assessment to determine if a quantitative impairment test is necessary. ASU 2017-04 is effective for annual and interim periods in fiscal years beginning after December 15, 2019 with early adoption permitted for any goodwill impairment tests performed after January 1, 2017. The new guidance is to be applied prospectively. We are currently evaluating the impact of this accounting guidance, including the timing of adoption.

9

---

In August 2017, the FASB issued Accounting Standards Update No. 2017-12, Derivatives and Hedging (Topic 815): Targeted Improvements to Accounting for Hedging Activities (“ASU 2017-12”), which provides new accounting guidance to simplify and improve the reporting of hedging relationships to better portray the economic results of an entity’s risk management activities in its financial statements. In addition to that main objective, the amendments in this Update make certain targeted improvements to simplify the application of the hedge accounting guidance in current GAAP. ASU 2017-12 is effective for fiscal years beginning after December 15, 2018, and interim periods within those fiscal years. Early application is permitted in any interim period after the issuance of this Update. We are currently evaluating the impact of this accounting guidance, including the timing of adoption.

We do not believe that any other recently issued, but not yet effective accounting standards, if adopted, would have a material impact on our consolidated financial statements.

 

2. 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 under 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 include 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. 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 (ASC 606)

 

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 FASB Accounting Standards Codification 605, Revenue Recognition (“ASC 605”), including identifying performance obligations in the contract, estimating the amount of variable consideration to include in the transaction price and allocating the transaction price to each separate performance obligation.  Additionally, ASC 606 provides guidance related to costs of obtaining a contract with a customer that an entity expects to recover.

 

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 adopted the standard effective on January 1, 2018 using the modified retrospective method. We also implemented internal controls, and continue to refine, our updated processes and key systems to allow us to continue to comply with the new requirements.

 

The reported results for the three and six months ended June 30, 2018 reflect the adoption of ASC 606. The comparative information for the three and six months ended June 30, 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 table below reflects the cumulative adjustments that were made to balances previously reported in the condensed consolidated balance sheet as of December 31, 2017. The majority of the cumulative adjustments were recorded during the quarter ended March 31, 2018. During the quarter ended June 30, 2018, we identified additional cumulative adjustments, which resulted in an increase to retained earnings of $14.0 million, an increase to contract assets of $15.9 million, an increase to deferred taxes, net of $4.9 million and a decrease to deferred revenue of $3.0 million.  

 

10

---

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 condensed consolidated balance sheet and statement of operations as of and for the three and six months ended June 30, 2018 to the pro-forma amounts assuming the previous guidance of ASC 605 had been in effect:

 

 

 

 

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.

11

---

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 were eligible for capitalization under ASC 606 as they were incremental costs solely associated with new or renewal contracts that we expected 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 initial 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 portions are included in prepaid expenses and other current assets, and other assets, respectively, in our consolidated balance sheets.

 

At June 30, 2018, we had $26.5 million and $36.0 million of capitalized costs to obtain or fulfill a contract included in prepaid expenses and other current assets and other assets, respectively, in our consolidated balance sheets. During the three ended June 30, 2018, we recognized $7.6 million of amortization expense related to such capitalized costs, of which $7.5 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. During the six months ended June 30, 2018, we recognized $15.8 million of amortization expense related to such capitalized costs, of which $15.5 million is included in selling, general and administrative expenses and $0.3 million is included in cost of revenue in our consolidated statement 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 under ASC 606 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 change 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.

12

---

 

One of the product offerings under our CareInMotion^TM platform requires a significant client service customization to enable the functionality of the software before the customer can obtain benefit from using the product. The significant customization cannot be performed by a third party. Software products and client services are separately identifiable in these contracts, but the performance obligations are not considered distinct in the context of the contract. Therefore, these products and services are treated as combined performance obligations.  

 

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 product 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 granted represents a separate performance obligation.

The breakdown of revenue recognized related based on the origination of performance obligations and elected accounting expedients is presented in the table below:

 

 

           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.8 billion as of June 30, 2018, of which we expect to recognize approximately 38% over the next 12 months, and the remaining 62% 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.3 million and $0.5 million during the three and six months ended June 30, 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 a customer for certain travel expenses necessary to provide on-site services to the 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 a 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.

 

13

---

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:

 

 

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 platform, which requires a significant client service customization. In all instances, we determined that we are offering functional IP as compared with a symbolic IP. Functional IP is a right to use IP because the IP has standalone functionality and a customer can use the IP as it exists at a point in time.

 

14

---

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: