EP1831832A1

EP1831832A1 - Dynamic system and method for automatically checking and forwarding damage notes and damage claims

Info

Publication number: EP1831832A1
Application number: EP05849817A
Authority: EP
Inventors: Manuel Bolano; Loraine Van Eeden; Arnold Glogg
Original assignee: Swiss Reinsurance Co Ltd
Current assignee: Swiss Re AG
Priority date: 2004-12-27
Filing date: 2005-12-21
Publication date: 2007-09-12
Also published as: WO2006074682A2; EP1711916A1; US20090119132A1; WO2006069952A2; US8583458B2

Description

Dynamic system and method for the automated verification and transmission of claims and claims

The present invention relates to a dynamic system for automated checking and transmission of damage reports and claims, and a corresponding method. In particular, the invention relates to verification and delivery systems used in multi-stage damage coverage systems.

Each year, many industries and businesses experience high claims losses. Such cases of damage also occur in private persons. On the one hand, this affects damage caused to industry and businesses by any external circumstances, such as storms (hurricanes, floods, etc.), fire, war, terrorist attacks, etc., but also damages caused by liability, such as Example product liability (especially in the chemical or pharmaceutical industry, etc.) or incorrect or inexpertly performed work arise. Due to the general trend towards globalization and the associated conglomeration of industry and the worldwide distribution of products, such damages can increasingly take on tens of millions or even billions of euros. Thus, the continued existence of entire companies and branches of business can depend on a careful, efficient coverage of possible damage. In order to ensure the coverage of large amounts of damage, today there are usually multi-level insurance systems with primary insurers and reinsurers. In reinsurance, cover for a single risk or a large number of individual risks with common characteristics is transferred wholly or in part from one primary insurer to another insurer, without dissolving the original insurance. As a result, the primary insurer can pass on partial amounts of the insured sum to be reinsured, which is why reinsurance is also referred to as the insurer's insurance. Only through the interaction between a primary insurer and a reinsurer can the loss cover be successfully guaranteed, even for major risks and claims. The technical basis for effective damage coverage is the secure and error-free recording, assignment, checking and transmission of the occurred damage cases. In addition to the actual amount of damage, more and more cases of damage are often accompanied by lengthy and cost-intensive legal proceedings if the legal situation is unclear. Such pending

Procedures often lead to great uncertainty of potential investors and investors (for example, stock market investors) for the industry in question, as many examples from the chemical, tobacco and food industries, but also for example from the automotive and construction industries (earthquake resistance of buildings, etc.). ) occupy. It is also clear, of course, that an insurance system should be as secure as possible from claims that have been reported incorrectly or fraudulently with corresponding claims, since the functioning as such is otherwise called into question. With the large sum of damage cases, the individual case can hardly be sensibly checked without effective automation of the procedure. It therefore satisfies a great need of industry to have a functioning, efficient and automated verification of cases.

In the state of the art, the individual cases of damage are normally only checked by the primary insurer for their accuracy and accuracy. Secondary or reinsurance companies usually check the claims only with regard to formal requirements and also only on a random basis. However, the conventional methods of damage detection tend to be full of errors. In particular, the manual recording, input and processing of the data contribute significantly to this. In most cases a distinction can be made between administrative and formal criteria (administrative accounting) and technical criteria (technical accounting) when assessing damage. Both detection methods are typically performed manually or at best semi-automatically. The same applies to secondary or reinsurance companies. For reinsurers, the situation is usually even more difficult, as reinsurers often do not have easy access to the data banks of the primary insurer. As a result, the review of the claims by the reinsurer is usually limited to a random check. Numerous automatic or semi-automatic methods for checking the accuracy of the claims for damage are therefore known in the state of the art. Thus, for example, the patent US 6,810,382 such a test method for claims for illness and / or accidents. In a first step, a claim is recorded, in a second step, the data of the claim is further processed and the amount of the severance pay negotiated and in a third step, finally, the loss amounts are settled or the corresponding persons compensated. Although this procedure automates individual steps, it still does not allow fully automated control and verification of claims. Another control method is presented, for example, in US Pat. No. 2004/0220784. This method allows predicting the number and size of claims for a given insurance policy. Thus, this procedure also indirectly allows a certain review of the claims, also for secondary or reinsurers. The disadvantage of this prior art is that the individual cases of damage can not really be checked, but the control is based solely on stochastic predictions.

