Summary of Significant Accounting Policies	3 Months Ended
May 31, 2019
Accounting Policies [Abstract]
Summary of Significant Accounting Policies	Summary of Significant Accounting Policies Basis of presentation The unaudited interim consolidated financial statements as of and for the three months ended May 31, 2019 have been prepared by the Company pursuant to the rules and regulations of the SEC for interim financial reporting. These consolidated statements are unaudited and, in the opinion of management, include all adjustments (consisting of normal recurring adjustments and accruals) necessary for a fair statement of the consolidated balance sheets, consolidated operating results, consolidated other comprehensive income and consolidated cash flows for the periods presented in accordance with accounting principles generally accepted in the U.S. (“U.S. GAAP”). Operating results for the three months ended May 31, 2019 are not necessarily indicative of the results that may be expected for the fiscal year ending February 29, 2020. Certain information and footnote disclosures normally included in annual financial statements prepared in accordance with U.S. GAAP have been omitted in accordance with the SEC’s rules and regulations for interim reporting. These unaudited financial statements should be read in conjunction with the Company’s Consolidated Financial Statements, including notes thereto, included in the Company’s Annual Report on Form 10-K for the fiscal year ended February 28, 2019. Other than the accounting pronouncement adopted during the three months ended May 31, 2019 related to accounting for leases as described below, there have been no changes to the Company’s significant accounting policies from those described in NOTE 2—Summary of Significant Accounting Policies to the Consolidated Financial Statements contained in the Company’s Annual Report on Form 10-K for the fiscal year ended February 28, 2019. The Company adopted Accounting Standards Update 2016-02, Leases, now commonly referred to as Accounting Standards Codification Topic 842 (“ASC 842”), effective March 1, 2019, using the modified retrospective method, which does not require adjustments to comparative periods nor require modified disclosures in those comparative periods. Certain amounts for the three months ended May 31, 2018 have been reclassified to conform to the current period presentation. The Company’s fiscal year ends on the last day of February, and the Company identifies fiscal years by the calendar years in which they end. For example, the fiscal year ending February 29, 2020 is referred to as “fiscal 2020.” Consolidation policy The accompanying Consolidated Financial Statements include the accounts of the Company and all of its wholly owned subsidiaries. All significant inter-company accounts and transactions are eliminated in consolidation. There are no significant foreign exchange restrictions on the Company’s foreign subsidiaries. Use of estimates The preparation of financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the balance sheet dates and the reported amounts of revenue and expenses during the reporting periods. Actual results could differ from such estimates. Estimates are used for, but not limited to, revenue recognition, goodwill and other long-lived assets, share-based compensation, income taxes and loss contingencies. Revenue recognition The Company derives its revenues from subscription contracts and training and service contracts. Revenue is recognized when performance obligations, as stipulated in the contracts, are transferred to a customer for an amount that reflects the consideration the Company expects to receive in exchange for those subscription contracts and training and service contracts. The Company applies the following five steps to recognize revenue: 1) Identify the contract with a customer. The Company determines that it has a contract with a customer when the contract is approved, the party’s rights regarding the products and services to be transferred can be identified, the payment terms for the products and services are identified, the customer’s ability and intent to pay can be determined, and the contract has commercial substance. Judgment is used to assess the customer’s ability and intent to pay, which is based upon factors including the customer’s historical payment experience or credit and financial information pertaining to the customer. 2) Identify the performance obligations in the contract. The Company’s performance obligations are identified based on the products and services that will be transferred to the customer that are both capable of being distinct and are distinct in the context of the contract and consist of (i) subscription offerings, including non-proprietary open-source software code delivered to the customer, software support subscriptions delivered to the customer, software support subscriptions embedded in partner products and learning subscriptions and (ii) training and services, including professional services sold at a fixed fee, professional services sold on a time-and-material-basis, training courses or units, and consulting units. In limited cases, the option to purchase additional subscription offerings or training and services may be offered at a price representing a material right. In such cases, the option to purchase is considered a distinct performance obligation. 3) Determine the transaction price. The Company determines transaction price based on the consideration expected to be received in exchange for transferring certain performance obligations to the customer. In determining the transaction price, variable consideration, if any, would be considered if, in management’s judgment, it is probable that a significant future reversal of cumulative revenue under the contract will not occur. The Company’s contracts do not contain significant financing components. Specifically, the Company does not typically extend customer payment terms beyond a standard 30- to 60-day term and as a result the Company has elected the one-year-or-less safe harbor expedient and does not impute any interest. The Company has elected to exclude all taxes from the transaction price (e.g., sales, use, value-added, etc.). Revenue is recognized net of such taxes. 4) Allocate the transaction price to performance obligations in the contract. When a contract contains a single performance obligation, the entire transaction price is allocated to that one performance obligation. Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation based on a relative standalone selling price (“SSP”). The Company typically determines SSP based on the observable price when the Company sells the subscriptions or training and services separately, taking into consideration the geographical region of the customer, type of offering and sales channel. In instances where SSP is not directly observable, the Company determines SSP either from the renewal rate paid for the performance obligation to the extent it is the same rate as stipulated in the initial customer contract or by using the expected-cost-plus-margin approach. 5) Recognize revenue when or as the performance obligation is satisfied. Revenue is recognized at the time the related performance obligation is satisfied by transferring the promised subscription offerings and training and services to a customer. For each performance obligation, a determination is made as to whether the control is transferred over time or at a point in time. For performance obligations satisfied over time, a method to measure progress toward complete satisfaction is selected, based upon the most faithful depiction of performance. The selected method for each performance obligation type is applied consistently to similar contracts. Subscription revenue Subscription revenue is comprised of direct and indirect sales of subscriptions relating to Red Hat technologies. Accounts receivable and deferred revenue are recorded at the time a customer enters into a binding and non-cancellable subscription agreement for the purchase of a subscription, subscription services are made available to the customer and the customer is billed. The deferred revenue amount is recognized as revenue ratably over the subscription period. Red Hat technologies are generally offered with base subscription periods of either one year or three years; the majority of the Company’s subscriptions have terms of one year. Under these subscription agreements, renewal rates are generally specified for renewal terms of one year or three years. Subscriptions generally entitle the end user to the technology itself and post-contract customer support, generally consisting of varying levels of support services as well as access to security updates, fixes, functionality enhancements, upgrades to the technologies, each on an if and when available basis, and compatibility with an ecosystem of certified hardware and software, during the term of the subscription. The Company sells its offerings through two principal channels: (1) direct, which includes sales by the Company’s sales force as well as web store sales, and (2) indirect, which includes certified cloud and service providers (“CCSPs”), distributors, original equipment manufacturers (“OEMs”), systems integrators and value added resellers. The Company recognizes revenue from the sale of Red Hat technologies ratably over the period of the subscription beginning on the commencement date of the subscription agreement. The Company has determined that the delivery of software code underlying the subscription is a distinct performance obligation as it is both capable of being distinct and is distinct within the context of a customer contract. The Company uses a non-proprietary open source development and licensing model to provide its software technologies to customers and therefore the amount of transaction price allocated to the underlying software code is negligible. The Company derives a portion of its revenue from CCSPs that provide public clouds with, and allow users to consume, computing resources as a service. The Company earns revenue based on subscription units consumed by the CCSP or its end users. The Company uses its historical cloud-usage data to estimate the amount of revenue earned and recognized each month and adjusts to actual amounts earned upon receipt of usage reports from the CCSPs in the following month. The differences between actual amounts earned and estimates made have generally been insignificant. Training and services revenue Training and services revenue is comprised of revenue for consulting, engineering and customer training courses or units and education services. Consulting services consist of time-based units or fixed-fee arrangements. For time-based arrangements, revenue is recognized over time as these services are performed and for fixed-fee arrangements, revenue is recognized based on the proportion of services performed. Engineering services represent revenue earned under fixed-fee arrangements with the Company’s OEM partners and other customers to provide for significant modification and customization of Red Hat technologies. The Company recognizes revenue for these fixed-fee engineering services based on a proportional performance basis using actual costs incurred to date over the estimated total projected costs, which includes a representative profit margin. A representative profit margin is determined based on analysis of a population of similar contracts by region. Revenue for customer training and education services is recognized on the dates the services are performed. See NOTE 17—Segment Reporting for further information, including revenue by geographic area and significant product and service offerings. Contract Balances Timing of revenue recognition may differ from the timing of invoicing to customers. The Company records a receivable when revenue is recognized prior to invoicing, or deferred revenue when revenue is recognized subsequent to invoicing. For multi-year arrangements, the Company will generally invoice customers upfront or annually at the beginning of each annual coverage period. See below for the accounting policy related to receivables and see NOTE 13—Deferred Revenue and Performance Obligations for further information on deferred revenue balances. Accounts receivable and allowance for doubtful accounts Trade accounts receivable are recorded at the invoiced amount and do not bear interest. The allowance for doubtful accounts is the Company’s estimate of the amount of probable credit losses in the Company’s existing accounts receivable. The Company determines the allowance based on historical write-off experience and other qualitative factors. The Company reviews its allowance for doubtful accounts monthly. Past due balances over 90 days and over a specified amount are reviewed individually for collectability. All other balances are reviewed on a pooled basis by type of receivable. Account balances are charged off against the allowance when the Company determines it is probable the receivable will not be recovered. The Company does not have off-balance sheet credit exposure related to its customers. Unbilled receivables related to subscription and training and services contracts are included in accounts receivable. See NOTE 3—Accounts Receivable for further information on accounts receivable balances. Deferred selling costs Deferred commissions are the incremental costs that are directly associated with non-cancellable subscription contracts with customers and consist of sales commissions and certain related fringe benefits earned by the Company’s sales force. The commissions are deferred and amortized on a straight-line basis over a period that approximates the subscription period. In determining the period that approximates the subscription period, the Company utilizes a portfolio approach that allows for the analysis of customer contracts with similar characteristics. The Company has determined that the effects on the financial statements of the portfolio approach would not differ materially from an individual customer contract analysis approach. The commission payments are paid in full subsequent to the month in which the customer’s service commences. The deferred commission amounts are recoverable through the future revenue streams under the non-cancellable customer contracts. In addition, the Company has the ability and intent under the commission plans with its sales force to recover commissions previously paid to its sales force in the event that customers breach the terms of their subscription agreements and do not fully pay for their subscription agreements. See NOTE 6—Deferred Selling Costs for further information on deferred commissions and the related amortization of deferred commissions. Leases The Company determines if an arrangement is a lease at inception. As part of that determination, the Company considers whether there is an implicitly or explicitly identified asset in an arrangement and whether the Company, as the lessee, has the right to control that asset. Operating leases are included in operating right-of-use (“ROU”) assets, accounts payable and accrued expenses, and operating lease liabilities in the Company’s Consolidated Balance Sheets. Finance leases are included in property and equipment, other current obligations, and other long-term obligations in the Company’s Consolidated Balance Sheets. ROU assets represent the Company’s right to use an underlying asset for the lease term and lease liabilities represent the Company’s obligation to make lease payments arising from the lease. Variable lease payments, other than those based on a rate or index, are not included in the recognition of ROU assets and lease liabilities but instead are recognized in the Consolidated Statement of Operations in the period in which the obligation for those payments is incurred. Operating lease ROU assets and liabilities are recognized at commencement date based on the present value of lease payments over the lease term. As most of the Company’s leases do not provide an implicit borrowing rate, the Company’s incremental borrowing rate at commencement date is used to determine the present value of lease payments. The lease terms may include options to extend or to purchase when it is reasonably certain that the Company will exercise those options. For termination options, the Company will adjust the lease term unless it is reasonably certain that the option will not be taken. Lease expense for lease payments is recognized on a straight-line basis over the lease term. The Company has lease arrangements with both lease and non-lease components, which are generally accounted for as a single lease component. Additionally, for certain equipment leases, the Company applies a portfolio approach to effectively account for the operating lease ROU assets and liabilities. Recent accounting pronouncements Accounting pronouncements adopted In August 2018, the FASB issued Accounting Standards Update 2018-15, Intangibles—Goodwill and Other—Internal-Use Software: Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract (a consensus of the FASB Emerging Issues Task Force) (“ASU 2018-15”). The FASB issued ASU 2018-15 to align the requirements for capitalizing implementation costs in a cloud computing arrangement service contract with the requirements for capitalizing implementation costs incurred for an internal-use software license. The Company early adopted this standard effective March 1, 2019. The adoption of this standard did not significantly impact the Company’s Consolidated Financial Statements. In February 2016, the FASB issued Accounting Standards Update 2016-02, Leases (Topic 842) (“ASU 2016-02”). The FASB issued ASU 2016-02 to increase transparency and comparability among organizations with respect to accounting for leases by requiring the recognition of ROU assets and lease liabilities on the balance sheet. For income statement purposes, the FASB retained a dual model, requiring leases to be classified as either operating or finance. Along with ASU 2016-02, the Company also adopted Accounting Standards Update 2018-10, Codification Improvements to Topic 842 Leases (“ASU 2018-10”), Accounting Standards Update 2018-11, Targeted Improvements to Topic 842 Leases (“ASU 2018-11”), Accounting Standards Update 2018-20, Leases (Topic 842) Narrow-Scope Improvements for Lessors (“ASU 2018-20”) and Accounting Standards Updated 2019-01, Leases (Topic 842): Codification Improvements (“ASU 2019-01”), now commonly referred to as Accounting Standards Codification Topic 842 (“ASC 842”). The Company adopted ASC 842 as of March 1, 2019. The Company adopted ASC 842 using the transition method, which does not require adjustments to comparative periods nor require modified disclosures in those comparative periods. The Company elected the transition package of practical expedients permitted within the new standard, which among other things, allows the carryforward of the historical lease classification. Further, upon adoption of the new guidance, the Company elected the practical expedients to combine lease and non-lease components for all asset classes and to not recognize ROU assets and lease liabilities for short-term leases for all asset classes. ASC 842 had a material impact on the Company’s Consolidated Balance Sheets, but did not have an impact on the Consolidated Statements of Operations. The most significant impact was the recognition of ROU assets and lease liabilities for operating leases. At adoption, the Company recognized operating ROU assets of $237.4 million and operating lease liabilities of $244.5 million. Finance leases are not significant to the Company’s financials. The transition adjustment recognized in retained earnings as of March 1, 2019, was not material. See NOTE 4—Leases for further information on the Company’s lease arrangements.

