> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components

Message Content Inventory Archived, and was part of release 201301 :
 Identifier : M0122 - Contrat, versement libre - (Contrat ou investissement - Information sur versement libre encaissé)-
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info )
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 4
Seq. n° n
u
d
(*)		 Data element
Code list
 Usage
 Mandatory
Conditional
Optional (**)
Condition(s)
Indicator
Identifier
Version
10  
Message issuing date and time
No
-
-
Mand.
 
20  
Message content inventory identifier
No
-
-
Mand.
 
30 u 
Message content inventory version
No
-
-
Mand.
 
40  
Contrat
No
-
-
Mand.
 
50 u 
Nature du document
Yes
4
Mand.
 
60  
Type de modification
Yes
5
Mand.
 
70 u 
Type de police
Yes
7
Option.
 
80  
Produit
No
-
-
Option.
 
90  
Date d'effet
No
-
-
Mand.
 
100  
Numéro de police
No
-
-
Mand.
 
110  
Numéro d'avenant
No
-
-
Mand.
 
120  
GUID (Globally Unique IDentifier) du message, sera référencé par le(s) document(s) annexe(s)
No
-
-
Cond.
Mandatory when added documents are sent. 
130  
Référence des paiements
No
-
-
Option.
 
140 n 
Référence des conditions générales
No
-
-
Mand.
1..n présences 
150  
Etat de la police
Yes
2
Mand.
 
160  
Prime brute
No
-
-
Option.
 
170  
Frais de quittance
No
-
-
Option.
 
180  
Total à payer
No
-
-
Option.
 
190  
Coûts techniques
No
-
-
Option.
 
200  
Frais de commercialisation
No
-
-
Option.
 
210  
Prime nette
No
-
-
Option.
 
220  
Commission
No
-
-
Option.
 
230  
Commission d'acquisition - total
No
-
-
Option.
 
240  
Charges
No
-
-
Option.
 
250  
Frais
No
-
-
Option.
 
260  
Charges et frais
No
-
-
Option.
 
270  
Frais de fractionnement
No
-
-
Option.
 
280  
Autres coûts à ajouter à la prime nette
No
-
-
Option.
 
290  
Nombre de documents annexes
No
-
-
Cond.
Mandatory when added documents are sent. 
300  
Participation coassurance
No
-
-
Option.
 
310  
Pourcentage d'encaissement coassurance
No
-
-
Option.
 
320  
Majoration selon périodicité
No
-
-
Option.
 
330 n 
URL conditions générales
No
-
-
Option.
0..n présences 
340  
Assureur
No
-
-
Mand.
 
350  
Assureur - Numéro CBFA
No
-
-
Mand.
 
360  
Assureur - Type d'assureur en coassurance
Yes
1
Option.
 
370  
Intermédiaire
No
-
-
Mand.
 
380  
Intermédiaire - Numéro CBFA
No
-
-
Option.
 
390  
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
No
-
-
Mand.
 
400  
Intermédiaire - Référence police producteur
No
-
-
Mand.
 
410 u 
Preneur d'assurance
No
-
-
Mand.
one of PTY003GRPv5- PTY003PMv5- PTY003PPv6 
420  
Objet de risque
No
-
-
Mand.
1..n presencies 

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