US Pat. No. 2004/0122717 also shows a test method for claims for damages in which, in particular, claims for damage during illnesses and dental visits can be accurately recorded and passed on. For this purpose, the method uses a first database with insurance-relevant information about the respective insured and a second database with insurance-relevant information about the respective doctors or dentists. The damage claims entered are compared with the information in the respective databases, so that only the accurate data from the databases is forwarded to the insurer. This method also has the disadvantage that only certain details of the recorded damage cases can be checked, while many relevant information can still not be checked automatically.

Another system is described in international patent application WO 01/93173. It allows an efficient and easy Transmission of claims through a computerized system. In particular, this system is suitable for the transmission of disease data of a patient from a doctor to the corresponding insurance. The data to be transmitted is adapted to the formal requirements of each insurer, so that they are also indirectly checked for consistency and accuracy. However, the described system can not guarantee an automated systematic check of the data to be transmitted. Finally, also in the European patent application EP 1 220 131 a transmission system for the claims is shown, in which the compensation for damages is reimbursed by replacement products. However, claims are not automatically controlled in this system.

It is therefore an object of this invention to propose a dynamic system and a corresponding method for the automated checking and transmission of claims and claims that do not have the above-mentioned disadvantages of the prior art. In particular, it should be a solution that allows, in multi-stage systems for damage coverage, to detect, assign, review and transmit damage cases and adjust them if necessary. At the same time, the system should be able to adapt dynamically.

According to the present invention, this object is achieved in particular by the elements of the independent claims. Further advantageous embodiments are also evident from the dependent claims and the description.

In particular, these objects are achieved by the invention in that the dynamic system comprises cellular, decentralized detection units with assigned areas for recording damage records based on first control parameters, wherein a damage record comprises at least one event parameter for the respective area, that the system comprises a central unit, which central unit is bidirectionally connected to the detection units via a network, wherein at least event parameter data from the detection units to the Central unit can be transmitted, that the central unit comprises a filter module for selecting first and second damage records based on at least one threshold assigned to the respective area, that the central unit comprises an analysis module for detecting and eliminating first damage records erroneously detected by the detection units based on second control parameters, in that the central unit comprises a control module for dynamically adjusting and storing the thresholds associated with the respective areas based on the filtered first damage records, and the central first unit transmits the filtered first damage records without erroneously detected first damage records to the processing apparatus, releasing them for multi-stage damage coverage become. The second control parameters may include, for example, at least data for automated checking of cash CaII and / or countersignature and / or policy and / or validity period and / or risk threshold value for the respective area and / or goodwill payments (ex gratia). Among other things, this invention has the advantage that damage reports and claims for damage in multilevel damage coverage systems can be automatically recorded, checked and transmitted smoothly between the various system levels. In addition, the invention has, inter alia, the advantage that the dynamic system can adapt itself or the threshold values assigned to a region in a self-organizing manner to a specific area. Only this allows complete automation of the system or process. Furthermore, automated checking, checking and filtering of claims or claims for damages can also be carried out by second or reinsurance companies, without the possibility of only checking samples (peer review). The automated control and monitoring of claims allows insurance and reinsurance companies to better assess the risk and adjust the premiums accordingly. In particular, the system or the corresponding method is also suitable for personal injury, for example in health and / or life insurance systems (such as deaths and / or illnesses, etc.) as well as consequences of accidents to persons etc. and not only for PNC coverages (such as Example daily allowance and / or passenger and / or passenger insurance covers etc.). The system can be fully automated and / or semi-automated realized with Semi-automation individual modules and / or system components are executed manually. In particular, it may make sense that, for example, the damage validation is realized manually in the system due to internal work flows. The components necessary for the system can be implemented, for example, in terms of hardware and / or software. When

