Message Content Inventory |
Identifier : M0125 - Contrat, message production origine courtier hors contrat - (Message Production / Productie Bericht)
- Approved
, and is part of release 202201 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Broker
Receiver : Insurer
Status : 2 - Version : 6
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
40 |
Contrat
|
No
|
-
|
-
|
Mand.
|
|||
50 |
Type de police
|
Yes
|
11
|
Option.
|
PolicyProductcode
|
|||
60 |
Produit
|
No
|
-
|
-
|
Option.
|
if present- then both code AND label
|
ProductNameProductcode ProductDetail ProductIdentifier CodeListIdentifier ProductName
|
|
70 |
Date d'effet
|
No
|
-
|
-
|
Mand.
|
InceptionDate
|
||
80 |
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.
|
MessageGuidReference
|
|
81 |
GUID (Globally Unique IDentifier) du message référencé
|
No
|
-
|
-
|
Cond.
|
Mandatory when the message is a response to some previously received message-question
|
ReferencedMessageGuidReference
|
|
90 |
Référence des paiements
|
No
|
-
|
-
|
Option.
|
PaymentReference
|
||
91 |
Référence des paiements (SEPA)
|
No
|
-
|
-
|
Option.
|
PaymentReferenceSepaReference
|
||
100 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
|
110 |
Acte de gestion
|
No
|
-
|
-
|
Mand.
|
Action...
|
||
120 | u |
Acte de gestion - Code MPB origine courtier
|
Yes
|
16
|
Mand.
|
CodeMpbOriginBrokerCode
|
||
130 |
Acte de gestion - Texte de communication
|
No
|
-
|
-
|
Option.
|
CommunicationText
|
||
140 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
150 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
151 |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
CompanyNumberReference
|
||
152 |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
EstablishmentUnitNumberReference
|
||
153 |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
||
160 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
InsurerInCaseOfCoInsuranceCode
|
|||
170 |
Assureur - Correspondant - Correspondant, gestionnaire
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
180 |
Assureur - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
190 |
Assureur - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID
|
||
200 |
Assureur - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
||
210 |
Assureur - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID
|
||
220 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
||
230 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
240 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
241 |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
CompanyNumberReference
|
|
242 |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
EstablishmentUnitNumberReference
|
|
243 |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
||
250 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
BrokerPolicyReference
|
||
260 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
261 |
Intermédiaire - Correspondant - Identifiant plate-forme
|
No
|
-
|
-
|
Option.
|
Actually = XGH+1++:x--x' = recipient user address
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
270 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
280 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID
|
||
290 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
||
300 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID
|
||
310 | u |
Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
one of PTY003GRPv13- PTY003PMv13- PTY003PPv14
|
PartyMainPolicyHolder
|
311 | u |
Co-preneur d'assurance
|
No
|
-
|
-
|
Option.
|
PTY003PPv14 based PTY+017
|
PartyAdditionalPolicyHolder
|
320 | u |
Objet de risque
|
No
|
-
|
-
|
Mand.
|
1..n presencies RODGENv18
|
ObjectInsured...
|
330 |
Message end
|
No
|
-
|
-
|
Mand.
|
(*) 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.