Description of Business, Basis of Presentation and Significant Accounting Policies

Description of the Business. Teradata Corporation (“Teradata” or the “Company”) is a global leader in analytic data platforms, marketing and analytic applications, and related services. The Company’s analytic data platforms are comprised of software, hardware, and related business consulting and support services for data warehousing and big data analytics.

Basis of Presentation. The financial statements are presented on a consolidated basis and include the accounts of the Company and its wholly-owned subsidiaries in accordance with accounting principles generally accepted in the United States of America (“GAAP”).

Use of Estimates. The preparation of financial statements in conformity with GAAP requires management to make estimates and judgments that affect the reported amounts of assets and liabilities, the disclosure of contingent assets and liabilities at the date of the financial statements, and revenues and expenses during the period reported. On an ongoing basis, management evaluates these estimates and judgments, including those related to allowances for doubtful accounts, the valuation of inventory to net realizable value, impairments of goodwill and other intangibles, stock-based compensation, pension and other postemployment benefits, and income taxes and any changes will be accounted for on a prospective basis. Actual results could differ from those estimates.

Revenue Recognition. Teradata’s solution offerings typically include software, software subscriptions (unspecified when-and-if-available upgrades), hardware, maintenance support services, and other consulting, implementation and installation-related (“consulting”) services. Teradata records revenue when it is realized, or realizable, and earned. Teradata considers these requirements met when:


•	Persuasive evidence of an arrangement exists


•	The products or services have been delivered to the customer


•	The sales price is fixed or determinable and free of contingencies or significant uncertainties


•	Collectibility is reasonably assured

Teradata reports revenue net of any taxes assessed by governmental authorities that are imposed on and concurrent with specific revenue-producing transactions. The Company assesses whether fees are fixed or determinable at the time of sale. Standard payment terms may vary based on the country in which the agreement is executed, but are generally between 30 days and 90 days. Payments that are due within six months are generally deemed to be fixed or determinable based on a successful collection history on such arrangements, and thereby satisfy the required criteria for revenue recognition. Teradata delivers its solutions primarily through direct sales channels, as well as through alliances with system integrators, other independent software vendors and distributors, and value-added resellers (collectively referred to as “resellers”). In assessing whether the sales price to a reseller is fixed or determinable, the Company considers, among other things, past business practices with the reseller, the reseller’s operating history, payment terms, return rights and the financial wherewithal of the reseller. When Teradata determines that the contract fee to a reseller is not fixed or determinable, that transaction is deferred and recognized upon sell-through to the end customer.

The Company’s deliverables often involve delivery or performance at different periods of time. Revenue for software is generally recognized upon delivery with the hardware once title and risk of loss have been transferred. Revenue for software subscriptions, which provide for unspecified upgrades or enhancements on a when-and-if-available basis, is recognized straight-line over the term of the subscription arrangement. Revenue for maintenance support services is also recognized on a straight-line basis over the term of the contract. Revenue for other consulting, implementation and installation services is recognized as services are provided. In certain instances, acceptance of the product or service is specified by the customer. In such cases, revenue is deferred until the acceptance criteria have been met. Delivery and acceptance generally occur in the same reporting period. The Company’s arrangements generally do not include any customer negotiated provisions for cancellation, termination or refunds that would significantly impact recognized revenue.

The Company evaluates all deliverables in an arrangement to determine whether they represent separate units of accounting. A deliverable constitutes a separate unit of accounting when it has standalone value, and if the contract includes a general right of return relative to the delivered item, delivery or performance of the undelivered items is considered probable and substantially in the control of Teradata. Most of the Company’s products and services qualify as separate units of accounting and are recognized upon meeting the criteria as described above.

For multiple deliverable arrangements that contain non-software related deliverables, the Company allocates revenue to each deliverable based upon the relative selling price hierarchy and if software and software-related deliverables are also included in the arrangement, to those deliverables as a group based on the best estimate of selling price (“BESP”) for the group. The selling price for a deliverable is based on its vendor-specific objective evidence of selling price (“VSOE”) if available, third-party evidence of selling price (“TPE”) if VSOE is not available, or BESP if neither VSOE nor TPE is available. The Company then recognizes revenue when the remaining revenue recognition criteria are met for each deliverable. For the software group or arrangements that contain only software and software-related deliverables, the revenue is allocated utilizing the residual or fair value method. Under the residual method, the VSOE of the undelivered elements is deferred and accounted for under the applicable revenue recognition guidance, and the remaining portion of the software arrangement fee is allocated to the delivered elements and is recognized as revenue. The fair value method is similar to the relative selling price method used for non-software deliverables except that the allocation of each deliverable is based on VSOE. For software groups or arrangements that contain only software and software-related deliverables in which VSOE does not exist for each deliverable (fair value method) or does not exist for each undelivered element (residual method), revenue for the entire software arrangement or group is deferred and not recognized until delivery of all elements without VSOE has occurred, unless the only undelivered element is postcontract customer support (“PCS”) in which case the entire software arrangement or group is recognized ratably over the PCS period.

