The Open Contracting for Infrastructure Data Standard (OC4IDS, version 0.9, standard.open-contracting.org/infrastructure/) mandates beneficial ownership disclosure at the project level. Most implementations ignore this requirement for the first eighteen months. When investigators from civil society finally try to use the portal, they find that the company names are meaningless, they link to registered entities that share addresses, directors, and bank accounts. The beneficial ownership data that would expose these connections is absent. This article explains exactly how to capture beneficial ownership data at the source so investigators can use it from day one.

Why Beneficial Ownership Disclosure Fails at the Portal Level

Infrastructure portals typically collect beneficial ownership in the wrong place at the wrong time. Technical teams build a separate module that contractors must fill in after they win a contract. This approach fails for three reasons: contractors treat post-award disclosure as optional, the data is not linked to the procurement record, and the registry is never integrated with the OC4IDS project record.

Definition

Principles

openownership.org/principles/, published 2019 and updated 2021

The Open Ownership Principles (openownership.org/principles/, published 2019 and updated 2021) define beneficial ownership as information about the natural persons who ultimately own or control a legal entity. These principles, adopted by 53 countries as of Open Ownership's 2022 annual report (openownership.org/resources/), require that disclosure happen at the point of bidding, not after award. The Uganda PPDA portal (gpp.ppda.go.ug, operational since 2015) integrates beneficial ownership requirements directly into the procurement registration process. This single design decision makes every subsequent contract record auditable.

The Technical Architecture That Works

Three Components of Effective Beneficial Ownership Integration in OC4IDS
ComponentWhat It DoesImplementation Note
Point-of-registration captureCollects beneficial ownership when company registers, not after awardMandatory field in e-procurement registration form
OCDS linkage via Parties arrayOwnership data travels with procurement records automaticallyShared structure, no duplicate data entry
Registry cross-referenceValidates declared owners against national companies registerPhase 2 , Open Ownership Register API for cross-checking

Effective beneficial ownership integration in OC4IDS requires three connected components:

  • Point-of-registration capture: Beneficial ownership data is collected when the company registers in the e-procurement system, not when it wins a bid. The OC4IDS Parties array stores this data linked to each project record (see the reference implementation at standard.open-contracting.org/infrastructure/latest/en/guidance/).
  • OCDS linkage: The procurement phase uses OCDS (standard.open-contracting.org/latest/en/) to record tender and award data. When OCDS data feeds into OC4IDS, ownership data travels with it automatically using the shared Parties array structure.
  • Registry cross-reference: The portal links declared beneficial owners to the national companies registry. The Open Ownership Register (register.openownership.org, launched 2017) provides a public API (documented at register.openownership.org/api-docs) for cross-referencing declared ownership against verified registration data from 11 national registers.

What Investigators Need From the Data

Investigative journalists and parliamentary audit committees use beneficial ownership data to answer one question: did the same person profit from multiple contracts in the same project? The Kaduna State Infrastructure Data Portal (ipdata.kdsg.gov.ng, launched 2022), tracking 1,496 infrastructure projects in Kaduna State, Nigeria, demonstrates the investigative value. When project contracts are linked to beneficial owners in the OC4IDS framework, a single query reveals whether one ultimate owner controls multiple subcontractors on the same road construction project.

Definition

CoST

Construction Sector Transparency Initiative, infrastructuretransparency.org

CoST (Construction Sector Transparency Initiative, infrastructuretransparency.org) has documented this use case across its member countries. CoST's 2022 Annual Report (infrastructuretransparency.org/resources/) covers 21 member programmes and identifies beneficial ownership linkage as a critical transparency gap in portal assessments, flagged as absent in the majority of OC4IDS implementations assessed during CoST's independent Assurance Process that year. The CoST Assurance Process, independent verification of disclosed data by engineers and civil society (methodology first published 2012, updated 2019, see infrastructuretransparency.org/approach/), is the primary internationally recognised framework for evaluating infrastructure transparency portal effectiveness.

Counterargument

The Counterargument: Privacy and Complexity

