Loading…

Lufax (6623.HK) backlog: remaining performance obligations

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

Data as of .

Lufax backlog history

CN¥0CN¥20BCN¥40BDec 2019Dec 2020Dec 2021Dec 2022Dec 2023Dec 2024Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in CNY. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
31 Dec 2024CN¥5.06BCN¥8.16B0.6 yrsn/a
31 Dec 2023CN¥8.63BCN¥15.3B0.6 yrsn/a
31 Dec 2022CN¥18.9BCN¥29.2B0.6 yrsn/a
31 Dec 2021CN¥30.8BCN¥38.3B0.8 yrsn/a
31 Dec 2020CN¥33.8BCN¥41.2B0.8 yrsn/a
31 Dec 2019CN¥43.5BCN¥41.9B1.0 yrsn/a

Questions

What is Lufax's backlog?
Lufax reported CN¥5.06B of remaining performance obligations at 31 Dec 2024, down 41% from a year earlier. That is 0.6 years of trailing revenue already under contract.
How fast does Lufax's backlog turn into revenue?
Over the last twelve months Lufax recognised revenue equal to about 95% 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.