Loading…

Teradata (TDC) backlog: remaining performance obligations

How much revenue Teradata already has under contract, how fast it converts, and who it is with.

Data as of .

Teradata backlog history

$0$1B$2BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025Jun 2026Sep 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Sep 2026$2.00B$1.67B1.2 yrs$477M
30 Jun 2026$2.03B$1.69B1.2 yrs$572M
31 Mar 2026$2.03B$1.69B1.2 yrs$615M
31 Dec 2025$2.18B$1.66B1.3 yrs$544M
30 Sep 2025$1.86B$1.65B1.1 yrs$539M
30 Jun 2025$1.84B$1.68B1.1 yrs$533M
31 Mar 2025$1.98B$1.70B1.2 yrs$561M
31 Dec 2024$2.30B$1.75B1.3 yrs$522M
30 Sep 2024$2.18B$1.80B1.2 yrs$495M
30 Jun 2024$2.30B$1.80B1.3 yrs$539M
31 Mar 2024$2.40B$1.82B1.3 yrs$586M
31 Dec 2023$2.68B$1.83B1.5 yrs$592M

Questions

What is Teradata's backlog?
Teradata reported $2.00B of remaining performance obligations at 30 Sep 2026, up 7% from a year earlier and down 1% from the previous quarter. That is 1.2 years of trailing revenue already under contract. Book-to-bill last quarter: 0.93.
How fast does Teradata's backlog turn into revenue?
Over the last twelve months Teradata recognised revenue equal to about 83% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.