Syntax Independent Components

Implementation Related Components

Message Content Inventory Identifier : M0403 - Demande, liste de quittances / Vraag, lijst kwijtingen - (Demande liste de quittances impayées / Aanvraag van een lijst van onbetaalde kwijtingen)
- ( UN/Edifact MIG : Fr / Nl )
Version : 1
Status : 3
n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
XML-tag
UN/EDIFACT representation (including comments)
Indicator
Identifier
Version
 
Date de début de période
No
-
-
Option.
 
PremiumPeriod PeriodStartDate 
DTM+041 
 
Type de demande des impayés
Yes
EW20
1
Option.
 
 
ATT+EW20 
 
Commission
No
-
-
Option.
 
Commission CommissionAmount 
MOA+015 
 
Intermédiaire
No
-
-
Option.
 
PartyRole InsuranceProvider Intermediary 
PTY+002 
 
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
No
-
-
Option.
 
Intermediary BrokerAccountIdentifier 
PTY+002(X044-2) 
 
Intermédiaire - Code carte d'échange
No
-
-
Option.
 
InsuranceProvider Exchange80DestineeCode 
PTY+002(X076) 
 
Assureur
No
-
-
Option.
 
PartyRole Insurer 
PTY+006 
 
Assureur - Numéro CBFA
No
-
-
Option.
 
InsuranceProvider ICBIdentifier 
PTY+006(X044-1) 
 
Assureur - Code carte d'échange
No
-
-
Option.
 
InsuranceProvider Exchange80DestineeCode 
PTY+006(X076) 

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