Control system, the system according to the invention, for example, also directly, for example by means of a Rapportierungsmoduls the manually acquired data of a technical accounting are compared and automated and / or semi-automated and / or manually compared. Any irregularities could then be detected and filtered out by the system, for example. However, the control system can also be used, for example, as an intermediate module in the workflows of technical accounting, without the system according to the invention having a direct connection to an accounting and / or billing system. The system was based, for example, on the fact that certain damage records or damage events or damage cases are taken out of the technical accounting process and transferred to the system according to the invention for individual assessment. After that, for example, the damage records would flow back into the normal technical accounting process for completion.

In an embodiment variant, the central unit comprises a calculation module for determining premiums for customer parameters assigned to a region. One of the advantages of this embodiment variant is that the premiums can be automated, optimized and adapted. For the customer, the most optimal premium based on the latest data can be calculated easily and quickly at any time.

In another embodiment, this includes

Calculation module Means for iteratively adjusting the premiums based on the corrected first and second damage records. Among other things, this embodiment variant has the same advantages as the preceding embodiment variant, with the iterative adaptation of the premiums representing a particularly advantageous adaptation method from the series. In yet another embodiment variant, the central unit comprises an expert module for checking medical information data, if these are assigned to a damage record. Among other things, this has the advantage that damage reports in the health sector can be easily and automatically monitored and controlled.

In a further embodiment variant, the second control parameters comprise at least one upper claim threshold, wherein all damage records above the claim threshold are automatically assigned to the first damage records. This has the advantage, among other things, that all damage notifications that are above a certain amount of damage are actually checked or checked by the system.

In one embodiment, the central processing unit comprises means for checking multiple claims, wherein all damage records above the claim threshold value are assigned to the first damage records. This has the advantage, among other things, that events that have been incorrectly recorded, for example, twice or more times, are automatically detected and filtered out by the system, which allows substantial time and material savings.

At this point it should be noted that the present

Invention also relates to a corresponding method in addition to the inventive system.

Hereinafter, embodiments of the present invention will be described by way of examples. The examples of the embodiments are illustrated by the following enclosed figures:

FIG. 1 shows a block diagram which schematically shows an exemplary embodiment of a dynamic system 40 according to the invention for the automated checking and transmission of damage reports and claims. FIG. 2 shows a block diagram which schematically illustrates an exemplary embodiment of a technical accounting according to the invention.

FIG. 3 shows a block diagram which schematically illustrates a claim check (reference number 209) of an exemplary embodiment of a technical accounting according to FIG. 2 or the invention.

Figure 4 is a block diagram schematically illustrating a dynamic system of a reinsurer according to the invention.

Figure 1 illustrates an architecture that may be used to implement the invention. In this embodiment, the dynamic system 40 for automated checking and transmission of damage reports and claims for multi-stage damage coverage includes decentralized, cellular detection units 10/11/12 with associated areas 50/51/52. By means of the detection units 10/11/12 damage records or corresponding damage events based on first control parameters, for example, can be detected cellularly. The detection units 10/11/12 may for example be associated with primary insurances, be fully automated or semi-automated, and include corresponding hardware and / or software components. A damage record and / or damage event may include one or more event parameters for the respective area 50/51/52.

The control system 40 comprises a central processing unit 20. The central processing unit 20 is bidirectionally connected to the detection units 10/11/12 via a network 30. The network 30 may comprise, for example, networks, such as local area network (LAN), wide area network (WAN) or the Internet, for example via the public switched telephone network (PSTN) or a public land mobile network (PLMN) Mobile Network) such as GSM (Global System for Mobile Communication) or UMTS (Universal Mobile Telephone System) networks, etc. Via the network 30 at least event parameter data can be transmitted from the detection units 10/11/12 to the central unit 20. By way of example, the detection units can be uniquely identified and / or authenticated by the central unit by means of an identification module. The central processing unit 20 comprises a filter module 22 for selecting first and second damage records based on at least one threshold associated with the respective area 50/51/52. The central processing unit 20 includes an analysis module 21 for detecting and eliminating first damage records erroneously detected by the detection units based on second control parameters. Filter module 22 and analysis module 21 may be realized, for example hardware and / or software. The second control parameters may include, for example, at least data for the automated check of cash CaII and / or countersignature and / or policy and / or validity period and / or risk threshold value for the respective area and / or ex gratia payments. Also, the second control parameters may include at least one upper claim threshold, wherein all damage records above the claim threshold are automatically assigned to the first damage records.

