Loading…

OneSpan (OSPN) backlog: remaining performance obligations

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

Data as of .

OneSpan backlog history

$0$100M$200MDec 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$113M$253M0.4 yrs$59.2M
30 Jun 2026$100M$246M0.4 yrs$63.3M
31 Mar 2026$98.0M$246M0.4 yrs$63.1M
31 Dec 2025$106M$243M0.4 yrs$74.2M
30 Sep 2025$103M$241M0.4 yrs$53.4M
30 Jun 2025$101M$241M0.4 yrs$57.4M
31 Mar 2025$96.4M$242M0.4 yrs$54.8M
31 Dec 2024$104M$243M0.4 yrs$70.9M
30 Sep 2024$91.0M$245M0.4 yrs$51.3M
30 Jun 2024$98.1M$248M0.4 yrs$59.3M
31 Mar 2024$87.7M$242M0.4 yrs$59.5M
31 Dec 2023$92.4M$235M0.4 yrs$73.5M

Questions

What is OneSpan's backlog?
OneSpan reported $113M of remaining performance obligations at 30 Sep 2026, up 10% from a year earlier and up 13% from the previous quarter. That is 0.4 years of trailing revenue already under contract. Book-to-bill last quarter: 1.20.
How fast does OneSpan's backlog turn into revenue?
Over the last twelve months OneSpan recognised revenue equal to about 249% 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.