Desktop x-wide (min-width 1920px) Desktop wide (max-width 1440px) Tablet Querformat (1024px) Tablet Hochformat (768) Narrow (600) Mobile (480)
About LEI | Common Data File Formats

Level 2 Data: Relationship Record (RR) CDF Format



In May 2017, the process of enhancing the Legal Entity Identifier (LEI) data pool, by including ‘Level 2’ data to answer the question of ‘who owns whom’, began. Specifically, legal entities that have or acquire an LEI will report their ‘direct accounting consolidating parent’ as well as their ‘ultimate accounting consolidating parent’.

Distinct procedures apply regarding direct and ultimate parents with and without an LEI.

If the direct and / or ultimate parent of an LEI registrant has obtained an LEI, the following applies: The child legal entity will be obliged to provide the LEI, respectively, of its direct and ultimate parent to the LEI issuing organization. The Relationship Record CDF (RR-CDF) format applies to relationship records for LEI registrants whose direct and ultimate parents have obtained an LEI. It defines the technical format which specifies how Level 2 data, i.e. relationship records, is stored and transferred between LEI issuing organizations, the Global Legal Entity Identifier Foundation (GLEIF) and all users of the data.

GLEIF published the RR-CDF format version 1.0 in November 2016 for information. In May 2017, GLEIF published a further update: RR-CDF format version 1.1. The detailed technical specification document and the corresponding XML schema definition are available for download at the foot of this page. Changes introduced in version 1.1, compared to the RR-CDF format version 1.0, are minor and backwards compatible. These changes are detailed in section 1.7 (‘Release Notes’) of the technical specification document available below.

Also in May 2017, GLEIF published version 1.1 of the document ‘State Transition Rules for the Relationship Record Common Data File Format (Including Validation Rules)’ (see below). This defines general business rules to be observed by LEI issuers collecting Level 2 data and provides specific instructions on how to apply the RR-CDF format version 1.1. The validation rules describe aspects to be considered by LEI issuing organizations in the process of validating accounting consolidation relationships.

The RR-CDF format contains elements which, respectively:

  • Identify the legal entities involved.
  • Specify the type and other characteristics (e.g. dates) of the relationship.
  • Show relationship validation and reporting information collected by the LEI issuing organization responsible for managing the relationship record.

The GLEIF Concatenated Files, which are available for download, include specific information on an LEI record and related reference data based on the relevant reporting format.

  • Level 2 RR-CDF Concatenated File: GLEIF published the first Level 2 RR-CDF Concatenated File on 8 May 2017. It contains the Level 2 data that allows the identification of the direct and ultimate parents of a legal entity whose direct and ultimate parents have an LEI. It is important to note that the information included in the Level 2 RR-CDF Concatenated File does not yet cover the complete LEI population for the following reason: The collection and validation of Level 2 data by the LEI issuing organizations for LEIs that existed prior to May 2017 takes place with the annual renewal of the LEI. Renewal means that the reference data connected to an LEI is re-validated annually by the managing LEI issuer against a third party source. It is expected that Level 2 data for the complete LEI population will be available in the course of the first half of 2018, i.e. towards the end of the one-year renewal cycle after the date when collection of Level 2 data started.

The diagram below shows the structure of the RR-CDF format, including definitions of the data content to be provided.

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 The date at which the relationship information was first collected by the ManagingLOU 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 RegistrationStatusEnum The level of relationship validation provided by the ManagingLOU. [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]
The Relationship Record Common Data File (RR-CDF) format

For information regarding LEI registrants whose direct and / or ultimate parents do not have an LEI, refer to this dedicated GLEIF website page: Level 2 Data: Parent Reference Data Format.

Please address questions on the RR-CDF format to leidata@gleif.org.


Relevant Files for Download


How an LEI can help your business get fit for the future

  • Improved risk management.
  • Increased operational efficiency.
  • More accurate calculation of exposures.
  • Simplified regulatory reporting.
  • Ensured counterparties for any business process.
  • Unique counterparty identification globally.

Follow five easy steps to apply for an LEI number

  1. Review your LEI requirements.
  2. Explore your LEI issuer's website of choice.
  3. Provide your 'business card' information.
  4. Verify and submit your LEI request.
  5. Make payment.