The filtered first damage records are sent to the central unit 20 without falsely detecting first damage records

Processing device 25 transmitted and released for single and / or multi-stage damage coverage. The threshold values assigned to the respective areas 50/51/52 can, for example, be dynamically adjusted based on the filtered first damage records by means of the control module 21 of the central unit 20. The control module 21 can also be realized, for example, in terms of hardware and / or software. For example, the central processing unit 20 may also include a calculation module 23 for determining premiums for customer parameters associated with an area. This allows premiums to be dynamically calculated and / or adjusted region-specific. For this purpose, the calculation module 23 can include corresponding hardware- and / or software-configured means for iteratively adjusting the premiums based on the corrected first and second damage records. For applications in the health sector, it may be useful for the central unit 20 to comprise an expert module 24 for checking medical information data, if these are assigned to a damage record. The central unit 20 may in particular comprise means for checking multiple claims, wherein all damage records above the claim threshold are automatically assigned to the first damage records. These means may be associated with the filter module 22, the analysis module 21 or the control module 21, or be implemented as an independent hardware and / or software module.

For example, in the system 40, a distinction can be made between administrative accounting and technical accounting. Of course, however, the two steps can be integrated, in series or in parallel. In the account, the system 40 first receives the notification of the detection and / or the occurrence of a damage record. This can be done, for example, by means of a registration unit 10/11/12 as an external automated or semi-automated submission service, by means of an individual claim, by means of a claim for damages (cash call), by means of other claims for reimbursement and / or an incoming damage invoice or claim. This can in particular include, for example, the reading of an application form, an electronic claim for damages, a notification via the Internet (for example by means of secure file transfer), a postal letter or an electronic mail, etc. Next, the system 40 may include, for example, administrative requirements such as signature, countersignature, date bordereaux, cash caII, etc. The damage claim of the corresponding damage record is set to "notified" in the system 40, whereupon the damage amount is reserved, for example, by means of the processing device 25. Furthermore, for example, the completeness of the required data can be checked and, if not present, appropriate steps to supplement or reject the claim. In the same way, for example, further determinable administrative criteria can be checked by means of the system 40, for example policy is not sufficiently reinsured or not at all and / or not covered by appropriate policy, premiums not paid, etc. The damage records to be further examined may be based, for example, on the following criteria: amounts of damage greater than the area limit and / or threshold of the assigned area 50/51 / 52 voluntary payments or goodwill payments made by the primary insurer and / or claims for damages, for example, over a longer period than specified, and / or claim for damages, clear indications of fraud / fraudulent intentions of the user / client or manipulation of the registration unit 50/51/52 and / or claims relating to so-called death claims (cases in which the insured person dies) and living benefit claims (cases in which the amount of the damage is due to the surviving insured person) etc .. Living Benefit Claims For example, additional checks such as medical information (if available damage verification within a predetermined time limit, for example 3 years, by a claims expert, etc.

Figure 2 shows schematically an embodiment of a technical accounting according to the invention. In reference number 201 (1st level), otherwise, the client (primary insurer or customer of a primary insurer) and / or user of the dynamic system 40 sends and / or sends one

Notification to the technical accounting and / or operator of the dynamic system 40. In the second stage (reference number 202), the loss record or event is checked for ex-gratia and 203 records the relevant data if it is an ex-gratia case , In step 205 (3rd stage), it is checked whether assignable

Reinsurance contracts or policies exist for the event. If not, the damage record or damage event is rejected 204. 208 (4th stage) checks the event for a cash caII. For a Cash CaII 207, the event is forwarded directly to the 6th stage 209 for expedited processing. If it is not a cash caII 210, the central processing unit checks in stage 5 whether it is an isolated loss event or whether other loss events are related or correlated with it. If not, as described above, the transfer to the 6th stage 209 for processing or validation of the claim. The validation level 6 will be described in more detail below in particular with reference to FIG. If there are correlating damage records, all correlated damage records from the damage records are filtered out by means of 212. If, according to the sixth stage 209, a damage record is validated as "not in order" 213, the damage record is either rejected 204 or further information is requested or recorded 200 by the central unit 20. Finally, the reference list 214 is checked With the 8th stage 215 the damage sums reserved in the system. Under determinable boundary conditions 216, a specific damage record can be passed on to further specialized expert modules 218 or other checking units 218. In particular, damage records can already be approved for payment 217, if necessary. If the damage record is released for payment, the 9th stage 219 takes over the settlement and payment of the loss. This can be automated or semi-automated. In reference number 221, the

Central unit 20, the data on the information necessary for billing. In the 10th stage 223 further expert systems and / or modules can be appended and the data released for further review 225. For example, the payment or billing of the claim amount may be made depending on or independent of the outcome under 225. In particular, the 10th level at 226 may include storing and managing classified (paid / rejected / unpaid / pending etc.) damage records. The reference number 227 may include, for example, a hardware and / or software automated or semi-automated expert system that additionally reviews 224 the transmitted (for example suspicious) damage records. For example, if a damage record is rejected, the data is sent directly to 226 for storage. On the other hand, if a damage record is accepted 220, the described billing procedure can begin with 219.

Figure 3 shows a possible embodiment of the

Validation level 6. Reference number 300 checks whether all necessary information is available to system 40 for validation. If not, further information is requested 301. By 303 it is checked whether it is an isolated damage record or damage event or whether further damage events are related or correlated with it. If not, as above, the transfer to 302 for the collection and / or storage of damage records and for further processing or validation of the claim. If there are correlated damage records, then by means of 302 all correlated damage records from the damage records are filtered out or collected. Reference number 306 includes a random modulus for random selection of damage records. 315 checks whether the corresponding damage record can be assigned to a reinsurance contract or policy or not. If not, the damage record is rejected 309. For isolated damage records according to 303, for example, with predeterminable conditions it can be determined whether the damage record should be individually checked or not. 307. If not, it can be decided by means of 304, for example, whether the damage record should be recognized 310 or not. If not, for example, randomly correlating

Damage records (eg, fraudulently or mistakenly double or multiple recorded damage records). If the damage record was not recognized, 312 will check if the same damage record has already been recorded. If so, the damage record is rejected 305. If no, 313 checks whether the damage record has already been rejected. 314 supplements the corresponding damage record with additional information, if available in the system. By means of determinable conditions, the 6th stage can be concluded 320 or it can be checked whether payments or further payments 319 are necessary, for example based on a change in the insurance benefit. 316 checks if modifications based on 319 are necessary and if not, for example, 318 can be used to check if already closed case is reopened. 322 verifies a possible assignment to already existing, similar cases, for example to damage records based on the same or similar thing. 321, for example, checks whether a contract that can be assigned to the damage record is legally valid and signed. If not, for example, 324 corresponding units may be notified and / or data transmitted to the appropriate units. 326 checks whether the policy that can be assigned to the claim is reinsured. It is about voluntary insurance cover 327, for example, enhanced and / or additional terms of pay for acquisitions may be considered 330, if not 328. If the premiums allocated to the contract are not properly paid, the record of damage may be rejected 325.

If the payment of the premium or premiums can be assigned 329 by the system 40, in a next step 331 it can be checked, for example, whether this is an "early claim". If the assignment can not be made by the system 40, the damage record is forwarded to the expert unit 332, which handles the further processing. The expert unit 332 can be hardware and / or software, automated and / or semi-automated realized. If the damage record does not correspond to an early claim, Module 343 checks whether the damage record is adequately covered by the insurance policy. If not, the damage record is rejected 337. If the damage record is covered by the insurance policy, the system verifies that this type of insurance policy is covered by the associated registration unit 10/11/12 through a reinsurance contract 336. If not, then the damage record is rejected 337. 342 checks whether exclusion reasons can be assigned to the damage record. If not, the damage record is also rejected here 337. By means of 343, for example, determinable parameters can be checked by means of which the billing time can be determined, that is, for example, immediately or at a definable later point in time. The module 344 informs the associated detection unit and / or the user and / or the injured party accordingly. By means of 346, for example, the payment amount or the amount of damage can be checked. If not, for example, the damage record can also be rejected 337 or the amount of damage redefined. 333 reviews the contract limits or other contract condition parameters of the reinsurance policy. If the contract limits are exceeded, the damage is passed on to an expert unit 340 and / or transmitted, which takes over the further processing. For example, modules 340 and 332 may be performed by the same system unit. 335 checks the area limits or other limits associated with the corresponding area 50/51/52. If multiple coverage exists 339, this may, for example, change the area limits or other limits associated with the corresponding area 50/51/52 338. If this does not affect the area limits or multi-coverage does not exist, it may be useful to use other determinable characteristics of the damage record 341. If suspicions can be established, the damage remedy is passed on to and / or transmitted to an expert unit 340 for further processing. The same can be done in a review of the damage record by means of additional area parameters assigned to the particular area 50/51/52. Reference Number 347 does a final and / or summary audit of the damage record before it is released for payment or billing 348.

FIG. 4 schematically shows another dynamic control system of a reinsurer according to the invention. The reference numbers may, for example, be given as follows: System 40 receives damage event data from a registration unit 10/11/12 (technical accountig) 400. Data of the damage record is supplemented for further processing, if necessary 401. With 402, conditional parameters such as individual conditions (e.g. For example, medical data, work condition data, past activities, member agreements, employment agreements, damage event estimates or decision conditions, etc.) or general conditions (such as audits or claim amount, etc.). If further information is required by the customer 403, the corresponding registration unit 10/11/12 and / or the customer is informed 404 and the further information is acquired 405. If further medical services and / or data are required, the corresponding instruction is sent to a medical unit 408 409. When legal services and / or data are needed 413, the appropriate instruction is sent to a legal entity 414 and / or expert module that collects the required data and to the system 40 415. If the claim is within the power of attorney 416, it is checked whether the system 40 can make a decision 421 based on the data. If the claim is not within power of attorney 416, for example, a detailed check may be made by an expert module 411 which which carries out further steps and decisions or handles the processing of the damage record. It may also request further information 406. If a decision is possible 416, then the system 40 makes the decision and informs the parties concerned. The informing can be carried out, for example, automatically and / or semi-automatically. In particular, the corresponding outputs are made by means of output units 419, such as damage assessment data, application data, reports, reports etc. Further, for example, by means of the system 40, the corresponding data regarding billing, request for additional information, etc. to the customer and / or the Registration unit 10/11/12 be transmitted. If no decision is possible 416, the system may transmit the damage record to a module 421 for further detailed processing. For example, at processing 420, the module 421 may individually validate the damage record, update the operating parameters of the system 40 (thereby dynamically changing the system or adapt to the changed condition), marketing / paragraph requirements, etc. If so If the sales conditions are at stake 424, for example, further specialized verification modules such as modules for verifying large amounts of damage or ex-gratia payments can be interposed. Based on their data 422 or if paragraph requirements 424, a final decision is made by system 40 425/429. The customer can be 426 either informed directly 426 or for example by means of 430 on the associated registration unit 10/11/12. If the customer is informed directly, for example, the associated registration unit 10/11/12 can also be informed by means of 427 or via a local representative or a corresponding module 428. All the modules and units mentioned can be realized according to the invention either in terms of hardware or software.

Claims

claims

1. A dynamic system (40) for the automated checking and transmission of damage reports and claims in the case of multi-stage damage coverage systems, wherein damage records can be detected and transmitted to a processing device (25), characterized in that

the system (40) comprises decentralized cellular detection units (10/11/12) with assigned areas (50/51/52) for recording damage records based on first control parameters, wherein a damage record comprises at least one event parameter for the respective area (50/51/52). 51/52),

