Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian defence manufacturers reconcile under Defence Acquisition Procedure 2020 with milestone-based payments across five procurement categories, offset-discharge obligations of 30% on contracts above ₹2,000 crore, MoD vendor codes alongside PAN, Performance Bank Guarantees of 5-10% held through warranty, retention money sitting 24-36 months past delivery, customs duty on imported components, and Section 393(1)(a) contractor TDS on every sub-contracting payment.
Reconcile each contract against DAP-2020 category-specific milestone schedule, track offset discharge against the 30% obligation using Defence Offset Management Wing documentation, maintain dual identifier (MoD vendor code + PAN) on every invoice, age PBG by validity period with 90/60/30 day expiry alerts, age retention money by contract milestone with release-request trigger at warranty expiry, deduct Section 393(1)(a) code 1002 on sub-contractor payments and Section 413 code 1062 on foreign technical-service payments.
Contract master keyed by MoD contract number with DAP category tag, milestone schedule, offset obligation amount, PBG register and retention schedule; vendor master with MoD vendor code, PAN, GSTIN and MSME flag; offset discharge register with multiplier rules; customs duty register per imported component shipment; Section 393(1)(a) deduction matrix with code 1002 default.
A weekly defence-contract dashboard showing milestone-billed-vs-paid by contract, offset discharge percentage against obligation, PBG status with expiry alerts, retention money aged by milestone and contract, customs duty reconciled against landed cost, monthly Section 393 TDS challan tied to sub-contractor payments by code 1002.
A DPSU vendor in Bangalore handling a ₹150 crore Buy (Indian-IDDM) contract for sub-system supply closes April books and pulls the contract ageing: ₹15 crore advance received and adjusted against milestone billing, ₹78 crore billed across four delivered milestones, ₹6.4 crore pending milestone certification on the fifth, ₹11.25 crore retention money expected to sit on MoD’s books through a 30-month warranty period, and a ₹15 crore PBG against the same contract auto-extending every six months until warranty expiry. Each piece carries a different reconciliation discipline and defence manufacturing reconciliation India runs unlike any commercial-sector reconciliation — the buyer’s payment behaviour is rule-bound, slow, and document-intensive, and the vendor’s books have to mirror that exactly.
Quick reference
| Item | Value |
|---|---|
| Parent procurement framework | Defence Acquisition Procedure 2020 (DAP-2020) |
| Procurement categories | Buy (Indian-IDDM), Buy (Indian), Buy and Make (Indian), Buy (Global), Buy and Make |
| Sectoral authority | Ministry of Defence (MoD) + DGQA + service HQs + DPSUs |
| Offset threshold | Contracts above ₹2,000 crore; offset obligation 30%+ of contract value |
| Typical PBG | 5% to 10% of contract value, held through warranty (often 24-36 months) |
| Typical retention | 5% to 10% of contract value, released at final acceptance / warranty expiry |
| Startup channel | iDEX (Innovations for Defence Excellence) + Mission DefSpace |
| Key TDS codes | 1002 (Section 393(1)(a) contractor), 1012 (Section 393(1)(k) purchase), 1062 (Section 413 non-resident) |
DAP-2020 categories and their cash-flow profiles
Defence Acquisition Procedure 2020 organises capital procurement into five categories — each with its own approval ladder, indigenous content thresholds, and milestone payment structure:
- Buy (Indian-IDDM) — indigenously designed, developed and manufactured, with at least 50% indigenous content. Deepest milestone gating, longest payment cycle, highest documentation burden, and most favourable category for an Indian vendor when the DPSU’s R&D base supports it.
- Buy (Indian) — manufactured in India with at least 50% indigenous content but not necessarily indigenously designed.
- Buy and Make (Indian) — Buy phase with a foreign OEM followed by Make phase under licence with an Indian production agency.
- Buy (Global) — global vendors, USD-denominated payments common, Section 413 withholding considerations on technical-service components.
- Buy and Make — foreign OEM transfers technology to an Indian PSU or licensed manufacturer.
Reconciliation must encode the category at contract-master level because the milestone definitions, PBG requirements and offset applicability all vary by category.
The reconciliation rails
Rail 1 — Milestone-based payment reconciliation
A defence contract is structured as: advance (typically 10% against an advance bank guarantee), milestone payments distributed across delivery stages (60-80% across design freeze, first article inspection, type approval, bulk production milestones, factory acceptance test, site acceptance test, deployment), and retention (5-10%) released at final acceptance or warranty expiry.
Reconciliation runs a milestone register per contract: milestone description, scheduled date, contractual amount, billed amount, invoice number, certification status, payment date, payment amount, variance. Common exceptions: milestone billed before certification (parked); milestone certified but payment delayed beyond contractual window (raise interest-on-delayed-payment clause); milestone partially paid against a buyer dispute on liquidated damages (LD) for delay. LD reconciliation itself is a sub-rail — the buyer typically deducts LD at 0.5% per week up to a 5% cap, and the vendor’s books must mirror the LD deduction or contest it.
Rail 2 — Offset-clause discharge
For contracts above ₹2,000 crore, DAP-2020 requires the foreign OEM (in Buy (Global) or Buy and Make) to discharge offsets equal to at least 30% of contract value. Discharge is achieved through eligible purchases from Indian DPSUs and MSMEs, technology transfer to Indian entities, or investment into the defence ecosystem, with multipliers applied to specific categories (MSME purchases often carry a 1.5x multiplier, critical technology transfer higher).
An Indian recipient of offset-attributed purchases must maintain offset documentation per the Defence Offset Management Wing requirements — these purchases attract Defence Offset Management Wing audits and offset-credit certificates that the foreign OEM uses to discharge against its obligation. Reconciliation at the Indian recipient ties each offset-attributed PO/invoice to its offset-credit certificate.
Rail 3 — MoD vendor code alongside PAN
MoD maintains a vendor master keyed by a MoD vendor code, issued at vendor registration with DGQA, the SHQ acquisition wing, or the DPSU contracting authority. PAN, GSTIN and MSME registration are captured separately. The MoD payment release runs against the MoD vendor code while the TDS deposit and GST filing run against PAN/GSTIN. The vendor’s books must carry both identifiers on every invoice; a common exception in the first months of a vendor relationship is a correct MoD code with a PAN that doesn’t match the income tax department’s records, blocking TDS credit until corrected.
Rail 4 — Performance Bank Guarantee tracking
PBG of 5-10% of contract value is submitted at contract signing, often with auto-extension clauses, and held through the warranty period (typically 24 to 36 months past final acceptance). Reconciliation maintains a PBG register per contract: issuing bank, instrument number, face value, validity period, auto-extension clause, expiry alerts at 90/60/30 days. A lapsed PBG is a covenant breach and a material reconciliation exception that can block subsequent milestone releases on the same or other contracts with the same buying authority.
Rail 5 — Retention money
Retention of 5-10% of contract value held until final acceptance and warranty expiry creates a long-tail receivable. Retention amounts can sit on the buyer’s books for 24-36 months past physical delivery. Reconciliation ages each retention by contract milestone, links to the corresponding PBG, and triggers a release-request workflow at warranty expiry. The general pattern is covered at retention money reconciliation.
Rail 6 — Tax overlay and customs duty
Section 393(1)(a), code 1002 — contractor TDS on every sub-contracting payment, civil works, transport, AMC and similar contracts at 1%/2%, threshold ₹30,000 per transaction and ₹1 lakh aggregate. See Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092 India.
Section 393(1)(k), code 1012 — purchase-of-goods TDS at 0.1% above ₹50 lakh aggregate per vendor PAN per year, when vendor turnover exceeds ₹10 crore. See Section 393(1)(k) purchase-of-goods TDS for manufacturers.
Section 413, code 1062 — withholding on payments to foreign technical-service providers, DTAA rates apply with TRC, Form 15CA/15CB required.
Customs duty reconciliation — imported components for indigenisation programmes carry concessional customs duty under specific defence-import notifications. Each shipment must reconcile the bill of entry, customs duty paid (BCD, IGST on import, SWS), and the landed cost booked in the project ledger. Misclassification under HS code can lead to retrospective customs duty demand.
Cross-era note: Form 26AS data from before 1 April 2026 carries legacy section references (194C for code 1002, 194Q for code 1012, 195 for code 1062) — reconciliation against historical data must keep the cross-reference live for at least one full tax-year cycle.
iDEX and Mission DefSpace startup contracting
The Innovations for Defence Excellence (iDEX) framework and Mission DefSpace channel small contracts (often below ₹50 crore) to startups and MSMEs with a faster procurement cycle. The reconciliation pattern is similar to DAP but with simplified milestone gating and lighter offset/PBG mechanics — startups typically face shorter payment cycles but tighter delivery windows.
Worked example — DPSU vendor on a ₹150 crore contract
A DPSU vendor handling a ₹150 crore Buy (Indian-IDDM) sub-system supply contract over a 30-month execution period plus 30-month warranty:
- Advance received: ₹15 crore (10%) against advance bank guarantee
- Milestone billing structure: six milestones at 12-13% each = ₹120 crore total milestone value
- Retention: ₹11.25 crore (7.5%) released at warranty expiry month 60
- PBG: ₹15 crore (10%) held through warranty, auto-extending every six months
- Sub-contracting spend on this contract: ~₹45 crore over execution; monthly Section 393(1)(a) code 1002 TDS deduction ~₹4-7 lakh
- Imported critical components: ~₹18 crore, customs duty reconciled per bill of entry under defence-import notification
- LD risk: 0.5% per week up to 5% cap = up to ₹7.5 crore exposure on the contract
The structured reconciliation closes weekly with milestone-billed-vs-paid, PBG validity, retention ageing, and LD exposure all visible.
For the current DAP framework and offset policy, the Ministry of Defence (MoD) is the authoritative source.
What automated reconciliation changes
Manual defence-vendor reconciliation across six rails is a 10-14 day month-end exercise at a multi-contract DPSU. Purpose-built reconciliation software India treats each rail as a structured variance stream. TransactIG carries 24+ industry presets, including a configuration that handles DAP-category-aware milestone tracking, offset-discharge ledgers, dual-identifier vendor masters, PBG expiry alerts, retention ageing, and the Section 393/413 deduction map. Customer outcomes include match-rate improvement from 51% to 88%. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound three-way match rail see three-way matching software India.