> Syntax independent - MCIs - Messages > Details
|
Message Content Inventory |
Identifier : M0302 - Quittance, BRB / Kwijting, BRB - (Bordereau Retour / RetourBorderel)-
- Approved
, and is part of release 20100501
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) ( Additional information is present below the details-table ) |
Sender : Broker
Receiver : Insurer
Status : 2 - Version : 2
|
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 |
Quittance
|
No
|
-
|
-
|
Mand.
|
||
50 | u |
Code opération B.R.B.
|
Yes
|
3
|
Mand.
|
||
60 |
Date de début
|
No
|
-
|
-
|
Option.
|
||
70 |
Numéro de la quittance ( compagnie )
|
No
|
-
|
-
|
Option.
|
Si présent- numéro unique / Indien aanwezig- een uniek nummer
|
|
80 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
||
90 |
Unité monétaire
|
Yes
|
3
|
Option.
|
|||
100 |
Total à payer
|
No
|
-
|
-
|
Option.
|
||
110 |
Commission
|
No
|
-
|
-
|
Option.
|
||
120 | u |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
130 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
||
140 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
||
150 |
Preneur d'assurance - Nom officiel
|
No
|
-
|
-
|
Option.
|
||
160 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
||
170 |
Message end
|
No
|
-
|
-
|
Mand.
|
(*) 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.