in that the system (40) comprises a central unit (20), which central unit (20) is bidirectionally connected to the detection units (10/11/12) via a network (30), wherein at least event parameter data are received from the detection units (10/11/12 ) are transferable to the central unit (20),

in that the central unit (20) comprises a filter module (22) for selecting first and second damage records based on at least one threshold associated with the respective area (50/51/52),

in that the central unit (20) comprises an analysis module (21) for detecting and eliminating first damage records erroneously detected by the detection units (10/11/12) based on second control parameters,

the central unit (20) comprises a control module (21) for dynamically adjusting and storing the threshold values associated with the respective areas (50/51/52) based on the filtered first damage records, and in that the filtered first damage records can be transmitted to the processing device (25) by means of the central unit (20) without falsely recorded first damage records, whereby they are released for multi-stage damage coverage.

2. Dynamic system (40) according to claim 1, characterized in that the central unit (20) comprises a calculation module (23) for determining premiums for an area (50/51/52) associated customer parameters.

A dynamic system (40) according to claim 3, characterized in that the calculation module (23) comprises means for iteratively adjusting the premiums based on the corrected first and second damage records.

4. Dynamic system (40) according to any one of claims 1 to 3, characterized in that the second control parameters at least data for automated verification of cash CaII and / or countersignature and / or policy and / or validity period and / or risk threshold for each area (50/51/52) and / or grace payments (ex-gratia).

