Surety Bonds Are Heading Into CRILC: What Credit Reporting Does to Bonding Capacity

On 6 August 2026 The Economic Times reported that regulators are weighing bringing insurance surety bond exposures under the RBI's Central Repository of Information on Large Credits (CRILC). The reasoning in the report is narrow and specific: surety bonds, which often serve as an alternative to bank guarantees on projects, are not always captured by credit information systems, which creates a blind spot on a borrower's total contingent liabilities.

That blind spot is not an accident of drafting. It is the direct consequence of surety being an insurance contract rather than a banking facility. When a contractor asks its bank for a performance guarantee, the bank books a non-fund-based limit, blocks margin money, reports the exposure through the credit information system, and every other lender can see it. When the same contractor buys a performance bond from an insurer, the obligation sits on an insurer's book under IRDAI supervision, and the bank consortium sees nothing.

Since surety bonds became a live alternative in the Indian market, that invisibility has been part of the sales pitch, whether or not anyone said so out loud. Government departments and central public sector enterprises have increasingly permitted contractors to use surety bonds instead of bank guarantees precisely to free up capital, and issuance has grown into thousands of crores. A contractor moving a bond off its bank limits recovers headroom on its non-fund-based line and releases the cash or fixed deposit pledged as margin. If the CRILC proposal is notified, that headroom stops being invisible even though it does not move back onto the bank's books.

The contingent liability already exists. A contractor with INR 400 crore of live performance bonds owes that obligation to its obligees today, and its counter-indemnity to the insurer is already enforceable under the Indian Contract Act, 1872. Reporting into CRILC would not create a new debt, increase its borrowings, or change a single term of the bond wording.

What changes is who can see it and when. CRILC is a lender-facing repository, so once surety exposures are pooled there, three groups gain a view they do not have today:

1. The contractor's existing bank consortium, which currently sizes fund-based and non-fund-based limits against a picture that omits surety-backed obligations.
2. A new lender running diligence before sanctioning a facility, who today would have to take the contractor's own disclosure at face value.
3. Indirectly, rating agencies and, through them, the pricing of the contractor's debt, because contingent liabilities feed adjusted gearing in most rating methodologies.

The practical effect is that the contractor's bonding programme and its borrowing programme stop being separate conversations. A contractor that took surety to keep bank limits free will find those bank limits assessed against a fuller picture of what it has already promised. Whether that reduces sanctioned headroom depends entirely on how the contractor's bankers were treating disclosed contingent liabilities in the first place, which is exactly what a CFO can find out now rather than after notification.

The useful exercise is not a lobbying position, it is a scenario run. Model the balance sheet as your bankers would see it if every live surety bond appeared alongside your bank guarantees, and do it before the next tender rather than after.

The five numbers to pull

• Total live surety bond exposure by type: bid, performance, advance payment and retention. Advance-payment bonds deserve separate treatment because the cash has already left the obligee, so an invocation is a near-certain call rather than a contested one.
• The run-off profile: how much of that exposure expires in the next four quarters, and how much runs through a defence liability or maintenance period well past practical completion.
• Your non-fund-based limit utilisation today, and what it would have been had the surety-backed obligations stayed on the bank line.
• Counter-indemnity terms across your insurers, including any cash collateral, promoter guarantee or lien on receivables you have already given.
• Covenant headroom in your existing sanction letters on any ratio that picks up contingent liabilities.

The last point is the one that bites first. A contractor whose loan documentation caps total contingent liabilities as a multiple of tangible net worth may find that a previously unreported surety book consumes a covenant it was never tested against. That is a conversation to have with a relationship manager voluntarily, holding your own numbers, rather than in response to a CRILC extract.

Pooled reporting cuts both ways, and the underwriting side of it is the more interesting half. Today a surety underwriter assessing a mid-market contractor sees the financials the contractor supplies, the order book the contractor describes, and whatever the commercial credit bureau holds on funded facilities. What the underwriter cannot reliably see is how much surety capacity the same contractor has already taken from other insurers.

That gap creates the classic aggregation problem in a young market. Four insurers can each write what looks like a prudent INR 50 crore line on the same contractor, each believing it holds a modest share of a well-spread programme, and collectively hold INR 200 crore of correlated exposure to one balance sheet. Because a contractor default triggers every bond at once, the correlation between those four exposures on the day it matters is close to one. Underwriting discipline built on individual-file judgement does not catch this, and reinsurance treaties priced on assumed spread do not either.

If surety exposures land in CRILC, an insurer with access to that data would price the same contractor differently in at least three ways:

• Aggregate capacity per obligor becomes enforceable rather than aspirational, because the underwriter can see the total rather than infer it.
• The marginal bond on a contractor already carrying a heavy surety book prices higher, which is the correct signal and the one the market currently cannot send.
• Counter-indemnity structures tighten where aggregate exposure is concentrated, because recovery prospects on a contractor with four simultaneous invocations are materially worse than on one with a single bond outstanding.

