Business liability claims: Separate facts and demands

When a commercial customer reports damage, separating facts, demands and unresolved assessments helps. As an intermediary, you can support preparation so the insurer understands the situation and the customer knows the responsible contacts. A well organised notification begins before the final loss amount is known. The business should see what information exists and what professional assessment remains outstanding.

Distinguish the event from the demand first

Ask what happened and what the business actually knows. Damaged equipment is an observed condition. A client’s statement that the business must pay is a demand. An assumption about the cause is an assessment. Keeping these levels separate creates a clear basis for investigation. None becomes confirmed simply because it was stated first.

Describe the timeline in understandable steps: when work occurred, damage was noticed and a demand arrived. These dates may differ. Use known information and mark uncertain times. A retrospectively polished story is less useful than an honest account with an explicit gap requiring an original document or responsible person’s answer.

Also separate direct observation from later reports. An employee may describe work without seeing damage discovered later. A client may report damage without knowing its cause. Record what each statement relates to, so investigators can see which part it supports and which conclusion remains open.

Do not wait for the final invoice before notifying

Section 104 of Germany’s Insurance Contract Act provides one week to notify circumstances that could create responsibility towards a third party. A third party claim must likewise be notified within one week. Certain court matters and investigations require notification without undue delay. Read the actual contract too and clarify its reporting channel. Establishing the final amount is a different task from initial notification.

Identify what has already been reported and what must follow. A missing repair invoice is no useful reason to leave the incident unidentified internally. Help the customer involve the responsible claims department through the intended route. The account can state exactly what is unknown. Invent neither an additional fixed extension nor a guaranteed insurer response time.

Court documents need separate attention. Reporting internally to a broker does not automatically answer what action a court or authority requires. GDV model B3-3.2.2 treats these matters and time-bound responses to certain documents separately. Customers should clarify an actual document and required steps with the insurer and, where needed, qualified legal advisers. Waiting for general claim feedback does not replace that assessment.

Identify the relevant insurance precisely

Connect the incident to the actual contract: which policyholder, activity and version of conditions? A common brand does not identify the entity. If several policies exist, leave uncertainty explicit and obtain clarification. An arbitrary policy number does not make a notification professionally correct merely because it was found in a system.

Describe work understandably: was third party property worked on, equipment accepted for repair or a product already supplied? These facts help direct assessment. You need not classify the claim conclusively under a coverage clause yourself. A clear sequence is more useful than a premature label concealing important details.

The GDV model terms AVB BHV, October 2026 distinguish assessment, defence against unfounded demands and indemnification against established obligations. Section 100 of the Insurance Contract Act also mentions defence against unfounded claims. Explain that notification prepares assessment; it does not establish that a demand is valid or will be paid.

Preserve originals separately from later additions

Distinguish the original demand from additions. An initial amount can change after another invoice. Keep the sequence and dates instead of replacing the first message with a cleaned summary. An overview can show which version is current, while preserving what the customer actually received and forwarded at each stage.

Use information needed for the incident and the business’s appropriate established transmission routes. An initial note about property damage does not need unrelated people’s private documents collected pre-emptively. Ask the responsible handler which addition is necessary. Customers can supply it specifically, without completeness becoming indiscriminate document sharing.

Label your summaries as summaries. An organised timeline helps, but does not replace the client’s original statement or invoice. Keep conflicting documents visible and let the responsible party clarify what is accurate. This supports assessment better than apparent consistency created by silently deleting an inconvenient detail.

A fictional property loss shows the sequence

The following incident, weekdays and amounts are fictional, not an actual claim notification.

An installation business works on Monday. On Tuesday its client reports damaged fittings, suspects installation caused them and initially asks for €6,000. The business did not observe damage while working. Separate the work date, discovery or report and alleged cause. Record the demand as a demand and the cause as information still requiring assessment.

The business notifies through its intended claims route and records missing information. On Thursday a repair quotation for €7,200 arrives, €1,200 above the initial €6,000. It adds to the basis of the demand without deciding responsibility or coverage. The original message remains part of the history.

The claims department asks about the working area and existing records of the fittings’ condition. Help assign that question to the business. Do not replace unknown facts with convenient assumptions. The overview can state: notified, new document received, specified information requested. “Claim admitted” would be a different, unsubstantiated statement without an actual corresponding decision.

The customer asks whether to promise a particular payment immediately. Treat this as a separate coordination question, not an automatic consequence of notification. The business obtains the appropriate insurer response and legal advice if necessary. Useful support routes the question and possible consequences to the responsible party instead of inventing a personal settlement promise.

Explain admissions without false automatic consequences

Section 105 of the Insurance Contract Act renders ineffective an agreement freeing the insurer from payment because the policyholder settles or admits a claim without consent. Do not claim every admission automatically removes all cover. That would misstate the provision. Equally, it does not mean every voluntarily promised payment is insured regardless of the actual claim.

Under GDV model A1-4.1, admissions or settlements without consent bind the insurer only within the described extent of a claim that would exist anyway. Actual entitlement and contract need professional assessment. Separate factual communication from a statement about liability, settlement or payment. Appropriate individual wording belongs with responsible coordination and, where needed, legal advice.

Customers understandably may want to help quickly while questions remain. Help identify what the client wants, what is established and what answer is missing. This is humane and factual. It requires neither aggressive rejection of every complaint nor premature promises. Customers gain an identifiable path towards professional handling of their actual concern.

Recognise new documents as new steps

Classify later communications by content. Another invoice, further factual information and a court document mean different things. Filing everything as another claim email can hide necessary action. Record what is new and which responsible party needs to know. Assessment of a deadline or legal consequence remains with the qualified person responsible.

Also route loss mitigation and further work questions appropriately. GDV model B3-3.2.1 addresses duties and reasonable insurer instructions. It does not create technical instructions for damaged equipment. Involve the appropriate professionals where safety is affected. Your organisational support enables coordination rather than authorising repair or continued operation.

Check whether a follow-up asks for facts or assessment. “What work took place that day?” requires facts. “Is it covered?” requires a professional contractual answer. One person may not provide both. Assign questions by content and mark pending parts, so a complete factual description is not mistaken for confirmed cover.

When the client adds several demand items, retain their original descriptions. Repairs and claimed loss of use concern different amounts and bases. You need not decide entitlement to forward them separately. Also distinguish an amount merely announced from one explained by a particular document. This helps the claims handler request the missing basis specifically.

Close with an understandable progress statement

Summarise separately what was notified, documents added, who is examining which question and which answer is missing. Completed transmission is not a completed claim decision. Clear allocation helps the business identify its next task and lets your team resume from the actual position without reinventing the history.

Support new business liability contacts professionally

Register as a broker, intermediary or commercial insurer on the business liability purchase page. New enquiries open personal conversations; risk information is not promised as already collected. The welcome email leads to webRichtung Customer, where you see the current price before a binding lead order. Your advice clarifies actual needs and the appropriate next step.