Attention
This is v0.2 of the Beneficial Ownership Data Standard. It includes updates to the data model and additional codelist information.
Implementers should be aware that future changes are anticipated, before a version 1.0 release. However, from this v0.2 release onwards, any structural changes, or major definitional changes will only take place following consultation, with a clear changelog provided, and with the documentation of previous versions maintained in archive form.
The schema specifies a structure, fields and codelists but does not yet enforce validation constraints on most fields.
Support for representing details of indirect beneficial ownership relationships (where a beneficial owner owns or controls an entity through intermediaries):
isComponent
property has been added to all three Statement objects. It takes a boolean value and indicates whether a Statement represents part of a primary indirect ownership-or-control relationship.componentStatementIDs
property has been added to Ownership-or-control Statements. It takes an array of Statement IDs, indicating which component statements provide detail about the parent Ownership-or-control Statement.A required publicationDetails
property has been added to all three Statement objects. It represents metadata for Statements: information about their original publisher. Sub-properties (and their sub-properties) are:
publicationDate
*bodsVersion
*license
publisher
* (name
, url
)* required
A hasPepStatus
property (taking a boolean value) has been added to Person Statements. It is only to be used where disclosure requirements require that Politically Exposed Persons are flagged.
PEP Status objects now have the additional properties missingInfoReason
and source
.
A taxResidencies
property has been added to Person Statements. It takes an array of Country objects.
Support for more structured accounts of missing and anonymised data:
unspecifiedPersonDetails
has been added to Person Statements (with a required reason
sub-property)unspecifiedEntityDetails
has been added to Entity Statements (with a required reason
sub-property)The reason
sub-property draws on the Unspecified Reason codelist (as does the Ownership-or-control Statement’s interestedParty.unspecified
property).
pepStatus
property of Person Statements has been renamed pepStatusDetails
(and still references an array of PEP Status objects).personType
property of Person Statements is now required.Annotation.motivation
is ‘linking’, Annotation.url
is required.missingInfoReason
property has been removed from Person and Entity Statements. It has been replaced with unspecifiedPersonDetails
and unspecifiedEntityDetails
respectively.beneficialOwnershipOrControl
property added to Interest object. Takes a boolean value. Can be used to assert that an interest between a natural person and an entity makes that person a beneficial owner.pepStatus
property added to Person Statement object. Allows a natural person to be recorded as a politically exposed person (with a related reason, jurisdiction, start date and end date).annotations
property added to all three types of statement. Annotations provide a way of including additional (structured) data or transforming existing data in a targeted way.unspecified
property replaces the nullParty
option for interested parties. An unspecifiedReason codelist provides options for describing why an interested party is not recorded.statementGroup
objects (each object with its own statement group id) are no longer used to package arrays of statements. This reflects a flattening of the structure of BODS formatted data.nullParty
option for interested parties. See unspecified
property in the Added section above.