

Standard	Description	Date/Method of Adoption	Effect on financial statements or other significant matters
Adopted During the Six Months Ended June 30, 2019
ASU 2016–02	This standard requires lessees to recognize leases on-balance sheet and disclose key information about leasing arrangements.	The Company adopted ASU 2016–02 effective January 1, 2019, using the modified retrospective approach, and all practical expedients permitted under the transition guidance.	In February 2016, the Financial Accounting Standards Board (“FASB”) issued ASU 2016–02, Leases (Topic 842), which requires leases with a duration greater than twelve months to be recognized on the balance sheet as right-of-use (“ROU”) assets and lease liabilities. We adopted the new standard using the modified retrospective approach and have elected the package of practical expedients permitted under the transition guidance, including the hindsight practical expedients for expired or existing contracts, which allowed us to carryforward our historical determination of (i) whether a contract is or contains a lease, (ii) lease classification and (iii) initial direct costs. Additionally, we elected the practical expedients which allowed us to (i) not perform an allocation of lease and non-lease components for real estate leases, (ii) continue to account for short-term leases under Topic 840 and (iii) utilize our incremental borrowing rate (“IBR”), rather than the rate implicit in each lease, to calculate the present value of the remaining lease payments. As such, the unaudited condensed consolidated financial statements for the period ended June 30, 2019 are presented under the new standard, while comparative periods presented continue to be reported in accordance with Topic 840. The most significant impact of adoption was the recording of operating lease ROU assets and operating lease liabilities on our unaudited condensed consolidated balance sheets at January 1, 2019. Refer to Note 14, Leases, for more information. The standard did not materially impact our results of operations or cash flows.
ASU 2018–15	This standard clarifies the accounting for capitalizing implementation costs in a cloud computing arrangement that is a service contract. The standard provides that implementation costs be treated using the same criteria 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.	Effective January 1, 2019, the Company early adopted ASU 2018–15 on a prospective basis.	Under the standard, we now capitalize implementation costs related to our cloud migration of technology platforms to the cloud. Such amounts are amortized over the lesser of the term of the hosting arrangement, considering any explicit renewal options for which we are reasonably certain to exercise, or the useful life of the underlying hosted software. This standard did not materially impact our results of operations, cash flows or consolidated financial position.

Not Yet Adopted as of June 30, 2019
ASU 2016–13	This standard requires financial assets measured at amortized cost to be presented at the net amount expected to be collected. The measurement of expected credit losses will be based on historical experience, current conditions and reasonable and supportable forecasts that impact the collectability of the reported amount.	The standard is effective January 1, 2020.	The current expected credit loss model outlined in the ASU differs from existing US GAAP as it based on expected rather than incurred losses. The standard requires a cumulative effect of initial application to be recognized in retained earnings at the date of initial application. The Company has established a cross-functional task force charged with evaluating the requirements of the new standard, the availability and extent of historical data, relevant economic indicators and the impact this standard will have on our processes, systems and internal controls. We are currently in the process of gathering historical data, selecting our credit loss model, assessing system requirements and evaluating disclosure requirements. Though the Company continues to assess the impact of adoption, we currently believe the most significant effects of the ASU will be incorporating economic factors into our credit loss reserve methodologies and providing expanded disclosures on expected credit losses. At this time, the impact on credit loss reserves is not expected to be material.