> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : DPTDAMGEN - - (Claimant - Damage - données communes) - Approved , and is part of release 202001
- ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 2 - Version : 5
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2 XML and JSON representation (***)
Indicator
Identifier
Version
10  
Claimant - Damage - type of damage
No
-
-
Mand.
Generic- completed with one of (DPTDAM001.v3 / DPTDAM002.v1 / DPTDAM00x.v1) 
Loss... 
20  
Claimant - Damage - Damaged object - type of object
No
-
-
Mand.
Multiple presencies possible - extended with DPTDAMDODGEN.v3 
ObjectDamaged... 
30  
Claimant - Damage - Settlement - type of settlement
No
-
-
Option.
Multiple presencies possible 
Settlement... 
40  
Claimant - Damage - Settlement - Date de comptabilisation
No
-
-
Cond.
Mandatory in message when from insurer 
AccountingDate 
50  
Claimant - Damage - Settlement - Date de début de période
No
-
-
Option.
 
PeriodStartDate 
60  
Claimant - Damage - Settlement - Date de fin de période
No
-
-
Option.
 
PeriodEndDate 
70  
Claimant - Damage - Settlement - Numéro de la note de calcul
No
-
-
Option.
 
AssessmentReference 
80  
Claimant - Damage - Settlement - Numéro de compte agent
No
-
-
Option.
 
AgentAccountReference 
90 u 
Claimant - Damage - Settlement - Nature de paiement
Yes
1
Cond.
Mandatory - except in PAT+005 
NatureOfPaymentCode 
100 u 
Claimant - Damage - Settlement - Type de paiement (avance ou solde)
Yes
2
Cond.
Mandatory - except in PAT+005 
PaymentAdvanceOrBalanceCode 
110 u 
Claimant - Damage - Settlement - Mode de paiement
Yes
3
Cond.
Mandatory - except in PAT+005 
MeansOfPaymentCode 
120  
Claimant - Damage - Settlement - Originaire du paiement
Yes
1
Option.
 
PayingPartyCode 
130  
Claimant - Damage - Settlement - Destinataire du paiement
Yes
1
Option.
 
AddresseeOfThePaymentCode 
140  
Claimant - Damage - Settlement - Paiement effectué
No
-
-
Option.
 
PaymentDoneBinary 
150 u 
Claimant - Damage - Settlement - Montant prestation
No
-
-
Cond.
Mandatory - except in PAT+005 
PaidAmountAmount 
160  
Claimant - Damage - Settlement - Texte de communication
No
-
-
Option.
 
CommunicationText 
170  
Claimant - Damage - Settlement - Bénéficiaire
No
-
-
Mand.
 
PartyBeneficiary 
180  
Claimant - Damage - Settlement - Bénéficiaire - Identifiant
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
190  
Claimant - Damage - Settlement - Bénéficiaire - Nom officiel
No
-
-
Mand.
 
OfficialName NameDetail LastName FirstName NameExtension 
200  
Claimant - Damage - Settlement - Bénéficiaire - Adresse
No
-
-
Mand.
 
OfficialAddress 
210  
Claimant - Damage - Settlement - Bénéficiaire - Type de bénéficiaire
Yes
1
Mand.
 
BeneficiaryCode 
220  
Claimant - Damage - Settlement - Destinataire (d'un paiement)
No
-
-
Mand.
 
PartyRecipientOfPayment 
230  
Claimant - Damage - Settlement - Destinataire - Identifiant
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
240  
Claimant - Damage - Settlement - Destinataire - Nom officiel
No
-
-
Mand.
 
OfficialName NameDetail LastName FirstName NameExtension 
250  
Claimant - Damage - Settlement - Destinataire - Code BIC
No
-
-
Option.
 
BicReference 
260  
Claimant - Damage - Settlement - Destinataire - Numéro IBAN
No
-
-
Option.
 
InternationalBankAccountNumberReference 
270  
Claimant - Damage - Settlement - Destinataire - Numéro de compte agent
No
-
-
Option.
 
AgentAccountReference 
280  
Claimant - Damage - Settlement - Risk object
No
-
-
Mand.
Multiple presencies possible 
ObjectInsured... 
290  
Claimant - Damage - Settlement - Risk object - Instance name
No
-
-
Option.
 
RiskObjectDetail ObjectName 
300  
Claimant - Damage - Settlement - Risk object - Instance ID at insurer
No
-
-
Option.
 
RiskObjectDetail ObjectIdentifier CodeListIdentifier 
310  
Claimant - Damage - Settlement - Risk object - Instance ID at intermediary
No
-
-
Option.
 
RiskObjectDetail ObjectIdentifier CodeListIdentifier 
320  
Claimant - Damage - Settlement - Risk object (véhicule) - Marque / modèle / type
No
-
-
Option.
 
MakeModelTypeName NameDetail LastName FirstName 
330  
Claimant - Damage - Settlement - Risk object (bâtiment) - Situation du risque
No
-
-
Option.
 
RiskAddress 
340  
Claimant - Damage - Settlement - Risk object - Guarantee
No
-
-
Mand.
Multiple presencies possible 
Guarantee... 
350  
Claimant - Damage - Settlement - Risk object - Guarantee - Formula
No
-
-
Option.
 
Formula FormulaDetail FormulaQualifier FormulaName 
360  
Claimant - Damage - Settlement - Risk object - Guarantee - Nature de paiement
Yes
2
Option.
 
NatureOfPaymentCode 
370  
Claimant - Damage - Settlement - Risk object - Guarantee - Montant franchise
No
-
-
Option.
 
ExemptionAmount 
380  
Claimant - Damage - Settlement - Risk object - Guarantee - Montant TVA
No
-
-
Option.
 
VatAmount 
390  
Claimant - Damage - Settlement - Risk object - Guarantee - Montant prestation
No
-
-
Option.
 
PaidAmountAmount 
400  
Claimant - Damage - Settlement - Risk object - Guarantee - Montant à ajouter au montant prestation
No
-
-
Option.
 
AmountToBeAddedToTheAmountPaidAmount 
410  
Claimant - Damage - Settlement - Risk object - Guarantee - Montant à déduire du montant prestation
No
-
-
Option.
 
AmountToBeDeductedFromTheAmountPaidAmount 
420  
Claimant - Damage - Settlement - Risk object - Guarantee - TVA pourcentage
No
-
-
Option.
 
VatPercentage 
430  
Claimant - Damage - Settlement - Risk object - Guarantee - TVA pourcentage récupération
No
-
-
Option.
 
VatExemptionInClaimPercentage 
440  
Claimant - Damage - Settlement - Risk object - Guarantee - Texte de communication
No
-
-
Option.
 
CommunicationText 

(*) n u d : new / updated / deleted since previous version.

(**) 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.

(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.