|
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0603 - Récapitulation, fichier(s) PRENOT / Samenvatting, PRENOT bestanden - (Totaux de contrôle fichier(s) PRENOT / PRENOT bestanden, controle-totalen) - ( UN/Edifact MIG : Fr / Nl ) |
Version : 1 Status : 3 |
| n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
XML-tag |
UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
Date de comptabilisation
|
No
|
-
|
-
|
Option.
|
AccountingDocument AccountingDate
|
DTM+005
|
||
Mode d'encaissement de la quittance
|
Yes
|
B003
|
1
|
Option.
|
PremiumNotification InvoiceCollectionTypeCode
|
ATT+B003
|
||
Unité monétaire
|
Yes
|
A660
|
3
|
Option.
|
AccountingDocument AccountingDocumentCurrencyCode
|
ATT+A660
|
||
Prime nette
|
No
|
-
|
-
|
Option.
|
Premium PremiumAmount
|
MOA+013
|
||
Montant commission
|
No
|
-
|
-
|
Option.
|
Commission CommissionAmount
|
MOA+015
|
||
Montant à payer
|
No
|
-
|
-
|
Option.
|
BordereauLine ToBePaidTotalAmount
|
MOA+012
|
||
Nombre de documents expédiés pour ce mode d'encaissement
|
No
|
-
|
-
|
Option.
|
QTY+076
|
|||
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyRole InsuranceProvider Intermediary
|
PTY+002
|
||
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
InsuranceProvider ICBIdentifier
|
PTY+002(X044-1)
|
||
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
Intermediary BrokerAccountIdentifier
|
PTY+002(X044-2)
|
||
Intermédiaire - Code carte d'échange
|
No
|
-
|
-
|
Mand.
|
InsuranceProvider Exchange80DestineeCode
|
PTY+002(X076)
|
||
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyRole Insurer
|
PTY+006
|
||
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
InsuranceProvider ICBIdentifier
|
PTY+006(X044-1)
|
||
Assureur - Code carte d'échange
|
No
|
-
|
-
|
Mand.
|
InsuranceProvider Exchange80DestineeCode
|
PTY+006(X076)
|
||
(*) 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.