[corpospec]
Entity pillar · v0.16.0

ubo BeneficialOwner

Beneficial-owner record per BDR 0064 §2. Distinct from `Stakeholder` (the cap-table economic position) and from `Person` (the natural-person record). One `BeneficialOwner` record per `(entity, person)` pair can cover multiple regimes.

$id · https://corpospec.com/schemas/v0.16.0/ubo.schema.json

View raw JSON → ← all schemas

Fields

Field Type Required Description
confidentiality Confidentiality yes Confidentiality rendering rule.
effective_percentage number yes Aggregated percentage that triggered disclosure. Multiply along the chain for indirect ownership (Maik 100% of Beevelop UG × Beevelop UG 100% of Unstarter GmbH = 100% effective).
entity PathRef yes The entity being disclosed (the "subject company").
id PathRef yes PathRef identifier, conventionally `entity/ubo/<entity-slug>-<person-slug>`.
person PathRef yes The natural-person beneficial owner. PathRef into `people/**`. The fiktiver wirtschaftlich Berechtigter (Geschäftsführer fallback when the chain breaks) is also a Person PathRef.
pii_class PiiClass yes Sensitivity classification of this record. UBO records are special-category by default; carries personal data with regulatory retention.
regime UboRegime[] yes Disclosure regimes this record satisfies. A single record can cover multiple regimes if the underlying facts apply.
retention_until IsoDate yes Default retention is 5 years post-relationship-end per GwG §10.
status UboStatus yes Status of this disclosure.
threshold_basis UboBasis yes Why this person crossed the threshold.
chain PathRef[] — Ordered list of intermediate `OwnershipInterest` edges from `person` to `entity`. Empty when direct.
disclosed_to DisclosureRecipient[] — Counterparties to whom the UBO disclosure has been provided under their KYC/MLD obligations.
legal_review_date IsoDate? — Date of last GwG §10/§11 KYC review.
note string? — Free-form context.
pep_status boolean? — Politically Exposed Person flag per FATF Recommendations 12 / 22.
registry_filings RegistryFiling[] — Per-regime filing receipts.
source_of_funds string? — High-risk jurisdictions may demand source-of-funds for AML.
trust_role TrustRole? — Trust sub-role when the subject entity is a trust.

Definitions

Shared types referenced within this schema.

Confidentiality
Cross-cutting confidentiality classification used across privacy, security, knowledge, IR pillars. Default rendering rule: `corpospec-report` excludes `Restricted | BoardOnly | InvestorOnly` records from public output unless an explicit audience parameter overrides. See BDR 0076 §1.
DisclosureRecipient
Optional disclosure recipient record — banks, auditors, fund administrators that have received the UBO disclosure under their KYC / MLD obligations.
type: object
IsoDate
ISO 8601 date (YYYY-MM-DD).
type: string
PathRef
Path-based cross-reference relative to .corpospec/ root. Pattern: `^[a-z0-9_-]+(/[a-z0-9_.-]+)+$`
pattern: ^[a-z0-9_-]+(/[a-z0-9_.-]+)+$
PiiClass
Personal-data classification on every record carrying personal data, per BDR 0070 / BDR 0069 / BDR 0078. Used by `corpospec-report` to gate rendering and by the privacy pillar's RoPA records to determine safeguards.
RegistryFiling
Per-regime filing receipt evidencing the UBO disclosure.
type: object
TrustRole
Trust-specific role on a UBO record. Used when the subject entity is a trust (BDR 0064 OpenQuestion 3); captured as a sub-role on `BeneficialOwner.trust_role`.
enum: "settlor", "trustee", "protector", "beneficiary", "named_class_of_beneficiaries"
UboBasis
Why a natural person crossed the disclosure threshold for the subject entity.
UboRegime
Per-regime applicability of a beneficial-owner disclosure. One record can cover multiple regimes simultaneously.
UboStatus
Lifecycle status of a BeneficialOwner record.

Reference in your YAML

# yaml-language-server: $schema=https://corpospec.com/schemas/v0.16.0/ubo.schema.json