Related party transactions are a governance risk that official sources can partially illuminate. The question is not whether a transaction occurred — it is whether the parties on both sides of it share a common controller, and whether that relationship was disclosed in any filed document. This report maps what the sources show, in what order, and where the chain stops.
The angle here is governance: who controls the counterparty, what the shareholder can enforce, and what the filed record confirms or contradicts. Control is the operative question. Ownership structure, director appointments, and filed financial statements are the instruments.
What the report establishesCommon controllers across counterparty and target; director overlaps; transactions disclosed in filed financial statements. Sources: corporate registries, filed accounts, insolvency registers — verified September 2026. What the sources do not showUndisclosed side agreements, informal control arrangements, and transactions routed through jurisdictions with no public filing requirement. These gaps are named before payment. Price tiersSignal €1,350 · Standard €2,850 · Extended €6,300. Scope defined per tier below. Condition of accessNo single international register covers related party relationships. Each jurisdiction is queried separately; access conditions vary by registry and are described in the report brief.A related party relationship leaves a trace in official sources only when it was required to be disclosed. The disclosure requirement depends on jurisdiction, entity type, and transaction size. Three categories of trace exist.
Director overlap. A person serving as director of both the target and the counterparty appears in corporate registry filings in most jurisdictions. The overlap is verifiable where both registries are accessible and where director data is filed in a structured or searchable form.
Shareholder commonality. A shared ultimate owner appears in the record only where beneficial ownership disclosure is mandatory and the register is accessible. In EU jurisdictions, access to UBO registers has been restricted following CJEU judgment C-37/20. In the United Kingdom, the Persons with Significant Control register remains publicly accessible. In the United States, FinCEN's beneficial ownership database is not publicly accessible. The report identifies, per jurisdiction, what level of ownership data is available and from which source.
Transaction disclosure in filed accounts. Where a company is required to file financial statements, related party transactions above a materiality threshold must be disclosed in the notes. The disclosure names the counterparty and the transaction amount. This is the most direct documentary trace — and the most dependent on the quality of the filing.
| Trace type | Source | Accessible without registration | Structured data |
|---|---|---|---|
| Director overlap | Corporate registry | Varies by jurisdiction | Varies |
| Shareholder commonality | UBO / PSC register | Restricted in EU post C-37/20; open in UK | Partial |
| Transaction disclosure | Filed financial statements | Varies by jurisdiction | No — narrative text |
| Insolvency proceedings | Insolvency register | Varies | Partial |
The report follows a fixed sequence. Each step produces a documented finding or a documented gap. Neither is suppressed.
Step 1 — Entity identification. The counterparty is identified in the relevant corporate registry by legal name, registration number, and registered address. Where the entity operates under a trade name, the legal entity behind it is established first.
Step 2 — Director and officer mapping. Current and historical directors are extracted from the registry. The same names are cross-referenced against the target's director record. Overlaps are flagged with the dates of concurrent appointment.
Step 3 — Ownership layer. The ownership structure of the counterparty is traced to the level the available sources permit. Where a UBO register is accessible, it is queried. Where it is not, the corporate registry's shareholder list is used. The report states explicitly at which level the chain stops and why.
Step 4 — Filed financial statements. Where the counterparty is required to file accounts, the most recent available filing is reviewed for related party transaction disclosures. The report records what was disclosed, the period covered, and the filing date.
Step 5 — Insolvency and enforcement check. The counterparty is checked against the relevant insolvency register and, where accessible, enforcement databases. A negative result is recorded with the caveat that filed applications may not yet appear in the register.
Step 6 — Cross-reference against the target. Findings from steps 1–5 are compared against the equivalent record for the target. Discrepancies between what the counterparty disclosed and what the target's record shows are identified as a separate finding.
The shareholder's enforcement position depends on what the corporate law of the relevant jurisdiction requires the company to disclose, and to whom. This report does not provide legal advice on enforcement rights. It establishes the factual predicate: what was filed, what was required to be filed, and what the gap between the two looks like in the documentary record.
Where filed accounts disclose a related party transaction, the report extracts the disclosure verbatim and records the filing date. Where accounts were required but not filed, that fact is recorded. Where the jurisdiction does not require filing of accounts at all, that is stated as a structural limit of the source, not a finding about the company.
The distinction matters for a buyer or shareholder assessing whether a transaction was concealed or merely not required to be disclosed. Both outcomes appear in the record differently. The report does not characterise which applies — that is a legal question outside the scope of a factual compilation.
Official sources establish what was filed. They do not establish what occurred.
A related party transaction that was not required to be disclosed will not appear in any registry. A transaction disclosed in filed accounts may be described in terms that do not identify the counterparty by name. A director overlap that existed before the current filing period may not appear in the current record if historical data is not retained by the registry.
Specific limits that apply across jurisdictions covered in this report:
The ceiling of what the sources allow is stated before payment. Where a specific limit applies to the counterparty or jurisdiction in scope, it is identified in the report brief before the engagement is confirmed.
Discrepancies between sources are a finding in their own right. Three patterns recur in related party transaction reports.
Registry versus filed accounts. The corporate registry shows a director who is not named in the related party disclosures of the filed accounts. This may indicate that the director's role in the transaction was not considered material, or that the disclosure was incomplete. The report records both the registry entry and the accounts entry without resolving the discrepancy.
UBO register versus shareholder list. The beneficial ownership register names a different ultimate owner than the shareholder list in the corporate registry. This may reflect a timing difference between filings, or a structural difference in how the two registers define control. The report records both entries with their respective filing dates.
Counterparty filing versus target filing. The counterparty's accounts disclose a transaction with a related party that matches the target's description, but the target's accounts contain no corresponding disclosure. The report records the asymmetry and identifies the filing periods involved.
| Tier | Price | What is included | What is NOT included |
|---|---|---|---|
| Signal | €1,350 | Entity identification; director and officer mapping; ownership layer to the level sources permit; insolvency check; written summary of findings and gaps | Filed financial statement review; cross-reference against target record; discrepancy analysis |
| Standard | €2,850 | All Signal scope; filed financial statement review for the most recent available period; cross-reference against target record; discrepancy analysis; source extracts | Historical financial statement review beyond the most recent period; jurisdictions beyond the primary registration jurisdiction |
| Extended | €6,300 | All Standard scope; historical financial statement review across available periods; multi-jurisdiction coverage where the counterparty operates through subsidiaries or related entities; full discrepancy matrix across all sources | Verification of facts not appearing in any official source; legal advice on enforcement rights or transaction validity |
What triggers the need for this report? A transaction between the target company and a counterparty where a common controller is suspected but not confirmed. The report establishes what the official record shows about the relationship between the two entities before the transaction is completed or challenged.
Can the report confirm that a transaction was a related party transaction? The report establishes what the sources show: director overlaps, shared ownership to the level the sources permit, and disclosures in filed accounts. Whether those facts constitute a related party transaction in the legal sense of a given jurisdiction is a legal question outside the scope of a factual compilation.
What if the counterparty is registered in a jurisdiction with no public filing requirement? That structural limit is identified before the engagement is confirmed. The report records what is available — typically entity identification and, where accessible, director data — and states explicitly what cannot be established from public sources.
How current is the data? Each source is queried at the time of the report. Filing dates are recorded for every extracted document. Where a registry does not show a filing date, the query date is recorded instead.
What is the difference between Signal and Standard? Signal establishes the structural picture: who the counterparty is, who controls it, and whether it is solvent. Standard adds the transactional layer: what the counterparty disclosed in its filed accounts, and whether that matches the target's record.
How long does the report take? Turnaround depends on the number of jurisdictions in scope and the accessibility of the relevant registries. The brief provided before engagement confirms the expected timeframe for the specific counterparty and jurisdiction.
Sources
Corporate registry data, filed financial statements, and insolvency register entries are queried at the time of each report. No single international register covers related party relationships across jurisdictions. The following source categories are used depending on jurisdiction:
Registry names, URLs, and access conditions applicable to the specific counterparty and jurisdiction are identified in the report brief before engagement is confirmed.
Sources verified: September 2026.
Disclaimer: This report is a factual compilation from official registers and public sources. It is provided for informational purposes only, does not constitute legal advice, and contains no legal qualification of the facts established. VLO Law Firm assumes no liability for actions taken or not taken based on this material. For advice regarding your particular situation, please contact info@vlolawfirm.com.
Author: Elena Moretti — Partner, Continental Europe, VLO Law Firm