> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 201101 :
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 : 2
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  
Nature du document
Yes
3
Mand.
 
MessageNatureProcesscode 
60  
Type de modification
Yes
5
Mand.
 
ChangeTypeProcesscode ProcessingIndicatorDetail ProcessingIndicatorValueCoded 
70  
Type de police
Yes
5
Option.
 
PolicyProductcode 
80  
Produit
No
-
-
Option.
 
ProductNameProductcode ProductDetail ProductIdentifier CodeListResponsibleAgencyCoded 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  
Etat de la police
Yes
2
Mand.
 
ContractStatusCode 
150  
Prime brute
No
-
-
Option.
 
GrossPremiumAmount 
160  
Frais de quittance
No
-
-
Option.
 
PremiumNotificationCostsAmount 
170  
Total à payer
No
-
-
Option.
 
TotalToBePaidAmount 
180  
Coûts techniques
No
-
-
Option.
 
TechnicalExpensesAmount 
190  
Frais de commercialisation
No
-
-
Option.
 
CommercializationExpensesMotorLiabilityAmount 
200  
Prime nette
No
-
-
Option.
 
NetPremiumAmount 
210  
Commission
No
-
-
Option.
 
CommissionAmount 
220  
Commission d'acquisition - total
No
-
-
Option.
 
AcquisitionCommissionTotalAmount 
230  
Charges
No
-
-
Option.
 
ChargesAmount 
240  
Frais
No
-
-
Option.
 
CostAmount 
250  
Charges et frais
No
-
-
Option.
 
ChargesAndCostsAmount 
260  
Frais de fractionnement
No
-
-
Option.
 
SplittingCostsAmount 
270  
Autres coûts à ajouter à la prime nette
No
-
-
Option.
 
OtherCostsToBeAddedToTheNetPremiumAmount 
280  
Nombre de documents annexes
No
-
-
Cond.
Mandatory when added documents are sent. 
DocumentsAttachedQuantity 
290  
Participation coassurance
No
-
-
Option.
 
ParticipationOfCoInsurerPercentage 
300  
Pourcentage d'encaissement coassurance
No
-
-
Option.
 
PercentageCoInsuranceCollectionPercentage 
310  
Majoration selon périodicité
No
-
-
Option.
 
SurchargeDependingOnPeriodPercentage 
320  
Assureur
No
-
-
Mand.
 
PartyInsurer 
330  
Assureur - Numéro CBFA
No
-
-
Mand.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
340  
Assureur - Type d'assureur en coassurance
Yes
1
Option.
 
InsurerInCaseOfCoInsuranceCode 
350  
Intermédiaire
No
-
-
Mand.
 
PartyIntermediary 
360  
Intermédiaire - Numéro CBFA
No
-
-
Option.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
370  
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
No
-
-
Mand.
 
PartyIdentificationDetail PartyIdentifier CodeListIdentifier 
380  
Intermédiaire - Référence police producteur
No
-
-
Mand.
 
BrokerPolicyReference 
390 u 
Preneur d'assurance
No
-
-
Mand.
 
PartyMainPolicyHolder 
400 u 
Objet de risque
No
-
-
Mand.
 
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.