The unaudited interim consolidated financial statements as of and for the three months ended May 31, 2019 have been prepared by the Company pursuant to the rules and regulations of the SEC for interim financial reporting. These consolidated statements are unaudited and, in the opinion of management, include all adjustments (consisting of normal recurring adjustments and accruals) necessary for a fair statement of the consolidated balance sheets, consolidated operating results, consolidated other comprehensive income and consolidated cash flows for the periods presented in accordance with accounting principles generally accepted in the U.S. (“U.S. GAAP”). Operating results for the three months ended May 31, 2019 are not necessarily indicative of the results that may be expected for the fiscal year ending February 29, 2020. Certain information and footnote disclosures normally included in annual financial statements prepared in accordance with U.S. GAAP have been omitted in accordance with the SEC’s rules and regulations for interim reporting. These unaudited financial statements should be read in conjunction with the Company’s Consolidated Financial Statements, including notes thereto, included in the Company’s Annual Report on Form 10-K for the fiscal year ended February 28, 2019. Other than the accounting pronouncement adopted during the three months ended May 31, 2019 related to accounting for leases as described below, there have been no changes to the Company’s significant accounting policies from those described in NOTE 2—Summary of Significant Accounting Policies to the Consolidated Financial Statements contained in the Company’s Annual Report on Form 10-K for the fiscal year ended February 28, 2019.