5. Dynamic system (40) according to any one of claims 1 to 4, characterized in that the central unit (20) comprises an expert module (24) for checking medical information data, if they are assigned to a damage record.

6. Dynamic system (40) according to one of claims 1 to 5, characterized in that the second control parameters comprise at least one upper claim threshold, wherein all damage records above the claim threshold are automatically assigned to the first damage records.

7. Dynamic system (40) according to one of claims 1 to 6, characterized in that the central unit (20) comprises means for checking multiple claims, with all damage records above the Claim threshold automatically assigned to the first damage records.

8. A dynamic method for the automated verification and transmission of damage reports and claims for multi-stage damage coverage, whereby damage records are recorded and transmitted to a processing device (25), characterized

that damage records in assigned areas (50/51/52) are recorded by means of decentralized detection units (10/11/12) of a cellular system (40) based on first control parameters, wherein a damage record comprises at least one event parameter for the respective area (50/51 / 52),

in that a central unit (20) of the cellular system (40) is bidirectionally connected to the detection units (10/11/12) via a network (30), at least event parameter data being transmitted from the detection units (10/11/12) to the central unit (20 ) be transmitted,

in that first and second damage records are selected by means of a filter module (22) of the central unit (20) based on at least one threshold value assigned to the respective area (50/51/52),

