À propos du LEI Formats du fichier commun de données
Remarque :

Les termes et définitions figurant dans le graphique sont fournis avec le format du fichier commun de données (FCD) en langue anglaise que vous pouvez télécharger ci-dessous. La GLEIF ne traduit pas les documents techniques rédigés en anglais et, par conséquent, le contenu de ce graphique apparaît en anglais.

Données de Niveau 2 : Format d'enregistrement des relations (RR) CDF



La base de données sur les Identifiants d'entité juridique (LEI) inclut les données de 'Niveau 2' répondant à la question 'qui appartient à qui'. Plus précisément, les entités juridiques qui ont ou qui acquièrent un LEI déclarent leur ‘société mère directe de consolidation comptable’ ainsi que leur ‘société mère ultime de consolidation comptable’.

Des procédures distinctes s'appliquent aux sociétés mères directes et ultimes avec et sans LEI.

Si la société mère directe et/ou ultime d'une entité demandant un LEI a obtenu un LEI, les dispositions suivantes s'appliquent : L'entité juridique affiliée sera tenue de fournir le LEI de sa société mère directe et de sa société mère ultime, respectivement, à l'organisation émettrice de LEI. Le Format d'enregistrement des relations-CDF (RR-CDF) s'applique aux enregistrements des relations pour les entités demandant un LEI dont les sociétés mères directes et ultimes ont obtenu un LEI. Il définit le format technique qui spécifie comment les données de Niveau 2, soit les enregistrements des relations, sont stockées et transférées entre les organisations émettrices de LEI, la Global Legal Entity Identifier Foundation (GLEIF) et tous les utilisateurs des données.

En novembre 2016, la GLEIF a publié des informations sur le format RR-CDF version 1.0. En mai 2017, la GLEIF a publié une mise à jour supplémentaire : Format RR-CDF version 1.1. Vous pouvez télécharger le document de spécifications techniques détaillé et la définition correspondante du schéma XML au bas de cette page. Les changements apportés à la version 1.0 du format RR-CDF par la version 1.1 sont mineurs et rétrocompatibles. Ces changements sont détaillés à la section 1.7 (‘Notes de version’) du document de spécifications techniques disponible ci-dessous.

Le format RR-CDF contient des éléments qui, respectivement:

  • Identifient les entités juridiques concernées.
  • Précisent le type et d’autres caractéristiques (les dates par exemple) de la relation.
  • Montrent les informations sur la validation des relations et les rapports recueillies par l’organisation émettrice de LEI chargée de gérer l’enregistrement des relations.

Le tableau ci-dessous montre la structure du format RR-CDF, y compris les définitions du contenu des données à fournir.

