# The Black Light for Public Money: The Contract Names the Company, Not the Person Who Controls It

A public contract names the company that won it and can still hide the person who controls it; the one move that connects the two is matching a shared organization identifier, not matching company names.

By Michael Cengkuru · June 2026 · Interactive version: https://cengkuru.com/essays/black-light/

## The story

Slovakia learned this the hard way. Vahostav-SK, the country's largest construction firm, had won several large state highway contracts. In 2015 it went bankrupt, leaving hundreds of subcontractors largely unpaid. Its ownership structure traced through New Zealand, then Cyprus, then Costa Rica, ending in private persons abroad. The public record had named the company on the contract and hidden the people behind it. The scandal pushed Slovakia to build a Register of Public Sector Partners: companies seeking public contracts now have to disclose their beneficial owners before public money moves.

That case is real. To show how the fix works mechanically, the essay then walks through a simplified case it labels a composite example: a city spends fifty million dollars on a new hospital wing. The procurement record names the buyer, a City Health Authority, and the supplier, Acme Infrastructure Ltd, with a value of $50,000,000 awarded in 2025 (composite example). Anyone can look up the winning supplier's exact name. That is not the same as knowing who profits.

The project record itself is not thin. OC4IDS, the Open Contracting for Infrastructure Data Standard, tracks the whole life of an infrastructure project: identification, preparation, tender, award, implementation, completion, maintenance, and decommissioning, with sustainability, climate-finance, and value-for-money modules. Think of it as the project's receipt book. It can even carry beneficial owners, in a beneficialOwners field on each party. But that field is only as good as what was collected, and in most disclosures it sits empty. The public trail stops at the supplier company.

A company cannot get rich. Only the people who own it can. The fifty million went to Acme, but a company is just a vessel: the money makes someone richer, a human being or several who own or control it, often sitting behind holding companies and trusts. That hidden set of real people is what beneficial ownership means: not who signed the contract, but who ultimately profits from it. Who they are lives in a different standard, BODS, the open standard for company-ownership registers: a family tree built from Entity, Person, and Relationship records.

The obvious way to connect the two records fails. Match the company by name and you hit the name trap: a city clerk types "Acme LLC," the ownership registry holds "ACME Limited," a third system says "A.C.M.E. Infra." One company, four spellings. Text matching produces false matches, missed matches, and duplicate entities. You never reliably reach the owner that way.

The move that works is matching a shared organization identifier instead. The LEI is the clean global example: a unique 20-character alphanumeric code for one legal entity, issued under GLEIF. The procurement record gives the supplier a scheme and an ID; the ownership record can carry the same official identifier on its entity. When both use the same scheme and the same ID, the join is a lookup, not a guess. Where no LEI exists, a national company-register identifier works the same way, as long as both datasets use it. The identifier shown in the essay, DEMO0000DEMO0000DEMO, is a placeholder, not a real LEI, so no real entity is attached to the composite chain.

The identifier does one precise thing: it proves the supplier on the receipt and the entity in the ownership data are the same organization. That opens the right tree. From there, BODS relationship statements do the climbing, rung by rung: the supplier at the base, a cross-border parent above it, a trust above that, and a controlling person at the top, each rung recorded as direct or indirect, with the share held.

Why this matters is the essay's ten-supplier table (composite example). A year of emergency procurement: thirty non-competitive contracts awarded fast to ten companies with different names and different addresses. Read the receipt book alone and it looks like a healthy, diverse market responding to a crisis. Run the identifier join across all ten and the family tree flags the same controlling person behind every one. Diverse on paper, one owner underneath.

Once the two books interoperate, this stops being a one-off expose and becomes a standing check. Three numbers, recomputed every month, describe a market's exposure: the share of contract value held by the top owner, the number of "competing" bids that resolve to common owners, and the share of value with no disclosed owner. The figures in the essay's market report (61 percent, 7 bids, 44 percent) are composite example numbers that show what the check would measure.

The honest claim, stated plainly: LEIs do not cover every supplier, registers go stale, and some ownership is hidden on purpose. Joined data surfaces risk patterns that merit investigation, patterns like common ownership, undisclosed conflicts, and concentration. It does not establish wrongdoing. A red owner node means "investigate here," never "guilty."

## The data

| Figure | Where it appears | Evidence state |
| --- | --- | --- |
| Vahostav-SK: Slovakia's largest construction firm, several state highway contracts, 2015 bankruptcy, hundreds of subcontractors largely unpaid | The real case beat | Real, cited (Open Ownership; Transparency International Slovakia; Open Government Partnership) |
| Ownership traced through New Zealand, Cyprus, and Costa Rica to private persons abroad | The real case beat | Real, cited (same sources) |
| Slovakia's Register of Public Sector Partners: disclosure of beneficial owners required before public contracts | The real case beat | Real, cited (same sources) |
| $50,000,000 hospital-wing contract: City Health Authority to Acme Infrastructure Ltd, awarded 2025 | The contract card | Composite example (labeled on the graphic) |
| 30 emergency contracts, 10 suppliers, 1 beneficial owner underneath | The ten-supplier table and the wheel | Composite example (labeled on the graphic) |
| 61% of contract value held by the top owner; 7 "competing" bids with common owners; 44% of value with no disclosed owner | The market exposure report | Composite example (labeled illustrative on the graphic) |
| LEI: a unique 20-character alphanumeric code for one legal entity | The identifier beat | Real (GLEIF) |
| DEMO0000DEMO0000DEMO | The identifier chip | Placeholder, not a real LEI |
| OC4IDS 0.9.5 field paths: project-level parties[] with an identifier object; suppliers via contractingProcesses[].summary.suppliers[]; beneficialOwners on each party | The project record beat and method note | Real, verified against documentation, June 2026 |
| BODS 0.4 structure: Entity, Person, and Relationship records; recordType and recordDetails; identifiers[] | The ownership tree beat and method note | Real, verified against documentation, June 2026 |

## Sources

- OC4IDS 0.9.5, Open Contracting for Infrastructure Data Standard: https://standard.open-contracting.org/infrastructure/latest/
- BODS 0.4, Beneficial Ownership Data Standard: https://standard.openownership.org/en/0.4.0/
- XI-LEI code list, org-id.guide: https://org-id.guide/list/XI-LEI
- LEI, Global Legal Entity Identifier Foundation (GLEIF): https://www.gleif.org/
- Open Ownership (named as a source for the Vahostav-SK / Slovakia case; no URL given in the essay)
- Transparency International Slovakia (named as a source for the Vahostav-SK / Slovakia case; no URL given in the essay)
- Open Government Partnership (named as a source for the Vahostav-SK / Slovakia case; no URL given in the essay)
- Register of Public Sector Partners, Slovakia (named in the essay; no URL given)
- Michael Cengkuru: https://cengkuru.com