Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Defence contracts over 3-7 year programmes run through 5-9 milestone payment stages (advance through SAT and retention release), with MoD vendor code carried alongside PAN, advance bank guarantee against the 10-15% advance, GST time-of-supply splitting goods/services per milestone, Section 393(1)(a) code 1002 TDS on sub-contractor pay, Section 393(1)(k) code 1012 on purchase, Section 413 code 1062 on any foreign technical-service payment, advance recovery scheduled against later milestones, and ARC/RPC release certificate closing 30+ months after final acceptance.
Encode milestone schedule per contract with deliverable, buyer acceptance step and payment trigger, maintain dual identifier (MoD vendor code + PAN) on every invoice, age milestone-billed vs paid against contract calendar, run advance bank guarantee with reducing exposure against recovery schedule, apply GST time-of-supply per milestone leg (goods at invoice, services at advance receipt), deduct Section 393(1)(a) code 1002 on subcontractor invoices and Section 393(1)(b) code 1003 on professional fees, manage ARC/RPC release-request lifecycle after warranty expiry.
Contract master with milestone schedule, deliverable type per milestone, payment percentage per milestone, retention rate, PBG rate, warranty period; vendor master with MoD vendor code, PAN, GSTIN, MSME flag; advance bank guarantee register with face value and reducing-balance schedule; GST time-of-supply rule per milestone leg; Section 393(1)(a)/(b)/(k) vendor rate matrix; ARC/RPC release-request workflow; CDA (Controller of Defence Accounts) payment-cycle tracker.
A weekly defence-contract reconciliation dashboard per contract showing milestone-billed vs paid with stage detail, MoD vendor code and PAN cross-reference status, advance balance with recovery schedule progress, GST time-of-supply applied per leg, monthly Section 393 TDS challan tied to subcontractor pay, ARC/RPC release-request lifecycle status, CDA payment ageing, and total working-capital position across active contracts.
A defence systems supplier in Hyderabad holding a ₹200 crore Buy (Indian-IDDM) contract for an electronic warfare sub-system pulls the milestone ledger at the close of Year 2: ₹20 crore advance received against advance bank guarantee, with ₹8.4 crore already recovered through Milestones 1 and 2 (₹11.6 crore advance still outstanding); ₹38 crore billed across two completed milestones (design freeze and first-article delivery); ₹14.2 crore pending CDA payment processing on Milestone 3 (type approval); and a ₹4.6 crore monthly subcontractor pay run with Section 393(1)(a) code 1002 TDS at 2% deposited quarterly. The MoD vendor code (issued by DGQA at registration) and the company’s PAN sit side-by-side on every invoice; the GST time-of-supply rule splits each milestone between goods and service consideration; and the contract runs 24 more months to SAT plus 30 months of warranty before retention release through ARC. The defence milestone payment reconciliation India stack is a multi-year, multi-stage, multi-identifier ledger that has to be reconciled weekly to keep working capital visible.
Quick reference
| Item | Value |
|---|---|
| Governing framework | Defence Acquisition Procedure 2020 (DAP-2020) |
| Typical contract tenor | 3-7 years from award to final acceptance |
| Typical advance | 10-15% against advance bank guarantee |
| Milestone payment stages | 5-9 typical (advance, design freeze, prototype/first article, type approval/FAT, bulk production, SAT, final acceptance) |
| Typical retention | 5-10% per progress payment |
| Typical PBG | 5-10% of contract value |
| Warranty period | 24-36 months from final acceptance |
| Payment processor | Controller of Defence Accounts (CDA) for most service contracts |
| Vendor identification | MoD vendor code (issued by DGQA/SHQ/DPSU) + PAN |
| GST law on goods advance | Notification 66/2017 — no GST at advance receipt for goods |
| Key TDS codes | 1002 (Section 393(1)(a) contractor), 1003 (Section 393(1)(b) professional), 1012 (Section 393(1)(k) purchase), 1062 (Section 413 non-resident) |
How does a defence contract’s payment structure actually look
A typical ₹200 crore Buy (Indian-IDDM) contract over 48 months runs through seven payment milestones:
| Milestone | Trigger | % of contract | Cumulative |
|---|---|---|---|
| Advance | Contract signing + advance bank guarantee | 10% (₹20 crore) | 10% |
| M1 — Design freeze | Design package approved by buying agency | 8% (₹16 crore) | 18% |
| M2 — First article delivery | Prototype delivered and inspected | 15% (₹30 crore) | 33% |
| M3 — Type approval / FAT | Factory acceptance test passed | 20% (₹40 crore) | 53% |
| M4 — Bulk production batch 1 | First production batch delivered | 17% (₹34 crore) | 70% |
| M5 — Bulk production batch 2 | Second batch delivered | 15% (₹30 crore) | 85% |
| M6 — SAT / Final acceptance | Site acceptance and commissioning | 10% (₹20 crore) | 95% |
| Retention release | Warranty expiry + ARC | 5% (₹10 crore) | 100% |
Each milestone is paired with a defined deliverable, an inspection/acceptance step by the buying agency (DGQA, user formation, designated test agency), and a payment authorisation routed through the CDA (Controller of Defence Accounts) for actual disbursement. The CDA’s processing cycle typically runs 30-90 days from milestone certification to bank credit.
How does the MoD vendor code coexist with PAN
MoD maintains a vendor master keyed by a MoD vendor code, distinct from PAN. The code is issued at vendor registration by:
- DGQA — for quality-assurance-approved vendors
- SHQ acquisition wings — Army HQ acquisition wing, Naval HQ acquisition wing, Air HQ acquisition wing, Coast Guard HQ
- DPSU contracting authorities — when a DPSU (HAL, BEL, BEML, BDL, Mazagon Dock, GRSE, etc.) sub-contracts to private industry
The MoD vendor code is used for:
- Payment routing within the CDA system
- Contract assignment tracking
- Performance history (rating, past disputes)
- Eligibility for future tenders
PAN remains the statutory tax identifier — for TDS deposit by the buyer (where applicable), for Form 26AS reflection, for income-tax return filing. Both must appear correctly on every invoice. A reconciliation common exception in the first months of a vendor’s onboarding is one of:
- Correct PAN, incorrect MoD vendor code: payment may route to a wrong vendor’s account
- Correct MoD vendor code, incorrect PAN: TDS reflects incorrectly in 26AS
- PAN of parent entity vs PAN of contracting subsidiary: cross-entity payment / tax confusion
Reconciliation must validate both identifiers on every invoice and maintain the cross-reference in the vendor master.
How is GST time-of-supply applied across milestones
Section 13 of the CGST Act governs time of supply. Notification 66/2017 exempts goods-supply advance from GST at receipt; service-supply advance triggers GST on receipt under the literal Section 13 rule.
Defence contracts are typically composite — each milestone carries some goods consideration (deliverable hardware) and some service consideration (engineering, integration, testing). The milestone payment treatment must split:
- Goods leg of the milestone: GST triggers at the invoice/dispatch event, not at advance
- Service leg of the milestone: GST triggers at advance receipt (if structured as advance) or at invoice (if structured as invoiced service)
A ₹40 crore Milestone 3 payment for type approval, where the FAT certifies the prototype and 8 units are dispatched, may split as ₹30 crore goods (8 units × ₹3.75 crore) and ₹10 crore service (FAT support, engineering, integration). Two separate GST treatments apply.
Reconciliation must hold this goods/service split per milestone at contract setup, drive the invoice format accordingly, and ensure the GSTR-1 / GSTR-3B reporting reflects the correct time-of-supply per leg.
How is the advance bank guarantee tracked
A ₹20 crore advance against advance bank guarantee on a ₹200 crore contract has a reducing-balance lifecycle:
- At contract signing: ABG face value ₹20 crore, advance balance outstanding ₹20 crore
- Recovery schedule: typically pro-rata against subsequent milestones — e.g. 25% recovery against M1, M2, M3, M4 each. Or fully recovered against the FAT milestone.
- At M1 completion (₹16 crore milestone, 25% advance recovery = ₹4 crore): advance outstanding ₹16 crore, milestone net payable ₹12 crore. ABG continues at ₹20 crore until bank amendment.
- At M2 completion (additional ₹4 crore recovery): advance outstanding ₹12 crore. ABG can be amended to ₹16 crore if bank-vendor process allows.
- At M4 (full recovery): advance balance zero, ABG released by bank.
Reconciliation must run the advance recovery schedule, age the ABG against current advance balance, and trigger amendment/release with the bank at recovery milestones.
How does Section 393 TDS overlay the milestone payment chain
Subcontracting payments to Tier 2 vendors attract Section 393 across multiple sub-sections:
- Section 393(1)(a) code 1002 — sub-contractor work (manufacturing services, assembly, integration, testing, AMC). 1% individual/HUF, 2% company/firm. Threshold ₹30,000 per transaction, ₹1 lakh aggregate.
- Section 393(1)(b) code 1003 — professional fees (design consultancy, certification engineering, technical writing, legal). 10% above ₹50,000 aggregate per FY.
- Section 393(1)(k) code 1012 — purchase of goods. 0.1% above ₹50 lakh aggregate per vendor per FY (when buyer turnover above ₹10 crore).
- Section 413 code 1062 — foreign technical-service payments or royalty for imported software/firmware. Rate per DTAA (typically 10%) or Act rate (20%) with TRC and Form 10F documentation.
Reconciliation maintains the vendor-rate matrix with code defaults, applies the correct deduction on every payment, and deposits the monthly TDS challan against the principal’s TAN. See Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092 India.
Three-Way Match Exception Cost Calculator
Quantify the cost of unresolved PO-GRN-invoice exceptions on multi-year defence subcontracting — exceptions delay CDA payment processing and ripple into milestone slippage.
Open the Exception Cost Calculator →What does the CDA payment processing cycle look like
The Controller of Defence Accounts (CDA) processes most defence supply payments. The cycle:
- Milestone certification by buying agency — DGQA/user/test agency signs off on the deliverable
- Vendor invoice submission with supporting documentation — invoice, milestone certificate, ABG status, retention computation, PBG status, MoD vendor code reference
- CDA review and audit — financial scrutiny, computation verification, TDS deduction by CDA where applicable (some payments deduct TDS at source by CDA against vendor PAN)
- Payment authorisation — typically 30-60 days from invoice submission depending on complexity and any clarifications
- Bank credit to vendor — typically 5-15 days from authorisation
Total cycle: typically 30-90 days from milestone certification to bank credit. Long-running clarifications can extend to 120-180 days. Reconciliation must age CDA-pending invoices and follow up at 60/90/120 day thresholds.
Worked example — ₹200 crore contract over 4 years, 7 milestones
- Contract value: ₹200 crore
- Advance 10%: ₹20 crore against ₹20 crore ABG
- Year 2 cumulative position:
- M1 (design freeze) certified and paid: ₹16 crore − ₹4 crore advance recovery − ₹1.2 crore retention = ₹10.8 crore net received
- M2 (first article) certified and paid: ₹30 crore − ₹4 crore advance recovery − ₹2.25 crore retention = ₹23.75 crore net received
- M3 (type approval) certified, invoice submitted, CDA processing 47 days: ₹40 crore − ₹4 crore advance recovery − ₹3 crore retention = ₹33 crore net expected
- Advance recovered to date: ₹8 crore; advance outstanding: ₹12 crore; ABG continuing at ₹20 crore until next bank amendment cycle
- Total billed and recognised: ₹46 crore (M1 + M2)
- Total received: ₹34.55 crore
- Awaiting CDA: ₹33 crore (M3)
- Retention accumulated: ₹3.45 crore (on M1 and M2 billed amounts)
- PBG outstanding: ₹16 crore face value (8% of contract)
- Subcontractor TDS deposited Q1 + Q2 cumulative: ₹86 lakh under code 1002, ₹14 lakh under code 1003, ₹4.2 lakh under code 1012
- Remaining contract life: 24 months to SAT plus 30 months warranty = 54 months to retention release
- Total working capital tied up at this point: ₹3.45 crore retention + ₹16 crore PBG contingent + bank charges on ABG and PBG quarterly
MoD authority reference
For DAP-2020 milestone payment structure, MoD vendor code system, CDA payment processing, advance bank guarantee requirements and ARC/RPC release process see the Ministry of Defence (MoD).
What automated reconciliation changes
Manual milestone reconciliation across 4-8 active defence contracts, with multi-stage payment ledgers, MoD vendor code cross-reference, advance recovery schedules, GST time-of-supply per leg, CDA payment ageing, and Section 393/413 TDS deposits is a 5-7 day month-end exercise at a meaningful defence vendor — and the longer-tenor ledgers slip if reconciliation lags. Purpose-built reconciliation software India configures the milestone flow as a structured workflow with contract master, milestone schedule with deliverable / acceptance / payment, MoD vendor code + PAN cross-reference, ABG recovery schedule, GST time-of-supply per leg, CDA ageing dashboard and TDS deduction matrix. TransactIG carries 24+ industry presets including defence configurations. Customer outcomes include match-rate improvement from 51% to 88% on multi-year ledgers and CDA-pending exposure surfacing 4-6 weeks earlier. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the inbound procurement match see three-way matching software India.