Teradata’s analytic database software and hardware products are sold and delivered together in the form of a “Node” of capacity as an integrated technology solution. Because both the analytic database software and hardware platform are necessary to deliver the analytic data platform’s essential functionality, the database software and hardware (Node) are excluded from the software rules and considered a non-software related deliverable. Teradata software applications and related support are considered software-related deliverables. Additionally, the amount of revenue allocated to the delivered items utilizing the relative selling price or fair value method is limited to the amount that is not contingent upon the delivery of additional items or meeting other specified performance conditions (the non-contingent amount).

VSOE is based upon the normal pricing and discounting practices for those products and services when sold separately. Teradata uses the stated renewal rate approach in establishing VSOE for maintenance and subscriptions (collectively referred to as PCS). Under this approach, the Company assesses whether the contractually stated renewal rates are substantive and consistent with the Company’s normal pricing practices. Renewal rates greater than the lower level of our targeted pricing ranges are considered to be substantive and, therefore, meet the requirements to support VSOE. In instances where there is not a substantive renewal rate in the arrangement, the Company allocates revenue based upon BESP, using the minimum established pricing targets as supported by the renewal rates for similar customers utilizing the bell-curve method. Teradata also offers consulting and installation-related services to its customers, which are considered non-software deliverables if they relate to the nodes. These services are rarely considered essential to the functionality of the data warehouse solution deliverable and there is never software customization of the proprietary database software. VSOE for consulting services is based on the hourly rates for standalone consulting services projects by geographic region and are indicative of the Company’s customary pricing practices. Pricing in each market is structured to obtain a reasonable margin based on input costs.

In nearly all multiple-deliverable arrangements, the Company is unable to establish VSOE for all deliverables in the arrangement. This is due to infrequently selling each deliverable separately (such is the case with our nodes), not pricing products or services within a narrow range, or only having a limited sales history. When VSOE cannot be established, attempts are made to establish TPE of the selling price for each deliverable. TPE is determined based on competitor prices for similar deliverables when sold separately. However, Teradata’s offerings contain significant differentiation such that the comparable pricing of products with similar functionality cannot typically be obtained. This is because Teradata’s products contain a significant amount of proprietary technology and its solutions offer substantially different features and functionality than other available products. As Teradata’s products are significantly different from those of its competitors, the Company is unable to establish TPE for the vast majority of its products.

When the Company is unable to establish selling prices using VSOE or TPE, the Company uses BESP in its allocation of arrangement consideration. The objective of BESP is to determine the price at which the Company would transact a sale if the product or service was sold on a standalone basis. The Company determines BESP for a product or service by considering multiple factors including, but not limited to, geographies, market conditions, product life cycles, competitive landscape, internal costs, gross margin objectives, purchase volumes and pricing practices.

The primary consideration in developing BESP for the Company’s nodes is the bell-curve method based on historical transactions. The BESP analysis is at the geography level in order to align it with the way in which the Company goes to market and establishes pricing for its products. The Company has established discount ranges off of published list prices for different geographies based on strategy and maturity of Teradata’s presence in the respective geography. There are distinctions in each geography and product group which support the use of geographies and markets for the determination of BESP. For example, the Company’s U.S. market is relatively mature and most of the large transactions are captured in this market, whereas the International markets are less mature with generally smaller deal size. Additionally, the prices and margins for the Company’s products vary by geography and by product class. BESP is analyzed on a semi-annual basis using data from the 4 previous quarters, which the Company believes best reflects most recent pricing practices in a changing marketplace.

The Company reviews VSOE, TPE and its determination of BESP on a periodic basis and updates it, when appropriate, to ensure that the practices employed reflect the Company’s recent pricing experience. The Company maintains internal controls over the establishment and updates of these estimates, which includes review and approval by the Company’s management. For the year ended December 31, 2015 there was no material impact to revenue resulting from changes in VSOE, TPE or BESP, nor does the Company expect a material impact from such changes in the near term.