This is why the proposal is not simply a cost imposed on contractors. A surety market that can see its own aggregate exposure can extend capacity to good contractors with more confidence, which is the outcome the whole bank-guarantee substitution policy was aiming at. The broader 2026 reform context that surety supervision sits inside, running through the IRDAI's 137th Authority Meeting on 28 July 2026 and the wider reform agenda around it, points the same way: surety is being treated as a standing line rather than an experiment, and standing lines need exposure data.

Assume for the sake of planning that the proposal is notified in some form. The transition is where the disruption sits, not the end state.

In the first two quarters after any notification, expect the market to sort contractors into two groups. Contractors whose aggregate surety exposure turns out to be modest relative to their turnover and net worth will find capacity easier to obtain, because the underwriter no longer has to price for the unknown. Contractors carrying heavy multi-insurer books will find at least one of their insurers reassessing, and renewal pricing on that book is where the pain concentrates.

Rates on individual bonds are less likely to move than aggregate limits. Surety pricing in India has been competitive because the market is chasing volume in a line that has yet to see a meaningful loss cycle. The binding constraint after pooling is capacity per obligor, not price per bond, so the contractor that struggles will be the one told it has reached a ceiling rather than the one quoted a higher rate.

There is also a timing asymmetry worth flagging to clients. Bonds issued before any notification will still be outstanding after it, so a contractor cannot avoid the visibility by front-loading issuance. What front-loading does buy is certainty on terms for the current tender pipeline, which is a legitimate reason to move a placement forward but not a reason to over-issue against contracts that have not been awarded.

The weakest version of the surety pitch has always been "it keeps the exposure off your credit record". That version was never the real case and, if this proposal is notified, it stops being available at all. Brokers still selling it will find the client discovering the change from its banker instead of from them, which is a poor way to learn it.

The durable case for surety against a bank guarantee rests on four things that CRILC reporting does not touch:

1. Margin money. A bank guarantee typically locks cash or a fixed deposit as margin. A surety bond is underwritten against the contractor's credit standing and a counter-indemnity, so the working capital stays in the business. Visibility of the obligation does not put the cash back in a lien.
2. Non-fund-based limit headroom. Even with CRILC reporting, the surety bond does not consume the sanctioned non-fund-based limit itself. The bank may assess the contractor differently, but the limit is not drawn down.
3. Capacity diversification. A contractor whose entire bonding capacity comes from one bank consortium is exposed to that consortium's appetite. Adding insurer capacity spreads that dependency, which matters most in exactly the conditions where banks tighten.
4. Underwriting on execution, not just collateral. A surety underwriter reads order-book quality, execution track record and sector concentration. A contractor with a strong record and a thin balance sheet can sometimes get further with an insurer than with a lender.

Run that pitch and the CRILC proposal becomes a talking point rather than a problem. It also changes what a broker needs on file, because the differences between insurers now matter more, not less. Invocation conditions, notice periods, the extent of the contractor's release at completion and the recourse the insurer takes under its counter-indemnity all vary between bond forms in a market where wordings are not standardised. Reading those alongside the aggregate-exposure picture is what turns a placement into advice. Understanding the policy wording on an on-demand versus conditional bond is the difference between a bond that responds sensibly and one that generates a wrongful-invocation fight.

Nothing here requires waiting for a notification. Each of these is worth doing on its own merits, and each becomes more valuable if the proposal lands.

For the contractor CFO: build the consolidated surety register described above, reconcile it against what your contingent-liability disclosures already say, and take it to your lead banker before anyone takes it to you. If a covenant is tight, renegotiate it while you are the one raising the issue.

For the broker: pull every client's aggregate surety position across insurers, not just the bonds you placed. Flag the clients whose aggregate looks heavy relative to turnover, because those are the accounts where a capacity reassessment will surface first, and a client who hears it from you in September is a client you keep.

For the underwriter: treat single-obligor aggregation as a live control now rather than as a data problem to be solved by a future repository. Ask for a declaration of surety exposure with other insurers at proposal stage, and price the marginal bond against the declared total. The declaration is imperfect, and it is still better than the current position of pricing each file as though it were the only one.

The wider point is that the reporting gap between bank guarantees and surety bonds was always a transitional feature of a new product, not a permanent design. Contractors, brokers and insurers who built a position that depends on the gap staying open have a narrower base than they think. Those who built on margin money, capacity diversification and underwriting quality lose nothing when the data starts flowing.

Sarvada gives commercial insurance brokers structured, searchable access to insurer surety and bond wordings, so the invocation conditions and counter-indemnity terms behind a contractor's bonding programme can be compared before the bond is issued rather than after it is called. Request Access to read the credit picture and the wording picture together.