ores.refdata.counterparty_identifier

UUID uniquely identifying this counterparty identifier.

Surrogate key for the counterparty identifier record.

The counterparty this identifier belongs to.

References the parent counterparty record.

uuid_gen()

The identification scheme for this identifier.

References the party_id_scheme lookup table (e.g. LEI, BIC).

// no_generator_suffix: validated enum, a "-<idx>" suffix would be invalid.
// Rotate so a batch of several identifiers for one counterparty gets
// distinct schemes (max one identifier per scheme per counterparty).
[idx]{
    static constexpr const char* schemes[] = {
        "LEI", "BIC", "MIC", "NATIONAL_ID", "CEDB",
        "NATURAL_PERSON", "ACER", "DTCC_PARTICIPANT_ID", "MPID", "INTERNAL"};
    return std::string(schemes[idx % 10]);
}()

The identifier value.

The actual identifier string within the scheme. Part of the natural key alongside counterparty_id and id_scheme — a counterparty can hold more than one identifier under the same scheme as long as the value differs.

std::string(faker::string::alphanumeric(20))

Optional description of this identifier.

Free text description providing additional context.

std::string("Test identifier")

Whether this is the identifier the tenant resolves the counterparty by. At most one live identifier per counterparty may hold it.

A counterparty carries identifiers under several schemes, and nothing in them says which one decides who the counterparty is. A screen that needs one applies a precedence of its own, LEI first and then BIC. Once the tenant can state the choice, that precedence is what it starts from.

// The first row a batch generates carries the LEI scheme, which is the
// precedence a screen applied while the column did not exist. Ten schemes
// rotate per counterparty, so at most one of its rows is marked.
[idx]{
    return idx % 10 == 0;
}()

An ORE alias is a name an ORE document uses, and an import resolves the name to one counterparty, so within a tenant a name may be the alias of one counterparty only. Other schemes keep the per-counterparty key above.

A second identifier cannot claim the mark while the first holds it. The write is refused rather than quietly leaving two rows that both say they are authoritative.

Note: counterparty_id is deliberately not exposed as a Detail field – like Book's parent_portfolio_id, it's always known from the owning context (the counterparty's own Identifiers tab) and set programmatically before the dialog is shown, never user-chosen.