Perpetual licenses, term licenses, hosting arrangements and software as a service. Teradata’s application offerings include perpetual licenses, term licenses, hosting arrangements and software as a service. For software arrangements that include a perpetual license, the residual method is typically used because the Company does not have VSOE for its perpetual licenses. This is because the perpetual license is never sold standalone. If the license is of limited life and does not require the Company to host the software for the customer, the software is considered a term license. Teradata’s term licenses are typically offered for application software and include a right-to-use license, PCS and consulting services. The revenue for these arrangements are typically recognized ratably over the contract term. The term of these arrangements varies between one and five years and may or may not include hosting services. In most arrangements the pricing is bundled to the customer. If the term license is hosted, the customer has the right to take possession of the software at any time during the hosting period. The customer’s rights to the software in these circumstances are not dependent on additional software payments or significant penalties, and the customer can feasibly run the software on its own hardware or contract with another party to host the software. If these criteria are not met, the hosting arrangement is accounted for outside the software rules as a software as a service arrangement. Under a software as a service arrangement, the license, PCS and hosting fee are recognized ratably over the term of the contract.

Shipping and Handling. Product shipping and handling costs are included in cost of products in the Consolidated Statements of Income.

Cash and Cash Equivalents. All short-term, highly-liquid investments having original maturities of three months or less are considered to be cash equivalents.

Allowance for Doubtful Accounts. Teradata establishes provisions for doubtful accounts using both percentages of accounts receivable balances to reflect historical average credit losses and specific provisions for known issues.

Inventories. Inventories are stated at the lower of cost or market. Cost of service parts is determined using the average cost method. Finished goods inventory is determined using actual cost.

Available-for-sale Securities. Available-for-sale securities are reported at fair value. Unrealized holding gains and losses are excluded from earnings and reported in other comprehensive income. Realized gains and losses are included in other income and expense in the Consolidated Statements of Income.

Long-Lived Assets

Property and Equipment. Property and equipment, leasehold improvements and rental equipment are stated at cost less accumulated depreciation. Depreciation is computed over the estimated useful lives of the related assets primarily on a straight-line basis. Equipment is depreciated over 3 to 20 years and buildings over 25 to 45 years. Leasehold improvements are depreciated over the life of the lease or the asset, whichever is shorter. Total depreciation expense on the Company’s property and equipment for December 31 was as follows:



In millions	2015		2014		2013
Depreciation expense	$	53	$	51	$	48

Capitalized Software. Direct development costs associated with internal-use software are capitalized and amortized over the estimated useful lives of the resulting software. The costs are capitalized when both the preliminary project stage is completed and it is probable that computer software being developed will be completed and placed in service. Teradata typically amortizes capitalized internal-use software on a straight-line basis over three years beginning when the asset is substantially ready for use.

Costs incurred for the development of big data, marketing and analytic applications are expensed as incurred based on the frequency and agile nature of development. Costs incurred for the development of data warehousing software that will be sold, leased or otherwise marketed are capitalized when technological feasibility has been established. Technological feasibility is established when planning, designing and initial coding activities that are necessary to establish the product can be produced to meet its design specifications. In the absence of a program design, a working model is used to establish technological feasibility. These costs are included within capitalized software and are amortized over the estimated useful lives of four years using the greater of the ratio that current gross revenues for a product bear to the total of current and anticipated future gross revenues for that product or the straight-line method over the remaining estimated economic life of the product beginning when the product is available for general release. Costs capitalized include direct labor and related overhead costs. Costs incurred prior to technological feasibility and after general release are expensed as incurred. The following table identifies the activity relating to capitalized software:



	Internal-use Software									External-use Software
In millions	2015			2014			2013			2015			2014			2013
Beginning balance at January 1	$	13		$	12		$	12		$	186		$	183		$	161
Capitalized	6			7			6			61			68			72
Amortization	(6		)	(6		)	(6		)	(70		)	(65		)	(50		)
Ending balance at December 31	$	13		$	13		$	12		$	177		$	186		$	183

The aggregate amortization expense (actual and estimated) for internal-use and external-use software for the following periods is:



	Actual		For the year ended (estimated)
In millions	2015		2016		2017		2018		2019		2020
Internal-use software amortization expense	$	6	$	6	$	4	$	3	$	—	$	—
External-use software amortization expense	$	70	$	66	$	56	$	36	$	19	$	—

