> Syntax independent - MCIs - Messages > Details > Representations
Syntax Independent Components

Implementation Related Components

Message Content Inventory Archived, and was part of release 200601 :
Identifier : ICD1xx - - (Données spécifiques des garanties Vie)
Sender :
Receiver :
Status : 3 - Version : 1
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
4  
Garantie, type
No
-
-
Mand.
 
ICD+1xx 
Guarantee... 
5  
Date prestation du capital vie
No
-
-
Option.
 
DTM+027 
LifeBenefitPaymentDate 
10  
Date dernière péréquation
No
-
-
Option.
 
DTM+140 
LastEqualizationDate 
15  
Type de solde restant dû
Yes
1
Option.
 
ATT+1222 
DebtBalanceCode 
20  
Régime d'imposition de la prestation
Yes
1
Option.
 
ATT+1404 
PerformanceTaxabilityCode 
25  
Contrat génère des participations bénéficiaires
No
-
-
Option.
 
BIN+1010 
ContractGeneratesProfitsharingBinary 
30  
Contrat assujetti à péréquation
No
-
-
Option.
 
BIN+1020 
ContractSubjectToEqualizationBinary 
35  
Imposition de la prestation
No
-
-
Option.
 
BIN+1405 
PerformanceTaxationLiabilityBinary 
40  
Capital vie
No
-
-
Option.
 
MOA+023 
LifeBenefitAmount 
45  
Capital décès
No
-
-
Option.
 
MOA+026 
DeathBenefitAmount 
50  
Participation bénéficiaire acquise vie
No
-
-
Option.
 
MOA+024 
AcquiredBonusLoadingForLifeAmount 
55  
Participation acquise décès
No
-
-
Option.
 
MOA+027 
AcquiredBonusLoadingForDeathAmount 
60  
Coëfficient multiplicateur ACRA
No
-
-
Option.
 
QTY+129 
AIARMultiplicatorQuantity 
65  
Taux d'intérêt solde restant dû
No
-
-
Option.
 
PCD+008 
RateOnRemainingBalanceDuedPercentage 
69  
Bénéficiaire
No
-
-
Option.
 
PTY+014 
PartyBeneficiary 
70  
Bénéficiaire - Nom officiel
No
-
-
Option.
 
NME+001 
OfficialName 
75  
Bénéficiaire - Type de bénéficiaire standard
Yes
1
Option.
 
ATT+1910 
StandardBeneficiaryCode 
80  
Bénéficiaire - Type de bénéficiaire acceptant
Yes
1
Option.
 
ATT+1A10 
AcceptingBeneficiaryCode 
85  
Bénéficiaire - Bénéficiaire a accepté l'avantage du contrat
No
-
-
Option.
 
BIN+1911 
BeneficiaryAcceptedTheContractualBenefitBinary 
89  
Cessionnaire
No
-
-
Option.
 
PTY+053 
PartyCessionary 
90  
Cessionnaire - Nom officiel
No
-
-
Option.
 
NME+001 
OfficialName 
95  
Cessionnaire - Numéro du dossier
No
-
-
Option.
 
RFF+017 
FileReference 
100  
Cessionnaire - Description
No
-
-
Option.
 
FTX+019 
DescriptionText 
110  
Sous-garanties
No
-
-
Option.
 
ISD+xxx 
SubGuarantee... 

(*) 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.