India's defence procurement reforms have brought roughly 16,000 MSMEs into indigenous supply chains through positive indigenisation lists, domestic sourcing mandates, and platforms like SRIJAN and iDEX. Yet the payment architecture these firms enter, governed by CGDA accounting protocols, DGQA inspection sequencing, and milestone-based contract structures, was designed for large PSU-to-PSU settlement cycles. Why does defence procurement liberalisation consistently expand the supplier base without extending the financial infrastructure that makes MSME participation financially viable?
India's defence indigenisation push accelerated from 2016 onwards. Positive Indigenisation Lists were published in tranches. The Defence Acquisition Procedure was revised in 2020 to reserve categories for Indian vendors. The SRIJAN portal identified thousands of imported components that domestic firms could substitute. iDEX created a pipeline for startups to enter the defence innovation space. Each of these interventions expanded the procurement aperture. None of them touched the payment machinery that sits on the other side of the contract.
That payment machinery is structurally distinct from civilian procurement. In civilian government purchasing, payments flow through the Pay and Accounts Officer into the PFMS architecture, a system that, for all its delays, at least operates under a recognisable disbursement logic. Defence payments operate through an entirely separate accounting chain. The Controller General of Defence Accounts maintains its own network of Principal Controllers spread across commands and production units. Every payment claim passes through a pre-audit function before release. The state built an indigenisation architecture on top of a payment system that was never consulted during the design. The MSME Ministry drafted the policy intent; the CGDA inherited the disbursement obligation.
The Integrated Financial Advisor is the institutional node inside every Defence HQ and Defence PSU whose concurrence is operationally required at every milestone, and whose queries are the single most common source of payment delay that MSME contractors report. The IFA is an officer posted from the Indian Defence Accounts Service who sits inside the Service HQ or the procurement authority's own architecture, holds financial concurrence authority over scheme proposals, contract modifications, and milestone payments, and reports administratively to the MoD Finance Division while functioning operationally inside the sponsoring organisation. For civilian procurement, the Financial Advisor architecture in a ministry serves a similar function; for defence procurement, the IFA operates at a more granular level, with concurrence required not just at the scheme level but at individual milestone-payment level.
An MSME supplier whose milestone delivery has been accepted by DGQA and certified by the user unit still waits for the IFA's concurrence before the CGDA's pre-audit function releases the payment. The IFA's institutional orientation is specifically fiscal caution, and the questions the IFA raises reflect the institutional exposure the IFA carries under CAG audit and internal audit review. A query from the IFA on whether a milestone deliverable was strictly within the contractual specifications, whether price escalation has been calculated per contract terms, or whether the milestone certification chain has documented the specific quality assurance steps prescribed, is a query that the contractor must answer in writing, and the clock does not start moving until the answer is accepted.
The reform that MSME industry associations have consistently represented on, the establishment of MSME-specific payment cells with IFA time-bounds, has been acknowledged at the MoD level but has not been operationalised at the granular IFA level where the delays actually sit. The institutional observation is that defence MSME payment reform has focused on the sourcing architecture and the contract architecture; the financial concurrence architecture, which is where the delay actually sits, has not been reformed at the same tempo.
The deeper structural problem is that defence contracts do not generate the kind of clean, unconditional invoices that platforms like TReDS are designed to discount. A typical MSME supplying components to a defence PSU operates under a milestone-based contract with inspection gates administered by the Directorate General of Quality Assurance. Goods are manufactured, delivered to the buyer's premises, and then held in a quality assurance queue. Payment is not triggered by delivery. Payment is triggered by DGQA clearance, which operates on its own institutional timeline with its own staffing constraints and its own procedural sequencing. The MSME's working capital is locked not by a payment delay in the administrative sense, but by an inspection architecture that sits between delivery and the first accounting entry. This is the distinction that most discussions of MSME liquidity in defence miss entirely. The delay is not bureaucratic sloth. It is an embedded feature of the quality assurance regime, and no invoice discounting platform can accelerate what is, by design, a sequential compliance gate.
The indigenisation push asked MSMEs to capitalise themselves into defence manufacturing; the payment architecture they enter operates on a tempo their working capital cycles were not designed to absorb. The indigenisation push created a supplier base; the payment machinery ensures that base remains perpetually fragile.
The proposal to extend TReDS into defence procurement, discussed at a CGDA-chaired meeting with MSME Ministry and industry representatives in April 2026, acknowledges this mismatch. But the composition of that meeting reveals why resolution is unlikely to be swift. Three distinct institutional domains sat at the table: defence accounts (CGDA), MSME policy (MSME Ministry), and RBI-regulated financial infrastructure (TReDS platforms). Each domain operates under its own compliance logic, its own reporting hierarchy, and its own definition of what constitutes a payable obligation. The CGDA's accounting standards require pre-audit verification before a payment claim is recognised. TReDS requires an accepted invoice, a buyer-confirmed obligation, to initiate discounting. The question of when a defence invoice becomes "accepted" in TReDS terms, given DGQA inspection sequencing and CFA-level sanction requirements, is not a technology problem. It is a definitional problem across three institutional vocabularies that have never been harmonised. This is a coordination breakdown dressed as a liquidity problem, and the meeting format itself, three ministries, no single owner, no binding outcome mechanism, confirms the diagnosis.
There is a further layer that receives almost no attention. Defence PSUs, the primary buyers in this supply chain, are themselves subject to budgetary release schedules from the Ministry of Defence. HAL, BEL, BEML, and others receive their operational funds through a budget allocation cycle that does not always align with vendor payment timelines. When MoD's capital expenditure releases are bunched in the final quarter, the PSU's own payment capacity is lumpy. The MSME at the bottom of this chain absorbs the liquidity shock of every upstream scheduling mismatch. Extending TReDS to this ecosystem without addressing the budget release cadence that governs PSU cash positions would create a discounting platform where the underlying buyer's own liquidity is seasonally constrained. The financier discounting the invoice would be pricing not just MSME credit risk, but the budgetary rhythm of the Indian defence establishment.
The 45-day payment mandate under Section 9 of the MSMED Act technically applies to all buyers, including government entities. But defence contracts routinely structure payment obligations around milestones, inspections, and stage-wise deliveries that make the 45-day clock ambiguous from the start. When does the clock begin: at delivery, at DGQA inspection completion, at CFA-level acceptance, at pre-audit clearance by the PCDA? Each interpretation yields a different payment timeline, and the Act does not adjudicate between them for defence-specific contracts. The statutory protection that was supposed to shield MSMEs from payment delays dissolves the moment it encounters a contract structure where "delivery" and "acceptance" are separated by an institutional process that neither the MSME nor the buyer fully controls.
Domestic defence production has grown from approximately ₹46,430 crore in 2014-15 to ₹1.27 lakh crore in 2023-24. The policy ambition is working. The supplier base is expanding. The production numbers are real. What remains unreformed is the financial plumbing that connects a completed order to cash in an MSME's account. Until that plumbing is treated as a procurement reform problem rather than a banking infrastructure problem, the indigenous defence base will continue to grow in number while remaining structurally undercapitalised.