Estimated expense, which is recorded to cost of sales for external use software, is based on capitalized software at December 31, 2015 and does not include any new capitalization for future periods.

Valuation of Long-Lived Assets. Long-lived assets such as property and equipment, acquired intangible assets and internal capitalized software are reviewed for impairment when events or changes in circumstances indicate that the carrying amount of the assets may not be recoverable. An impairment loss would be recognized when estimated future undiscounted cash flows expected to result from the use of the asset and its eventual disposition are less than the carrying amount.

Goodwill. Goodwill represents the excess of the purchase price in a business combination over the fair value of net tangible and intangible assets acquired. Goodwill amounts are not amortized, but rather are tested for impairment annually or upon occurrence of an event or change in circumstances that would more likely than not reduce the fair value of a reporting unit below its carrying amount. See Note 3- Goodwill and Acquired Intangibles for additional information.

Assets and Liabilities Held for Sale. The Company classifies assets and liabilities (disposal groups) to be sold as held for sale in the period in which all of the following criteria are met:


•	Management, having the authority to approve the action, commits to a plan to sell the disposal group;


•	The disposal group is available for immediate sale in its present condition subject only to terms that are usual and customary for sales of such disposal groups;


•	An active program to locate a buyer and other actions required to complete the plan to sell the disposal group have been initiated;


•	The sale of the disposal group is probable, and transfer of the disposal group is expected to qualify for recognition as a completed sale, within one year, except if events or circumstances beyond the Company’s control extend the period of time required to sell the disposal group beyond one year;


•	The disposal group is being actively marketed for sale at a price that is reasonable in relation to its current fair value; and


•	Actions required to complete the plan indicate that it is unlikely that significant changes to the plan will be made or that the plan will be withdrawn.

The Company initially measures a disposal group that is classified as held for sale at the lower of its carrying value or fair value less costs to sell. Any loss resulting from this measurement is recognized in the period in which the held for sale criteria are met. Conversely, gains are not recognized until the date of sale. The Company assesses the fair value of a disposal group less costs to sell each reporting period it remains classified as held for sale and reports any subsequent changes as an adjustment to the carrying value of the disposal group, as long as the new carrying value does not exceed the carrying value of the disposal group at the time it was initially classified as held for sale.

Upon determining that a disposal group meets the criteria to be classified as held for sale, the Company reports the assets and liabilities of the disposal group under Assets held for sale and Liabilities held for sale in the Consolidated Balance Sheets. Refer to Note 15 for further information on the Company’s assets and liabilities held for sale.

Warranty. Provisions for product warranties are recorded in the period in which the related revenue is recognized. The Company accrues warranty reserves using percentages of revenue to reflect the Company’s historical average warranty claims.

Research and Development Costs. Research and development costs are expensed as incurred (with the exception of the capitalized software development costs discussed above). Research and development costs primarily include labor-related costs, contractor fees, and overhead expenses directly related to research and development support.

Pension and Postemployment Benefits. The Company accounts for its pension and postemployment benefit obligations using actuarial models. The measurement of plan obligations was made as of December 31, 2015. Liabilities are computed using the projected unit credit method. The objective under this method is to expense each participant’s benefits under the plan as they accrue, taking into consideration salary increases and the plan’s benefit allocation formula. Thus, the total pension or postemployment benefit to which each participant is expected to become entitled is broken down into units, each associated with a year of past or future credited service.

The Company recognizes the funded status of its pension and postemployment plan obligations in its consolidated balance sheet and records in other comprehensive income certain gains and losses that arise during the period, but are deferred under pension accounting rules.

Foreign Currency. Assets and liabilities of non-U.S. subsidiaries that operate in a local currency environment are translated into U.S. dollars at period-end exchange rates. Income and expense accounts are translated at daily exchange rates prevailing during the period. Adjustments arising from the translation are included in accumulated other comprehensive income, a separate component of stockholders’ equity. Gains and losses resulting from foreign currency transactions are included in determining net income.

Income Taxes. Income tax expense is provided based on income before income taxes in the various jurisdictions in which the Company conducts its business. Deferred income taxes reflect the impact of temporary differences between assets and liabilities recognized for financial reporting purposes and such amounts recognized for tax purposes. These deferred taxes are determined based on the enacted tax rates expected to apply in the periods in which the deferred assets or liabilities are expected to be settled or realized. Teradata recognizes tax benefits from uncertain tax positions only if it is more likely than not the tax position will be sustained on examination by taxing authorities, based on the technical merits of the position. The Company records valuation allowances related to its deferred income tax assets when it is more likely than not that some portion or all of the deferred income tax assets will not be realized.

