Summary

  • Leonardo DRS reported US$8.787 billion of June 2026 backlog and the same US$8.787 billion of remaining performance obligations, but it split backlog into US$5.092 billion funded and US$3.695 billion unfunded firm orders.
  • The company expects about 22% of RPO to become revenue in the next six months, while roughly 45% relates to Navy electric-power and propulsion contracts expected over as long as 11 years. Neither disclosure is a cash-collection or appropriation schedule.

The attractive version of the DRS quarter begins with one very large number. Revenue rose to US$913 million in the second quarter, bookings were US$1.085 billion, and funded backlog reached a record US$5.092 billion. The 10-Q then gives total backlog as US$8.787 billion. In the revenue note, it gives total remaining performance obligations—RPO—as US$8.787 billion too.

It would be easy to call the number a revenue runway and stop there. That would collapse four ledgers that the filing keeps separate: a firm order, authorization or appropriation, accounting revenue and cash. The equality between the two totals does not erase those differences. It makes the definitions more important.

DRS defines funded backlog as the revenue value of orders under existing contracts for which funding is appropriated or otherwise authorized, less revenue already recognized. That balance was US$5.092 billion at 30 June. The company defines unfunded backlog as the revenue value of firm orders under existing contracts for which funding has not yet been appropriated, again less revenue already recognized. That balance was US$3.695 billion.

“Unfunded” does not mean imaginary. The company calls these firm orders under existing contracts. But it also does not mean that the amount has already crossed the appropriation or authorization boundary that DRS uses for funded backlog. The financial consequence is not supplied by the label alone. The filing does not allocate the US$3.695 billion by program, identify the appropriation path for each order, or disclose when particular amounts will become funded.

The same caution applies to RPO. The company says US$8.787 billion of transaction price is allocated to performance obligations not yet satisfied or only partly satisfied. It expects approximately 22% of that June balance to be recognized as revenue over the next six months, with the rest thereafter. That is an expectation about revenue recognition, not a promise that 22% will be appropriated, shipped, accepted, invoiced or collected in the same period.

The long end has a defined but still limited description. Approximately 45% of RPO relates to long-term U.S. Navy electric-power and propulsion contracts expected to be recognized over a span of up to 11 years. “Up to 11 years” is a recognition horizon for a portion of the balance. It is not an eleven-year annual-revenue schedule. The filing does not state how much of the Navy portion is funded, which years carry the work, what cash arrives in each year, or how margins develop by program.

The current-period results show why a single conversion rate would be false precision. The 10-Q attributes Q2 revenue growth to conversion of funded backlog and higher demand. It also reports US$270 million of cash at quarter end and US$31 million of net operating cash use for the first six months. The earnings release reports US$6 million of second-quarter free cash flow and no outstanding borrowings under the credit facility at quarter end. Those are distinct time periods and distinct measures. They cannot be divided into US$8.787 billion to create a yield, a collection rate or a financing conclusion.

Contract balances reinforce the separation. At 30 June, DRS reported US$1.002 billion of contract assets and US$598 million of contract liabilities. It recognized US$320 million of revenue during the first half that had been in the opening contract-liability balance. Those balances say that billing and recognition occur on different schedules for at least part of the portfolio. They do not reconcile the RPO total to the funded/unfunded split, cash receipts or future working-capital needs.

The management question is consequently narrower than “how big is the backlog?” Readers should ask which ledger is moving. A rise in funded backlog makes the authorized-work portion larger. A rise in unfunded backlog adds firm orders whose appropriation state remains unresolved. A change in RPO can alter the revenue-recognition horizon. A change in contract assets, liabilities, receivables or cash addresses a different part of the conversion path.

The Q2 release also announced the proposed US$450 million Raft acquisition. The materials used here do not state which cash, credit, debt or operating source funds that transaction. It belongs outside any arithmetic based on funded backlog, RPO or the quarter-end cash balance.

The positive evidence is real: DRS has a record funded backlog, bookings above quarterly revenue, and an identified long-duration Navy program population. The missing evidence is equally real: no program-level appropriation schedule, no funded-state allocation for the 22% recognition expectation, and no cash bridge. Treating the headline as a cash runway would turn the disclosed record into a claim the record does not make.

Sources