A visual essay / The Beneficial Ownership Data Standard

The name on the certificate is not the owner.

A company name is where the record starts. It is not where accountability ends. Here is a company certificate. Pull one line. Watch the name become a network, the network become a human record, and the human record become a dated claim you can test.

Name it. Link it. Date it. Test it.

BODS v0.4 Pull the line Teaching walkthrough, real record at the end Plain version
scroll
Scene 01 · The door

The record names the company.

Mirembe Infrastructure Ltd has won a public contract. Public money: a road, a clinic, a classroom block. The registry gives you a clean record with the company's name on it. It does not tell you who is behind it.

A company name is not an owner. It is a door.

Here is why a name is not enough. One member of the committee that awarded this contract is named Amina K. If the person who benefits from Mirembe is also Amina K., that is a conflict of interest worth knowing. Maybe it is a coincidence of names. You cannot tell from a certificate. You have to open the door.

Scene 02

The first answer is another company.

Pull the line and it leaves the certificate. It lands on Lakefront Holdings Ltd, a 60% shareholder. Useful. Not enough. A company cannot ultimately enjoy private benefit or hold a conflict of interest.

In BODS, each company is an entity
Scene 03

Ownership is not a list. It is a route.

Read it like an x-ray, not a conspiracy board. Lakefront leads to Blue Gate Nominees, a nominee: a company that holds shares in its own name on someone else's behalf. The nominee leads toward a person. The route can pass through companies, nominees and legal arrangements before it reaches whoever benefits or controls.

Direct is a straight line. Indirect is a route.

Direct and indirect
Scene 04 · The question

The line reaches a human being. And it is the same name.

The person who benefits from Mirembe is Amina K. The same Amina K. who sat on the committee that awarded its contract. This does not mean guilt. It means the question can finally be asked properly: of a person, not a name on a door.

recordType: person
names:
- type: legal
  fullName: Amina K.
birthDate: 1979 // YYYY, where disclosed
nationalities: [ where disclosed ]

A beneficial owner is not whoever is listed near the company. The person must be connected by an ownership or control relationship. The line had to reach here before the conflict could even be named, and naming it is not the same as proving it.

That is the idea

A company name was a door. The line went through companies and a nominee, and reached a person, who turns out to be on the committee. That is the whole point, and you can stop here. What follows is how the standard records a trail like this so anyone else can check it.

Scene 05 · Freeze the chase

BODS turns the chase into three kinds of statement.

Now that you have seen why the company name was not enough, here is the model that made the chase recordable. A BODS dataset is a list of statements, each about one of three things.

recordType: entity

Entity

The legal thing: a company, trust or other arrangement. What is being owned or controlled.

Entity = the legal thing.

recordType: person

Person

The natural human being who may own, control or benefit. The one you just reached.

Person = the human.

recordType: relationship

Relationship

The link: a party's interest in an entity, with its type, share, and whether it is direct or indirect.

Relationship = the reason the line exists.

Scene 06 · The hinge

The relationship is the hinge.

If the company was the door, the relationship statement is the hinge: it is what connects the company to the person. It names a subject and an interestedParty, then lists interests. Each interest carries its own directOrIndirect and a beneficialOwnershipOrControl flag.

Worth keeping straight: that flag is a property of each interest, not a single switch on the relationship.

Scene 07 · The breadcrumbs

The route, recorded.

When ownership is indirect, the primary relationship still names the beneficial owner. The intermediary hops are kept as component relationships, referenced from the primary one.

componentRecords · isComponent

A claim is not a fact. A dated, sourced claim is something you can test.

Name it entity, personLink it relationshipDate it source, dateTest it query
Scene 08 · What the data actually claims

This is still a claim. Its value is that it is testable.

A source said it, on a date, under a disclosure rule. BODS does not say "this is the truth." It says "this source made this claim, on this date, and you can now check it."

CLAIM
The statement, with its provenance
statementDate: 2026-06-14
source:
type: ["selfDeclaration"]
recordStatus: new
NOT PROOF BY ITSELF
What it is not
verified: no, not a finding
immutable: yes, never edited
updates: new statements only
conflicts: recorded, not hidden