The preparation of financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the balance sheet dates and the reported amounts of revenue and expenses during the reporting periods. Actual results could differ from such estimates. Estimates are used for, but not limited to, revenue recognition, goodwill and other long-lived assets, share-based compensation, income taxes and loss contingencies.

The Company derives its revenues from subscription contracts and training and service contracts. Revenue is recognized when performance obligations, as stipulated in the contracts, are transferred to a customer for an amount that reflects the consideration the Company expects to receive in exchange for those subscription contracts and training and service contracts.

1) Identify the contract with a customer. The Company determines that it has a contract with a customer when the contract is approved, the party’s rights regarding the products and services to be transferred can be identified, the payment terms for the products and services are identified, the customer’s ability and intent to pay can be determined, and the contract has commercial substance. Judgment is used to assess the customer’s ability and intent to pay, which is based upon factors including the customer’s historical payment experience or credit and financial information pertaining to the customer.

2) Identify the performance obligations in the contract. The Company’s performance obligations are identified based on the products and services that will be transferred to the customer that are both capable of being distinct and are distinct in the context of the contract and consist of (i) subscription offerings, including non-proprietary open-source software code delivered to the customer, software support subscriptions delivered to the customer, software support subscriptions embedded in partner products and learning subscriptions and (ii) training and services, including professional services sold at a fixed fee, professional services sold on a time-and-material-basis, training courses or units, and consulting units. In limited cases, the option to purchase additional subscription offerings or training and services may be offered at a price representing a material right. In such cases, the option to purchase is considered a distinct performance obligation.

