Dynacons Systems & Solutions Limited announces a new order win

The Rs 137.15 crore Supreme Court contract is equivalent to approximately 4.42% of DSSL’s latest disclosed Rs 3,104 crore order book. The order value is inclusive of GST ^[1], while the Rs 3,104 crore order book was reported as of Q1 FY27 ^[2]. On the assumption that this contract was not already included in that order-book figure, the pro forma order book would be about Rs 3,241.15 crore, with the new contract representing 4.23% of that amount.

Revenue recognition timeline

The project is scheduled for execution over three years and includes supply, installation, testing and commissioning of 728 servers, together with software, 24x7 support and remote/on-site support throughout the contract period ^[1].

Revenue recognition should therefore occur in stages:

• Hardware and implementation: recognized as servers are supplied, installed, tested, commissioned and the relevant project milestones are completed.
• Support and services: recognized over the three-year support period, subject to the applicable accounting milestones and service delivery.
• Timing: management has stated that revenue follows delivery and project milestones rather than being recognized entirely when the order is won ^[2].

A simple straight-line illustration would imply gross contract value of approximately Rs 45.72 crore per year, or Rs 11.43 crore per quarter, over three years. This is only a mechanical allocation, not company guidance: actual recognition could be front-loaded as server deployment occurs, while support revenue is likely to be spread across the service period. Since the announced value includes GST and no milestone-wise billing or revenue schedule has been disclosed, reported accounting revenue should not be assumed to equal the straight-line GST-inclusive amounts.

The contract’s margin cannot be quantified from the disclosure, and it should not be assumed to earn the company’s recent consolidated EBITDA margin. The Supreme Court project is a blended, infrastructure-heavy engagement: server supply, installation, testing, commissioning, software provisioning, system integration and three years of 24x7 support. Its Rs 137.15 Crore value is inclusive of GST. ^[3]

Comparison with historical margins

• Contract margin: Not disclosed. The company has not provided project-level cost, gross margin, EBITDA margin or margin guidance for this order. Management has also stated that it does not provide margin guidance. ^[2]
• System Integration segment: A separately reported historical EBITDA-margin series for the System Integration segment is not present in the cited disclosures. The closest qualitative reference is to historical company EBITDA margins of approximately 6–7%, but this is not identified as a segment-specific series. ^[4]
• Current consolidated benchmark: DSSL reported consolidated EBITDA margins of 10.6% for FY26, 9.9% in Q1 FY26 and 13.3% in Q1 FY27. ^{[5] [6] [7]}

Analyst read: The project is likely to have a mixed margin profile. The server procurement and deployment component is typically more hardware- and working-capital-intensive, while the three-year support, monitoring and integration component may carry better recurring economics. Therefore, the contract’s blended margin could improve as support revenue becomes a larger share of execution, but there is no evidence to conclude that the initial project margin will match the recent 13.3% consolidated EBITDA margin.

The appropriate comparison is thus directional rather than numeric: the contract appears more aligned with DSSL’s traditional systems-integration economics than with its latest consolidated margin peak, with potential for margin support from the recurring service component. The key missing data is the contract’s hardware-versus-services revenue split and project-level cost structure.

The contract is procurement-intensive and likely requires some working-capital bridging, but the evidence does not establish that DSSL must fund the entire server build upfront. The Supreme Court project is valued at Rs 137.15 Crores including GST and requires supply, installation, testing and commissioning of 728 servers, cables and accessories, followed by three years of support across 728 district courts.^[1] This implies a meaningful initial procurement and deployment requirement rather than a purely service-led contract.

Working-capital exposure

• Inventory/procurement: The hardware scope is substantial, but the contract filing does not state whether DSSL can procure progressively against site-wise milestones, or whether it must purchase all 728 server systems before deployment.^[1]
• Supplier funding: Management has said that, for large contracted projects, back-to-back OEM support is locked at order finalisation, which should reduce speculative inventory risk; however, it does not eliminate the need to bridge procurement, logistics and installation costs before customer collections.^[4]
• Existing balance-sheet position: At Q1 FY27, the latest reported trade-receivable and trade-payable balances carried forward were Rs 602.19 Crores and Rs 445.85 Crores respectively.^{[8] [9]} The implied receivables less payables gap was therefore Rs 156.34 Crores, derived from those balances. Cash and equivalents were Rs 12.88 Crores and total debt was Rs 81.22 Crores at the same reporting point.^{[10] [11]}
• Cash conversion: FY26 reported cash conversion was 30.4%, while operating cash flow was 3.2% of revenue.^{[12] [13]} These figures argue against assuming that a large hardware project will automatically self-fund through internally generated cash.

Payment milestones versus the cash cycle

The BSE contract intimation gives the scope, value and three-year execution period, but it does not provide the advance, procurement, delivery, installation, acceptance, retention or payment milestones.^[1] Consequently, alignment with DSSL’s cash conversion cycle cannot be demonstrated.

The key distinction is:

• Favourable structure: customer advance or payment on purchase-order placement, followed by billing on delivery and commissioning. This would allow customer cash to fund much of the OEM procurement.
• More demanding structure: DSSL pays OEMs upfront, invoices only after installation or acceptance, and faces retention or delayed government payments. That would extend the cash cycle and increase reliance on payables, debt or other financing.

Analyst inference: The contract creates a material working-capital risk, but not necessarily a speculative-inventory risk, because the equipment is tied to a specific customer deployment and management indicates back-to-back OEM arrangements. The decisive missing information is the milestone schedule and the extent of customer advances; without it, the project’s cash profile cannot be matched confidently to the reported receivables-payables cycle.