Syntax Independent Components
Implementation Related Components
Implementation Related Components
|
|
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0302 - Quittance, BRB / Kwijting, BRB - (Bordereau Retour / RetourBorderel) - ( 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 |
||||||
Code opération B.R.B.
|
Yes
|
BBRB
|
2
|
Mand.
|
PremiumNotification BRBOperationCode
|
GIS+BBRB
|
||
Date de début
|
No
|
-
|
-
|
Option.
|
PremiumPeriod PeriodStartDate
|
DTM+041
|
||
Numéro de la quittance ( compagnie )
|
No
|
-
|
-
|
Option.
|
Si présent- numéro unique / Indien aanwezig- een uniek nummer
|
PremiumNotification InvoiceIdentifier
|
RFF+027
|
|
Numéro de police
|
No
|
-
|
-
|
Mand.
|
Contract ContractIdentifier
|
RFF+001
|
||
Unité monétaire
|
Yes
|
A660
|
3
|
Option.
|
AccountingDocument AccountingDocumentCurrencyCode
|
ATT+A660
|
||
Total à payer
|
No
|
-
|
-
|
Option.
|
BordereauLine ToBePaidTotalAmount
|
MOA+012
|
||
Commission
|
No
|
-
|
-
|
Option.
|
Commission CommissionAmount
|
MOA+015
|
||
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 - Référence police producteur
|
No
|
-
|
-
|
Option.
|
ContractAsIntermediated BrokerPolicyIdentifier
|
PTY+002, RFF+003
|
||
Preneur d'assurance - Nom officiel
|
No
|
-
|
-
|
Option.
|
Party AbbreviatedName / PhysicalPerson FamilyName plus others / LegalPerson LegalPersonName
|
PTY+003, NME+001
|
||
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
InsuranceProvider ICBIdentifier
|
PTY+006(X044-1)
|
||
(*) 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.