Articles in this section

How insurance claims relate to damage cases

Published:
Updated:

This article explains how insurance claims in the Versicherung module relate to damage cases (Schadensfälle) in the Schadenmanagement (damage management) module, so you understand which module owns which data. Working with claims requires the versicherung:claims permission.

The core relationship

Every insurance claim is anchored to exactly one damage case. The damage case describes the incident - what happened, to which vehicle, and when - while the insurance claim describes the financial and contractual side with the insurer. One damage case is the source of truth for the incident; the claim is how you pursue cover for it.

Damage case (Schadenmanagement)Insurance claim (Versicherung)
Schadensnummer (damage number)Claim number
Affected vehicleLinked policy covering that vehicle
Incident date and descriptionClaim type and fault classification
Case status (for example, open)Claim status, reserve, and settlement

Why the split exists

The two modules serve different audiences. Schadenmanagement handles the operational side of an incident - opening the case, tracking deadlines, and moving the case through its status. Versicherung handles the insurance side - which policy applies, who the adjuster is, what the insurer reserves and pays, and whether any money is recovered through subrogation (Regress). Keeping them separate means the insurance team can work claims without changing the underlying incident record.

Note: You raise a claim from a damage case; you do not create a standalone claim in Versicherung. If a claim you expect is missing, confirm the damage case exists and that a claim has been raised against the insurer.

How the two stay connected

  • The claim carries the damage case's Schadensnummer, so you can search claims by it in the Versicherung module.
  • Filtering claims by vehicle uses the vehicle recorded on the linked damage case.
  • Linking the claim to a policy connects the incident to the specific contract that covers it, which is what makes cost and loss-ratio reports meaningful.

A typical end-to-end flow

  1. A vehicle is damaged. A FleetManager opens a damage case in Schadenmanagement and assigns a Schadensnummer.
  2. A claim is raised against the insurer for that damage case.
  3. In the Versicherung module, you open the claim and link it to the policy that covers the vehicle.
  4. You classify the claim (type and fault), record the adjuster, and set a reserve amount.
  5. As the insurer works the claim, you update its status, settlement amount, and subrogation progress.
  6. When resolved, you set the closed date and closure reason, and the damage case can be closed in Schadenmanagement.
Tip: Search by Schadensnummer to jump straight from an incident conversation to its insurance claim - it is the fastest way to reconcile what operations and the insurance team each see.

Insurers and access

Insurance companies are maintained in Schadenmanagement and reused across both modules, which is why the same insurer appears on damage cases, claims, and policies. Access is also separate: the versicherung:claims permission governs the insurance claim, while damage cases are governed by the damage management module's own permissions. A user may be able to see a claim without being able to edit the underlying case, or vice versa.

Related

  • Record an insurance claim
  • Track claim status and payouts
  • Insurance reports overview
  • What the insurance module manages
AH
Written by Alexander Hagemann
Updated:
Access denied
Access denied