Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian EPC and engineering contractors typically run a portfolio of 15-40 active Performance Bank Guarantees (PBGs) across 10-30 customer contracts, totalling 5-10% of cumulative contract value, with each PBG valid through execution plus warranty (12-24 months from commissioning) and incurring 0.5-1% per annum bank commission billed quarterly with 18% GST; the PBG ledger must distinguish from retention (cash withheld by customer), track release triggers (commissioning, warranty expiry, no-claim certificate), handle extensions on programme delays with the extension cost mapped as pass-through or contractor absorbed, and reconcile monthly to the issuing-bank statement.
Build a per-PBG register keyed on the contractor's internal PBG number with linked issuing-bank instrument number, beneficiary, contract reference, PBG value, validity start and end, release trigger and quarterly commission accrual; tie each PBG to the contract milestone tracker (order acceptance trigger for issuance, commissioning certificate or warranty expiry for release); maintain an expiry calendar with 60 / 30 / 7-day renewal alerts; for every BG commission debit on the bank statement, post the cost to finance expense and claim ITC under Section 16 of the CGST Act against the bank's tax invoice; on programme delay, raise an extension request 60 days before expiry and classify the extension cost as pass-through or contractor-borne; reconcile monthly against the issuing-bank statement for new issuances, releases and live PBGs.
PBG register with internal PBG number, bank instrument number, issuing bank, beneficiary, contract reference, PBG value, validity start / end, release trigger (commissioning / warranty / no-claim), quarterly commission rate; expiry calendar with renewal alert thresholds; bank statement BG commission ledger with GSTR-2B match for ITC; programme variance tracker driving extension requests; contract clause mapping classifying extension cost as pass-through or contractor cost; monthly two-way reconciliation against issuing-bank statement.
A monthly PBG close where the contractor's PBG register reconciles to the issuing-bank statement with new issuances, releases and live PBGs all matched; BG commission entries on bank statements tie to GSTR-2B and the ITC claim under Section 16; expiry calendar drives 60 / 30 / 7-day renewal alerts; release triggers on completed projects are actioned with the customer; extension costs are accrued as pass-through or contractor cost per contract clause; contingent liability disclosure ties to the PBG portfolio outstanding.
An EPC engineering contractor in Chennai operates a portfolio of 8 active customer contracts totalling ₹400 crore of cumulative contract value, supported by 23 active Performance Bank Guarantees totalling ₹35 crore (about 9% of cumulative contract value, blended). The PBGs are issued by four banks — two public-sector and two large private-sector — with average validity of 28 months (14-month execution plus 14-month warranty, blended). BG commission rate is 0.75% per annum on the face value, billed quarterly in advance with 18% GST. The CFO’s monthly close runs across a PBG register rail, an issuing-bank statement reconciliation rail, a BG commission accrual rail with ITC claim under Section 16, an expiry calendar rail with renewal alerts, an extension request rail driven by programme variance, and a release trigger rail keyed to commissioning and warranty expiry. This guide walks each rail and ties them back to the broader engineering and capital goods reconciliation in India framework. For the defence-sector-specific PBG and retention pattern, see the related defence-PBG-retention tracking article in the same cluster.
Quick reference
| Item | Section / Standard | Key threshold or rate |
|---|---|---|
| PBG size | Contract / engineering norms | Typically 5-10% of contract value |
| PBG validity | Contract / engineering norms | Execution + warranty (typically 12-24 months from commissioning) |
| BG commission | Bank tariff | Typically 0.5-1% per annum on face value |
| BG commission GST | CGST Act (financial service) | 18% with ITC available |
| BG commission ITC | Section 16 CGST + Rule 36 | Available against bank’s GSTR-2B-reflected invoice |
| Retention (cash) | Contract / engineering norms | Typically 5-10%, balance-sheet receivable |
| PBG (bank-issued) | RBI Master Direction on guarantees | Off-balance-sheet contingent liability |
| Renewal alert | Operational control | Typically 60 / 30 / 7 days before expiry |
| Release triggers | Contract clauses | Commissioning certificate, warranty expiry, no-claim certificate |
| Extension cost | Bank tariff + contract | Prorated commission; pass-through or contractor cost per contract |
Rail 1 — PBG register: the per-PBG ledger
The PBG register is the contractor’s master ledger keyed on an internal PBG number. Each entry carries: linked issuing-bank instrument number (the bank’s own reference), issuing bank name, beneficiary (the customer), contract reference, PBG face value, validity start date, validity end date, release trigger clause (commissioning, warranty, no-claim certificate), quarterly commission rate, cumulative commission accrued, and current status (live, extension-pending, released, invoked). For the Chennai EPC contractor with 23 active PBGs, the register is a 23-row table updated monthly with new issuances, renewals, extensions and releases.
A common reconciliation error: an internal PBG number is allocated and the contract milestone marked complete in the project tracker, but the bank instrument is not actually issued (waiting on margin money deposit or bank documentation). The contract’s order acceptance trigger fires without the underlying PBG live — a customer-default risk that surfaces at first customer payment delay.
Rail 2 — Issuing-bank statement reconciliation
Each of the four banks issues monthly statements listing the contractor’s live PBGs with face value, beneficiary, validity, expiry date and outstanding commission. The two-way reconciliation:
- Bank-listed but not in contractor register: typically PBGs that the contractor has tracked as released (commissioning certificate received, customer’s release letter sent to bank) but the bank’s records haven’t yet updated. Resolution: chase the bank for the release acknowledgement.
- Contractor register but not in bank statement: typically newly issued PBGs that the bank’s reporting cycle hasn’t yet captured (1-2 month lag). Resolution: confirm bank-side issuance via the underlying instrument copy.
Monthly reconciliation closes both directions and feeds the contingent-liability disclosure in the audited financial statements (Ind AS / Schedule III).
Rail 3 — BG commission accrual and ITC claim under Section 16
The bank charges quarterly commission in advance — typically 0.5-1% per annum on the face value. For a single ₹5 crore PBG at 0.75% annual rate, the quarterly commission is ₹93,750 plus 18% GST of ₹16,875 — invoiced on the first day of the quarter, with payment auto-debited from the contractor’s current account. The reconciliation rail:
- Bank statement entry on debit date — debit posted to BG commission expense (P&L) and GST input to ITC ledger
- Bank’s tax invoice received within 30 days under Section 31 of the CGST Act with GSTIN, supply description, value, tax rate
- Bank’s GSTR-1 filing reflects the invoice — appears in contractor’s GSTR-2B in the next month
- ITC claim in the contractor’s GSTR-3B Table 4(A)(5) for the period in which GSTR-2B reflects the entry
For the Chennai contractor with ₹35 crore PBG portfolio at 0.75% annual rate, annual BG commission is ₹26 lakh plus ₹4.7 lakh GST, with the GST entirely claimable as ITC subject to the GSTR-2B match.
Rail 4 — Expiry calendar and renewal alerts
The expiry calendar runs against the PBG register’s validity end date. The control hierarchy:
- 60 days before expiry: alert triggers a project review — is the underlying customer obligation (warranty period, performance period) still live? If yes, renewal request prepared.
- 30 days before expiry: renewal request submitted to bank with margin money refreshed if needed; customer informed of impending PBG continuity
- 7 days before expiry: escalation if renewal pending; risk of un-renewed PBG against live obligation
An expired PBG against a still-live obligation is treated by the customer as a default event. Even where the contractor has no actual performance failure, the customer can invoke contract penalties (typically liquidated damages at 0.5-1% of contract value per week of default).
Rail 5 — Extension cost on programme delays
Programme delays are common on long-cycle EPC projects — site readiness lag, customer change orders, scope creep, monsoon delays, force majeure events. Where a project’s commissioning slips and the original PBG validity is breached, the PBG must be extended. The bank charges extension fee (typically the prorated commission for the extension period, sometimes at a higher rate if risk reassessment is unfavourable) plus may require additional margin money deposit.
The contract clause matters: where the delay is attributable to the customer (change orders, scope creep, site readiness), the extension cost is typically a contract pass-through — the contractor invoices the customer separately for the extension cost. Where attributable to the contractor (resource shortage, sub-vendor delays, execution issues), it’s a contractor-absorbed cost. The reconciliation rail tags every extension against its cause and routes the cost accordingly.
Rail 6 — Release triggers and PBG retirement
Release triggers per the contract:
- Execution-period PBG: released on issue of the commissioning certificate by the customer
- Warranty-period PBG: released on expiry of the warranty period or on issue of the no-claim certificate by the customer
- Combined execution + warranty PBG: released on completion of warranty period
On the trigger event, the contractor obtains a release letter from the customer addressed to the issuing bank, the bank cancels the PBG and releases any underlying margin money to the contractor. The bank statement updates within 1-2 months. The reconciliation rail tracks the trigger date, the customer letter date, the bank cancellation date and the margin money release date — typical end-to-end cycle is 60-90 days.
Worked example: 23 active PBGs, ₹400 Cr portfolio, monthly close
The Chennai EPC contractor closes the month with: 23 active PBGs totalling ₹35 crore face value across 8 customer contracts; 4 PBGs in the 60-day renewal window; 1 PBG in the 30-day window with renewal request submitted to issuing bank last week; 1 PBG cancelled this month following warranty expiry on a ₹40 crore contract; 1 new PBG issued for a ₹50 crore contract that signed in the prior month, with order-acceptance milestone triggered. Quarterly BG commission accrued: ₹6.6 lakh plus ₹1.2 lakh GST, with ITC claimable in the GSTR-3B for the period. Bank-statement reconciliation: 2 PBGs showing as “live” on the bank statement that the contractor’s register has already marked as “released” — pending bank acknowledgement. Contingent liability disclosure (Ind AS / Schedule III) for the audit: ₹35 crore PBGs outstanding, with breakdown by counterparty bank, beneficiary and expiry profile.
Size the cost of un-renewed PBG and commission ITC exceptions
An un-renewed PBG against a live obligation, a missed BG commission ITC claim, or a mis-allocated extension cost each carry a recoverable cost in cash, ITC, and customer-relationship terms. Use the exception cost calculator to size the impact across your active PBGs.
Open the Three-Way-Match Exception Cost Calculator →What automated reconciliation changes
EPC engineering finance teams running the PBG rails on spreadsheets typically lose 4-6 days per monthly close to the issuing-bank statement reconciliation, the expiry calendar maintenance and the BG commission ITC claim. Purpose-built reconciliation software India configured with the PBG preset carries the per-PBG register, the issuing-bank statement two-way reconciliation, the BG commission accrual and Section 16 ITC claim workflow, the expiry calendar with 60 / 30 / 7-day alerts, the extension request workflow with pass-through / contractor-cost classification and the release trigger tracker out of the box. Cross-link to mobilisation advance recovery reconciliation for the advance BG that runs alongside, and to retention money reconciliation patterns for the cash-retention rail. Customer outcomes include match-rate improvement from 51% to 88% on the procurement rail and a 50-65% reduction in close time on the PBG workflow. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022) once the ERP and treasury system export a structured contract, PBG register, bank statement and commission invoice extract. For the headline three-way match rail see three-way matching software India. For the RBI Master Direction on guarantees, see the Reserve Bank of India. Cross-reference the manufacturing reconciliation in India pillar for the wider close pattern.