Message Content Inventory |
Identifier : M0901 - Prévention fraude, envoi R.S.R. / Fraudepreventie, versturen R.S.R. - (As in Community MIG's - Datassur - RSR : Envoi par la compagnie / Zending door de maatschappij)
- Approved
, and is part of release 2005pre - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Datassur
Status : 2 - Version : 1
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
10 |
Message about fraud prevention
|
No
|
-
|
-
|
Mand.
|
|||
20 |
Message about fraud prevention - RSR upload
|
No
|
-
|
-
|
Mand.
|
|||
30 |
Message domain
|
No
|
-
|
-
|
Mand.
|
this message id domain independent
|
Domain
|
|
40 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
50 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
60 |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
||
70 |
Type de transaction RSR
|
Yes
|
1
|
Mand.
|
RsrTransactionProcesscode
|
|||
80 |
Code release RSR
|
Yes
|
0
|
Mand.
|
RsrReleaseProcesscode
|
|||
90 |
Branche
|
Yes
|
1
|
Mand.
|
BranchProductcode ProductDetail ProductIdentifier
|
|||
100 |
Sous-branche
|
Yes
|
1
|
Mand.
|
SubBranchProductcode ProductDetail ProductIdentifier
|
|||
110 |
Moment de l'événement
|
No
|
-
|
-
|
Mand.
|
MomentOfTheEventDateTime
|
||
120 |
Date de constation des faits
|
No
|
-
|
-
|
Mand.
|
FactsEstablishmentDate
|
||
130 |
Numéro de la fiche Datassur
|
No
|
-
|
-
|
Mand.
|
DatassurRecordReference
|
||
140 |
Motif d'enregistrement
|
Yes
|
1
|
Mand.
|
ReasonForRegistrationCode
|
|||
150 |
Tranche de montant
|
Yes
|
1
|
Mand.
|
AmountBracketCode
|
|||
160 |
Adresse douteuse
|
No
|
-
|
-
|
Mand.
|
DatassurRegistrationAddressCodeProbablyIncorrectBinary
|
||
170 |
Il y a-t-il contestation de la fiche RSR
|
No
|
-
|
-
|
Mand.
|
DatassurRegistrationDisputeBinary
|
||
180 |
Total des indemnités
|
No
|
-
|
-
|
Mand.
|
TotalBenefitsAmount
|
||
190 |
Nombre de sinistres
|
No
|
-
|
-
|
Mand.
|
ClaimsQuantity
|
||
200 |
Nombre de sinstres responsables
|
No
|
-
|
-
|
Mand.
|
ClaimsAtFaultQuantity
|
||
210 |
Preneur
|
No
|
-
|
-
|
Mand.
|
PartyMainPolicyHolder
|
||
220 |
Preneur - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName
|
||
230 |
Preneur - Adresse
|
No
|
-
|
-
|
Mand.
|
OfficialAddress AddressDetail StreetName
|
||
240 |
Preneur - Date de naissance
|
No
|
-
|
-
|
Option.
|
BirthDate
|
||
250 |
Preneur - Numéro TVA
|
No
|
-
|
-
|
Option.
|
VatReference
|
||
260 |
Preneur - Personne physique ou morale
|
Yes
|
1
|
Mand.
|
NaturalOrLegalPersonCode
|
|||
270 | u |
Preneur - Langue
|
Yes
|
3
|
Mand.
|
LanguageCode
|
||
280 |
Preneur - Sexe
|
Yes
|
1
|
Mand.
|
GenderCode
|
|||
290 |
Preneur - Statut juridique
|
Yes
|
1
|
Mand.
|
LegalFormCode
|
|||
300 |
Preneur - Qualité de la personne dans le dossier
|
Yes
|
2
|
Mand.
|
CapacityOfThePartyInTheFileCode
|
|||
310 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
320 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
formerly named UPEA/BVVO / OCA/CDV -number
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
330 |
Assureur - Numéro du dossier
|
No
|
-
|
-
|
Mand.
|
FileReference
|
||
340 |
Assureur - Numéro de la fiche Datassur
|
No
|
-
|
-
|
Mand.
|
DatassurRecordReference
|
||
350 |
Assureur - Correspondant
|
No
|
-
|
-
|
Mand.
|
RelatedCorrespondentOrManager
|
||
360 |
Assureur - Correspondant - Identifiant
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
370 |
Assureur - Correspondant - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName
|
||
380 |
Objet de risque
|
No
|
-
|
-
|
Option.
|
ObjectInsuredUndefinedObject
|
||
390 |
Objet de risque - Situation du risque
|
No
|
-
|
-
|
Mand.
|
RiskAddress
|
||
400 |
Message end
|
No
|
-
|
-
|
Mand.
|
(*) 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.