Stock-based Compensation. Stock-based payments to employees, including grants of stock options, restricted shares and restricted share units, are recognized in the financial statements based on their fair value. The fair value of each stock option award on the grant date is estimated using the Black-Scholes option-pricing model with the following assumptions: expected dividend yield, expected stock price volatility, weighted-average risk-free interest rate and weighted average expected term of the options. The Company’s expected volatility assumption used in the Black-Scholes option-pricing model is based on Teradata's historical volatility. Prior to 2014, because the Company did not have a sufficient trading history as a standalone public company, the volatility was based on a blend of peer group volatility and Teradata volatility. The expected term for options granted is based upon historical observation of actual time elapsed between date of grant and exercise of options for all employees. Prior to 2015, the expected term assumption was based on the simplified method under GAAP, which is based on the vesting period and contractual term for each vesting tranche of awards. The mid-point between the vesting date and the expiration date was used as the expected term under this method. The risk-free interest rate used in the Black-Scholes model is based on the implied yield curve available on U.S. Treasury issues at the date of grant with a remaining term equal to the Company’s expected term assumption. The Company has never declared or paid a cash dividend.

Treasury Stock. Prior to the fourth quarter of 2014 when all treasury stock shares were retired, shares of the Company’s common stock repurchased through the share repurchase programs were held as treasury stock. Treasury stock was accounted for using the cost method. Beginning in the fourth quarter of 2014, stock repurchased through the share repurchase programs will be retired upon repurchase. The excess repurchase price over the par value is charged to retained earnings.

Earnings Per Share. Basic earnings per share is calculated by dividing net income by the weighted-average number of shares outstanding during the reported period. The calculation of diluted earnings per share is similar to basic earnings per share, except that the weighted-average number of shares outstanding includes the dilution from potential shares added from stock options, restricted share awards and other stock awards. Refer to Note 5 for share information on the Company’s stock compensation plans.

The components of basic and diluted earnings per share are as follows:



	For the year ended December 31
In millions, except earnings per share	2015			2014		2013
Net (loss) income attributable to common stockholders	$	(214	)	$	367	$	377
Weighted average outstanding shares of common stock	139.6			155.3		163.4
Dilutive effect of employee stock options, restricted shares and other stock awards	—			2.5		3.0
Common stock and common stock equivalents	139.6			157.8		166.4
(Loss) earnings per share:
Basic	$	(1.53	)	$	2.36	$	2.31
Diluted	$	(1.53	)	$	2.33	$	2.27

For 2015, due to the net loss attributable to Teradata common stockholders, largely due to the goodwill and acquired intangibles impairment charges, potential common shares that would cause dilution, such as employee stock options, restricted shares and other stock awards, have been excluded from the diluted share count because their effect would have been anti-dilutive. For 2015, the fully diluted shares would have been 141.9 million.

Options to purchase 4.5 million in 2015, 2.4 million shares in 2014 and 0.9 million shares in 2013 of common stock, were not included in the computation of diluted earnings per share because their exercise prices were greater than the average market price of the common shares and, therefore, the effect would have been anti-dilutive.

Recently Issued Accounting Pronouncements

Revenue Recognition. In May 2014, the Financial Accounting Standards Board ("FASB") issued new guidance that affects any entity that either enters into contracts with customers to transfer goods or services or enters into contracts for the transfer of nonfinancial assets unless those contracts are within the scope of other standards. The new guidance will supersede the revenue recognition requirements in the current revenue recognition guidance, and most industry-specific guidance. In addition, the existing requirements for the recognition of a gain or loss on the transfer of nonfinancial assets that are not in a contract with a customer are amended to be consistent with the guidance on recognition and measurement in this update. The core principle of the guidance is that an entity should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. To achieve that core principle, the FASB defines a five step process which includes the following: (1) identify the contract with a customer, (2) identify the performance obligations in the contract, (3) determine the transaction price, (4) allocate the transaction price to the performance obligations in the contract, and (5) recognize revenue when (or as) the entity satisfies a performance obligation.

In July 2015, the FASB issued a one-year delay in the effective date of the new standard. Under this guidance, the new revenue standard will be effective for annual reporting periods beginning after December 15, 2017, with early application permitted. The standard allows entities to apply the standard retrospectively for all periods presented or alternatively an entity is permitted to recognize the cumulative effect of initially applying the guidance as an opening balance sheet adjustment to retained earnings in the period of initial application. The Company is currently evaluating the impact on its consolidated financial position, results of operations and cash flows, as well as the method of transition that will be used in adopting the standard.

