> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : M0302 - Quittance, BRB / Kwijting, BRB - (Bordereau Retour / RetourBorderel) - Approved , and is part of release 20100501
- ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender : Broker
Receiver : Insurer
Status : 2 - Version : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10  
Message issuing date and time
No
-
-
Mand.
 
XEH+03+1+0302+++domain++++yyyymmddhhmm+xx' (=X916 and =X918) (domain is mandatory) 
20  
Message content inventory identifier
No
-
-
Mand.
 
XEH+03+1+0302+++domain++++yyyymmddhhmm+xx:::M0302' (=X943) 
30 u 
Message content inventory version
No
-
-
Mand.
 
XEH+03+1+0302+++domain++++yyyymmddhhmm+xx:::M0302:2' (=X944) 
40  
Quittance
No
-
-
Mand.
 
XEH+03+1 
50 u 
Code opération B.R.B.
Yes
3
Mand.
 
GIS+BBRB 
60  
Date de début
No
-
-
Option.
 
DTM+041 
70  
Numéro de la quittance ( compagnie )
No
-
-
Option.
Si présent- numéro unique / Indien aanwezig- een uniek nummer 
RFF+027 
80  
Numéro de police
No
-
-
Mand.
 
RFF+001 
90  
Unité monétaire
Yes
3
Option.
 
ATT+A660 
100  
Total à payer
No
-
-
Option.
 
MOA+012 
110  
Commission
No
-
-
Option.
 
MOA+015 
120 u 
Intermédiaire - Numéro FSMA
No
-
-
Option.
Since 15/7/2017 the FSMA no longer attributes such number 
PTY+002(X044-1) 
130  
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
No
-
-
Mand.
 
PTY+002(X044-2) 
140  
Intermédiaire - Référence police producteur
No
-
-
Option.
 
PTY+002, RFF+003 
150  
Preneur d'assurance - Nom officiel
No
-
-
Option.
 
PTY+003, NME+001 
160  
Assureur - Numéro FSMA
No
-
-
Mand.
 
PTY+006(X044-1) 
170  
Message end
No
-
-
Mand.
 
XET+03 

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