Operations & Best Practices

"Our Manager Said You're Covered" Is Not Cover: Rewriting the Placement SOP After Louis Dreyfus

In 2026 INSC 876 the Supreme Court held that no officer of an insurer, whatever their designation, can waive the Section 64VB requirement that premium precede risk. This piece rewrites the placement SOP around that holding: what must be in writing before binding, how to paper a mid-term limit increase, and what to do when the client's payment is in transit.

Tarun Kumar Singh
Tarun Kumar SinghStrategic Risk & Compliance SpecialistAIII · CRICP · CIAFP
9 min read

Listen to this article

Audio version • 9 min read

Section 64VBplacement SOPhold coveredbroker operationspremium warranty

Last reviewed: August 2026

What the Supreme Court held on 18 August 2026

In 2026 INSC 876, delivered on 18 August 2026, the Supreme Court restated the rule that decides more premium disputes than any policy wording: there is a statutory embargo under Section 64VB of the Insurance Act, 1938 on an insurer assuming risk if the premium has not been paid prior to such assumption, or within the time the statute stipulates. The dispute came out of a marine cargo turnover policy and a cotton-bale fire, facts and turnover arithmetic we set out separately in our note on the same judgment. This post takes the other half of the holding, the part about who inside an insurer can promise cover.

The insured's case rested on assurances. A divisional manager of the insurer had assured the insured that coverage would continue if instalments were paid on time, and the insured also pointed to an email assurance from the insurer's side. The bench found the email lacked authorisation under the company's own guidelines, and it rejected the waiver argument outright. The Court's formulation, as reported from the judgment, is the sentence every placement team should pin above the desk:

An agent cannot, by invoking actual or ostensible authority, confer upon the insurer a capacity which the statute itself withholds.

Read that carefully. The Court did not say the divisional manager was too junior, or that a more senior officer's assurance would have worked. It said the capacity to take risk without premium does not exist inside the insurer at all, so no officer can hand it out. Seniority, designation and apparent authority are all beside the point.

Why ostensible authority cannot cure a premium gap

Waiver and estoppel arguments work when the right being waived belongs to the party waiving it. An insurer can waive a policy condition it wrote for its own benefit. Section 64VB is different in kind. The bar on assuming risk before premium is received is imposed by statute on the insurer itself, which is why the Court framed it as a question of capacity rather than of consent.

That framing is what kills the assurance-based argument. Ostensible authority answers the question of whether an officer's act binds the company. It cannot answer the prior question of whether the company had the power to do the act at all. If the statute withholds the power, the most senior officer with the most convincing letterhead confers nothing.

For brokers, the operational translation is blunt. Every verbal comfort in circulation in the Indian commercial market, the "we will regularise the premium", the "consider yourself held covered, the endorsement will follow", the "the divisional office has approved it, pay when the board clears the funds", now carries a known judicial answer. If a loss falls in the gap, the assurance is worth nothing, and the client's recourse conversation turns toward the broker who relayed it.

The informal practices this judgment ends

Indian commercial placement runs on a layer of informal comfort that rarely appears in any file. The Louis Dreyfus holding removes the legal floor under all of it.

  • The regularisation promise. "Bind now, we will regularise the premium next week." There is no regularisation of risk already assumed without premium. The risk was never validly assumed.
  • The instalment comfort. An assurance that cover continues so long as instalments arrive on time is exactly what the insured relied on in this case, from a divisional manager, and it failed.
  • The unauthorised email. A written assurance is not automatically a valid one. The bench found the email in question lacked authorisation under company guidelines, so even the paper trail the insured did hold could not carry the weight.
  • The renewal drift. Allowing cover to be treated as continuing across a renewal date while the premium cheque is "being processed" is the same gap in a different costume.

The statute does leave prescribed routes. Section 64VB bars assumption of risk unless premium is received in advance, subject to exceptions such as a guarantee from a banking company or an advance deposit sufficient to cover the premium, carried forward in the draft Insurance Rules, 2026 notified via G.S.R. 652(E) dated 23 July 2026, which we read clause by clause in our note on the draft rules and premium-before-cover. Those exceptions share one feature: they are funded or secured mechanisms that exist in writing before the risk attaches. A manager's assurance is not on the list, and after 18 August 2026 no one can argue it belongs there by implication.

What the file must contain before you confirm cover