by means of an analysis module (21) of the central unit (20), based on second control parameters, the first damage records erroneously detected by the detection units (10/11/12) are filtered out,

that by means of a control module (21) of the central unit (20) the thresholds associated with the respective areas (50/51/52) are dynamically adjusted and stored based on the filtered first damage records, and

that by means of the central unit (20) the filtered first damage records without falsely recorded first damage records to the Processing device (25) are transmitted, wherein they are released for multi-stage damage coverage.

9. Dynamic method according to claim 8, characterized in that by means of a calculation module (23) premiums for a region (50/51/52) associated customer parameters are determined.

10. Dynamic method according to claim 9, characterized in that by means of a calculation module (23) premiums are iteratively adjusted based on the corrected first and second damage records.

11. Dynamic method according to one of claims 8 to 10, characterized in that the second control parameters at least data for the automated verification of cash CaII and / or countersignature and / or policy and / or validity period and / or risk threshold for the respective area (50 / 51/52) and / or grace payments (ex-gratia).

12. Dynamic method according to one of claims 8 to 11, characterized in that by means of an expert module (24) medical information data are checked, if they are assigned to a damage record.

13. Dynamic method according to one of claims 8 to 12, characterized in that the second control parameters comprise at least one upper claim threshold, wherein all damage records above the claim threshold are automatically assigned to the second damage records.

14. Dynamic method according to one of claims 8 to 13, characterized in that by means of the central unit (20) the

Damage records are checked for multiple claims, with all damage records above the claim threshold automatically assigned to the second damage records.