Most writing says "BODS reveals the real owner." The sharper, accurate claim is that BODS makes the ownership claim inspectable: sourced, dated and testable. Statements are immutable; a correction is a new statement that amends or confirms the old one, not an edit in place.

Scene 09 · The ledger

The statement changes. The record stays traceable.

Two IDs do different jobs. statementId identifies this claim. recordId identifies the thing the claim is about. A 2023 statement and a 2026 statement share one recordId: the share fell from 60 to 20, and the old claim is still in the record.

statementId = this claim. recordId = the thing the claim is about.

recordStatus moves new → updated for the same record. Nothing is edited in place.

Why insist on a record that never forgets? Because companies are built to be forgotten.

Scene 10 · The phoenix

The company is disposable. The person is not.

Say Mirembe gets flagged and dissolved. Six months later a new company appears, Riverbank Works Ltd: new name, new certificate, same beneficial owner. A flagged company can be closed and re-formed overnight. What it cannot easily shed, once the ownership record links them, is the person behind it.

A stable person recordId links the same human across every company they appear behind.

That persistence is the point: a regulator can see the pattern and ask the next question. A pattern worth checking is not a verdict on the person, and a fresh company name is not a fresh start on the record.

Scene 11 · Run the question

Once the record is linked, you can interrogate it.

Once company, person, relationship, source and date are linked, the record can be queried. Pick a question and watch the line move.

Mirembe Infrastructure Lakefront Holdings Blue Gate Nominees Amina K.
The line runs Mirembe → Lakefront → Blue Gate → Amina K. result: person reached through relationship statements limit: a sourced, dated claim, not proof
Two intermediary hops sit between Amina K. and Mirembe. result: directOrIndirect: indirect the route is held in componentRecords
One recordId, two statements: 60% in 2023, 20% in 2026. result: share.exact 60 → 20, nothing overwritten the older statement is still in the record
Blank is not the same as none. Where no owner is disclosed, the relationship records a reason instead of a person. result: interestedParty.reason: noBeneficialOwners the line is drawn broken, not hidden
The limits, stated plainly

BODS can show

  • who was declared as owner or controller
  • by which source
  • on which date
  • through which interest, direct or indirect

BODS cannot prove by itself

  • that the declaration is true
  • that the person is guilty of anything
  • that the structure shown is complete
  • that the register is current
The quiet move

Turn a sentence into linked evidence.

A sentence

Mirembe Infrastructure Ltd is 60% indirectly owned by Amina K., through Lakefront Holdings Ltd and Blue Gate Nominees Ltd.

Linked evidence
entity Mirembe Infrastructure Ltd
entity Lakefront Holdings Ltd
entity Blue Gate Nominees Ltd
person Amina K.
relationship the ownership route
source.type: ["selfDeclaration"]
statementDate: 2026-06-14

That is the standard's quiet move: a claim anyone can state in a sentence becomes a structure anyone can trace, date and test.

The payoff in one frame
Before · the certificate alone
Company: Mirembe Infrastructure Ltd
Shareholder: Lakefront Holdings Ltd
Owner: a name, not a person
After · the line followed
Beneficial owner: Amina K.
Interest: indirect shareholding
Route: Lakefront → Blue Gate
Source: selfDeclaration
Date: 2026-06-14
Status: claim, not proof
Scene 12 · The reveal

The certificate did not lie. It was incomplete.

The same bright underline from the first scene now runs unbroken from the company name, through the intermediaries, to a human record. The company was the door. The relationship was the hinge. The person was the question. The date made it evidence.

Beneficial ownership transparency begins when the company name stops being treated as the answer. BODS does not reveal truth. It makes ownership claims linkable, dated and testable.

A company name is where the record starts. The public-interest question is who the line reaches.

Method & sources

A teaching essay on the Beneficial Ownership Data Standard (BODS v0.4). The reader follows one editorial data line from a company certificate to the person behind it, then learns how the standard turns that chase into structured statements. The company network in this essay is fictional and the data line is a drawing device, not a feature of the standard. The standard facts below are drawn from the published BODS documentation.