3) Determine the transaction price. The Company determines transaction price based on the consideration expected to be received in exchange for transferring certain performance obligations to the customer. In determining the transaction price, variable consideration, if any, would be considered if, in management’s judgment, it is probable that a significant future reversal of cumulative revenue under the contract will not occur.

4) Allocate the transaction price to performance obligations in the contract. When a contract contains a single performance obligation, the entire transaction price is allocated to that one performance obligation. Contracts that contain multiple performance obligations require an allocation of the transaction price to each performance obligation based on a relative standalone selling price (“SSP”). The Company typically determines SSP based on the observable price when the Company sells the subscriptions or training and services separately, taking into consideration the geographical region of the customer, type of offering and sales channel. In instances where SSP is not directly observable, the Company determines SSP either from the renewal rate paid for the performance obligation to the extent it is the same rate as stipulated in the initial customer contract or by using the expected-cost-plus-margin approach.

5) Recognize revenue when or as the performance obligation is satisfied. Revenue is recognized at the time the related performance obligation is satisfied by transferring the promised subscription offerings and training and services to a customer. For each performance obligation, a determination is made as to whether the control is transferred over time or at a point in time. For performance obligations satisfied over time, a method to measure progress toward complete satisfaction is selected, based upon the most faithful depiction of performance. The selected method for each performance obligation type is applied consistently to similar contracts.

