Message Content Inventory |
Archived, and was part of release 201501 : Identifier : M0122 - Contrat, versement libre - (Contrat ou investissement - Information sur versement libre encaissé) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 3 - 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 | u |
Nature du document
|
Yes
|
5
|
Cond.
|
Mandatory and code = 4
|
MessageNatureProcesscode
|
|
60 | u |
Type de modification
|
Yes
|
6
|
Cond.
|
Mandatory and code = 11 / 12 / 13 / 14
|
ChangeTypeProcesscode ProcessingIndicatorDetail ProcessingIndicatorValueCoded
|
|
70 | u |
Type de police
|
Yes
|
8
|
Option.
|
PolicyProductcode
|
||
80 | u |
Produit
|
No
|
-
|
-
|
Option.
|
if present- then both code AND label
|
ProductNameProductcode ProductDetail ProductIdentifier CodeListIdentifier ProductName
|
90 |
Date d'effet
|
No
|
-
|
-
|
Mand.
|
InceptionDate
|
||
100 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
110 |
Numéro d'avenant
|
No
|
-
|
-
|
Mand.
|
EndorsementReference ReferenceDetail ReferenceContent
|
||
120 |
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
|
|
130 |
Référence des paiements
|
No
|
-
|
-
|
Option.
|
PaymentReference
|
||
140 | d |
Référence des conditions générales
|
No
|
-
|
-
|
Mand.
|
1..n présences
|
GeneralConditionsReference
|
150 |
Etat de l'acceptation de la nouvelle affaire ou du projet
|
Yes
|
2
|
Option.
|
StateOfAcceptanceCode
|
|||
160 |
Etat de la police
|
Yes
|
3
|
Mand.
|
ContractStatusCode
|
|||
169 | n |
Prime technique ou prime pure
|
No
|
-
|
-
|
Option.
|
BasePremiumAmount
|
|
170 | u |
Coûts techniques
|
No
|
-
|
-
|
Option.
|
TechnicalExpensesAmount
|
|
180 | u |
Frais de commercialisation
|
No
|
-
|
-
|
Option.
|
CommercializationExpensesMotorLiabilityAmount
|
|
190 | u |
Prime nette
|
No
|
-
|
-
|
Option.
|
NetPremiumAmount
|
|
200 | u |
Autres coûts à ajouter à la prime nette
|
No
|
-
|
-
|
Option.
|
OtherCostsToBeAddedToTheNetPremiumAmount
|
|
210 | u |
Frais de fractionnement
|
No
|
-
|
-
|
Option.
|
SplittingCostsAmount
|
|
220 | u |
Frais
|
No
|
-
|
-
|
Option.
|
CostAmount
|
|
230 | u |
Charges
|
No
|
-
|
-
|
Option.
|
ChargesAmount
|
|
240 | u |
Charges et frais
|
No
|
-
|
-
|
Option.
|
ChargesAndCostsAmount
|
|
250 | u |
Prime brute
|
No
|
-
|
-
|
Option.
|
GrossPremiumAmount
|
|
260 | u |
Frais de quittance
|
No
|
-
|
-
|
Option.
|
PremiumNotificationCostsAmount
|
|
270 | u |
Total à payer
|
No
|
-
|
-
|
Option.
|
TotalToBePaidAmount
|
|
280 | u |
Commission
|
No
|
-
|
-
|
Option.
|
CommissionAmount
|
|
290 | u |
Commission d'acquisition - total
|
No
|
-
|
-
|
Option.
|
AcquisitionCommissionTotalAmount
|
|
300 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
|
310 |
Participation coassurance
|
No
|
-
|
-
|
Option.
|
ParticipationOfCoInsurerPercentage
|
||
320 |
Pourcentage d'encaissement coassurance
|
No
|
-
|
-
|
Option.
|
PercentageCoInsuranceCollectionPercentage
|
||
330 |
Majoration selon périodicité
|
No
|
-
|
-
|
Option.
|
SurchargeDependingOnPeriodPercentage
|
||
340 | d |
URL conditions générales
|
No
|
-
|
-
|
Option.
|
0..n présences
|
UrlGeneralClausesText
|
350 | n |
Condition générale
|
No
|
-
|
-
|
Mand.
|
a minimum of one is mandatory
|
ClauseGeneral
|
360 | n |
Condition générale - Référence des conditions générales
|
No
|
-
|
-
|
Mand.
|
GeneralConditionsReference
|
|
370 | n |
Condition générale - URL conditions générales
|
No
|
-
|
-
|
Option.
|
UrlGeneralClausesText
|
|
380 | n |
Condition générale - Clause, titre
|
No
|
-
|
-
|
Option.
|
ClauseTitleText
|
|
390 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
400 | u |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
410 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
InsurerInCaseOfCoInsuranceCode
|
|||
420 |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
||
430 | u |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
440 | u |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
450 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Mand.
|
BrokerPolicyReference
|
||
460 | u |
Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
one of PTY003GRPv7- PTY003PMv7- PTY003PPv8
|
PartyMainPolicyHolder
|
470 | u |
Objet de risque
|
No
|
-
|
-
|
Mand.
|
1..n presencies RODGENv10
|
ObjectInsured...
|
(*) 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.