When Your Overseas Client Dictates Your Insurance: Meeting Contractual Cover Requirements

An Indian IT services firm, an engineering-design consultancy, or a manufacturer supplying a US or European buyer rarely gets to choose its own insurance programme any more. The insurance schedule of the client's master services agreement chooses it for them. A single US enterprise contract can demand professional indemnity of USD 5 million, commercial general liability of USD 2 million per occurrence, cyber liability of USD 3 million, workers-compensation to statutory limits, worldwide jurisdiction including the USA and Canada, additional-insured status for the client and its affiliates, a waiver of subrogation in the client's favour, primary and non-contributory wording, and 30 days' written notice of cancellation, all evidenced by a certificate before the first invoice is paid.

The vendor's procurement or legal team signs the contract, then hands the insurance schedule to a broker weeks later and asks for a certificate that matches it. That is where the friction starts, because a standard Indian policy issued to an Indian company does not natively carry US-style endorsements, and several of the requirements are not things an Indian insurer will grant without a specific extension, a loading, or a conversation.

This is a different problem from choosing the right product. The vendor already knows it needs professional-indemnity cover. The task here is compliance: reading the client's clause, translating each requirement into what an Indian insurer can actually endorse, closing the gaps that cannot be endorsed, and producing evidence a foreign counterparty will accept. Get it wrong and the client withholds payment, delays go-live, or, worse, discovers after a claim that the certificate on file did not deliver the protection the contract promised.

Insurance requirement clauses in Western contracts follow a recognisable grammar. Reading them precisely is the first job.

Limits and currency. "Professional liability of not less than USD 5,000,000 per claim and in the aggregate" sets both a per-claim and an annual cap, in dollars. An Indian PI policy is usually written in rupees, so the vendor must either buy a rupee limit that comfortably exceeds the dollar figure at a conservative exchange rate or arrange the policy limit in USD, which some Indian insurers will do for export-facing accounts.

Types of cover. The clause typically names several lines: professional liability or errors and omissions, commercial general liability, cyber or data-breach liability, and workers-compensation or employer liability. Each maps to a distinct Indian product, and the vendor needs all of them in force, not just PI.

Additional insured. "The Client and its affiliates shall be named as additional insureds" gives the client direct rights under the vendor's policy. On liability lines this is routine to endorse; on a professional-indemnity policy it is unusual and many insurers resist it, because PI is meant to respond to the insured professional's own negligence.

Waiver of subrogation. The vendor's insurer agrees not to pursue recovery against the client after paying a claim. This must be an endorsement on the policy; a promise in the contract alone does not bind the insurer.

Primary and non-contributory. The vendor's policy must pay first and must not ask the client's own insurance to contribute. This alters the normal contribution rule between policies and, again, needs specific wording.

Notice of cancellation. "30 days' prior written notice of cancellation or material change" asks the insurer to notify the client, a third party, before the cover lapses. Indian insurers will often endorse notice to the insured, but notice to a named third party is a separate request.

Read the insurance schedule before signing the contract, not after. Every one of these requirements has a cost or a limit on what an Indian insurer will grant, and the cheapest time to negotiate an unreasonable clause down is while the commercial terms are still open.

The single most consequential requirement in a US client contract is the jurisdiction and territory clause. "Coverage shall apply worldwide including the USA and Canada" is easy to write and hard to place.

Most Indian professional-indemnity and liability policies default to an Indian jurisdiction clause: claims must be brought and adjudicated in Indian courts under Indian law. That default exists for good reason. US litigation carries jury awards, punitive damages, contingency-fee plaintiff lawyers, and discovery costs that dwarf Indian court outcomes, so a policy that covers US-jurisdiction claims is a fundamentally different, more expensive risk. When an Indian vendor accepts a contract requiring USA and Canada jurisdiction, it is asking its insurer to accept that heavier exposure.

Indian insurers handle this in one of three ways. Some decline US and Canada jurisdiction entirely and offer only rest-of-world. Some offer it as a specific extension with a meaningful additional premium and often a separate, higher deductible for US-jurisdiction claims. Some place the account, or the US-exposed layer of it, with an overseas insurer or through a global programme where the capacity for US litigation risk sits with a market used to pricing it.

Translating the client's requirements into an Indian policy means knowing in advance which requests are routine, which cost extra, and which an Indian insurer will simply not grant.

Routine endorsements, usually available at little or no extra cost, include naming the client as an additional insured on general and public liability lines, a waiver of subrogation in the client's favour on those lines, and 30-day notice of cancellation to the insured. These are standard requests that most Indian insurers accommodate for export accounts.

Available but priced or negotiated: additional-insured status on a professional-indemnity policy (many insurers resist, some allow it narrowly), worldwide jurisdiction including USA and Canada (extension with loading), primary and non-contributory wording (insurers will often agree on liability lines but scrutinise it on PI), and third-party notice of cancellation to a named client (some insurers issue it, some will only notify the policyholder and expect the vendor to pass it on).

