IssuerID

Overview

IssuerID provides a unique, machine-readable identifier for an issuing entity using one of several recognised identification schemes. Because no single universal issuer identifier exists in financial markets, the element deliberately accommodates multiple schemes — including security-level identifiers such as CUSIP or SEDOL repurposed as issuer identifiers — selected via the idType attribute drawn from IssuerSecurityIDTypeEnum. It is a core building block of the issuer context package, sitting beneath Issuer within IssuerDetails, and underpins cross-system entity matching, research aggregation, and disclosure linkage.

Usage

In RIXML 2.x, IssuerID appears as an optional child of Issuer with cardinality 0..unbounded, allowing the same issuer to be tagged with multiple identifiers from different schemes. Publishers are encouraged to supply more than one IssuerID (for example, both a CUSIP and a Bloomberg ticker) to maximise the likelihood that downstream consumers can resolve the entity against their own reference data. Each instance carries two required attributes: idType (the scheme, from IssuerSecurityIDTypeEnum) and idValue (the identifier string itself). The optional publisherDefinedValue is used when idType is set to PublisherDefined, to name the custom scheme in use. Typical pairings include IssuerName for human-readable naming and IssuerSecurityID within Legal disclosures, which cross-references IssuerID values to link disclosures to specific entities. While some early user guides describe IssuerID as effectively required for meaningful issuer tagging (sources: user-guide-2.1 p.34, user-guide-2.2 p.36), the schema treats it as optional with multiples allowed (sources: data-dictionary-2.4 p.50, level-one-2.5 p.12).

Rules

• MUSTWhen idType is set to PublisherDefined, the publisherDefinedValue must be populated to identify the custom scheme in use.[RIXML User Guide v2.2 p.36] [RIXML User Guide v2.3 p.36]
• MUSTEach IssuerID instance must carry both idType and idValue (in v3, the identifier moves into the element content rather than the idValue attribute).[RIXML Research Data Dictionary v2.5.1 p.53] [RIXML Level One Addendum v2.5 p.12] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.51]↗
• SHOULDPublishers should include multiple IssuerID instances using different identifier schemes to improve cross-vendor matching reliability.[RIXML Level One Addendum v2.2 p.17] [RIXML Level One Addendum v2.3.1 p.12] [RIXML Level One Addendum v2.5 p.12]
• SHOULDFor RelatedProduct entries whose relationship type implies an issuer context (for example Model, IndustryReport, or InitiationReport), an IssuerID should be supplied to ground the relationship.[RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.64]↗
• MAYBecause no universal issuer identification standard exists, security-level identifier types from IssuerSecurityIDTypeEnum (e.g. CUSIP, SEDOL) may be used as issuer identifiers.[RIXML User Guide v2.3 p.36] [RIXML Research Data Dictionary v2.4 p.50] [RIXML Research Data Dictionary v2.5.1 p.53]

Relationships

• child-ofIssuer — IssuerID is a child of Issuer within IssuerDetails, with cardinality 0..unbounded in RIXML 2.x.
• constrainsIssuerSecurityIDTypeEnum — The idType attribute is constrained to values from IssuerSecurityIDTypeEnum, which permits security identifier schemes to be reused for issuer identification.
• referenced-byIssuerSecurityID — IssuerSecurityID (used in Legal disclosures) references IssuerID values appearing elsewhere in the product metadata to link disclosures to specific entities; the issuerID attribute must resolve to a declared IssuerID.
• complementsIssuerName — IssuerID is typically paired with IssuerName to provide both machine-readable and human-readable identification of the issuing entity.
• child-ofIssuerIDList — In the RIXML v3 draft, IssuerID becomes a child of IssuerIDList rather than appearing directly under Issuer.