How to Analyse Defence Company Results: Order Books, Execution and Working Capital

A defence-company result is an execution report on a portfolio of long-duration contracts. The order book is potential revenue, but only executable work, completed milestones and customer acceptance become reported revenue and cash. Analysts therefore need to connect orders, production, margins and working capital. Our HAL order-book guide develops the underlying contract bridge in more detail.

Reconstruct the order-book movement

The basic bridge is:

Closing order book = opening order book + new orders − revenue executed − cancellations or scope changes

Company disclosures do not always present every component on the same basis, so document the definition and date. Check whether the reported total includes nominated orders, optional quantities, joint ventures, export orders or contracts awaiting final approvals.

Order-book-to-revenue provides a rough visibility measure. If the closing order book is four times trailing revenue, it does not mean revenue will quadruple. It means the current book represents roughly four years of trailing revenue before considering execution schedules, new orders and constraints.

Test executability rather than admiring the total

For large contracts, record:

• customer and programme;
• total value;
• order date;
• delivery schedule;
• current execution stage;
• imported or vendor-dependent content;
• advances received;
• milestone and acceptance terms; and
• expected margin range, if supportable.

An order can be economically attractive but delayed by design changes, engine availability, testing or customer acceptance. The model should move the delivery schedule when evidence changes rather than preserve the headline order value in the original years.

Use revenue and margin as control totals

Altys’s consolidated trailing-year snapshot through June 2026 recorded revenue of approximately ₹33,785 crore for Hindustan Aeronautics and ₹28,717 crore for Bharat Electronics. Reported TTM growth was about 7.4 per cent for HAL and 19.8 per cent for BEL.

Their EBITDA margins were approximately 29.6 and 28.6 per cent respectively. EBITDA growth was only about 1.1 per cent for HAL and 15.1 per cent for BEL in the same snapshot. The difference between revenue and EBITDA growth points to mix, cost or timing questions. It is not evidence enough to assign a cause.

Revenue recognition matters

Defence contracts can recognise revenue on delivery, milestones or percentage-of-completion principles depending on the contract and accounting policy. Ask:

1. What performance obligation was satisfied?
2. Was customer acceptance required?
3. Did unbilled revenue or contract assets rise?
4. Were liquidated damages, provisions or estimate revisions recorded?
5. Did the quarter contain a concentrated delivery?

Quarterly seasonality is often pronounced. A single weak quarter may reflect acceptance timing, while repeated delays across programmes may indicate a structural execution constraint.

Build the margin bridge by programme mix

Margins can change because of programme mix, indigenisation, imported components, employee costs, provisions, warranty obligations and the stage of a contract.

Separate manufacturing, services, spares, development work and exports where disclosure permits. A high-margin repair or spares mix can lift a quarter without changing the economics of the production backlog. A new programme can begin with lower margin and improve as learning and localisation increase.

Working capital is part of the contract

Advances can fund production before delivery. Inventories and contract assets can then build during execution. Receivables may rise after billing while the company waits for payment.

Track these items together:

• customer advances and contract liabilities;
• inventory, including work in progress;
• contract assets or unbilled revenue;
• trade receivables;
• provisions; and
• operating cash flow.

Positive profit with negative cash is not automatically a red flag in a milestone business, but it requires a contract-level explanation. Persistent growth in inventory or receivables faster than execution deserves attention.

Separate order announcements from model changes

An announced project, request for proposal, approval, letter of intent and signed contract are different stages. The model should not treat them equally.

A disciplined evidence ladder might be:

1. policy or budget intention;
2. formal approval;
3. tender or nomination;
4. signed contract;
5. disclosed delivery schedule;
6. production milestone; and
7. accepted delivery and revenue.

Forecast probability and timing should rise as the programme moves up the ladder.

The quarterly defence checklist

1. Opening and closing order book on a consistent definition.
2. New orders, execution and cancellations.
3. Programme schedules and dependencies.
4. Revenue-recognition milestones.
5. Segment and programme mix.
6. Margin bridge and provisions.
7. Advances, inventory, contract assets and receivables.
8. Operating cash conversion.
9. Capacity and supply-chain constraints.
10. Delivery promises and monitoring dates.

Altys can link the order evidence, reported financials, guidance history and monitoring triggers. The goal is not to predict every delivery. It is to know which contract assumption changed, when it changed and what that does to the model.

Data note: Altys consolidated financial snapshot for the trailing 12 months ended 30 June 2026, available by 13 September 2026. Figures are rounded. Order-book definitions and programme facts must be checked in the corresponding company disclosures.