Loading…

RingCentral (RNG) backlog: remaining performance obligations

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

Data as of .

RingCentral 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.70B$2.62B1.0 yrs$296M
30 Jun 2026$2.70B$2.58B1.0 yrs$295M
31 Mar 2026$2.70B$2.55B1.1 yrs$257M
31 Dec 2025$2.60B$2.52B1.0 yrs$269M
30 Sep 2025$2.60B$2.49B1.0 yrs$262M
30 Jun 2025$2.60B$2.46B1.1 yrs$263M
31 Mar 2025$2.60B$2.43B1.1 yrs$249M
31 Dec 2024$2.60B$2.40B1.1 yrs$262M
30 Sep 2024$2.60B$2.36B1.1 yrs$261M
30 Jun 2024$2.60B$2.31B1.1 yrs$262M
31 Mar 2024$2.50B$2.25B1.1 yrs$247M
31 Dec 2023$2.40B$2.20B1.1 yrs$234M

Questions

What is RingCentral's backlog?
RingCentral reported $2.70B of remaining performance obligations at 30 Sep 2026, up 4% from a year earlier and flat from the previous quarter. That is 1.0 years of trailing revenue already under contract. Book-to-bill last quarter: 1.00.
How fast does RingCentral's backlog turn into revenue?
Over the last twelve months RingCentral recognised revenue equal to about 99% 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.