Subscription revenue is comprised of direct and indirect sales of subscriptions relating to Red Hat technologies. Accounts receivable and deferred revenue are recorded at the time a customer enters into a binding and non-cancellable subscription agreement for the purchase of a subscription, subscription services are made available to the customer and the customer is billed. The deferred revenue amount is recognized as revenue ratably over the subscription period. Red Hat technologies are generally offered with base subscription periods of either one year or three years; the majority of the Company’s subscriptions have terms of one year. Under these subscription agreements, renewal rates are generally specified for renewal terms of one year or three years. Subscriptions generally entitle the end user to the technology itself and post-contract customer support, generally consisting of varying levels of support services as well as access to security updates, fixes, functionality enhancements, upgrades to the technologies, each on an if and when available basis, and compatibility with an ecosystem of certified hardware and software, during the term of the subscription. The Company sells its offerings through two principal channels: (1) direct, which includes sales by the Company’s sales force as well as web store sales, and (2) indirect, which includes certified cloud and service providers (“CCSPs”), distributors, original equipment manufacturers (“OEMs”), systems integrators and value added resellers.

The Company recognizes revenue from the sale of Red Hat technologies ratably over the period of the subscription beginning on the commencement date of the subscription agreement. The Company has determined that the delivery of software code underlying the subscription is a distinct performance obligation as it is both capable of being distinct and is distinct within the context of a customer contract. The Company uses a non-proprietary open source development and licensing model to provide its software technologies to customers and therefore the amount of transaction price allocated to the underlying software code is negligible. The Company derives a portion of its revenue from CCSPs that provide public clouds with, and allow users to consume, computing resources as a service. The Company earns revenue based on subscription units consumed by the CCSP or its end users. The Company uses its historical cloud-usage data to estimate the amount of revenue earned and recognized each month and adjusts to actual amounts earned upon receipt of usage reports from the CCSPs in the following month. The differences between actual amounts earned and estimates made have generally been insignificant.

