Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0410 - Demande, modification des renseignements du preneur / Vraag, wijziging gegevens verzekeringsnemer - (Communication à l'assureur des modification légales des données du preneur. Ce message ne sert pas à opérer des corrections. / Mededeling aan de verzekeraar van de gewijzigde wettelijke gegevens van de verzekeringsnemer. Dit bericht is niet bedoeld voor correcties na foute mededelingen.)
- Approved
, and is part of release 202701 |
Sender : Broker
Receiver : Insurer
Status : 2 - Version : 15
|
| 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+04+1+0410+++domain++++yyyymmddhhmm+xx' (=X916 and =X918)
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+04+1+0410+++domain++++yyyymmddhhmm+xx:::M0410' (=X943)
|
ExchangeUnitBusinessContentDescription
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+04+1+0410+++domain++++yyyymmddhhmm+xx:::M0410:15' (=X944)
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 40 |
Corrigez la dénomination, sinon la raison sociale
|
Yes
|
1
|
Mand.
|
GIS+A1ZV+x--x
|
ChangeNameProcesscode
|
|||
| 50 |
Modifiez l'adresse
|
Yes
|
1
|
Mand.
|
GIS+A094+x--x
|
ChangePolicyHolderAddressProcesscode
|
|||
| 60 |
Modifiez l'adresse de correspondance
|
Yes
|
1
|
Mand.
|
GIS+A09C+x--x
|
ChangePolicyholderCorrespondenceAddressProcesscode
|
|||
| 70 |
Modifiez l'adresse de facturation
|
Yes
|
1
|
Mand.
|
GIS+A1ZR+x--x
|
ChangeBillingAddressProcesscode
|
|||
| 80 |
Changement données de communication
|
Yes
|
1
|
Mand.
|
GIS+A1ZP+x--x
|
ChangeContactInformationProcesscode
|
|||
| 90 |
Changement ou communication nationalité
|
Yes
|
1
|
Mand.
|
GIS+A1ZO+x--x
|
ChangeNationalityProcesscode
|
|||
| 100 |
Changement forme juridique
|
Yes
|
1
|
Mand.
|
GIS+A1ZN+x--x
|
ChangeLegalFormProcesscode
|
|||
| 110 |
Echangez des données client en masse
|
Yes
|
1
|
Mand.
|
Cannot be True if another GIS is True. See BBP# 37.
|
GIS+A1ZZ+x--x
|
ExchangeCustomerDataInBulkProcesscode
|
||
| 120 |
Avenant et bloc-retour sont attendus
|
Yes
|
1
|
Mand.
|
GIS+A09E+x--x
|
AmendmentAndResponseRecordExpectedProcesscode
|
|||
| 130 |
Date lecture adresse athentique
|
No
|
-
|
-
|
Cond.
|
Mandatory with official address authentified
|
DTM+160:ddmmyyyy:001
|
AuthenticAddressTakenDate
|
|
| 140 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001:x--x
|
PolicyReference
|
||
| 150 |
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. (complementing document present)
|
RFF+084:x--x
|
MessageGuidReference
|
|
| 160 |
Données eID conformes
|
No
|
-
|
-
|
Option.
|
BIN+A09X+x--x
|
EidDataUnchangedBinary
|
||
| 170 |
Adresse officielle authentique
|
No
|
-
|
-
|
Cond.
|
Mandatory with official address present
|
BIN+A1ZQ+x--x
|
OfficialAddressAuthenticBinary
|
|
| 180 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134:x--x
|
DocumentsAttachedQuantity
|
|
| 190 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PTY+006
|
PartyInsurer
|
||
| 200 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PTY+006+x--x:006
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 210 |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+075:x--x'
|
CompanyNumberReference
|
||
| 220 |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+076:x--x'
|
EstablishmentUnitNumberReference
|
||
| 230 |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
PTY+006 - RFF+107:x--x'
|
LegalEntityIdentifierReference
|
||
| 240 |
Intermédiaire - Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
PartyIntermediary
|
||
| 250 |
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
|
|
| 260 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x:002
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 270 |
Intermédiaire - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
Added as FSMA-broker-id abandoned 15/7/2017
|
PTY+002 - RFF+075:x--x
|
CompanyNumberReference
|
|
| 280 |
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
|
|
| 290 |
Intermédiaire - LEI
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+107:x--x
|
LegalEntityIdentifierReference
|
||
| 300 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+003
|
BrokerPolicyReference
|
||
| 310 |
Intermédiaire - Correspondant
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210
|
RelatedCorrespondentOrManager
|
||
| 320 |
Intermédiaire - Correspondant - Nom officiel
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - NME+001
|
OfficialName
|
||
| 330 |
Intermédiaire - Correspondant - Numéro de téléphone bureau
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - COM+006
|
OfficeTelephoneCommID
|
||
| 340 |
Intermédiaire - Correspondant - Numéro de fax
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - COM+002
|
FaxCommID
|
||
| 350 |
Intermédiaire - Correspondant - e-Mail
|
No
|
-
|
-
|
Option.
|
PTY+002 - RPT+210 - COM+003
|
EmailAddressCommID
|
||
| 360 | u |
Preneur d'assurance - Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
one of PTY003GRPv18- PTY003PMv18- PTY003PPv19
|
PTY+003 (-GRP/PM/PP)
|
PartyMainPolicyHolder
|
| 370 | u |
Preneur d'assurance complémentaire
|
No
|
-
|
-
|
Option.
|
PTY003PPv19 based PTY+017
|
PTY+017 (-003PP)
|
PartyAdditionalPolicyHolder
|
| 380 |
Message end
|
No
|
-
|
-
|
Mand.
|
XET+04
|
|||
(*) 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.