Loading…

Omnicom (OMC) backlog: remaining performance obligations

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

Data as of .

Omnicom backlog history

$0$10B$20BDec 2025Mar 2026Jun 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$426M$24.8B0.0 yrs$2.31B
30 Jun 2026$456M$22.4B0.0 yrs$2.13B
31 Mar 2026$425M$19.8B0.0 yrs$1.95B
31 Dec 2025$498M$17.3B0.0 yrs$1.73B

Questions

What is Omnicom's backlog?
Omnicom reported $426M of remaining performance obligations at 30 Sep 2026 and down 7% from the previous quarter. That is 0.0 years of trailing revenue already under contract. Book-to-bill last quarter: 0.99.

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.