Often refused or heavily restricted: a full contractual-liability assumption where the vendor's policy is asked to cover liabilities the vendor took on by contract that it would not have had at law, uncapped indemnities, and blanket additional-insured wording covering an open-ended list of the client's affiliates and their customers. Indian insurers underwrite the insured's own negligence, not the insured's contract drafting, and a requirement that effectively converts the policy into a guarantee of the vendor's contractual promises will be declined.

The practical discipline is to build a two-column mapping: the client's requirement on the left, what the insurer confirms in writing on the right, and a flagged gap wherever the two do not meet. Every flagged gap is either negotiated with the client, closed with an extension, or accepted as an uninsured contractual exposure the vendor's management signs off on knowingly.

Even when the cover is correctly placed, Indian vendors routinely stumble on the last step: producing evidence the foreign client will accept.

US clients frequently ask for an ACORD 25 certificate of liability insurance, the standard evidence form their own domestic vendors provide. Indian insurers do not issue on the ACORD form; they issue their own certificate of insurance or a cover note in their house format. A US procurement portal that only accepts an ACORD upload can reject an Indian insurer's certificate on format alone, even though the underlying cover is compliant. The workaround is to provide the insurer's certificate together with a covering letter mapping each contract requirement to the corresponding policy section, and, where the client insists, to escalate to the insurer or broker for a certificate drafted to mirror the ACORD headings.

The certificate-of-insurance itself has to name the correct insured entity, the correct additional insureds, the policy numbers, the limits in the currency the contract specifies, the policy period, and confirmation of the specific endorsements (waiver of subrogation, primary and non-contributory, notice of cancellation). A certificate that lists limits but does not evidence the endorsements is incomplete for a demanding client.

At scale, a vendor serving dozens of enterprise clients, each with its own insurance schedule and renewal-date certificate demand, needs a tracking system so that every client always holds a current certificate and no contract falls out of compliance at renewal. Certificate management is an operational function, not a once-a-year task.

Not every requirement in a client's insurance schedule is reasonable, and Indian vendors too often treat the clause as non-negotiable when the client's own risk team would accept a sensible alternative.

The strongest negotiating positions are these. Where the required limit is disproportionate to the contract value, a vendor delivering a USD 400,000 engagement asked to carry USD 10 million of professional indemnity can propose a limit proportionate to the exposure, often accepted with a short justification. Where the client demands additional-insured status on a professional-indemnity policy, the vendor can point out that PI covers the vendor's own professional negligence and that additional-insured status is conceptually mismatched, offering instead a waiver of subrogation, which achieves much of what the client actually wants. Where the client requires a specific US-domiciled insurer or an AM Best rating that no Indian insurer holds, the vendor can offer an Indian insurer with an acceptable financial-strength rating or arrange the exposed layer through a global programme.

Where a requirement genuinely cannot be met, silence is the worst option. A vendor that signs a contract it cannot comply with, then produces a certificate that quietly omits the missing endorsement, is exposed on two fronts: breach of the insurance covenant, and an uninsured liability if the very risk the endorsement was meant to cover materialises. It is better to raise the gap during negotiation, propose the closest achievable alternative, and get the client's written acceptance of the substitution.

The bargaining power cuts both ways. Foreign clients want the Indian vendor's delivery capability and price, and their procurement teams routinely accept reasonable substitutions when the vendor explains, with a broker's backing, exactly what the Indian market can and cannot provide. The vendors that lose this negotiation are usually the ones that never open it.

For an Indian vendor with a growing book of overseas clients, insurance compliance becomes a recurring workflow rather than a per-contract scramble. The workflow has five repeatable steps.

1. Intake at contract stage. Every prospective contract's insurance schedule is reviewed before signing, and its requirements are extracted into a structured record: line, limit, currency, jurisdiction, endorsements, certificate format.
2. Map to the in-force programme. Each requirement is checked against the vendor's existing policies. Where the programme already satisfies the requirement, it is marked compliant; where it does not, the gap is flagged.
3. Close gaps deliberately. Each gap is resolved by an endorsement, a limit increase, a jurisdiction extension, a negotiated substitution accepted by the client, or a documented decision to carry the exposure uninsured.
4. Issue and track certificates. A current certificate reflecting the actual endorsements goes to each client, and a register tracks every client's certificate against the vendor's policy-renewal dates so nothing lapses out of compliance.
5. Renew with continuity. At each policy renewal, the vendor confirms that the renewed wording still carries every endorsement its client contracts rely on, because a renewal on slightly different terms can silently drop a jurisdiction extension or a waiver that a client contract still requires.

The recurring failure across this segment is a mismatch between the certificate on the client's file and the endorsements actually in the policy. Sarvada's searchable database of insurer policy wordings lets a vendor's broker compare which insurers grant USA and Canada jurisdiction, additional-insured status on PI, and third-party cancellation notice, and on what terms, so the programme is placed on wordings that genuinely satisfy the client's schedule rather than a certificate that only appears to.