RelationshipData
Header [1,1]
ContentDate The date and time as of which the data contained in the file is valid. LEIDateTimeProfile A date and time, including the timezone, based on ISO 8601. [1,1]
Originator The LEI of the entity that created the content of this file. LEIType A Legal Entity Identifier (LEI) code, conforming to ISO 17442. [0,1]
FileContent A code describing the content of this relationship record file. FileContentEnum A code denoting the publisher of the relationship data file (GLEIF or LOU), the publication status (public or internal use) and the content type (full file, delta file or query response). [1,1]
DeltaStart The date and time of the baseline relative to which this file contains new or changed Relationship Records. LEIDateTimeProfile A date and time, including the timezone, based on ISO 8601. [0,1]
RecordCount The number of relationship records in the file. Must be a positive whole (integer) number, or zero (0). xs:nonNegativeInteger A positive whole number or zero (0). [1,1]
Extension This Extension element may contain any additional elements required to extend the Header container element. ExtensionType Data element(s) defined by the sender of the file. A description of Extension element structure and content should be provided separately. [0,1]
Record [0,*]
Relationship [1,1]
StartNode An LEI or ISO 17442-compatible ID for the entity at the "start" of a directional relationship. NodeType An LEI or provisional (ISO 17442-compatible) technical identifier for a legal entity in the relationship, together with a code indicating the type of identifier. [1,1]
EndNode An LEI or ISO 17442-compatible ID for the entity at the "end" of a directional relationship. NodeType An LEI or provisional (ISO 17442-compatible) technical identifier for a legal entity in the relationship, together with a code indicating the type of identifier. [1,1]
RelationshipType A unique code designating the specific category of a directional relationship between two legal entities. RelationshipCategoryType A unique code designating the specific category of a directional relationship between two legal entities. [1,1]
RelationshipPeriods A collection of paired beginning and end dates relating to: the relationship itself, periods (e.g. accounting cycles) covered by documents demonstrating the relationship, or the filing date(s) of those documents. RelationshipPeriodsType A collection of paired beginning and end dates, defining a time period of a type indicated by an enumerated code: the relationship itself, periods (e.g. accounting) covered by documents demonstrating the relationship, or the filing date(s) of those documents. [0,1]
RelationshipStatus The status of the legal entities\' relationship itself: ACTIVE or INACTIVE. RelationshipStatusEnum The status of the legal entities\' relationship itself (e.g. currently active, historical only). [1,1]
RelationshipQualifiers Any additional qualitative attributes that help to categorize the relationship. RelationshipQualifiersType Additional qualitative attributes that help to categorize the relationship more specifically. [0,*]
RelationshipQuantifiers Any additional quantitative attributes that help to categorize the relationship. RelationshipQuantifiersType Additional quantitative attributes of the relationship, including units where applicable, according to a particular measurement method. [0,*]
Extension This Extension element may contain any additional elements required to extend the Header container element ExtensionType Data element(s) defined by the sender of the file. A description of Extension element structure and content should be provided separately. [0,1]
Registration [1,1]
InitialRegistrationDate A date and time, including the timezone, based on ISO 8601. LEIDateTimeProfile A date and time, including the timezone, based on ISO 8601. [1,1]
LastUpdateDate The date at which the information was most recently updated by the ManagingLOU LEIDateTimeProfile A date and time, including the timezone, based on ISO 8601. [1,1]
RegistrationStatus The status of the legal entity\'s relationship record registration with the ManagingLOU lei:RegistrationStatusEnum A value of type RegistrationStatusEnum in a file conforming to this standard SHALL be one of the following code strings:
  • PENDING_VALIDATION - A relationship data report that has been submitted and which is being processed and validated, prior to publication
  • PUBLISHED - A relationship record that has been validated and published, and which identifies a relationship that was reported by an entity that was an operating legal entity as of the last update
  • DUPLICATE - A relationship record that has been determined to be a duplicate of the same relationship as another relationship record; the DUPLICATE status is assigned to the non-surviving record
  • LAPSED - A relationship record that has not been renewed by the NextRenewalDate
  • RETIRED - The relationship is considered to have ended, but the relationship report is kept in publication for historical audit trail purposes
  • ANNULLED - A relationship record that was marked as erroneous or invalid after it was issued
  • TRANSFERRED - A relationship record that has been transferred to a different LOU as the managing LOU
  • PENDING_TRANSFER - A relationship record that has been requested to be transferred to another LOU. The request is being processed at the sending LOU
  • PENDING_ARCHIVAL - A relationship record is about to be transferred to a different LOU, after which its registration status will revert to a non-pending status
[1,1]
NextRenewalDate The next date by which the relationship information must be renewed and re-certified by the legal entity. LEIDateTimeProfile A date and time, including the timezone, based on ISO 8601. [0,1]
ManagingLOU The LEI of the LOU that is responsible for administering this relationship record. LEIType A Legal Entity Identifier (LEI) code, conforming to ISO 17442. [1,1]
ValidationSources Level of relationship validation. ValidationSourcesTypeEnum The level of relationship validation provided by the ManagingLOU. [1,1]
ValidationDocuments Type of source document(s) used for validating the relationship. ValidationDocumentsTypeEnum The type of source document(s) used by the ManagingLOU to validate the relationship. [1,1]
ValidationReference A reference to a specfic document or other source used as the basis of relationship validation for this relationship record. Tokenized500Type A free text string. [0,1]
Extension This Extension element may contain any additional elements required to extend the Header container element ExtensionType Data element(s) defined by the sender of the file. A description of Extension element structure and content should be provided separately. [0,1]
Extension [0,1]

Le format de fichier commun de données pour l’enregistrement des relations (FCD-ER)

Les règles de transition d’état et de validation (STVR) décrivent les règles de gestion et leur mise en œuvre technique en vue de l'émission, de la mise à jour, de la gestion et de la publication des données de référence du LEI, conformément aux formats de fichier commun de données (CDF). Les sections de ce document mentionnant les formats LEI-CDF 3.1 ou RR-CDF 2.1 entreront en vigueur le 1er mars 2022.

Veuillez adresser vos questions concernant le format RR-CDF à info@gleif.org.


Fichiers utiles à télécharger