What is reported
  • BODS expresses ownership and control as three statement types: entity, person and relationship statements, not rows in a table. A dataset is an array of statements.
  • A relationship names a subject and an interestedParty, then lists interests; each interest carries its own directOrIndirect and beneficialOwnershipOrControl flag, with share modelled as an object (exact, minimum, maximum).
  • A statementId identifies each claim; a recordId identifies the entity, person or relationship the claim is about. Statements are append-only: corrections are new statements (recordStatus new → updated → closed) that amend or confirm older ones, never edits in place.
The same chase, on a record you can open
  • The walkthrough above is a teaching illustration. This is the real thing. VÁHOSTAV, a.s. (Slovakia, IČO 31356648) is registered in the Register of Public Sector Partners, the register a company must enter before it can take public money. Its entry is public and free to open: rpvs.gov.sk entry 9678, registered 1 February 2017. The company traded as VÁHOSTAV - SK, a.s. until 1 July 2024.
  • Open it and the register does what a certificate cannot: it names three natural persons as beneficial owners, and it names the regulated authorised person who filed and vouched for that claim, with the date they last verified it. A name, a person, and someone answerable for the statement.
  • What the live record does not show you. Before the register existed, this company's ownership ran through New Zealand and Cyprus shells and private persons in Costa Rica; the register's arrival is what forced a named owner into public view, and Váhostav was one of only two companies ever fined under the first version of it. None of that is on the page today. The record resolves cleanly and still does not tell you what happened. Evidence state: the current register entry is Observed (retrieved 25 July 2026). The pre-2017 offshore chain is Cited, from Transparency International Slovakia (2017) and Open Ownership (2020); the original register entry that captured it no longer exists online, and the Costa Rica leg rests on secondary reporting, not a primary registry document.
Standards & companion
  • Beneficial Ownership Data Standard (BODS v0.4), published by Open Ownership. It is the schema this essay teaches.
  • BODS is built to be linkable, dated and testable, so a published company name can be connected to a person record.
  • Companion essay: The Black Light for Public Money shows the use case: joining OC4IDS procurement data (the Open Contracting for Infrastructure Data Standard) to ownership data via a shared identifier. This essay teaches the ownership data model itself; that essay applies it.
What is editorial
  • The data line: one bright strand that changes meaning at each stage: certificate underline, ownership trail, graph edge, ledger spine, query path. A metaphor for traceability, not a BODS field.
  • The company network is entirely fictional: Mirembe Infrastructure Ltd, Lakefront Holdings Ltd, Blue Gate Nominees Ltd, Riverbank Works Ltd and Amina K. Any resemblance to real companies or people is coincidental. The award-committee conflict and the dissolve-and-re-form ("phoenix") sequence are illustrative stakes to show why following the line matters; they are not a real case, and a repeated pattern behind one person is a flag to investigate, never a finding of wrongdoing.
  • The "SHAREHOLDER FOUND / NOT HUMAN" stamp and the query console are illustrations of the argument, not screenshots of a live tool. Field names follow BODS v0.4 (for example source.type uses the codelist value selfDeclaration; "no disclosable owners" is a relationship whose interestedParty.reason is noBeneficialOwners).
  • A red (broken) line appears only where the honest answer is missing, unknown or not disclosed, to show the model records absence rather than hiding it.

The honest claim, stated plainly: BODS makes ownership claims linkable, dated and testable. It does not, by itself, reveal the truth. A statement is a claim from a source as of a date. Its value is that you can trace it, challenge it, and check whether it changed. The standard structures accountability; it does not adjudicate it.

Bring me the system

If this essay names a decision you own, send a qualified brief: what is blocked, what outcome you need, and when.

Open a qualified brief →

A visual essay by Michael Cengkuru · cengkuru.com
The company network is fictional; standard facts verified against the published Beneficial Ownership Data Standard (v0.4) documentation, June 2026.
Built as a self-contained page: no framework, no tracking, no third-party scripts.
Download the plain version (Markdown)

← All essays