Notifying a claim under a warranty and indemnity policy puts the insured in a position that exists nowhere else in insurance: it must establish a breach of a contract to which its insurer is not a party, committed by a seller who is not in the room and who, its liability extinguished, has no reason left to take an interest. One first assumes the seller's absence simplifies everything. It is the opposite: since nobody argues for the seller, it is the insurer that builds that defense, because it cannot pay without having tested it. The insured therefore faces an opponent arguing on behalf of an absent party, with an insurer's resources and without the weaknesses of a seller in a hurry to settle.
Notification itself is subject to strict conditions, and the first is a deadline that starts earlier than instinct suggests. Wordings run the period from awareness of facts that MAY give rise to a claim, and not from certainty that a breach exists. The distinction is decisive: the duty bites at the moment an anomaly is seen, not at the moment it is understood. To this is added a content requirement, the facts, the warranty said to be breached, the estimate of loss, and an incomplete notification can be treated as no notification, which forfeits the deadline without anyone having said so.
From those two rules comes the tension that makes this module, and it traps competent teams. Investigating before notifying risks being out of time. Notifying before investigating risks filing a claim one cannot yet support, anchoring on a figure that will move, and handing the insurer a first document its counsel will reread for a year. The two prudent courses are contrary and one of them is fatal. The way out lies in an instrument already met elsewhere: notify early and thinly, on the facts alone, expressly reserving quantum. That preserves everything and asserts nothing.
It is therefore worth stating plainly what notifying means, because the error lies there and it is intellectual rather than negligent. A notification is not an assertion one must be able to prove, it is a preservation step. Serious teams wait until they hold a solid file, out of honesty as much as prudence, and are met with a deadline they did not know they were consuming while doing good work. Confusing the step that preserves with the demonstration that persuades is the most frequent reason a well founded claim fails to prosper.
Then comes the investigation, and the insurer redoes everything. It appoints its own lawyers and its own accountants, and it retakes the buyer's analysis document by document. A difficulty then settles in that few buyers anticipate: the advisers who wrote the due diligence on which the policy was underwritten are no longer neutral third parties. If the breach was detectable, their own work is in question. They therefore have an objective interest in characterizing the problem as concealment by the seller rather than omission by the review, and that interest can color advice without any bad faith. Seeing it early avoids being advised against oneself, and it is often healthy to entrust the claim to people other than those whose work might be questioned.
The burden of proof breaks into four distinct demonstrations, and they must be handled separately because one almost never loses on the first. It must be established that the warranty was false, that disclosure did not neutralize it, that loss exists, and how much it is worth. Winning the first point is the easy part and it is the one teams concentrate their energy on. Files are lost on the second, because a document was sleeping in the data room, and on the fourth, because the link between the breach and the amount claimed was not established item by item.
That leaves the settlement dynamic, better looked at coldly. The insurer is a repeat player, with no relationship to preserve with this particular buyer, and time costs it almost nothing. The buyer wants cash and the end of a file, it has an integration to run, and every month costs it management attention. Time therefore works structurally against it. The practical conclusion should be drawn rather than complained about: the buyer's leverage is not in the negotiation that follows notification, it is in the documents assembled before it. A complete file on the day of notification settles in months; a file built under the insurer's questions settles in years, or settles for half.
Five months after completion, a buyer's finance team notes, on March 4, an anomaly in the recognition of a supplier rebate that appears to have been recognized early. It continues its internal checks and escalates the point to management on March 20. External accountants are instructed and confirm on May 12 that the rebate was wrongly recognized across two financial years, overstating operating earnings by 900,000 euros. The buyer notifies the claim on May 20. The policy requires notification within thirty days of awareness of facts that may give rise to a claim. The insurer pleads late notification, taking March 4. The buyer replies that awareness presupposes an established breach, which only the May 12 confirmation provided. Who prevails?
The insurer, very probably, and the claim is imperilled on a purely procedural point while the merits are not in dispute. The clause targets facts that MAY give rise to a claim, not facts that establish one: an accounting anomaly noted on March 4 by the finance team is exactly that. The buyer's argument, that a diligent insured cannot notify every unverified anomaly, is reasonable as a matter of practice and loses as a matter of construction, because the clause is drafted precisely to take that judgment away from the insured and hand it to the calendar. What should have been done cost nothing and required no certainty: a two-paragraph notification, on March 4 or March 20, stating the facts observed and expressly reserving quantum. It asserts nothing, commits to no figure, and preserves everything. The error is intellectual rather than negligent: the team treated notification as an assertion it had to be able to support, when it is a preservation step, and it did good work while consuming its deadline. One detail remains that the insurer will exploit and that deserves to be seen: between the March 4 observation and the March 20 escalation, sixteen days passed inside the company. It was not the external accountants' work that ate the deadline, it was internal latency, and that is the only segment the buyer controlled entirely.
- 01The clock runs from awareness of facts that may give rise to a claim, not from certainty of a breach: the duty bites far earlier than instinct suggests.
- 02Notifying is not asserting, it is preserving: confusing the step that preserves with the demonstration that persuades is the commonest cause of late notification.
- 03Nobody argues for the absent seller, so the insurer builds that defense: the insured faces an opponent arguing for someone no longer there.
- 04Four proofs must be brought, the breach, the ineffectiveness of disclosure, the existence of loss and its amount, and files are lost on the second and the fourth.
- 05The buyer's leverage lies in the documents assembled before notification, never in the negotiation that follows: time costs the insurer nothing and the insured a great deal.