IPJ Formatos de Archivo de Datos Comunes

Datos de Nivel 2: Formato de Registro de Relaciones (RR) de CDF 2.1



El grupo de datos de Identificadores de Personas Jurídicas (IPJ) incluye los «datos de Nivel 2», que responden a la pregunta de «quién es dueño de quién». Concretamente, las personas jurídicas que posean o adquieran un IPJ comunican su «matriz directa responsable de la consolidación contable», así como su «matriz de control responsable de la consolidación contable».

La persona jurídica filial está obligada a proporcionar el IPJ, respectivamente, de su matriz directa y de control a la organización emisora de IPJ. El formato de Registro de Relaciones (RR-CDF) se aplica a los registros de relaciones relativos a empresas solicitantes de una inscripción de IPJ cuyas matrices directas y de control hayan obtenido un IPJ. Define el formato técnico que especifica el modo en que los datos de Nivel 2, es decir, los registros de relaciones, se almacenan y se transfieren entre organizaciones emisoras de IPJ, la Global Legal Entity Identifier Foundation (GLEIF) y todos los usuarios de los datos.

En noviembre de 2016, la GLEIF publicó el formato inicial de RR-CDF, versión 1.0. En mayo de 2017, la GLEIF publicó el formato de RR-CDF, versión 1.1, y en mayo de 2021, el formato de RR-CDF, versión 2.1. Los cambios introducidos en la versión 2.1, en comparación con la versión 1.1 del formato de RR-CDF, se basan en la política del CSR, «Política sobre relaciones y directrices de fondos para el registro de los fondos de inversión en el Sistema Global del IPJ», que describe detalladamente cómo se clasifican los datos de «Nivel 2» sobre «quién es dueño de quién», según los tipos de relaciones de los fondos. La definición del esquema XML correspondiente y el documento de notas de la versión pueden descargarse al pie de esta página.

El formato de RR-CDF contiene elementos que, respectivamente:

  • Identifican a las personas jurídicas implicadas.
  • Especifican el tipo y otras características (por ejemplo, fechas) de la relación.
  • Muestran validaciones de relaciones y datos de comunicación recopilados por la organización emisora de IPJ que gestiona el registro de relaciones.

El gráfico que figura más abajo muestra la estructura del formato de RR-CDF 2.1, incluidas las definiciones del contenido de datos que se facilitará.

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. RelationshipTypeEnum
  • IS_DIRECTLY_CONSOLIDATED_BY - The StartNode of the "child" entity has its accounts fully consolidated by the EndNode "parent" entity, in the sense given by the accounting standard(s) specified in RelationshipQualifiers;the EndNode entity is the closest fully consolidating parent to the StartNode entity in any applicable hierarchical ownership structure.
  • IS_ULTIMATELY_CONSOLIDATED_BY - The StartNode "child" entity has its accounts fully consolidated by the EndNode "parent" entity, in the sense given by the accounting standard(s) specified in the RelationshipQualifiers; the EndNode entity is the most distant fully consolidating parent from the StartNode entity in any applicable hierarchical ownership structure.
  • IS_INTERNATIONAL_BRANCH_OF - The StartNode is an international branch of the legal entity designated by EndNode (in jurisdiction country of StartNode). The EndNode is the Head Office and SHALL be an LEI.
  • new IS_FUND-MANAGED_BY - The StartNode is a fund managed by a main management entity. The EndNode is legally responsible for the constitution and operation of the fund.
  • new IS_SUBFUND_OF - The StartNode is a sub-fund to an umbrella fund. The EndNode is a legal entity with one or more than one sub-funds/compartments where each sub-fund/compartment has its own investment objectives, separate investment policies and strategies, segregation of assets, separate investors and which has segregated liability between sub-funds/compartments.
  • new IS_FEEDER_TO - The StartNode is a Feeder Fund,that is (almost) exclusively invested in a single other fund. The EndNode is the Master Fund that has identical investment strategies.
