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

Implementation Related Components

Message Content Inventory Identifier : DEDxxx - - (Données franchise) - Approved , and is part of release 202601
Sender :
Receiver :
Status : 2 - Version : 6
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  
Franchise - type
No
-
-
Option.
See the Recommendations page. 
DED+xxx 
Deductible... 
20 d 
Expression en (taux, montant, durée)
Yes
2
Option.
 
ATT+P11T+x--x 
ExemptionExpressedAsCode 
30 d 
Base de calcul
Yes
4
Option.
 
ATT+P11U+x--x 
ExemptionCalculationBaseCode 
40  
Type en terminologie Informex
Yes
1
Option.
 
ATT+CP01+x--x 
ExcessInformexCode 
50  
Maintien du délai de carence après 60 ans
No
-
-
Option.
 
BIN+2250+x--x 
UnrefundedPeriodMaintainedAbove60YearsBinary 
60  
Franchise contractuelle
No
-
-
Option.
 
BIN+P11R+x--x 
ContractualExemptionBinary 
70 d 
La franchise n'est pas d'application
No
-
-
Option.
 
BIN+P11S+x--x 
TheExemptionDoesNotApplyBinary 
80  
Franchise seuil
No
-
-
Option.
 
BIN+P11W+x--x 
ThresholdExemptionBinary 
90  
Franchise jeune conducteur
No
-
-
Option.
 
BIN+P11X+x--x 
ExemptionYoungDriverBinary 
100  
Franchise territoriale
No
-
-
Option.
 
BIN+P11Y+x--x 
LocalExemptionBinary 
110  
Franchise consignée
No
-
-
Option.
 
BIN+P11Z+x--x 
InBailmentOfTheExemptionBinary 
120  
Franchise en dommages corporels
No
-
-
Cond.
Possibly when under ICD4xx guarantee 
BIN+P12V+x--x 
CorporalDamagesExemptionBinary 
130  
Franchise en dommages matériels
No
-
-
Cond.
Possibly when under ICD4xx guarantee 
BIN+P12W+x--x 
MaterialDamagesExemptionBinary 
140  
Franchise en dommages mixtes
No
-
-
Cond.
Possibly when under ICD4xx guarantee 
BIN+P12X+x--x 
MixedDamagesExemptionBinary 
150  
Franchise en dommages immatériels
No
-
-
Cond.
Possibly when under ICD4xx guarantee 
BIN+P12Y+x--x 
ImmaterialDamagesExemptionBinary 
160  
Franchise en objets confiés
No
-
-
Cond.
Possibly when under ICD4xx guarantee 
BIN+P12Z+x--x 
EntrustedObjectsExemptionBinary 
170  
Franchise, montant
No
-
-
Option.
Index information mandatory 
MOA+033:x--x:EUR:2:(status)+(index):x--x:(decimals)+x--x:(decimals) 
ExemptionAmount 
180  
Valeur minimale
No
-
-
Option.
Index information mandatory 
MOA+115:x--x:EUR:2:(status)+(index):x--x:(decimals)+x--x:(decimals) 
MinimalValueOfFranchiseDeductableAmount 
190  
Valeur maximale
No
-
-
Option.
Index information mandatory 
MOA+116:x--x:EUR:2:(status)+(index):x--x:(decimals)+x--x:(decimals) 
MaximalValueOfFranchiseDeductableAmount 
200  
Franchise - intervention dès incapacité pourcentage
No
-
-
Option.
 
PCD+012:x--x:(decimals):(pourcent) 
InterventionAsOfIncapacityPercentage 
210  
Franchise - pourcentage sur valeur assurée
No
-
-
Option.
 
PCD+014:x--x:(decimals):(pourcent) 
FranchiseDeductableOnInsuredValuePercentage 
220  
Franchise - pourcentage sur montant des dégats
No
-
-
Option.
 
PCD+025:x--x:(decimals):(pourcent) 
FranchiseDeductableOnDamageAmountPercentage 
230 u 
Franchise - pourcentage (sur montant spécifié)
No
-
-
Option.
 
PCD+059:x--x:(decimals) 
FranchiseDeductablePercentage 
240  
Franchise - pourcentage minimal en incapacité de travail
No
-
-
Option.
 
PCD+069:x--x:(decimals):(pourcent) 
MinimumWorkIncapacityPercentage 
250  
Franchise, date de début de période
No
-
-
Option.
 
DTM+041:x--x:001 
PeriodStartDate 
260  
Franchise, date de fin de période
No
-
-
Option.
 
DTM+022:x--x:001 
PeriodEndDate 
270  
Délai de carence en jours, semaines, mois, ...
No
-
-
Option.
 
DTM+030:x--x:x--x 
WaitingDelayDuration 
280  
Délai d'attente en jours, semaines, mois, ...
No
-
-
Option.
 
DTM+139:x--x:x--x 
ExpiryDate 
290  
Franchise territoriale, le pays, code et/ou nom
No
-
-
Option.
 
ADR+008++++x--x+x--x 
EventAddress CountryCoded CountryName 

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