Loading…

Atlassian (TEAM) backlog: remaining performance obligations

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

Data as of .

Atlassian backlog history

$0$2B$4B$6BDec 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$4.70B$6.91B0.7 yrs$2.39B
30 Jun 2026$4.80B$6.57B0.7 yrs$2.66B
31 Mar 2026$4.00B$6.19B0.6 yrs$2.41B
31 Dec 2025$3.80B$5.76B0.7 yrs$2.43B
30 Sep 2025$3.30B$5.46B0.6 yrs$2.28B
30 Jun 2025$3.30B$5.22B0.6 yrs$2.48B
31 Mar 2025$2.90B$4.96B0.6 yrs$2.37B
31 Dec 2024$2.70B$4.79B0.6 yrs$2.20B
30 Sep 2024$2.30B$4.57B0.5 yrs$2.01B
30 Jun 2024$2.40B$4.36B0.6 yrs$2.11B
31 Mar 2024$2.30B$4.17B0.6 yrs$1.96B
31 Dec 2023$1.90B$3.89B0.5 yrs$1.65B

Questions

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