[1,1]
RelationshipPeriods The particular type of period, for example, the duration of the relationship itself, the filing or validity period of any documents demonstrating the relationship, or the accounting period they refer to. RelationshipPeriodsTypeEnum 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.
  • ACCOUNTING_PERIOD - The dates in this instance of RelationshipPeriod indicate the accounting period covered by the most recent validation documents for this relationship.
  • RELATIONSHIP_PERIOD - The dates in this instance of RelationshipPeriodindicate the duration of validity of the relationship itself, as distinct from any administrative or reporting aspects.
  • DOCUMENT_FILING_PERIOD - The dates in this instance of RelationshipPeriod indicate the validity period of a regulatory filing, accounting document, or other document demonstrating the relationship's validity.
[0,1]
RelationshipStatus The status of the legal entities\' relationship itself: ACTIVE, INACTIVE, or NULL. RelationshipStatusEnum The status of the legal entities relationship itself (e.g. currently active, historical only).
  • ACTIVE - As of the last report or update,the reporting legal entity reported that it is legally registered and/or operating, that the relationship detailed in this RelationshipRecord is still valid
  • INACTIVE -It has been determined that the relationship is ended, because entity that reported this relationship is no longer legally registered and/or operating; or the relationship is no longer valid for other reasons.
  • new NULL - The relationship status is not applicable.
[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.
  • QualifierDimension - Designates the optional list of additional qualitative attributes that help to categorize the relationship. The QualifierDimensionEnum contains the value ACCOUNTING_STANDARD as specified in the Relationship Record CDF version 2.1.
  • QualifierCategory - Specifies the additional qualitative attributes that help to categorize the relationship. This field must contain a valid QualifierCategoryTypeEnum as specified in the Relationship Record CDF version 2.1. A new value, new GOVERNMENT_ACCOUNTING_STANDARD has been added to the existing QualifierCategoryTypeEnum.
[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.
  • MeasurementMethod - Specifies the method of measurement (or set of rules) used to quantitatively categorize the relationship. This field contains a valid MeasurementMethodTypeEnum as specified in the Relationship Record CDF version 2.1.
  • QuantifierAmount - Specifies the quantity measured as a decimal (positive or negative) number, using a "." as the decimal point, with no spaces, and without thousand delimiters (e.g. ",").
  • QuantifierUnits - Specifies the units, where applicable, of a measurement made on a relationship. This field contains a valid QuantifierUnitsTypeEnum as specified in the Relationship Record CDF version 2.1.
[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.
  • PENDING - The validation of the relationship data provided by the registrant has not yet occurred. Records with this ValidationSources value SHALL NOT be published.
  • ENTITY_SUPPLIED_ONLY - Based on the validation procedures in use by the LOU responsible for the record, the information associated with this record has significant reliance on the information that a submitter provided due to the unavailability of corroborating information.
  • PARTIALLY_CORROBORATED - Based on the validation procedures in use by the LOU responsible for the record, the information supplied by the submitter can be partially corroborated by supporting sources (e.g. financial statements with other definitions of the relevant relationship type; quarterly or annual regulatory filings,contracts and other documents used in preparing financial statements).
  • FULLY_CORROBORATED - The relationship data provided by the registrant has been validated against an explicit relationship statement found in key sources (e.g. consolidated financial statements)
[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.
  • ACCOUNTS_FILING - A consolidated financial (accounting) statement, prepared and submitted to the relevant authority.
  • REGULATORY_FILING - A regulatory filing providing public information on legal entities and/or their relationships.
  • SUPPORTING_DOCUMENTS - Other documents supporting the validation of legal entities and/or their relationships.
  • CONTRACTS - Contract(s) attesting to the validity of legal entities and/or their relationships.
  • OTHER_OFFICIAL_DOCUMENTS - Other official document(s) attesting to the validity of legal entities and/or their relationships.
[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]

El formato de Archivo de Datos Comunes de Registro de Relaciones (RR-CDF) 2.1

Nota: los nuevos campos y valores de enumeración añadidos en la versión 2.1 del RR-CDF están resaltados en amarillo.

Las Reglas de Transición y Validación de Estado (STVR) describen las normas comerciales y su implantación técnica para la emisión, actualización, gestión y publicación de los Datos de Referencia del IPJ de acuerdo con los formatos del Archivo de Datos Comunes (CDF).

Para ver los documentos técnicos y los archivos de ejemplo necesarios para la actualización a las versiones actuales, consulte la página Documentos de apoyo.

Puede dirigir sus preguntas sobre el formato de RR-CDF a info@gleif.org.


Archivos relevantes para descargar