Loading…

Sap (SAP.DE) backlog: remaining performance obligations

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

Data as of .

Sap backlog history

€0€25B€50B€75BDec 2018Dec 2019Dec 2020Dec 2021Dec 2022Dec 2023Dec 2024Dec 2025Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in EUR. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
31 Dec 2025€90.5B€36.8B2.5 yrsn/a
31 Dec 2024€78.4B€34.2B2.3 yrsn/a
31 Dec 2023€58.7B€31.2B1.9 yrsn/a
31 Dec 2022€46.9B€30.9B1.5 yrsn/a
31 Dec 2021€39.9B€27.8B1.4 yrsn/a
31 Dec 2020€33.4B€27.3B1.2 yrsn/a
31 Dec 2019€33.3B€27.6B1.2 yrsn/a
31 Dec 2018€31.3B€24.7B1.3 yrsn/a

Backlog compared with peers

IT services & cloud software

CompanyBacklog1-year growthCoverageAs of
Sap SAP.DE€90.5B+15%2.5 yrs31 Dec 2025
Infosys INFY.NS$12.3B+13%0.6 yrs31 Mar 2025
Wipro WIPRO.NS₹365B+14%0.4 yrs31 Mar 2025

Questions

What is Sap's backlog?
Sap reported €90.5B of remaining performance obligations at 31 Dec 2025, up 15% from a year earlier. That is 2.5 years of trailing revenue already under contract.
How fast does Sap's backlog turn into revenue?
Over the last twelve months Sap recognised revenue equal to about 47% 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.