Infosys reported $12.3B of remaining performance obligations at 31 Mar 2025, up 13% from a year earlier. That is 0.6 years of trailing revenue already under contract.
Over the last twelve months it turned about 177% of its opening backlog into revenue (12-month conversion).
Twelve-month book-to-bill: 1.07, i.e. 1.07 of new orders for every 1 of revenue recognised.
Backlog growth minus revenue growth: +9 points — orders are running ahead of revenue.
The latest filed figure is more than 200 days old.
Infosys backlog history
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Infosys reported $12.3B of remaining performance obligations at 31 Mar 2025, up 13% from a year earlier. That is 0.6 years of trailing revenue already under contract.
How fast does Infosys's backlog turn into revenue?
Over the last twelve months Infosys recognised revenue equal to about 177% 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.