Training and services revenue is comprised of revenue for consulting, engineering and customer training courses or units and education services. Consulting services consist of time-based units or fixed-fee arrangements. For time-based arrangements, revenue is recognized over time as these services are performed and for fixed-fee arrangements, revenue is recognized based on the proportion of services performed. Engineering services represent revenue earned under fixed-fee arrangements with the Company’s OEM partners and other customers to provide for significant modification and customization of Red Hat technologies. The Company recognizes revenue for these fixed-fee engineering services based on a proportional performance basis using actual costs incurred to date over the estimated total projected costs, which includes a representative profit margin. A representative profit margin is determined based on analysis of a population of similar contracts by region. Revenue for customer training and education services is recognized on the dates the services are performed.

Timing of revenue recognition may differ from the timing of invoicing to customers. The Company records a receivable when revenue is recognized prior to invoicing, or deferred revenue when revenue is recognized subsequent to invoicing. For multi-year arrangements, the Company will generally invoice customers upfront or annually at the beginning of each annual coverage period. See below for the accounting policy related to receivables and see NOTE 13—Deferred Revenue and Performance Obligations for further information on deferred revenue balances.

Trade accounts receivable are recorded at the invoiced amount and do not bear interest. The allowance for doubtful accounts is the Company’s estimate of the amount of probable credit losses in the Company’s existing accounts receivable. The Company determines the allowance based on historical write-off experience and other qualitative factors. The Company reviews its allowance for doubtful accounts monthly. Past due balances over 90 days and over a specified amount are reviewed individually for collectability. All other balances are reviewed on a pooled basis by type of receivable. Account balances are charged off against the allowance when the Company determines it is probable the receivable will not be recovered. The Company does not have off-balance sheet credit exposure related to its customers. Unbilled receivables related to subscription and training and services contracts are included in accounts receivable. See NOTE 3—Accounts Receivable for further information on accounts receivable balances.

Deferred commissions are the incremental costs that are directly associated with non-cancellable subscription contracts with customers and consist of sales commissions and certain related fringe benefits earned by the Company’s sales force. The commissions are deferred and amortized on a straight-line basis over a period that approximates the subscription period. In determining the period that approximates the subscription period, the Company utilizes a portfolio approach that allows for the analysis of customer contracts with similar characteristics. The Company has determined that the effects on the financial statements of the portfolio approach would not differ materially from an individual customer contract analysis approach. The commission payments are paid in full subsequent to the month in which the customer’s service commences. The deferred commission amounts are recoverable through the future revenue streams under the non-cancellable customer contracts. In addition, the Company has the ability and intent under the commission plans with its sales force to recover commissions previously paid to its sales force in the event that customers breach the terms of their subscription agreements and do not fully pay for their subscription agreements. See NOTE 6—Deferred Selling Costs for further information on deferred commissions and the related amortization of deferred commissions.

