XML 25 R15.htm IDEA: XBRL DOCUMENT
v3.24.3

Commitments and Contingencies | 9 Months Ended
--- | ---
Sep. 30, 2024
Commitments and Contingencies Disclosure [Abstract] |
Commitments and Contingencies | Commitments and Contingencies Legal Proceedings. In the ordinary course of business, the Company is subject to proceedings, lawsuits, governmental investigations, claims and other matters, including those that relate to the environment, health and safety, employee benefits, export compliance, intellectual property, tax matters, shareholder matters, and other regulatory compliance and general matters. It is not currently a party to any litigation, nor is it aware of any pending or threatened litigation against it, that the Company believes would materially affect its business, operating results, financial condition or cash flows, other than the following. On June 14, 2024, a putative securities class action lawsuit was filed against the Company and certain of its officers in the United States District Court for the Southern District of California (the "Court"), captioned Ostrander v. Teradata Corporation, No. 24-cv-01034 (S.D. Cal.). The complaint asserts claims for alleged violations of federal securities laws related to statements concerning the Company’s business and 2023 financial outlook for Total ARR and Public Cloud ARR. The plaintiff seeks to represent a class of certain persons who purchased or otherwise acquired the Company’s stock during the period from February 13, 2023 to February 12, 2024 and seeks unspecified damages and other relief. On October 7, 2024, the Court appointed a lead plaintiff and lead counsel. The Company disputes the allegations in the complaint and intends to defend the case vigorously. The case is at an early stage, and the Company cannot reasonably estimate the amount of any potential financial loss or cost that could result from this lawsuit. On June 19, 2018, the Company and certain of its subsidiaries filed a lawsuit (the "TD-SAP 1" suit) in the U.S. District Court for the Northern District of California against SAP SE, SAP America, Inc., and SAP Labs, LLC (collectively, "SAP"). In the TD-SAP 1 lawsuit, the Company alleged, among other things, that SAP misappropriated certain of the Company’s trade secrets within the Company’s enterprise data analytics and warehousing products and used such trade secrets to help develop, improve, introduce, and sell one or more competing products. The Company further alleged that SAP employed anticompetitive practices using its substantial market position in the enterprise resource planning applications market to pressure the Company’s customers and prospective customers to use one or more of SAP's competing products and reduce or eliminate customers' and prospective customers' use of the Company's offerings. The Company sought an injunction barring SAP’s alleged conduct, monetary damages, and other available legal and equitable relief. In July 2019, SAP filed patent infringement counterclaims against the Company based on five of SAP’s U.S. patents. On August 31, 2020, the Company filed a second lawsuit against SAP (the "TD-SAP 2" suit) in the U.S. District Court for the Northern District of California, in which the Company alleged infringement by SAP of four of the Company's U.S. patents. On February 16, 2021, SAP filed additional patent infringement counterclaims against the Company in response. On the same day, SAP also filed a lawsuit in Germany (the "TD-SAP 3" suit) for infringement of a single German patent. In November 2021, the district court dismissed the Company’s antitrust claims and most of its trade secret claims in the TD-SAP 1 suit. In December 2021, the Company appealed that decision to the U.S. Court of Appeals for the Federal Circuit in Washington, D.C. That Court ruled the appeal should be heard by the Ninth Circuit Court of Appeals; the appeal was transferred to the Ninth Circuit and the court heard oral arguments on February 12, 2024, and the parties are awaiting the Court's ruling. In the meantime, the Company and SAP have entered into a partial settlement agreement that has resulted in full dismissal of all claims and counterclaims in the TD-SAP 2 suit in California and the TD-SAP 3 suit in Germany as well as a stay of all claims and counterclaims remaining in the TD-SAP 1 suit pending resolution of the Company’s appeal. Currently, it is not possible to determine the likelihood of a loss or a reasonably estimated range of loss, if any, pertaining to any of SAP’s remaining patent counterclaims in the TD-SAP 1 lawsuit. Other Contingencies. The Company provides its customers with certain indemnification rights. In general, the Company agrees to indemnify the customer if a third party asserts patent or other infringement on the part of the customer for its use of the Company’s offerings. The Company has indemnification obligations under its charter and bylaws to its officers and directors, and has entered into indemnification agreements with the officers and directors of its subsidiaries. From time to time, the Company also enters into agreements in connection with its acquisition and divestiture activities that include indemnification obligations by the Company. The fair value of these indemnification obligations is typically not readily determinable due to the conditional nature of the Company’s potential obligations and the specific facts and circumstances involved with each particular agreement. As such, the Company has generally not recorded a liability in connection with these indemnification arrangements. Historically, payments made by the Company under these types of agreements have not had a material effect on the Company’s consolidated financial condition, results of operations or cash flows. Concentrations of Risk. The Company is potentially subject to concentrations of credit risk on accounts receivable and financial instruments such as hedging instruments, and cash and cash equivalents. Credit risk includes the risk of nonperformance by counterparties. The maximum potential loss may exceed the amount recognized on the balance sheet. Exposure to credit risk is managed through credit approvals, credit limits, selecting major international financial institutions (as counterparties to hedging transactions) and monitoring procedures. Teradata’s business often involves large transactions with customers, and if one or more of those customers were to default in its obligations under applicable contractual arrangements, the Company could be exposed to potentially significant losses. However, management believes that the reserves for potential losses were adequate at September 30, 2024 and December 31, 2023. The Company is also potentially subject to concentrations of supplier risk. Our hardware components are assembled primarily by Flex Ltd. ("Flex"). Flex procures a wide variety of components used in the manufacturing process on behalf of the Company. Although many of these components are available from multiple sources, Teradata utilizes preferred supplier relationships to provide more consistent and optimal quality, cost and delivery. Typically, these preferred suppliers maintain alternative processes and/or facilities to ensure continuity of supply. Given the Company’s strategy to outsource its manufacturing activities to Flex and to source certain components from single suppliers, a disruption in production at Flex or at a supplier could impact the timing of customer shipments and/or Teradata’s operating results. In addition, a significant change in the forecasts to any of these preferred suppliers could result in purchase obligations for components that may be in excess of demand.

X
- References No definition available. + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for commitments and contingencies. + References Reference 1: http://www.xbrl.org/2009/role/commonPracticeRef -Topic 405 -SubTopic 30 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/405-30/tableOfContent Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 440 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 4 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147482648/440-10-50-4 Reference 3: http://www.xbrl.org/2009/role/commonPracticeRef -Topic 450 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/450/tableOfContent Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 954 -SubTopic 440 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147478522/954-440-50-1 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Topic 440 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 4 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org/1943274/2147482648/440-10-50-4 Reference 6: http://fasb.org/us-gaap/role/ref/legacyRef -Topic 440 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/440/tableOfContent + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration