Message Content Inventory |
Identifier : M0603 - Récapitulation, fichier(s) PRENOT / Samenvatting, PRENOT bestanden - (Totaux de contrôle fichier(s) PRENOT / PRENOT bestanden, controle-totalen)
- Approved
, and is part of release 201901 |
Sender : Insurer
Receiver : Broker
Status : 2 - Version : 3
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
|||||||
10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
XEH+06+1+0603+++domain++++yyyymmddhhmm+xx' (=X916 and =X918)
|
ExchangeUnitIssueDateTime
|
||
20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+06+1+0603+++domain++++yyyymmddhhmm+xx:::M0603' (=X943)
|
ExchangeUnitBusinessContentDescription
|
||
30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+06+1+0603+++domain++++yyyymmddhhmm+xx:::M0603:2' (=X944)
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
40 |
Date de comptabilisation
|
No
|
-
|
-
|
Option.
|
DTM+005
|
AccountingDate
|
||
50 |
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.
|
RFF+084
|
MessageGuidReference
|
|
60 |
Mode d'encaissement de la quittance
|
Yes
|
1
|
Option.
|
ATT+B003
|
NotificationCollectionModeCode
|
|||
70 |
Unité monétaire
|
Yes
|
3
|
Option.
|
ATT+A660
|
MonetaryUnitCode
|
|||
80 |
Prime nette
|
No
|
-
|
-
|
Option.
|
MOA+013
|
NetPremiumSplittedAmount
|
||
90 |
Montant commission
|
No
|
-
|
-
|
Option.
|
MOA+015
|
CommissionAmount
|
||
100 |
Montant à payer
|
No
|
-
|
-
|
Option.
|
MOA+012
|
TotalToBePaidAmount
|
||
110 |
Nombre de documents expédiés pour ce mode d'encaissement
|
No
|
-
|
-
|
Option.
|
QTY+076
|
DocumentsSentQuantity
|
||
120 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134
|
DocumentsAttachedQuantity
|
|
130 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
PartyIntermediary
|
||
140 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PTY+002+x--x:006
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
150 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x:002
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
160 |
Intermédiaire - Code carte d'échange
|
No
|
-
|
-
|
Mand.
|
PTY+002+++x--x:007
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
161 | n |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+075:x--x
|
CompanyNumberReference
|
162 | n |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+076:x--x
|
EstablishmentUnitNumberReference
|
163 | n |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+107:x--x'
|
LegalEntityIdentifierReference
|
|
170 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PTY+006
|
PartyInsurer
|
||
180 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PTY+006+x--x:006
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
190 | u |
Assureur - Code carte d'échange
|
No
|
-
|
-
|
Option.
|
PTY+006+++x--x:007
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
191 | n |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+075:x--x'
|
CompanyNumberReference
|
|
192 | n |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+076:x--x'
|
EstablishmentUnitNumberReference
|
|
193 | n |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+107:x--x'
|
LegalEntityIdentifierReference
|
|
200 | u |
Message end
|
No
|
-
|
-
|
Mand.
|
XET+06
|
(*) 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.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.