Operating leases are included in operating right-of-use (“ROU”) assets, accounts payable and accrued expenses, and operating lease liabilities in the Company’s Consolidated Balance Sheets. Finance leases are included in property and equipment, other current obligations, and other long-term obligations in the Company’s Consolidated Balance Sheets.

ROU assets represent the Company’s right to use an underlying asset for the lease term and lease liabilities represent the Company’s obligation to make lease payments arising from the lease. Variable lease payments, other than those based on a rate or index, are not included in the recognition of ROU assets and lease liabilities but instead are recognized in the Consolidated Statement of Operations in the period in which the obligation for those payments is incurred. Operating lease ROU assets and liabilities are recognized at commencement date based on the present value of lease payments over the lease term. As most of the Company’s leases do not provide an implicit borrowing rate, the Company’s incremental borrowing rate at commencement date is used to determine the present value of lease payments. The lease terms may include options to extend or to purchase when it is reasonably certain that the Company will exercise those options. For termination options, the Company will adjust the lease term unless it is reasonably certain that the option will not be taken. Lease expense for lease payments is recognized on a straight-line basis over the lease term.

In August 2018, the FASB issued Accounting Standards Update 2018-15, Intangibles—Goodwill and Other—Internal-Use Software: Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract (a consensus of the FASB Emerging Issues Task Force) (“ASU 2018-15”). The FASB issued ASU 2018-15 to align the requirements for capitalizing implementation costs in a cloud computing arrangement service contract with the requirements for capitalizing implementation costs incurred for an internal-use software license. The Company early adopted this standard effective March 1, 2019. The adoption of this standard did not significantly impact the Company’s Consolidated Financial Statements.

In February 2016, the FASB issued Accounting Standards Update 2016-02, Leases (Topic 842) (“ASU 2016-02”). The FASB issued ASU 2016-02 to increase transparency and comparability among organizations with respect to accounting for leases by requiring the recognition of ROU assets and lease liabilities on the balance sheet. For income statement purposes, the FASB retained a dual model, requiring leases to be classified as either operating or finance. Along with ASU 2016-02, the Company also adopted Accounting Standards Update 2018-10, Codification Improvements to Topic 842 Leases (“ASU 2018-10”), Accounting Standards Update 2018-11, Targeted Improvements to Topic 842 Leases (“ASU 2018-11”), Accounting Standards Update 2018-20, Leases (Topic 842) Narrow-Scope Improvements for Lessors (“ASU 2018-20”) and Accounting Standards Updated 2019-01, Leases (Topic 842): Codification Improvements (“ASU 2019-01”), now commonly referred to as Accounting Standards Codification Topic 842 (“ASC 842”). The Company adopted ASC 842 as of March 1, 2019.

The Company adopted ASC 842 using the transition method, which does not require adjustments to comparative periods nor require modified disclosures in those comparative periods. The Company elected the transition package of practical expedients permitted within the new standard, which among other things, allows the carryforward of the historical lease classification. Further, upon adoption of the new guidance, the Company elected the practical expedients to combine lease and non-lease components for all asset classes and to not recognize ROU assets and lease liabilities for short-term leases for all asset classes.

ASC 842 had a material impact on the Company’s Consolidated Balance Sheets, but did not have an impact on the Consolidated Statements of Operations. The most significant impact was the recognition of ROU assets and lease liabilities for operating leases. At adoption, the Company recognized operating ROU assets of $237.4 million and operating lease liabilities of $244.5 million. Finance leases are not significant to the Company’s financials. The transition adjustment recognized in retained earnings as of March 1, 2019, was not material.