Loading…

Community Financial System (CBU) backlog: remaining performance obligations

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

Data as of .

Community Financial System backlog history

$0$250M$500M$750MDec 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$1.70M$879M0.0 yrsn/a
30 Jun 2026$1.40M$859M0.0 yrsn/a
31 Mar 2026$2.50M$835M0.0 yrsn/a
31 Dec 2025$1.10M$818M0.0 yrsn/a
30 Sep 2025$1.90M$799M0.0 yrsn/a
30 Jun 2025$1.80M$781M0.0 yrsn/a
31 Mar 2025$2.60M$765M0.0 yrsn/a
31 Dec 2024$1.10M$746M0.0 yrsn/a
30 Sep 2024$2.20Mn/an/an/a
30 Jun 2024$2.60Mn/an/an/a
31 Mar 2024$3.60Mn/an/an/a
31 Dec 2023$800,000$652M0.0 yrsn/a

Questions

What is Community Financial System's backlog?
Community Financial System reported $1.70M of remaining performance obligations at 30 Sep 2026, down 11% from a year earlier and up 21% from the previous quarter. That is 0.0 years of trailing revenue already under contract. Book-to-bill last quarter: 1.00.

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.