SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0306 - Quittance, avis de retard de payement / Kwijting, bericht van betalingsachterstand - (Liste des quittances impayées / Lijst van onbetaalde kwijtingen)
- Approved
, and is part of release 201401 |
Sender : Insurer
Receiver : Broker
Status : 2 - Version : 3
|
| 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 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
XEH+03+1+0306+++domain++++yyyymmddhhmm+xx' (=X916 and =X918) (domain is mandatory)
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+03+1+0306+++domain++++yyyymmddhhmm+xx:::M0306' (=X943)
|
ExchangeUnitBusinessContentDescription
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+03+1+0306+++domain++++yyyymmddhhmm+xx:::M0306:3' (=X944)
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 40 |
Avis d'échéance - quittance
|
No
|
-
|
-
|
Mand.
|
XEH+03+1
|
|||
| 50 | n |
Code opération B.R.B.
|
Yes
|
3
|
Option.
|
GIS+BBRB+x--x
|
BRBOperationProcesscode
|
||
| 60 |
Date de comptabilisation
|
No
|
-
|
-
|
Option.
|
DTM+005
|
AccountingDate
|
||
| 70 |
Date de début de période
|
No
|
-
|
-
|
Option.
|
DTM+041
|
PeriodStartDate
|
||
| 80 |
Date de suspension des garanties
|
No
|
-
|
-
|
Option.
|
DTM+060:ddmmyyyy:001
|
SuspensionDate
|
||
| 90 |
Date de résiliation du contrat
|
No
|
-
|
-
|
Option.
|
DTM+019:ddmmyyyy:001
|
TerminationDate
|
||
| 100 |
Numéro de la quittance ( compagnie )
|
No
|
-
|
-
|
Option.
|
Si présent- numéro unique / Indien aanwezig- een uniek nummer
|
RFF+027
|
PremiumNotificationCompanyReference
|
|
| 110 |
Numéro de police
|
No
|
-
|
-
|
Option.
|
RFF+001
|
PolicyReference
|
||
| 111 | n |
GUID (Globally Unique IDentifier) du message, sera référencé par le(s) document(s) annexe(s)
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
RFF+084
|
MessageGuidReference
|
| 120 |
Statut de recouvrement ( de la quittance )
|
Yes
|
3
|
Option.
|
ATT+B051
|
CollectionStatusOfThePremiumInvoiceCode
|
|||
| 130 |
Total à payer
|
No
|
-
|
-
|
Option.
|
MOA+012
|
TotalToBePaidAmount
|
||
| 140 |
Commission
|
No
|
-
|
-
|
Option.
|
MOA+015
|
CommissionAmount
|
||
| 150 |
Frais de recouvrement
|
No
|
-
|
-
|
Option.
|
MOA+049
|
CollectionCostsAmount
|
||
| 160 |
Acompte
|
No
|
-
|
-
|
Option.
|
MOA+078
|
DownPaymentAmount
|
||
| 161 | n |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134
|
DocumentsAttachedQuantity
|
| 170 |
Action administrative - Demande information (URL action sur dossier spécifique)
|
No
|
-
|
-
|
Option.
|
FTX+050
|
UrlBusinessActionOnSpecificFileText
|
||
| 180 |
Intermédiaire
|
No
|
-
|
-
|
Option.
|
PTY+002
|
PartyIntermediary
|
||
| 190 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Option.
|
PTY+002(X044-2)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 200 |
Intermédiaire - Code carte d'échange
|
No
|
-
|
-
|
Option.
|
PTY+002(X076)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 210 |
Intermédiaire - Référence police producteur
|
No
|
-
|
-
|
Option.
|
PTY+002, RFF+003
|
BrokerPolicyReference
|
||
| 220 |
Preneur d'assurance
|
No
|
-
|
-
|
Option.
|
PTY+003
|
PartyMainPolicyHolder
|
||
| 230 |
Preneur d'assurance - Nom officiel
|
No
|
-
|
-
|
Option.
|
PTY+003, NME+001
|
OfficialName
|
||
| 240 |
Assureur
|
No
|
-
|
-
|
Option.
|
PTY+006
|
PartyInsurer
|
||
| 250 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
PTY+006(X044-1)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 260 |
Assureur - Code carte d'échange
|
No
|
-
|
-
|
Option.
|
PTY+006(X076)
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 270 |
Assureur - Type d'assureur en coassurance
|
Yes
|
1
|
Option.
|
PTY+006, ATT+A020
|
InsurerInCaseOfCoInsuranceCode
|
|||
(*) 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.