A placement SOP rewritten for this judgment starts from a single rule: no binding communication leaves the broker until the file holds proof that the 64VB condition is satisfied. In practice that means one of three things, each in writing.

  1. Evidence of premium receipt by the insurer. A UTR with a confirmed credit, or the insurer's premium acknowledgment. A screenshot of a payment initiation is not receipt.
  2. Evidence of a prescribed funding mechanism. A bank guarantee from a banking company in force for the amount, or a written insurer confirmation that an advance deposit or cash-deposit balance sufficient to cover the premium stands to the client's credit and is being appropriated to this risk.
  3. The insurer's written confirmation of inception, stating the inception date and time, issued after whichever of the two above applies, from the underwriting office and not from a relationship contact.

The inception date in the confirmation must be on or after the date the premium condition was met. A confirmation that recites an earlier inception to suit the client's contract or financier deadline documents a gap rather than closing it.

The companion discipline on cheques, remittance timelines and co-insurance premium chains is set out in our Section 64VB cash-before-cover playbook; this SOP layers the binding-communication controls on top of it.

Documenting a mid-term limit increase

Mid-term enhancements are where assurance-based cover most often creeps in, because the client wants the higher limit effective immediately and the additional premium takes days to move. The additional premium on an endorsement is premium for 64VB purposes, and the enhanced portion of the sum insured is risk the insurer has not assumed until that premium is received or secured.

The paper sequence should be fixed and non-negotiable:

  1. Client's written instruction stating the new limit sought and the date from which it is needed.
  2. Insurer's written quotation of the additional premium for the enhancement, from the underwriting office.
  3. Payment or appropriation evidence for the additional premium, or written confirmation that a deposit or guarantee mechanism covers it.
  4. The endorsement itself, with an effective date on or after step 3, checked against the quotation before it goes to the client.

Step 4 is where files fail quietly. An endorsement that arrives weeks later showing an effective date of the client's request, on the strength of someone's assurance that "it will be made effective from your email", is precisely the artefact this judgment strips of value. The Supreme Court's treatment of disputed mid-term sum insured changes in the Sayona Colors matter, covered in our documentation post, shows how heavily courts lean on what the file actually contains. The process mechanics sit in the mid-term endorsement workflow.

The escalation path when payment is genuinely in transit

The hard case is not the client who will not pay. It is the client whose funds are moving, board approval done, RTGS initiated, credit expected tomorrow, while cargo sails or a contract works policy must incept today. The old answer was a phone call and a comfort email. The SOP needs a real path.

Hour one: state the position in writing. Tell the client, in plain words, that cover has not attached and will not attach until the insurer receives the premium, and that no assurance from any insurer officer changes that. This message protects the client from acting uninsured and protects the broker from a later claim that it fostered the opposite belief.

Hour one to close of day: work the prescribed mechanisms. Ask the insurer's underwriting office, in writing, whether an existing advance deposit or cash-deposit balance can be appropriated to the risk today, or whether a banking company guarantee already held can be extended to it. These are the statutory exceptions, and they can lawfully bridge the exact gap the verbal assurance used to paper over.

If no mechanism exists: move the money, not the inception. Escalate inside the client to whoever can release an immediate RTGS. A same-day transfer with a confirmed credit beats any workaround. If the funds truly cannot land today, the inception moves to when they do, and every counterparty, financier included, is told the real date. Where a financier's interest is noted on the policy, the agreed bank clause post covers how to handle that conversation.

After credit: close the loop. Record the credit timestamp, obtain the insurer's written inception confirmation, and reconcile the two dates in the file. That reconciliation is the artefact a court will ask for.

Rewriting the SOP: controls, training and the E&O angle

Turning the judgment into standing practice takes four changes to the placement SOP, none of them expensive.

A binding-communication gate. Confirmation-of-cover emails, cover confirmations to financiers and certificates all issue from a template that requires the premium-evidence reference (UTR, deposit appropriation, or guarantee) to be filled in before the document can be sent. An empty field stops the communication.

A ban on relaying assurances. Placement staff may record an insurer officer's assurance in the file as a fact of the negotiation. They may not transmit it to the client as a statement about cover. The distinction goes into the SOP verbatim and into induction training.

An authorisation check on written confirmations. The email assurance in 2026 INSC 876 failed partly because it lacked authorisation under the insurer's own guidelines. A broker cannot audit an insurer's internal delegations, but it can insist that inception confirmations come from the underwriting office on the insurer's system rather than from a marketing contact's inbox, and treat anything else as unconfirmed.

