> Syntax independent - MCIs - Messages > Details
|
Message Content Inventory |
Identifier : DPTDAMGEN - - (Claimant - Damage - données communes)-
- Approved
, and is part of release 202201
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) ( Additional information is present below the details-table ) |
Sender :
Receiver :
Status : 2 - Version : 6
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
10 | u |
Claimant - Damage - type of damage
|
No
|
-
|
-
|
Mand.
|
Generic- completed with one of (DPTDAM001.v4 / DPTDAM002.v2 / DPTDAM00x.v2)
|
20 | u |
Claimant - Damage - Damaged object - type of object
|
No
|
-
|
-
|
Mand.
|
Multiple presencies possible - extended with DPTDAMDODGEN.v5
|
30 |
Claimant - Damage - Settlement - type of settlement
|
No
|
-
|
-
|
Option.
|
Multiple presencies possible
|
|
40 |
Claimant - Damage - Settlement - Date de comptabilisation
|
No
|
-
|
-
|
Cond.
|
Mandatory in message when from insurer
|
|
50 |
Claimant - Damage - Settlement - Date de début de période
|
No
|
-
|
-
|
Option.
|
||
60 |
Claimant - Damage - Settlement - Date de fin de période
|
No
|
-
|
-
|
Option.
|
||
70 |
Claimant - Damage - Settlement - Numéro de la note de calcul
|
No
|
-
|
-
|
Option.
|
||
80 |
Claimant - Damage - Settlement - Numéro de compte agent
|
No
|
-
|
-
|
Option.
|
||
90 | u |
Claimant - Damage - Settlement - Nature de paiement
|
Yes
|
2
|
Cond.
|
Mandatory - except in PAT+005
|
|
100 | u |
Claimant - Damage - Settlement - Type de paiement (avance ou solde)
|
Yes
|
2
|
Cond.
|
Mandatory - except in PAT+005
|
|
110 | u |
Claimant - Damage - Settlement - Mode de paiement
|
Yes
|
3
|
Cond.
|
Mandatory - except in PAT+005
|
|
120 |
Claimant - Damage - Settlement - Originaire du paiement
|
Yes
|
1
|
Option.
|
|||
130 |
Claimant - Damage - Settlement - Destinataire du paiement
|
Yes
|
1
|
Option.
|
|||
140 |
Claimant - Damage - Settlement - Paiement effectué
|
No
|
-
|
-
|
Option.
|
||
150 | u |
Claimant - Damage - Settlement - Montant prestation
|
No
|
-
|
-
|
Cond.
|
Mandatory - except in PAT+005
|
160 |
Claimant - Damage - Settlement - Texte de communication
|
No
|
-
|
-
|
Option.
|
||
170 |
Claimant - Damage - Settlement - Bénéficiaire
|
No
|
-
|
-
|
Option.
|
GDPR might not allow such info in case this is not the policyholder or the insured.
|
|
180 |
Claimant - Damage - Settlement - Bénéficiaire - Identifiant
|
No
|
-
|
-
|
Option.
|
||
190 |
Claimant - Damage - Settlement - Bénéficiaire - Nom officiel
|
No
|
-
|
-
|
Mand.
|
||
200 |
Claimant - Damage - Settlement - Bénéficiaire - Adresse
|
No
|
-
|
-
|
Mand.
|
||
210 |
Claimant - Damage - Settlement - Bénéficiaire - Type de bénéficiaire
|
Yes
|
1
|
Mand.
|
|||
220 |
Claimant - Damage - Settlement - Destinataire (d'un paiement)
|
No
|
-
|
-
|
Option.
|
GDPR might not allow such info in case this is not the policyholder or the insured.
|
|
230 |
Claimant - Damage - Settlement - Destinataire - Identifiant
|
No
|
-
|
-
|
Option.
|
||
240 |
Claimant - Damage - Settlement - Destinataire - Nom officiel
|
No
|
-
|
-
|
Mand.
|
||
250 |
Claimant - Damage - Settlement - Destinataire - Code BIC
|
No
|
-
|
-
|
Option.
|
||
260 |
Claimant - Damage - Settlement - Destinataire - Numéro IBAN
|
No
|
-
|
-
|
Option.
|
||
270 |
Claimant - Damage - Settlement - Destinataire - Numéro de compte agent
|
No
|
-
|
-
|
Option.
|
||
280 |
Claimant - Damage - Settlement - Risk object
|
No
|
-
|
-
|
Mand.
|
Multiple presencies possible
|
|
290 |
Claimant - Damage - Settlement - Risk object - Instance name
|
No
|
-
|
-
|
Option.
|
||
300 |
Claimant - Damage - Settlement - Risk object - Instance ID at insurer
|
No
|
-
|
-
|
Option.
|
||
310 |
Claimant - Damage - Settlement - Risk object - Instance ID at intermediary
|
No
|
-
|
-
|
Option.
|
||
320 |
Claimant - Damage - Settlement - Risk object (véhicule) - Marque / modèle / type
|
No
|
-
|
-
|
Option.
|
||
330 |
Claimant - Damage - Settlement - Risk object (bâtiment) - Situation du risque
|
No
|
-
|
-
|
Option.
|
||
340 |
Claimant - Damage - Settlement - Risk object - Guarantee
|
No
|
-
|
-
|
Mand.
|
Multiple presencies possible
|
|
350 |
Claimant - Damage - Settlement - Risk object - Guarantee - Formula
|
No
|
-
|
-
|
Option.
|
||
360 |
Claimant - Damage - Settlement - Risk object - Guarantee - Nature de paiement
|
Yes
|
2
|
Option.
|
|||
370 |
Claimant - Damage - Settlement - Risk object - Guarantee - Montant franchise
|
No
|
-
|
-
|
Option.
|
||
380 |
Claimant - Damage - Settlement - Risk object - Guarantee - Montant TVA
|
No
|
-
|
-
|
Option.
|
||
390 |
Claimant - Damage - Settlement - Risk object - Guarantee - Montant prestation
|
No
|
-
|
-
|
Option.
|
||
400 |
Claimant - Damage - Settlement - Risk object - Guarantee - Montant à ajouter au montant prestation
|
No
|
-
|
-
|
Option.
|
||
410 |
Claimant - Damage - Settlement - Risk object - Guarantee - Montant à déduire du montant prestation
|
No
|
-
|
-
|
Option.
|
||
420 |
Claimant - Damage - Settlement - Risk object - Guarantee - TVA pourcentage
|
No
|
-
|
-
|
Option.
|
||
430 |
Claimant - Damage - Settlement - Risk object - Guarantee - TVA pourcentage récupération
|
No
|
-
|
-
|
Option.
|
||
440 |
Claimant - Damage - Settlement - Risk object - Guarantee - Texte de communication
|
No
|
-
|
-
|
Option.
|
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.
Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard.
And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used".
Ideally we should implement the same ideas.