SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0126 - Contrat, message production origine assureur hors contrat - (Message Production, mais hors contrat / Productie Bericht, maar los van bestaand contract)
- Approved
, and is part of release 202001 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 2 - Version : 9
|
| 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 | u |
Type de police
|
Yes
|
11
|
Option.
|
PolicyProductcode
|
||
| 60 |
Produit
|
No
|
-
|
-
|
Option.
|
if present- then both code AND label
|
ProductNameProductcode ProductDetail ProductIdentifier CodeListResponsibleAgencyCoded 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
|
|
| 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 (ou tarifiare)
|
No
|
-
|
-
|
Mand.
|
multiple presencies
|
Action...
|
|
| 120 |
Acte de gestion - Destinataire documents demandés
|
Yes
|
3
|
Option.
|
DocumentsAddresseeProcesscode
|
|||
| 130 |
Acte de gestion - Date (prévu) de l'acte de gestion
|
No
|
-
|
-
|
Option.
|
AssumedExecutedDate
|
||
| 140 | u |
Acte de gestion - Code MPB origine assureur
|
Yes
|
9
|
Option.
|
CodeMpbOriginInsuranceCompanyCode
|
||
| 150 |
Acte de gestion - Texte de communication
|
No
|
-
|
-
|
Cond.
|
Mandatory with CMPB = 10
|
CommunicationText
|
|
| 160 |
Acte de gestion - URL action technique sur dossier spécifique
|
No
|
-
|
-
|
Cond.
|
IF CMPB = 52 Envoi CRM - interaction demandée THEN Allowed
|
UrlBusinessActionOnSpecificFileText
|
|
| 170 |
Acte de gestion - Destinataire
|
No
|
-
|
-
|
Cond.
|
Mandatory when GIS+A090=4
|
ActionManagementAct - PartyCorrespondent
|
|
| 180 |
Acte de gestion - Destinataire - Identifiant du Correspondant auprès de l'intermédiaire
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - PartyIdentificationDetail - PartyIdentifier - ValueSpecificToTheBroker_003
|
||
| 190 |
Acte de gestion - Destinataire - Identifiant du Correspondant auprès de la compagnie, de l'assureur
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - PartyIdentificationDetail - PartyIdentifier - ValueSpecificToTheCompany_002
|
||
| 200 |
Acte de gestion - Destinataire - Nom officiel
|
No
|
-
|
-
|
Mand.
|
ActionManagementAct - PartyCorrespondent - OfficialName
|
||
| 210 |
Acte de gestion - Destinataire - Nom officiel - Extension
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - OfficialName
|
||
| 220 |
Acte de gestion - Destinataire - Adresse - rue
|
No
|
-
|
-
|
Mand.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress AddressDetail StreetName
|
||
| 230 |
Acte de gestion - Destinataire - Adresse - numéro de maison
|
No
|
-
|
-
|
Mand.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress AddressDetail HouseNumber
|
||
| 240 |
Acte de gestion - Destinataire - Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress AddressDetail BoxNumber
|
||
| 250 |
Acte de gestion - Destinataire - Adresse - extension
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress AddressDetail AddressExtension
|
||
| 260 |
Acte de gestion - Destinataire - Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress AddressDetail AddressIdentifier
|
||
| 270 |
Acte de gestion - Destinataire - Adresse - adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress
|
||
| 280 |
Acte de gestion - Destinataire - Adresse - code postal
|
No
|
-
|
-
|
Mand.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress PostalCode
|
||
| 290 |
Acte de gestion - Destinataire - Adresse - localité
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress CityName
|
||
| 300 |
Acte de gestion - Destinataire - Adresse - code pays
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - OfficialAddress CountryCoded
|
||
| 310 |
Acte de gestion - Destinataire - Numéro du dossier
|
No
|
-
|
-
|
Option.
|
ActionManagementAct - PartyCorrespondent - FileReference - ReferenceContent
|
||
| 320 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
| 330 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 331 |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
CompanyNumberReference
|
||
| 332 |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
EstablishmentUnitNumberReference
|
||
| 333 |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
||
| 340 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
InsurerInCaseOfCoInsuranceCode
|
|||
| 350 |
Assureur - Correspondant - Correspondant, gestionnaire
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
| 360 |
Assureur - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
| 370 |
Assureur - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID
|
||
| 380 |
Assureur - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
||
| 390 |
Assureur - Correspondant - e-Mail
|
No
|
-
|
-
|
Mand.
|
EmailAddressCommID
|
||
| 400 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
||
| 410 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
| 420 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 421 |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
CompanyNumberReference
|
|
| 422 |
Intermédiaire - Numéro unité d'établissement
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
EstablishmentUnitNumberReference
|
|
| 423 |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
||
| 430 |
Intermédiaire - Numéro du dossier
|
No
|
-
|
-
|
Option.
|
FileReference
|
||
| 440 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
| 450 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
| 460 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
OfficeTelephoneCommID
|
||
| 470 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
||
| 480 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID
|
||
| 490 | u |
Preneur d'assurance
|
No
|
-
|
-
|
Option.
|
one of PTY003GRPv11- PTY003PMv11- PTY003PPv12
|
PartyMainPolicyHolder
|
| 491 | u |
Co-preneur d'assurance
|
No
|
-
|
-
|
Option.
|
PTY003PPv12 based PTY+017
|
PartyAdditionalPolicyHolder
|
| 500 | u |
Objet de risque
|
No
|
-
|
-
|
Option.
|
0..n presencies RODGENv16
|
ObjectInsured...
|
| 510 |
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.