generated from coulomb/repo-seed
Deepen beneficial ownership and registry identifier research; resolve canon questions
Add source notes on FinCEN CDD/BOI beneficial ownership and ISO 6523/ALEI registry identifier subtypes. Resolve OpenQuestions: Beneficial Ownership Relationship as dedicated type; Registry Identifier and Proxy Commercial Identifier as Reference layer specializations. Update glossary, conceptual model, terminology, downstream recommendations, and corpus index.
This commit is contained in:
@@ -64,6 +64,8 @@ The repository is focused on research and terminology. The corpus should collect
|
||||
- `kyc-aml-commercial-identity-binding.md`
|
||||
- `eidas-eudi-legal-person-wallet.md`
|
||||
- `salesforce-crm-commercial-record.md`
|
||||
- `beneficial-ownership-kyc-boi.md`
|
||||
- `registry-identifier-subtypes.md`
|
||||
|
||||
## Source Note Template
|
||||
|
||||
|
||||
179
research/commercial-identity/beneficial-ownership-kyc-boi.md
Normal file
179
research/commercial-identity/beneficial-ownership-kyc-boi.md
Normal file
@@ -0,0 +1,179 @@
|
||||
# Beneficial Ownership — CDD, BOI, and KYC Modeling
|
||||
|
||||
## Source Type
|
||||
|
||||
Regulatory framework synthesis. FinCEN CDD Rule (31 CFR 1010.230), Corporate
|
||||
Transparency Act / BOI reporting, FATF Recommendation 24, and KYC industry
|
||||
practice.
|
||||
|
||||
## Domain
|
||||
|
||||
Beneficial ownership identification for legal entity customers — financial
|
||||
institution due diligence, government transparency registries, and regulated
|
||||
commercial onboarding.
|
||||
|
||||
## Why This Source Matters
|
||||
|
||||
Beneficial ownership is the regulatory answer to "who really controls this
|
||||
legal entity customer?" It is **not** the same as corporate parent ownership
|
||||
(LEI Level 2), operational resource ownership (Cerbos), or CRM account hierarchy.
|
||||
Regulators impose **two independent prongs** (equity and control), trust
|
||||
look-through rules, nominee prohibitions, and evidence retention — all scoped
|
||||
to **counterparty risk**, not general graph semantics.
|
||||
|
||||
## Key Concepts
|
||||
|
||||
### FinCEN CDD Rule (customer due diligence)
|
||||
|
||||
- **Legal entity customer**: corporations, LLCs, general partnerships, and
|
||||
similar entities opening accounts at covered financial institutions.
|
||||
- **Beneficial owner — ownership prong**: each individual who directly or
|
||||
indirectly owns **25% or more** of equity interests.
|
||||
- **Beneficial owner — control prong**: a **single** individual with significant
|
||||
responsibility to control, manage, or direct the legal entity (e.g., CEO,
|
||||
CFO, managing member, general partner, president).
|
||||
- **Collection at account opening**: identify and verify BO identities when a
|
||||
new account opens (with 2026 exceptive relief allowing reuse after first
|
||||
account unless risk triggers update).
|
||||
- **Nominee prohibition**: legal entity must identify **ultimate** beneficial
|
||||
owners, not nominees or straw men.
|
||||
- **Trust look-through**: when a trust owns 25%+ equity, identify natural persons
|
||||
behind the trust (settlor, trustees, beneficiaries as applicable); a legal
|
||||
entity trustee does **not** satisfy the ownership prong — natural persons must
|
||||
be identified.
|
||||
- **Risk-based updates**: ongoing CDD may require BO refresh on triggering
|
||||
events, not only at opening.
|
||||
- **CIP alignment**: BO verification procedures must contain CIP-equivalent
|
||||
elements for individuals but are not identical to the institution's CIP.
|
||||
|
||||
### BOI / Corporate Transparency Act (entity reporting)
|
||||
|
||||
- **Distinct from CDD**: BOI is a **filing obligation on reporting companies**
|
||||
to FinCEN's BOI registry, not a financial-institution collection rule.
|
||||
- **Reporting company beneficial owner**: similar dual-prong concept (substantial
|
||||
ownership + substantial control) with FinCEN ID for individuals.
|
||||
- **US regulatory volatility (2025–2026)**: interim final rules and litigation
|
||||
have substantially narrowed or suspended BOI reporting for many US domestic
|
||||
entities. **CDD beneficial ownership collection by financial institutions
|
||||
remains in force** for covered institutions regardless of BOI reporting shifts.
|
||||
- **Foreign entities**: BOI and transparency expectations remain more relevant
|
||||
for non-US reporting companies and cross-border KYC.
|
||||
|
||||
### FATF Recommendation 24
|
||||
|
||||
- Requires countries to ensure adequate, accurate, and up-to-date **beneficial
|
||||
ownership information** on legal persons, accessible to competent authorities.
|
||||
- Supports **multi-prong** definitions (ownership threshold + control) and
|
||||
look-through for complex structures (trusts, nominees, layered ownership).
|
||||
- Drives national registries and financial-sector CDD alignment globally.
|
||||
|
||||
### KYC practice overlay
|
||||
|
||||
- Institutions may adopt **lower equity thresholds** for high-risk customers
|
||||
(e.g., 10%) under AML program risk policies.
|
||||
- **PEP screening** applies to beneficial owners, not only account signers.
|
||||
- **Sanctions screening** (OFAC) must cover identified beneficial owners.
|
||||
- BO evidence retained for years after relationship ends (BSA record retention).
|
||||
|
||||
## Relevant Terminology
|
||||
|
||||
| Term | Source meaning |
|
||||
| --- | --- |
|
||||
| Beneficial owner | Natural person owning 25%+ or exercising substantial control. |
|
||||
| Ownership prong | Equity-interest threshold test. |
|
||||
| Control prong | Significant management/control responsibility test. |
|
||||
| Legal entity customer | Entity opening a financial account subject to CDD. |
|
||||
| CDD Rule | FinCEN customer due diligence requirements (2016, amended). |
|
||||
| BOI / CTA | Corporate Transparency Act beneficial ownership information reporting. |
|
||||
| FinCEN ID | Individual identifier for BOI filers. |
|
||||
| Nominee / straw man | Non-ultimate owner; prohibited as BO response under CDD. |
|
||||
| Look-through | Identifying natural persons behind trusts or intermediary entities. |
|
||||
|
||||
## Modeling Assumptions
|
||||
|
||||
- **Beneficial ownership is relationship semantics**, not a new actor type.
|
||||
The natural person remains **Natural Person**; the assertion is regulatory.
|
||||
- **Ownership prong and control prong are orthogonal** — one person may satisfy
|
||||
both, and multiple persons may satisfy ownership prong while exactly one
|
||||
control-prong person is required under US CDD.
|
||||
- **Beneficial ownership ≠ corporate parent ownership** (LEI Level 2 describes
|
||||
corporate structure; BO describes natural persons behind a customer entity).
|
||||
- **Beneficial ownership ≠ Representation** (authorized signers may represent
|
||||
without being beneficial owners).
|
||||
- **Lifecycle is risk-triggered**, not merely account-open/close.
|
||||
- **Regulatory regime is a scope dimension** — US CDD, EU AMLD, FATF R24, and
|
||||
BOI filing may differ; canon models the relationship, downstream applies law.
|
||||
|
||||
## Identity-Canon Implications
|
||||
|
||||
### Resolved: dedicated relationship type
|
||||
|
||||
**Beneficial Ownership Relationship** is a first-class relationship type — **not**
|
||||
an Ownership subtype with `beneficial` metadata.
|
||||
|
||||
**Rationale:**
|
||||
|
||||
| Concern | Why not Ownership subtype |
|
||||
| --- | --- |
|
||||
| Semantic collision | Ownership in canon covers records, tenants, resources, corporate parents — not regulated natural-person BO. |
|
||||
| Dual prongs | Ownership prong (%) and control prong (role) are regulatory-specific; corporate Ownership edges lack this structure. |
|
||||
| Trust look-through | Requires intermediary entity traversal metadata absent from generic Ownership. |
|
||||
| Evidence & scope | BO ties to CDD/AML Evidence Source, Commercial Relationship, and jurisdictional scope — distinct lifecycle from LEI parent edges. |
|
||||
| Projection safety | Prevents Cerbos/Zanzibar "owner" tuples from silently implying KYC beneficial owner compliance. |
|
||||
|
||||
**Beneficial Owner** remains a glossary label for the **natural person** who is
|
||||
the target of a Beneficial Ownership Relationship — not a participation root.
|
||||
|
||||
### Recommended relationship fields
|
||||
|
||||
- `relationship_type`: `beneficial_ownership`
|
||||
- `source`: Natural Person
|
||||
- `target`: Organization / Legal Entity (the legal entity **customer**)
|
||||
- `scope`: jurisdiction + institution/program (e.g., US CDD, EU AMLD)
|
||||
- `ownership_prong`: boolean
|
||||
- `control_prong`: boolean
|
||||
- `equity_percentage`: optional numeric (when ownership prong)
|
||||
- `control_basis`: optional enum (e.g., `ceo`, `managing_member`, `general_partner`)
|
||||
- `intermediary_chain`: optional ordered list for trust/entity look-through
|
||||
- `evidence_reference`: CDD certification, BOI filing, registry extract
|
||||
- `lifecycle_state`: proposed, active, superseded, revoked
|
||||
- `regulatory_basis`: optional reference (CDD Rule, FATF R24, national statute)
|
||||
|
||||
### Mapping table
|
||||
|
||||
| Source concept | Canonical mapping |
|
||||
| --- | --- |
|
||||
| Beneficial owner (person) | Natural Person |
|
||||
| BO linkage | Beneficial Ownership Relationship |
|
||||
| CDD certification | Evidence Source |
|
||||
| Legal entity customer | Organization / Legal Entity + Commercial Relationship |
|
||||
| BOI filing record | Evidence Source (registry) on Legal Entity |
|
||||
| FinCEN ID | Identifier (government registry) on Natural Person |
|
||||
| PEP/sanctions hit on BO | Lifecycle State / Trust Relationship on BO relationship |
|
||||
| LEI Level 2 parent | Ownership Relationship (corporate structure — separate) |
|
||||
|
||||
## Terminology Conflicts
|
||||
|
||||
- **Beneficial owner (CDD)** vs. **beneficial owner (BOI filing)** vs.
|
||||
**beneficial owner (transparency registry)**: same conceptual person, different
|
||||
regulatory scopes and evidence — use `scope` and `regulatory_basis` metadata.
|
||||
- **Owner (Cerbos resource)** vs. **beneficial owner**: authorization attribute
|
||||
vs. regulated natural-person linkage.
|
||||
- **Shareholder** vs. **beneficial owner**: not all shareholders meet BO thresholds;
|
||||
control prong may identify non-shareholders.
|
||||
|
||||
## Open Questions
|
||||
|
||||
- Standard `control_basis` enum across jurisdictions (US CDD vs. EU AMLD wording).
|
||||
- Whether BOI FinCEN ID should map to Registry Identifier or generic Identifier.
|
||||
- Modeling **exempt** legal entity customers (publicly traded, government) as
|
||||
absence of BO relationship vs. explicit exemption Evidence.
|
||||
|
||||
## References
|
||||
|
||||
- FinCEN, CDD Rule FAQs — https://www.fincen.gov/resources/statutes-and-regulations/cdd-rule-faqs
|
||||
- FinCEN, CDD Final Rule — https://www.fincen.gov/resources/statutes-regulations/cdd-final-rule
|
||||
- FinCEN, Account Opening Exceptive Relief Order (FIN-2026-R001) — https://www.fincen.gov/system/files/2026-02/FinCEN-Order-CCDExceptiveRelief.pdf
|
||||
- FATF, Recommendation 24 — https://www.fatf-gafi.org/en/topics/fatf-recommendations.html
|
||||
- Open Ownership, reliable identifiers for corporate vehicles — https://www.openownership.org/en/publications/using-reliable-identifiers-for-corporate-vehicles-in-beneficial-ownership-data/
|
||||
- Internal: `kyc-aml-commercial-identity-binding.md`, `lei-gleif-legal-entity-identifier.md`
|
||||
@@ -83,7 +83,10 @@ Commercial Commitment + Evidence, not declared ad hoc.
|
||||
- **Commercial Relationship** — vendor/customer commercial link.
|
||||
- **Commercial Commitment** — enforceable or costly promise binding parties (contract,
|
||||
subscription, payment mandate, regulatory onboarding acceptance).
|
||||
- **Beneficial Owner linkage** — Natural Person to Organization for entity customers.
|
||||
- **Beneficial Ownership Relationship** — dedicated type from Natural Person to
|
||||
Organization/Legal Entity for KYC/CDD (not Ownership subtype).
|
||||
- **Registry Identifier** and **Proxy Commercial Identifier** — Reference layer
|
||||
subtypes with authority class, ICD scheme, and renewal lifecycle.
|
||||
|
||||
### Unchanged roots
|
||||
|
||||
@@ -112,8 +115,9 @@ Model as lifecycle events, not silent merges:
|
||||
|
||||
- Payment Credential vs. authentication Credential boundary in PCI contexts.
|
||||
- Smart contracts and automated Commercial Commitment lifecycle.
|
||||
- Cross-border registry Synonymity for same legal entity (LEI ↔ DUNS ↔ company reg).
|
||||
- Synonymity strength bands for LEI ↔ DUNS ↔ company reg crosswalks.
|
||||
- Reputation as first-class canon concept vs. Evidence Source aggregation.
|
||||
- Standard `control_basis` enum for Beneficial Ownership across jurisdictions.
|
||||
|
||||
## Source Notes in This Stack
|
||||
|
||||
@@ -124,6 +128,8 @@ Model as lifecycle events, not silent merges:
|
||||
- `kyc-aml-commercial-identity-binding.md`
|
||||
- `eidas-eudi-legal-person-wallet.md`
|
||||
- `salesforce-crm-commercial-record.md`
|
||||
- `beneficial-ownership-kyc-boi.md`
|
||||
- `registry-identifier-subtypes.md`
|
||||
- `../commercial-subscription/b2b-saas-subscriber-tenancy.md`
|
||||
- `../commercial-subscription/stripe-customer-billing.md`
|
||||
|
||||
|
||||
@@ -49,7 +49,8 @@ interest among counterparties.
|
||||
|
||||
## Identity-Canon Implications
|
||||
|
||||
- DUNS maps to **Identifier** on **Commercial Record** / **Organization**.
|
||||
- DUNS maps to **Proxy Commercial Identifier** (`scheme: 0060`,
|
||||
`authority_class: commercial_proxy`) on **Commercial Record** / **Organization**.
|
||||
- PAYDEX and credit file map to **Evidence Source** influencing **Trust Relationship**
|
||||
and counterparty risk.
|
||||
- UEI maps to **Identifier** (government authoritative) on Commercial Record.
|
||||
@@ -67,7 +68,7 @@ interest among counterparties.
|
||||
|
||||
| D&B / procurement concept | Candidate canonical concept |
|
||||
| --- | --- |
|
||||
| DUNS number | Identifier |
|
||||
| DUNS number | Proxy Commercial Identifier (ICD 0060) |
|
||||
| D&B business record | Commercial Record |
|
||||
| PAYDEX | Evidence Source (credit performance) |
|
||||
| UEI | Identifier (government registry) |
|
||||
|
||||
@@ -59,8 +59,9 @@ high-stakes counterparty records**.
|
||||
|
||||
- KYC onboarding creates **Commercial Record** + **Commercial Commitment** (regulated
|
||||
relationship) bound to **Natural Person** and/or **Organization/Legal Entity**.
|
||||
- **Beneficial owner** maps to **Natural Person** linked via **Ownership** or
|
||||
**Representation** to Organization customer.
|
||||
- **Beneficial owner** maps to **Natural Person** linked via **Beneficial
|
||||
Ownership Relationship** to Organization/Legal Entity customer (see
|
||||
`beneficial-ownership-kyc-boi.md`).
|
||||
- CIP evidence maps to **Evidence Source** with **Assurance Level**.
|
||||
- Ongoing monitoring produces **Evidence Source** events affecting **Lifecycle State**
|
||||
and **Trust Relationship**.
|
||||
@@ -80,7 +81,7 @@ high-stakes counterparty records**.
|
||||
| --- | --- |
|
||||
| Verified customer | Commercial Record + Actor binding |
|
||||
| CIP evidence | Evidence Source |
|
||||
| Beneficial owner | Natural Person + Ownership Relationship |
|
||||
| Beneficial owner | Natural Person + Beneficial Ownership Relationship |
|
||||
| Risk profile | Assurance Level + metadata on Commercial Relationship |
|
||||
| EDD review | Evidence Source (enhanced) |
|
||||
| Sanctions hit | Lifecycle State / Trust Relationship revocation |
|
||||
@@ -89,9 +90,13 @@ high-stakes counterparty records**.
|
||||
|
||||
## Open Questions
|
||||
|
||||
- Should Beneficial Owner be a canonical relationship role or Ownership subtype?
|
||||
- Standard `control_basis` enum across US CDD and EU AMLD wording.
|
||||
- How to model BOI registry volatility in lifecycle without canon becoming legal advice?
|
||||
|
||||
## Resolved (see beneficial-ownership-kyc-boi.md)
|
||||
|
||||
- Beneficial Owner → **Beneficial Ownership Relationship** (dedicated type, not Ownership subtype).
|
||||
|
||||
## References
|
||||
|
||||
- Thomson Reuters, Customer Identification Program overview — https://legal.thomsonreuters.com/blog/overview-customer-identification-program-cip/
|
||||
|
||||
@@ -51,7 +51,9 @@ requirements.
|
||||
|
||||
## Identity-Canon Implications
|
||||
|
||||
- LEI maps to **Identifier** for **Legal Entity** / **Organization** actors.
|
||||
- LEI maps to **Registry Identifier** (`scheme: 0199`, `authority_class:
|
||||
regulatory_global`, `renewal_required: true`) for **Legal Entity** /
|
||||
**Organization** actors.
|
||||
- Level 2 parent data maps to **Ownership** or structural Organization relationships.
|
||||
- LEI record maps to **Commercial Record** or authoritative **Identity Record**
|
||||
with registry **Evidence Source**.
|
||||
@@ -70,7 +72,7 @@ requirements.
|
||||
|
||||
| LEI concept | Candidate canonical concept |
|
||||
| --- | --- |
|
||||
| LEI code | Identifier (authoritative, global) |
|
||||
| LEI code | Registry Identifier (regulatory_global, ICD 0199) |
|
||||
| Legal entity | Legal Entity / Organization |
|
||||
| Level 1 data | Commercial Record / registry Profile |
|
||||
| Level 2 parent | Ownership Relationship |
|
||||
@@ -80,8 +82,12 @@ requirements.
|
||||
|
||||
## Open Questions
|
||||
|
||||
- Should authoritative registry identifiers (LEI, company reg number) be a distinct
|
||||
Identifier subtype with renewal semantics?
|
||||
- Synonymity strength when linking LEI to DUNS or national company reg numbers.
|
||||
|
||||
## Resolved (see registry-identifier-subtypes.md)
|
||||
|
||||
- Authoritative and proxy registry IDs → **Registry Identifier** subtype with
|
||||
authority class and renewal lifecycle.
|
||||
|
||||
## References
|
||||
|
||||
|
||||
182
research/commercial-identity/registry-identifier-subtypes.md
Normal file
182
research/commercial-identity/registry-identifier-subtypes.md
Normal file
@@ -0,0 +1,182 @@
|
||||
# Registry Identifier Subtypes — ISO 6523, ALEI, LEI, DUNS, UEI
|
||||
|
||||
## Source Type
|
||||
|
||||
Standards and registry synthesis. ISO/IEC 6523, ISO 17442 (LEI), ISO 8000-116
|
||||
(ALEI), GLEIF, D&B DUNS, SAM.gov UEI, EITI/Open Ownership identifier guidance.
|
||||
|
||||
## Domain
|
||||
|
||||
Authoritative and proxy organization identifiers used in commerce, procurement,
|
||||
financial markets, beneficial ownership transparency, and master data management.
|
||||
|
||||
## Why This Source Matters
|
||||
|
||||
Legal entities accumulate **multiple identifiers** from different registries —
|
||||
company registration numbers, LEI, DUNS, UEI, VAT — each with different
|
||||
**issuing authority**, **renewal rules**, and **trust basis**. Collapsing them
|
||||
into generic Identifier loses lifecycle, authority, and cross-registry linking
|
||||
semantics needed for commercial binding and BO transparency.
|
||||
|
||||
## Key Concepts
|
||||
|
||||
### ISO/IEC 6523 structure
|
||||
|
||||
ISO/IEC 6523 defines organization identification as:
|
||||
|
||||
- **International Code Designator (ICD)**: up to 4 digits identifying the issuing
|
||||
scheme authority (registered with ISO/IEC 6523-2).
|
||||
- **Organization identifier**: up to 35 characters within that scheme.
|
||||
- **Optional organization part identifier (OPI)**: sub-entity within organization.
|
||||
|
||||
Combined form enables global interchange (PEPPOL, EDIFACT, Schema.org `iso6523Code`).
|
||||
|
||||
Example ICD allocations relevant to commercial identity:
|
||||
|
||||
| ICD | Scheme | Authority type |
|
||||
| --- | --- | --- |
|
||||
| 0060 | D-U-N-S (DUNS) | Commercial proxy (D&B) |
|
||||
| 0088 | EAN Location Code (GLN) | GS1 location |
|
||||
| 0151 | Singapore UEN | Government registry |
|
||||
| 0199 | Legal Entity Identifier (LEI) | GLEIF / ISO 17442 |
|
||||
| 0209 | GS1 identification keys | GS1 |
|
||||
|
||||
(Full list maintained at iso6523.info and PEPPOL ICD codelists.)
|
||||
|
||||
### Authoritative vs. proxy identifiers (ISO 8000-116 / ALEI)
|
||||
|
||||
**Authoritative Legal Entity Identifier (ALEI)**: identifier assigned by a
|
||||
**government jurisdiction** authorized by statute to create legal entities and
|
||||
maintain authoritative registries. Format: jurisdiction prefix + register +
|
||||
local number (e.g., `US-DE.BER:3031657`).
|
||||
|
||||
**Proxy identifiers**: issued by institutions that do **not** create legal
|
||||
entities — DUNS (D&B), NCAGE (CAGE), and arguably LEI (GLEIF issues to existing
|
||||
legal entities but does not incorporate them).
|
||||
|
||||
**LEI nuance**: ISO 17442 / GLEIF is regulatory-mandated for financial
|
||||
transactions but is a **cross-jurisdiction overlay** on existing legal entities,
|
||||
not the incorporating register. Canon treats LEI as **Registry Identifier**
|
||||
with `authority_class: regulatory_global`.
|
||||
|
||||
### Renewal and lifecycle
|
||||
|
||||
| Identifier | Renewal / validity | Lifecycle driver |
|
||||
| --- | --- | --- |
|
||||
| LEI | Annual renewal required | GLEIF / LOU reaffirmation |
|
||||
| DUNS | No annual renewal; record updates | D&B data maintenance |
|
||||
| UEI | Persistent in SAM.gov | Entity registration status |
|
||||
| Company reg number | Jurisdiction-specific | Annual report / dissolution |
|
||||
| ALEI / IBRN | Tied to registry filing status | Government register |
|
||||
| VAT / tax ID | Jurisdiction-specific | Tax authority |
|
||||
|
||||
Renewal semantics belong on **Registry Identifier** lifecycle state, not on the
|
||||
Organization actor.
|
||||
|
||||
### Cross-registry linking
|
||||
|
||||
Same legal entity may hold LEI + DUNS + UEI + national company number.
|
||||
**Synonymity Assertion** (`same_as`, strong or authoritative) links Registry
|
||||
Identifiers when evidenced by registry crosswalk, LOU verification, or operator
|
||||
confirmation. Do not silently merge Commercial Records.
|
||||
|
||||
EITI and Open Ownership recommend **reliable organizational identifiers**
|
||||
(especially authoritative registration numbers) in beneficial ownership datasets
|
||||
to disambiguate corporate vehicles.
|
||||
|
||||
## Relevant Terminology
|
||||
|
||||
| Term | Source meaning |
|
||||
| --- | --- |
|
||||
| Registry Identifier | Identifier issued under a registered scheme with known authority. |
|
||||
| ICD | ISO 6523 International Code Designator for a scheme. |
|
||||
| ALEI | Authoritative Legal Entity Identifier (government register). |
|
||||
| Proxy identifier | Commercial or overlay ID not from incorporating authority. |
|
||||
| LOU | Local Operating Unit issuing LEIs. |
|
||||
| Renewal | Periodic reaffirmation of identifier validity (esp. LEI). |
|
||||
| Crosswalk | Mapping between identifiers for same entity. |
|
||||
|
||||
## Modeling Assumptions
|
||||
|
||||
- **Registry Identifier is an Identifier subtype**, not a Record layer entity.
|
||||
The registry **record** (GLEIF entry, D&B profile, SAM registration) maps to
|
||||
Commercial Record or Identity Record.
|
||||
- **Authority class** matters more than brand name (LEI vs. DUNS vs. company reg).
|
||||
- **Renewal is optional metadata** — present for LEI, absent for DUNS.
|
||||
- **ICD code** is the preferred `scheme` key for ISO 6523-aligned identifiers.
|
||||
- **Proxy Commercial Identifier** is a Registry Identifier with
|
||||
`authority_class: commercial_proxy` for DUNS-like schemes.
|
||||
|
||||
## Identity-Canon Implications
|
||||
|
||||
### Resolved: Registry Identifier subtype
|
||||
|
||||
Add **Registry Identifier** as an Identifier specialization in the Reference layer.
|
||||
|
||||
**Recommended fields:**
|
||||
|
||||
- `scheme`: ICD code or well-known scheme URI (e.g., `0199` for LEI, `0060` for DUNS)
|
||||
- `authority`: issuing body (GLEIF LOU, D&B, SAM.gov, Companies House, etc.)
|
||||
- `authority_class`: `government_registry` | `regulatory_global` | `commercial_proxy` | `tax`
|
||||
- `jurisdiction`: ISO country/subdivision when applicable
|
||||
- `value`: the identifier string
|
||||
- `renewal_required`: boolean
|
||||
- `lifecycle_state`: active, lapsed, revoked, expired, superseded
|
||||
- `last_renewed_at` / `expires_at`: when renewal applies
|
||||
- `evidence_source`: registry lookup, LOU issuance, API verification
|
||||
|
||||
### Proxy Commercial Identifier
|
||||
|
||||
**Proxy Commercial Identifier** is a Registry Identifier with
|
||||
`authority_class: commercial_proxy` — vendor-operated business keys (DUNS) used
|
||||
for credit and procurement but not legal incorporation. Keeps DUNS mapping
|
||||
explicit without conflating with ALEI or company registration numbers.
|
||||
|
||||
### Mapping table
|
||||
|
||||
| Source identifier | Canonical mapping |
|
||||
| --- | --- |
|
||||
| LEI code | Registry Identifier (`scheme: 0199`, `authority_class: regulatory_global`) |
|
||||
| DUNS | Proxy Commercial Identifier (`scheme: 0060`) |
|
||||
| UEI (SAM.gov) | Registry Identifier (`authority_class: government_registry`, US federal) |
|
||||
| Company registration number | Registry Identifier (`authority_class: government_registry`, jurisdiction-local) |
|
||||
| ALEI / IBRN | Registry Identifier (`authority_class: government_registry`, ISO 8000-116 format) |
|
||||
| VAT / EIN / tax ID | Registry Identifier (`authority_class: tax`) |
|
||||
| GLEIF registry entry | Commercial Record or Identity Record + Evidence Source |
|
||||
| D&B business profile | Commercial Record + PAYDEX as Evidence Source |
|
||||
| Same entity, multiple IDs | Synonymity Assertion between Registry Identifiers |
|
||||
|
||||
### Relationship to Beneficial Ownership
|
||||
|
||||
BO datasets should reference **Organization/Legal Entity** via Registry Identifier
|
||||
(authoritative company reg preferred; LEI as strong cross-border key). Beneficial
|
||||
Ownership Relationships attach to the entity actor, not to the identifier — but
|
||||
identifier quality affects Evidence strength on BO filings.
|
||||
|
||||
## Terminology Conflicts
|
||||
|
||||
- **Legal entity (LEI)** vs. **Organization (canon)**: LEI subset ⊂ organizations
|
||||
with financial/regulatory participation.
|
||||
- **DUNS business entity** vs. **Legal Entity**: D&B may assign DUNS to locations
|
||||
or branches not identical to juridical persons.
|
||||
- **Identifier** vs. **Commercial Record**: Stripe `customer_id` is scoped
|
||||
system Identifier; LEI is registry Identifier — different authority classes.
|
||||
|
||||
## Open Questions
|
||||
|
||||
- Whether `authority_class` enum needs `industry_association` (e.g., NCAGE).
|
||||
- Standard Synonymity strength when linking LEI ↔ DUNS (medium vs. strong).
|
||||
- PEPPOL / ISO 6523 OPI modeling for branch-level identifiers vs. Organization Unit.
|
||||
|
||||
## References
|
||||
|
||||
- ISO/IEC 6523 — https://www.iso.org/standard/25773.html
|
||||
- ISO 17442 (LEI) — https://www.iso.org/standard/78829.html
|
||||
- ISO 8000-116 (ALEI) — https://www.iso.org/standard/75117.html
|
||||
- GLEIF, Introducing the LEI — https://www.gleif.org/en/about-lei/introducing-the-legal-entity-identifier-lei
|
||||
- iso6523.info ICD list — http://iso6523.info/icd_list.pdf
|
||||
- PEPPOL ICD codelist — https://docs.peppol.eu/poacc/billing/3.0/codelist/ICD/
|
||||
- GSA, Unique Entity Identifier — https://www.gsa.gov/about-us/organization/federal-acquisition-service/fas-initiatives/integrated-award-environment/iae-systems-information-kit/unique-entity-identifier-update
|
||||
- EITI, Organisational identifiers guidance — https://eiti.org/sites/default/files/2023-11/Technical%20Guidance%20%E2%80%93%20Organisational%20identifiers%20guidance%20%20WEB.pdf
|
||||
- Open Ownership, reliable identifiers — https://www.openownership.org/en/publications/using-reliable-identifiers-for-corporate-vehicles-in-beneficial-ownership-data/
|
||||
- Internal: `lei-gleif-legal-entity-identifier.md`, `duns-commercial-credit-identity.md`
|
||||
Reference in New Issue
Block a user