Accounting for Share-based Payments with Performance Targets. In June 2014, the FASB issued new guidance that requires that a performance target that affects vesting and that could be achieved after the requisite service period, be treated as a performance condition. A reporting entity should apply existing guidance as it relates to awards with performance conditions that affect vesting to account for such awards. As such, the performance target should not be reflected in estimating the grant-date fair value of the award. Compensation cost should be recognized in the period in which it becomes probable that the performance target will be achieved and should represent the compensation cost attributable to the periods for which the requisite service has already been rendered. The amendments in this update are effective for annual periods, and interim periods within those annual periods beginning after December 15, 2015. Earlier adoption is permitted. This amendment is not expected to have a material impact on the Company's consolidated financial statements.

Income Statement Presentation by Eliminating the Concept of Extraordinary Items. This update eliminates from GAAP the concept of extraordinary items. The amendments in this update are effective for fiscal years, and interim periods within those fiscal years, beginning after December 15, 2015. A reporting entity may apply the amendments prospectively. A reporting entity also may apply the amendments retrospectively to all prior periods presented in the financial statements. Early adoption is permitted provided that the guidance is applied from the beginning of the fiscal year of adoption. This amendment is not expected to have a material impact on the Company's results of operations.

Simplifying the Presentation of Debt Issuance Costs. To simplify presentation of debt issuance costs, the amendments in this update require that debt issuance costs related to a recognized debt liability be presented in the balance sheet as a direct deduction from the carrying amount of that debt liability, consistent with debt discounts. The recognition and measurement guidance for debt issuance costs are not affected by the amendments in this update. For public business entities, the amendments in this update are effective for financial statements issued for fiscal years beginning after December 15, 2015, and interim periods within those fiscal years and shall be applied on a retrospective basis. Debt issuance costs as of December 31, 2015 were $3 million. The Company plans to adopt this amendment when effective. This amendment is not expected to have a material impact on the Company's consolidated financial position.

Intangibles, Goodwill and Other Internal-Use Software. The amendments in this update provide guidance to customers about whether a cloud computing arrangement includes a software license. If a cloud computing arrangement includes a software license, then the customer should account for the software license element of the arrangement consistent with the acquisition of other software licenses. If a cloud computing arrangement does not include a software license, the customer should account for the arrangement as a service contract. The guidance will not change current guidance for a customer’s accounting for service contracts. This amendment will be effective for annual periods, including interim periods within those annual periods beginning after December 15, 2015. Early adoption is permitted. The Company is currently evaluating the impact of this guidance on its consolidated financial position, results of operations and cash flows.

Business Combinations. In September 2015, the FASB issued new guidance that eliminates the requirement that an acquirer in a business combination account for measurement-period adjustments retrospectively. An acquirer will recognize a measurement-period adjustment during the period in which it determines the amount of the adjustment. The amendments in this update are effective for annual periods, and interim periods within those annual periods beginning after December 15, 2015. Earlier adoption is permitted. The Company does not expect this guidance to have significant impact on its consolidated financial statements.

Financial Instruments. In January 2016, the FASB issued new guidance which enhances the reporting model for financial instruments and related disclosures. This update requires equity securities to be measured at fair value with changes in fair value recognized through net income and will eliminate the cost method for equity securities without readily determinable fair values. The provisions are effective for public entities with fiscal years beginning after December 15, 2017, including interim periods within those fiscal years. Early adoption is permitted, in certain circumstances. The Company is currently evaluating the impact of this guidance on its consolidated financial position, results of operations and cash flows.

Recently Adopted Guidance

Income Taxes. In November 2015, the FASB issued new guidance to simplify the presentation of deferred income taxes. The amendments in this update require that deferred tax liabilities and assets be classified as noncurrent in a classified statement of financial position. For public business entities, the amendments in this update are effective for financial statements issued for annual periods beginning after December 15, 2016, and interim periods within those annual periods. The Company has early adopted the new guidance prospectively as of December 31, 2015. As such, we did not restate our December 31, 2014 Balance Sheet. As a result of this adoption, no deferred tax amounts were recorded in other current assets and other current liabilities in 2015, as compared to $28 million recorded in other current assets and $1 million recorded in other current liabilities in 2014.