A company wins a government tender after months of pre-qualification, technical evaluation, and financial bidding. The assumption is that the hardest part is over. In practice, the institutional architecture governing contract execution, milestone verification, payment through PAO and PFMS, variation orders, and performance bank guarantee release is an entirely separate system from the one that awarded the contract. What does the execution architecture look like, and why do companies routinely discover that delivery is easier than getting paid?
The tendering process is governed by GFR, CVC guidelines, and the procuring entity's internal procurement manual. The officer managing the tender has a defined process, a timeline, and an outcome: award the contract. Once the contract is awarded, the institutional ownership shifts. The programme division manages the deliverables. The finance division manages the payment. The quality assurance function verifies the milestones. Each operates on its own timeline, with its own compliance requirements, and no single officer owns the end-to-end process from delivery to payment. The company's single point of contact during the bidding phase fragments into three or four institutional channels during execution.
Government contracts are typically structured around milestones: delivery of equipment, installation, commissioning, training, and acceptance testing. Each milestone triggers a payment tranche. The company delivers against Milestone 3. The programme officer inspects and confirms delivery. But the payment is not triggered by the programme officer's confirmation. It is triggered by a formal acceptance certificate, which requires the programme officer's recommendation, the technical committee's endorsement, and the competent financial authority's approval. If any of these three is delayed, whether by the officer's workload, the committee's meeting schedule, or the CFA's travel, the payment cycle does not begin.
The company has delivered. The government has received. The system has not yet recognised the delivery as payable. The distance between physical delivery and the generation of a payable obligation is the single largest source of cash flow disruption for government contractors, and it is built into the institutional design.
Once a payable obligation is recognised, the payment enters the PAO/PFMS chain: pre-audit, budget head mapping, scheme code verification. If the quarterly allocation is exhausted, the payment waits. If the financial year is ending and the expenditure hasn't been booked, the payment may lapse and must be re-validated in the next fiscal year. The company's payment timeline is governed not by whether it has delivered, but by the budgetary rhythm of the Government of India's fiscal calendar.
Government contracts frequently require modifications during execution: a site condition that differs from the tender specification, an additional requirement identified by the user department, a change in technical standards between contract award and execution. Each modification requires a formal variation order. The variation order requires technical justification from the programme division, cost estimation from the contractor, financial concurrence from the internal finance wing, and approval from the competent financial authority. If the variation exceeds a defined threshold (typically 10-15% of the original contract value), it requires a fresh approval process that may involve the department head or, for large contracts, the Ministry of Finance.
A variation that takes the contractor two weeks to execute can take the government six months to formalise. During this period, the contractor has incurred the cost but cannot bill for it, because the variation order that authorises the expenditure has not been signed. The contractor who proceeds without a signed variation order risks the cost being disallowed in audit. The contractor who waits for the signed variation order delays the project and risks liquidated damages for late completion. The institutional design creates a situation where the contractor is penalised whether they act or wait.
Every government contract requires the contractor to furnish a Performance Bank Guarantee, typically 5-10% of the contract value, valid for the contract period plus a defect liability period (usually 12-24 months). The PBG is released only after the defect liability period expires and the user department certifies that no defects have been observed. In practice, obtaining this certification can take months beyond the defect liability period because no officer is incentivised to process the release promptly. The PBG ties up the contractor's banking limits for the entire duration. For a mid-sized company executing three or four government contracts simultaneously, the cumulative PBG exposure can consume a significant portion of its credit facilities.
The institutional logic is that the government is protecting itself against contractor default. The operational reality is that PBG release delays function as an interest-free deposit extracted from the contractor, with no compensating mechanism and no service-level commitment on release timelines.
The company that wins a government contract enters a payment architecture designed for fiscal control, not for commercial efficiency. Every safeguard, pre-audit, CFA approval, budget head mapping, PFMS validation, is individually rational. Collectively, they create a system where the contractor finances the government's consumption of its own goods and services. Working capital is locked in milestone verification delays, variation order approvals, and PBG releases. The company's project finance model, built on the assumption that payment follows delivery within 30-60 days, encounters an institutional reality where 90-180 days is routine and 270 days is not uncommon.
This is why experienced government contractors build payment delays into their bid pricing. The government pays more for goods and services than it would if its own payment architecture were faster. The cost of institutional inefficiency is not absorbed by the contractor. It is passed back to the government in the form of higher contract values. The architecture's procedural caution is itself priced into the bids the architecture procures.