A logged escalation path. The in-transit procedure above, with its written client notification, becomes a numbered SOP section with a checklist, so the pressure of a sailing date produces a documented sequence instead of a phone call.

The errors-and-omissions logic behind all four is simple. When assurance-based cover fails, the insurer now has a Supreme Court authority to stand behind, so the recovery theory shifts to the intermediary who let the client believe it was covered. The broker's protection is a file that shows the client was told the truth at every step.

Running these controls across a commercial book also means knowing how each insurer's wordings treat premium payment, instalment clauses and endorsement effective dates, because those vary. Sarvada gives broking teams structured, searchable access to insurer policy wordings and the intelligence around them, so the placement SOP can be tied to the exact contractual terms in play. Request Access to put that discipline into your binding workflow.

About the Author

Tarun Kumar Singh

Tarun Kumar Singh

Strategic Risk & Compliance Specialist

  • AIII
  • CRICP
  • CIAFP
  • Board Advisor, Finexure Consulting
  • Developer of the Behavioural Underinsurance Risk Index (BURI)

Tarun Kumar Singh is a seasoned risk management and insurance professional based in Bengaluru. He serves as Board Advisor at Finexure Consulting, where he advises insurance, fintech, and regulated firms on governance, growth, and trust. His work spans insurance broker regulatory frameworks across India, UAE, and ASEAN, IRDAI compliance and Corporate Agency model reform, VC governance in insurtech, and MSME insurance gap analysis. He is the developer of the Behavioural Underinsurance Risk Index (BURI), a framework applying behavioural economics to underinsurance and insurance fraud risk.

Frequently Asked Questions

Can a senior insurer officer's written assurance of cover ever substitute for premium payment?
No. In 2026 INSC 876 the Supreme Court held that an agent cannot, by invoking actual or ostensible authority, confer upon the insurer a capacity which the statute itself withholds. Section 64VB imposes a statutory embargo on the insurer assuming risk before premium is paid, so the question is one of the insurer's capacity, not of the officer's seniority or authority. The email assurance in that case failed for the further reason that the bench found it lacked authorisation under the insurer's own guidelines, but even a fully authorised assurance could not have created cover where premium had not been paid.
What are the lawful exceptions to paying premium before cover attaches?
Section 64VB of the Insurance Act, 1938 bars an insurer from assuming risk unless premium is received in advance, subject to prescribed exceptions such as a guarantee from a banking company or an advance deposit sufficient to cover the premium, reflected in the draft Insurance Rules, 2026 notified via G.S.R. 652(E) dated 23 July 2026. The common feature is that each exception is a funded or secured mechanism documented before the risk attaches. A verbal or email assurance from an insurer officer is not among the exceptions and cannot be treated as one.
What should a broker hold in writing before confirming cover to a client?
One of three artefacts, each in writing: evidence that the insurer has received the premium, such as a UTR with confirmed credit or the insurer's premium acknowledgment; evidence that a prescribed mechanism covers the premium, such as a banking company guarantee in force or a written confirmation that an advance deposit balance is being appropriated to the risk; and, following either of those, the insurer's written confirmation of inception stating the date and time, issued by the underwriting office. The confirmed inception date must be on or after the date the premium condition was met.
How should a mid-term sum insured increase be documented under Section 64VB?
Treat the additional premium as premium in its own right. The sequence is a written client instruction stating the new limit, a written insurer quotation of the additional premium from the underwriting office, payment or appropriation evidence for that premium, and only then the endorsement, with an effective date on or after the premium was received or secured. An endorsement backdated to the client's request date on the strength of an assurance is exactly the artefact the 18 August 2026 judgment deprives of value.
What should the broker do when the client's premium payment is in transit and cover is needed today?
First, tell the client in writing that cover has not attached and will not attach until the insurer receives the premium, whatever any insurer officer has said. Second, ask the insurer's underwriting office in writing whether a prescribed mechanism can bridge the gap today, such as appropriating an existing advance deposit or extending a banking company guarantee. Third, if no mechanism exists, escalate inside the client for an immediate RTGS rather than negotiating the inception date. If funds cannot land in time, the inception moves to the actual credit date and every counterparty is told the real position.

Related Glossary Terms

Related Insurance Types

Related Industries

Related Articles

Sarvada Intelligence

Ready to see Sarvada in action?

Explore the platform workflow or start a product conversation with our underwriting automation team.

Explore the platform