Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0303 - Quittance, DRQ / Kwijting, ATK - (Demande de Retour de Quittance/ Aanvraag Terugzending Kwijting)
- Approved
, and is part of release 200801 |
Sender : Broker
Receiver : Insurer
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 |
|||||||
| 5 |
Adressage des documents
|
Yes
|
1
|
Option.
|
GIS+B400
|
RoutingOfTheDocumentsProcesscode
|
|||
| 10 |
Date de début
|
No
|
-
|
-
|
Option.
|
DTM+041
|
PeriodStartDate
|
||
| 15 |
Numéro de la quittance ( compagnie )
|
No
|
-
|
-
|
Option.
|
Si présent- numéro unique / Indien aanwezig- een uniek nummer
|
RFF+027
|
PremiumNotificationCompanyReference
|
|
| 20 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001
|
PolicyReference
|
||
| 25 |
Motif de remise ( DRQ )
|
Yes
|
1
|
Mand.
|
ATT+B405
|
RemissionMotiveDRQCode
|
|||
| 30 |
Unité monétaire
|
Yes
|
3
|
Option.
|
ATT+A660
|
MonetaryUnitCode
|
|||
| 35 |
Total à payer
|
No
|
-
|
-
|
Option.
|
MOA+012
|
TotalToBePaidAmount
|
||
| 40 |
Commission
|
No
|
-
|
-
|
Option.
|
MOA+015
|
CommissionAmount
|
||
| 45 |
Texte de communication
|
No
|
-
|
-
|
Option.
|
FTX+018
|
CommunicationText
|
||
| 50 |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
PTY+002(X044-1)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
| 55 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002(X044-2)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 60 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
PTY+002, RFF+003
|
BrokerPolicyReference
|
||
| 65 |
Preneur d'assurance - Nom officiel
|
No
|
-
|
-
|
Option.
|
PTY+003, NME+001
|
OfficialName
|
||
| 69 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
PTY+006(X044-1)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
(*) 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.