Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0303 - Quittance, DRQ / Kwijting, ATK - (Demande de Retour de Quittance/ Aanvraag Terugzending Kwijting)
- Approved
, and is part of release 202501 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Broker
Receiver : Insurer
Status : 2 - Version : 3
|
| 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+0303+++domain++++yyyymmddhhmm+xx' (=X916 and =X918) (domain is mandatory)
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+03+1+0303+++domain++++yyyymmddhhmm+xx:::M0303' (=X943)
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+03+1+0303+++domain++++yyyymmddhhmm+xx:::M0303:3' (=X944)
|
|
| 40 |
Quittance
|
No
|
-
|
-
|
Mand.
|
XEH+03+1
|
||
| 50 |
Adressage des documents
|
Yes
|
1
|
Option.
|
GIS+B400
|
|||
| 60 |
Date de début
|
No
|
-
|
-
|
Option.
|
DTM+041
|
||
| 70 | u |
Numéro de la quittance ( compagnie )
|
No
|
-
|
-
|
Cond.
|
Mandatory if available.
|
RFF+027
|
| 80 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001
|
||
| 90 |
Motif de remise ( DRQ )
|
Yes
|
1
|
Mand.
|
ATT+B405
|
|||
| 100 |
Unité monétaire
|
Yes
|
3
|
Option.
|
ATT+A660
|
|||
| 110 |
Total à payer
|
No
|
-
|
-
|
Option.
|
MOA+012
|
||
| 120 |
Commission
|
No
|
-
|
-
|
Option.
|
MOA+015
|
||
| 130 |
Texte de communication
|
No
|
-
|
-
|
Option.
|
FTX+018
|
||
| 140 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
||
| 150 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PTY+002+x--x:006'
|
|
| 160 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x:002'
|
||
| 170 |
Intermédiaire - Code carte d'échange
|
No
|
-
|
-
|
Option.
|
PTY+002+++x--x:007'
|
||
| 180 |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+075:x--x
|
|
| 190 |
Intermédiaire - Numéro unité d'exploitation
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+076:x--x
|
|
| 200 |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+107:x--x
|
||
| 210 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
PTY+002, RFF+003
|
||
| 220 |
Preneur d'assurance
|
No
|
-
|
-
|
Option.
|
PTY+003
|
||
| 230 |
Preneur d'assurance - Identifiant auprès de l'assureur
|
No
|
-
|
-
|
Option.
|
PTY+003+x--x:002'
|
||
| 240 |
Preneur d'assurance - Identifiant auprès de l'intermédiaire
|
No
|
-
|
-
|
Option.
|
PTY+003+x--x:003'
|
||
| 250 |
Preneur d'assurance - Nom officiel
|
No
|
-
|
-
|
Option.
|
PTY+003 - NME+001
|
||
| 260 |
Preneur d'assurance - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+003 - RFF+075:x--x'
|
||
| 270 |
Preneur d'assurance - Numéro d'unité d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+003 - RFF+076:x--x'
|
||
| 280 |
Preneur d'assurance - LEI
|
No
|
-
|
-
|
Option.
|
PTY+003 - RFF+107:x--x'
|
||
| 290 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PTY+006
|
||
| 300 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PTY+006+x--x:006'
|
||
| 310 |
Assureur - Identifiant de l'intermédiaire auprès de la compagnie
|
No
|
-
|
-
|
Option.
|
PTY+006+x--x:002'
|
||
| 320 |
Assureur - Code carte d'échange
|
No
|
-
|
-
|
Option.
|
PTY+006+x--x:007'
|
||
| 330 |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+075:x--x'
|
||
| 340 |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+076:x--x'
|
||
| 350 |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+107:x--x'
|
||
| 360 |
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.