Message Content Inventory |
Archived, and was part of release 201001 : Identifier : M0118 - Contrat, projet - (Projet d'assurance - Données contrat) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 5
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
10 | n |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
|
20 | n |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
|
30 | n |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
40 |
Contrat
|
No
|
-
|
-
|
Mand.
|
|||
50 |
Type de police
|
Yes
|
5
|
Mand.
|
PolicyProductcode
|
|||
60 |
Produit
|
No
|
-
|
-
|
Option.
|
ProductNameProductcode
|
||
70 |
Date d'échéance principale
|
No
|
-
|
-
|
Mand.
|
MainRenewalMonthDay
|
||
80 |
Date d'effet
|
No
|
-
|
-
|
Mand.
|
InceptionDate
|
||
90 |
Date initiale du contrat
|
No
|
-
|
-
|
Option.
|
ContractInceptionDate
|
||
100 |
Date d'expiration
|
No
|
-
|
-
|
Option.
|
ExpiryDate
|
||
110 |
Durée
|
No
|
-
|
-
|
Option.
|
LengthDuration
|
||
120 |
Durée de reconduction du contrat
|
No
|
-
|
-
|
Option.
|
ContractContinuationDuration
|
||
130 |
Date première prime terme
|
No
|
-
|
-
|
Option.
|
NextPremiumInstallmentDate
|
||
140 |
Date dernière prime
|
No
|
-
|
-
|
Option.
|
LastPremiumDate
|
||
150 |
Date de mise en police package
|
No
|
-
|
-
|
Option.
|
InsertedIntoPackageDate
|
||
160 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
170 |
Numéro de la police remplacée
|
No
|
-
|
-
|
Option.
|
ReplacementPolicyReference
|
||
180 |
Numéro de police Assuralia
|
No
|
-
|
-
|
Option.
|
ProfessionalUnionOfInsuranceCompaniesPolicyReference
|
||
190 |
Numéro de groupement de polices
|
No
|
-
|
-
|
Option.
|
PolicygroupingNumberReference
|
||
200 |
Référence de la flotte
|
No
|
-
|
-
|
Option.
|
FleetReference
|
||
210 | n |
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
|
220 | n |
Référence des paiements
|
No
|
-
|
-
|
Option.
|
PaymentReference
|
|
230 |
Etat de l'acceptation de la nouvelle affaire ou du projet
|
Yes
|
2
|
Option.
|
StateOfAcceptanceCode
|
|||
240 |
Etat de l’acceptation du projet d'assurance sans couverture
|
Yes
|
1
|
Option.
|
StateOfProjectAcceptanceWithoutAnyCoverageCode
|
|||
250 | u |
Etat de la police
|
Yes
|
2
|
Mand.
|
ContractStatusCode
|
||
260 |
Fractionnement de la prime
|
Yes
|
3
|
Mand.
|
PaymentFrequencyCode
|
|||
270 |
Mode d'encaissement quittance terme
|
Yes
|
1
|
Mand.
|
CollectionModeCode
|
|||
280 |
Mode d'encaissement quittance comptant
|
Yes
|
1
|
Option.
|
PremiumNotificationCashCollectionCode
|
|||
290 |
Unité monétaire
|
Yes
|
3
|
Option.
|
MonetaryUnitCode
|
|||
300 |
Degré d'exonération de taxe
|
Yes
|
1
|
Option.
|
DegreeOfTaxExemptionCode
|
|||
310 |
Code communication des frais de fractionnement
|
Yes
|
1
|
Option.
|
SplittingCostsCommunicationCodeCode
|
|||
320 |
Indicateur police résultat de vente à distance
|
No
|
-
|
-
|
Option.
|
DesignationPolicyResultOfDistanceSellingBinary
|
||
330 |
Police avec aliments
|
No
|
-
|
-
|
Option.
|
ContractByMaintainedAllowanceBinary
|
||
340 |
Police avec abonnement
|
No
|
-
|
-
|
Option.
|
ContractBySubscriptionBinary
|
||
350 |
Police de coassurance
|
No
|
-
|
-
|
Option.
|
CoInsuringPolicyBinary
|
||
360 |
Réponse action commerciale
|
No
|
-
|
-
|
Option.
|
ResponseToCommercialActionBinary
|
||
370 |
Calcul frais de fractionnement sur impôts et frais
|
No
|
-
|
-
|
Option.
|
SplttingCostsUponTaxesAndCostsBinary
|
||
380 |
Calcul commission sur frais de fractionnement
|
No
|
-
|
-
|
Option.
|
CommissionUponSplittingCostsBinary
|
||
390 |
Prime brute
|
No
|
-
|
-
|
Option.
|
GrossPremiumAmount
|
||
400 |
Frais de quittance
|
No
|
-
|
-
|
Option.
|
PremiumNotificationCostsAmount
|
||
410 |
Total à payer
|
No
|
-
|
-
|
Option.
|
TotalToBePaidAmount
|
||
420 |
Coûts techniques
|
No
|
-
|
-
|
Option.
|
TechnicalExpensesAmount
|
||
430 |
Frais de commercialisation
|
No
|
-
|
-
|
Option.
|
CommercializationExpensesMotorLiabilityAmount
|
||
440 |
Prime nette
|
No
|
-
|
-
|
Option.
|
NetPremiumAmount
|
||
450 |
Montant Commission
|
No
|
-
|
-
|
Option.
|
CommissionAmount
|
||
460 | n |
Commission d'acquisition - total
|
No
|
-
|
-
|
Option.
|
AcquisitionCommissionTotalAmount
|
|
470 |
Montant Charges
|
No
|
-
|
-
|
Option.
|
ChargesAmount
|
||
480 |
Montant Frais
|
No
|
-
|
-
|
Option.
|
CostAmount
|
||
490 |
Montant Charges et frais
|
No
|
-
|
-
|
Option.
|
ChargesAndCostsAmount
|
||
500 |
Frais de fractionnement
|
No
|
-
|
-
|
Option.
|
SplittingCostsAmount
|
||
510 |
Autres coûts à ajouter à la prime nette
|
No
|
-
|
-
|
Option.
|
OtherCostsToBeAddedToTheNetPremiumAmount
|
||
520 | n |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
530 |
Participation coassurance
|
No
|
-
|
-
|
Option.
|
ParticipationOfCoInsurerPercentage
|
||
540 |
Pourcentage d'encaissement coassurance
|
No
|
-
|
-
|
Option.
|
PercentageCoInsuranceCollectionPercentage
|
||
550 |
Majoration selon périodicité
|
No
|
-
|
-
|
Option.
|
SurchargeDependingOnPeriodPercentage
|
||
560 |
Police connexe
|
No
|
-
|
-
|
Option.
|
DocumentRelatedPolicy
|
||
570 |
Police connexe - Type de police
|
Yes
|
5
|
Option.
|
PolicyProductcode
|
|||
580 |
Police connexe - Numéro de police
|
No
|
-
|
-
|
Option.
|
PolicyReference
|
||
590 |
Police connexe - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
FsmaReference
|
||
600 |
Police connexe - Capital
|
No
|
-
|
-
|
Option.
|
CapitalAmount
|
||
610 |
Police connexe - Prime de référence
|
No
|
-
|
-
|
Option.
|
ReferencePremiumAmount
|
||
620 |
Police reprise
|
No
|
-
|
-
|
Option.
|
DocumentPolicyTakeOver
|
||
630 |
Police reprise - Date initiale du contrat
|
No
|
-
|
-
|
Option.
|
ContractInceptionDate
|
||
640 |
Police reprise - Date d'expiration
|
No
|
-
|
-
|
Option.
|
ExpiryDate
|
||
650 |
Police reprise - Numéro de police
|
No
|
-
|
-
|
Option.
|
PolicyReference
|
||
660 |
Police reprise - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
FsmaReference
|
||
670 | u |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
|
680 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
690 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
InsurerInCaseOfCoInsuranceCode
|
|||
700 | u |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
|
710 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
720 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
730 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Mand.
|
BrokerPolicyReference
|
||
740 | u |
Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
PartyMainPolicyHolder
|
|
750 |
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.