Basis of Presentation and Significant Accounting Policies | Basis of Presentation and Significant Accounting Policies The accompanying unaudited condensed consolidated financial statements of IHS Markit have been prepared on substantially the same basis as our annual consolidated financial statements and should be read in conjunction with our Annual Report on Form 10-K for the year ended November 30, 2018 . In our opinion, these condensed consolidated financial statements reflect all adjustments necessary for a fair presentation of the financial position, results of operations, and cash flows for the periods presented, and such adjustments are of a normal, recurring nature. Our business has seasonal aspects. Our first quarter generally has our lowest quarterly levels of revenue and profit. We also experience event-driven seasonality in our business; for instance, CERAWeek, an annual energy conference, is typically held in the second quarter of each year. Another example is the biennial release of the Boiler Pressure Vessel Code (“BPVC”) engineering standard, which generates revenue for us predominantly in the third quarter of every other year. The most recent BPVC release was in the third quarter of 2017. Revenue Recognition In May 2014, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) 2014-09, which establishes a comprehensive new revenue recognition model designed to depict the transfer of goods or services to a customer in an amount that reflects the consideration the entity expects to receive in exchange for those goods or services. In March, April, and May 2016, the FASB issued ASU 2016-08, ASU 2016-10, and ASU 2016-12, respectively, which provide further revenue recognition guidance related to principal versus agent considerations, performance obligations and licensing, and narrow-scope improvements and practical expedients. These standards have all been codified in the FASB’s Accounting Standards Codification (“ASC”) Topic 606, “Revenue from Contracts with Customers.” On December 1, 2018, we adopted ASC Topic 606 using the modified retrospective transition method applied to our customer revenue contracts as of the adoption date. Revenue results for periods beginning after December 1, 2018 are presented in accordance with ASC Topic 606, while prior year amounts continue to be reported in accordance with ASC Topic 605, “Revenue Recognition.” The following table shows the cumulative effect of the changes made to the December 1, 2018 consolidated balance sheet for the adoption of ASC Topic 606 related to contracts that were in effect at the time of adoption (in millions): November 30, 2018 Adjustments due to adoption of ASC Topic 606 December 1, 2018 Accounts receivable, net $ 792.9 $ 29.8 $ 822.7 Other current assets 88.4 4.2 92.6 Other non-current assets 47.9 9.5 57.4 Deferred revenue 886.8 (28.8 ) 858.0 Deferred income taxes 699.9 16.3 716.2 Retained earnings 2,743.1 56.0 2,799.1 The net cumulative effect adjustment to retained earnings was primarily related to 1) the change in accounting for the license rights associated with certain term-based software license arrangements, which were historically recognized over the term of the contract, but are now recognized at contract inception based on estimated stand-alone selling price, and 2) the change in accounting for commission costs incurred to obtain a portion of our contracts, which costs were historically expensed as incurred, but are now deferred at contract inception and recognized over the expected customer life. For the first quarter of 2019, the adoption of ASC Topic 606 did not result in a material difference between what we reported under ASC Topic 606 and what we would have reported under ASC Topic 605. We disaggregate our revenue by segment (as described in Note 11) and by transaction type according to the following categories: • Recurring fixed revenue represents revenue generated from contracts specifying a relatively fixed fee for services delivered over the life of the contract. The fixed fee is typically paid annually or more periodically in advance. These contracts typically consist of subscriptions to our various information offerings and software maintenance, which provide continuous access to our platforms and associated data over the contract term. The revenue is usually recognized ratably over the contract term or for term-based software license arrangements, annually on renewal. The initial term of these contracts is typically annual (with some longer-term arrangements) and non-cancellable for the term of the subscription and may contain provisions for minimum monthly payments. • Recurring variable revenue represents revenue from contracts that specify a fee for services, which is typically not fixed. The variable fee is usually paid monthly in arrears. Recurring variable revenue is based on, among other factors, the number of trades processed, assets under management, or the number of positions we value, and revenue is recognized based on the specific factor used (e.g., for usage-based contracts, we recognize revenue in line with usage in the period). Many of these contracts do not have a maturity date, while the remainder have an initial term ranging from one to five years. Recurring variable revenue was derived entirely from the Financial Services segment for all periods presented. • Non-recurring revenue represents consulting (e.g., research and analysis, modeling, and forecasting), services, single-document product sales, perpetual license sales and associated services, conferences and events, and advertising. Revenue for services and other non-recurring revenue is recognized upon completion of the associated performance obligation. The following table presents our revenue by transaction type (in millions): Three months ended February 28, 2019 2018 Recurring fixed revenue $ 767.2 $ 683.3 Recurring variable revenue 136.0 117.1 Non-recurring revenue 143.2 131.7 Total revenue $ 1,046.4 $ 932.1 Our customer contracts may include multiple performance obligations; for example, we typically sell software licenses with maintenance and other associated services. For these transactions, we recognize revenue based on the relative fair value to the customer of each performance obligation as each performance obligation is completed. We record a receivable when a customer is billed or when revenue is recognized prior to billing a customer. Contract assets include unbilled amounts for multi-year customer contracts where payment is not yet due and where services have been provided up front but have not yet been billed. Contract assets were approximately $28.3 million as of February 28, 2019 and $29.8 million as of December 1, 2018, and are recorded in accounts receivable, net, in the consolidated balance sheets. Contract liabilities primarily include our obligations to transfer goods or services for which we have received consideration (or an amount of consideration is due) from the customer. As of February 28, 2019 and December 1, 2018, we had contract liabilities of $1,026.3 million and $858.0 million , respectively, which are recorded as deferred revenue in the consolidated balance sheets. The increase in contract liabilities from December 1, 2018 to February 28, 2019 was primarily due to billings of $984.2 million that were paid in advance or due from customers, partially offset by $815.9 million of revenue recognized for the three months ended February 28, 2019. We recognize an asset for the incremental costs of obtaining a contract with a customer if we expect the benefit of those costs to exceed one year. Certain sales commission programs are designed to promote the sale of products and services to new customers, and we therefore defer the incremental costs related to these programs over the expected customer life related to those products underlying the contracts. We record these expenses as selling, general and administrative expense within the consolidated statements of operations. Recent Accounting Pronouncements In February 2016, the FASB issued ASU 2016-02, which requires that lease assets and lease liabilities be recognized on the balance sheet, and that key information about leasing arrangements be disclosed. In July 2018, the FASB issued ASU 2018-11, which provides targeted improvements to ASU 2016-02 by providing an additional optional transition method and a lessor practical expedient for lease and nonlease components. The standard will be effective for us in the first quarter of our fiscal year 2020, although early adoption is permitted. We are currently evaluating the impact of this new standard on our consolidated financial statements, but believe that the most significant impact of adoption will be the recognition of right-of-use assets and lease liabilities associated with our operating leases. In August 2016, the FASB issued ASU 2016-15, which clarifies how certain cash receipts and cash payments are presented and classified in the statement of cash flows. The ASU is applied using a retrospective transition method to each period presented. We adopted the standard in the first quarter of 2019, and there was no material impact of adoption on our consolidated financial statements. In January 2017, the FASB issued ASU 2017-01, which clarifies the definition of a business to assist entities with evaluating whether transactions should be accounted for as acquisitions (or disposals) of assets or businesses. We adopted the standard in the first quarter of 2019, and there was no material impact of adoption on our consolidated financial statements. In January 2017, the FASB issued ASU 2017-04, which removes Step 2 from the goodwill impairment test. The standard will be effective for us in the first quarter of our fiscal 2021, although early adoption is permitted. We do not expect that the adoption of this ASU will have a significant impact on our consolidated financial statements. In March 2017, the FASB issued ASU 2017-07, which requires that the service cost component of pension expense be included in the same line item as other compensation costs arising from services rendered by employees, with the other components of pension expense being classified outside of a subtotal of income from operations. We adopted the standard in the first quarter of 2019, and the only impact on adoption was the reclassification of our net periodic pension and postretirement expense to non-operating expense. Because all of our pension plans are frozen, there is no service cost component of expense that remained in operating expense. In May 2017, the FASB issued ASU 2017-09, which provides guidance about which changes to the terms or conditions of a share-based payment award require an entity to apply modification accounting in Topic 718. We adopted the standard in the first quarter of 2019, and there was no material impact of adoption on our consolidated financial statements. In June 2018, the FASB issued ASU 2018-07, which simplifies the accounting for nonemployee share-based payment transactions. The amendments specify that Topic 718 applies to all share-based payment transactions in which a grantor acquires goods or services to be used or consumed in a grantor’s own operations by issuing share-based payment awards. The standard will be effective for us in the first quarter of our fiscal year 2020, although early adoption is permitted (but no sooner than the adoption of Topic 606). We early adopted this standard in the first quarter of 2019, and there was no material impact of adoption on our consolidated financial statements. In August 2018, the FASB issued ASU 2018-15, which addresses the accounting for implementation costs associated with a hosted service. The standard provides that implementation costs be evaluated for capitalization using the same criteria as that used for internal-use software development costs, with amortization expense being recorded in the same income statement expense line as the hosted service costs and over the expected term of the hosting arrangement. The standard will be effective for us in the first quarter of our fiscal 2021, although early adoption is permitted. The amendments will be applied either retrospectively or prospectively to all implementation costs incurred after the date of adoption. We do not expect that the adoption of this ASU will have a significant impact on our consolidated financial statements. |