Beneficial Ownership: Privacy Objection vs Established Precedent
ObjectionEstablished Counter-EvidenceSource
Publishing director names violates privacyApplies only to those competing for public funds, not general populationEU AML Directive 2018/843/EU
Public registers generate litigationNo significant privacy litigation reported post-implementationUK Companies House (public since 2016)
Registry integration is too complexSequenced approach: capture first, cross-reference in Phase 2Open Ownership Principles (openownership.org/principles/)
Low-capacity agencies cannot manage itMandatory form field requires no IT capacity beyond existing procurement systemUganda PPDA, integrated at registration

Critics raise two objections to mandatory beneficial ownership disclosure. First, that publishing personal information about company directors violates privacy regulations. Second, that the technical complexity of linking multiple registries is too high for low-capacity government agencies.

Definition

Kingdom

Companies House, find-and-update.company-information.service.gov.uk, mandatory since 2016 under the Small Business, Enterprise and Employment Act 2015

The privacy objection is answered by scope. OC4IDS beneficial ownership requirements apply only to natural persons who own shares in companies receiving public contracts. These individuals have chosen to compete for public funds; their ownership stake in the contracting entity is not private information in that context. The EU Anti-Money Laundering Directive (Directive 2018/843/EU) applies exactly this principle. Countries with public beneficial ownership registers, including the United Kingdom (Companies House, find-and-update.company-information.service.gov.uk, mandatory since 2016 under the Small Business, Enterprise and Employment Act 2015) and Ukraine (State Register, usr.minjust.gov.ua, public since 2015), have operated public beneficial ownership registers without successful legal challenges to the core disclosure requirement for individual company directors.

The complexity objection is answered by sequencing. You do not need a full registry integration on day one. Capture the beneficial ownership declaration in the procurement system as a mandatory field. Store it as a Party record in OC4IDS. Registry cross-referencing follows in a second phase. Incomplete data published today is far more useful than perfect data never published.

What to Do Next

If you are implementing an OC4IDS portal and have not yet addressed beneficial ownership, take these steps this week:

  • Add the mandatory field now. Modify your procurement registration form to require beneficial ownership declaration before any company can submit a bid. Map the declared data to the OC4IDS Parties array using the beneficialOwners field (see schema documentation at standard.open-contracting.org/infrastructure/latest/en/reference/schema/).
  • Publish raw declarations immediately. Do not wait for registry cross-referencing. Publish the declared beneficial ownership data in your OC4IDS output from day one. Imperfect transparency beats no transparency.
  • Plan the registry linkage. Contact your national companies registry and the Open Ownership team (openownership.org/contact) about API access for cross-referencing in the second phase. Open Ownership's Beneficial Ownership Data Standard (standard.openownership.org, version 0.3, 2021) provides the interoperability schema for this integration.

Beneficial ownership disclosure is the feature that turns an infrastructure portal into an anti-corruption tool. Without it, you publish procurement process data. With it, you publish accountability data, traceable from the initial budget allocation to the individuals who ultimately profited from it.

Playbook

Decision Table
OptionWhen to UseTradeoff
Adopt immediately Low-risk process and clear team ownership Fast progress, limited validation runway
Pilot first Uncertain data quality or mixed institutional capacity Slower scale-up, higher confidence
Defer pending controls Missing governance, QA, or monitoring guardrails Lower short-term output, better long-term durability
Execution Checklist
Failure Modes
  • Skipping the section "Why Beneficial Ownership Disclosure Fails at the Portal Level" during implementation.
  • Skipping the section "The Technical Architecture That Works" during implementation.
  • Skipping the section "What Investigators Need From the Data" during implementation.

Continue Reading

Designing a CoST Assurance Process That Produces Real Findings

Most CoST Assurance exercises produce compliance rates, not findings. This guide explains the design differences that determine whether an exercise identifies real discrepancies — including when physical site visits are essential and how to use a tiered verification approach.

Five Integration Patterns for OC4IDS Portals (and Their Failure Modes)

Connecting government source systems — IFMIS, e-procurement, project management databases — to an OC4IDS portal is what determines whether a transparency initiative survives. Five patterns emerge from real implementations, each with different trade-offs in complexity, maintenance risk, and data quality.

What 100,000 Contracts Taught Me About Procurement Transparency

After processing 100,000 procurement contracts in Uganda, I learned that disclosure isn't transparency. Here are the patterns the data revealed and what I'd build differently today.

Found this useful?

I write about open data systems, transparency, and implementation.

Read more articles →