Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : EPRENOTDET - Echange contextuel, données quittance - (Consultation quittance)
- Approved
, and is part of release 200601 |
Sender : Any
Receiver : Any
Status : 2 - 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 |
|||||||
| 10 |
Quittance
|
No
|
-
|
-
|
Mand.
|
XEH+03+1
|
|||
| 20 |
Date de comptabilisation
|
No
|
-
|
-
|
Mand.
|
DTM+005:x--x
|
AccountingDate
|
||
| 30 |
Numéro de police
|
No
|
-
|
-
|
Option.
|
RFF+001+x--x
|
PolicyReference
|
||
| 40 |
Numéro de quittance
|
No
|
-
|
-
|
Mand.
|
RFF+027+x--x
|
PremiumNotificationCompanyReference
|
||
| 50 |
Mode d'encaissement de la quittance
|
Yes
|
1
|
Mand.
|
ATT+B003+x--x
|
NotificationCollectionModeCode
|
|||
| 60 |
Type de quittance
|
Yes
|
2
|
Mand.
|
ATT+B001+x--x
|
PremiumInvoiceCode
|
|||
| 70 |
Total à payer
|
No
|
-
|
-
|
Mand.
|
MOA+012
|
TotalToBePaidAmount
|
||
| 80 |
Prime nette fractionnée
|
No
|
-
|
-
|
Mand.
|
MOA+013
|
NetPremiumSplittedAmount
|
||
| 90 |
Montant commission
|
No
|
-
|
-
|
Mand.
|
Zéro éventuel
|
MOA+015
|
CommissionAmount
|
|
| 100 |
Montant charges
|
No
|
-
|
-
|
Mand.
|
FMSA regulation based 20170223
|
MOA+016
|
ChargesAmount
|
|
| 110 |
Montant frais
|
No
|
-
|
-
|
Option.
|
MOA+017
|
CostAmount
|
||
| 120 |
Intermédiaire - Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
PartyIntermediary
|
||
| 130 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PTY+002+x--x:006
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 140 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x:002
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 150 |
Période assurée
|
No
|
-
|
-
|
Option.
|
0..n présences
|
PER+xxx
|
Period...
|
|
| 160 |
Période assurée - Date de début de période
|
No
|
-
|
-
|
Mand.
|
PER+xxx - DTM+041
|
PeriodStartDate
|
||
| 170 |
Période assurée - Date de fin de période
|
No
|
-
|
-
|
Mand.
|
PER+xxx - DTM+022
|
PeriodEndDate
|
||
| 180 |
Quittance - indication fin dossier
|
No
|
-
|
-
|
Mand.
|
XEH+03
|
|||
(*) 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.