Kyclara

Beneficial ownership: documenting the reconstruction in a client file

· Redazione Kyclara

Draft date: 8 November 2026. Author: Kyclara Editorial Team.

Documenting beneficial ownership requires more than entering a name in a questionnaire. The file should make it possible to follow the path connecting the client with the identified individual, showing the documents used and points requiring clarification. Client statements are one input to assess alongside other relevant information under the applicable framework.

This guide concerns the organisation of evidence. It does not provide a formula for identifying beneficial owners in every structure or describe access to registers subject to particular conditions. Legal criteria differ according to the entity type and require examination of current legislation. Numerical thresholds are not addressed here, to avoid reducing a broader assessment to a percentage.

Identify the client and the reconstruction date

Start with the subject entering the relationship. A trading name may differ from the actual legal entity. Record the relevant identifier and country, then state the date to which the reconstructed structure relates. An organisation chart from the previous year may be a useful starting point, but does not alone demonstrate the current position.

Distinguish the client from its representative and the entities in the ownership chain. A legal representative does not automatically become the beneficial owner by signing the questionnaire. If the identification process leads to someone exercising management powers, the reasons should explain the criterion applied rather than conflating roles that may coincide only in particular circumstances.

Map the chain without skipping stages

For a structure involving intermediate companies, show the connections requiring assessment. Each stage should have a documentary reference or be flagged as unresolved. If an interest is described only in a statement, identify that origin: do not present it as verified through a registry when that check was not performed.

A diagram helps when it makes relationships understandable to a reviewer, but should not replace documentation. Keep referenced documents in a repository accessible to assigned staff. When a connection changes, update the diagram and explain the change date, avoiding parallel versions that both appear current. The diagram and its references should be reviewed together so a revised image does not continue pointing to superseded evidence.

Record the question each document answers

A document may establish that a company exists without describing who controls it. Another may describe shareholders at a particular date without covering arrangements or powers relevant to the individual case. Link each source to the point it supports. Accumulating registry extracts does not automatically reconstruct a complex chain.

For overseas documents, assess readability and understanding. Where translation is needed, identify the text used and who checked the meaning of relevant passages. Do not give an informal translation the status of an attestation it does not possess. Uncertainty about a company category should remain open until a competent review resolves it.

Treat differences as questions to resolve

Where a statement and a documentary source differ, describe the precise point: person identified, date, role or corporate connection. A discrepancy may arise from a change after the document's date, an error or another cause. None of those explanations should be assumed without checking. Request the additional information needed to assess the difference.

Institutional beneficial ownership FAQs explain that the register supports rather than replaces customer due diligence. Availability and access conditions must be checked at the time of use. This guide should not be turned into a promise that every item can freely be obtained through a single portal. Equally, an inaccessible source should be recorded as a limitation rather than described as having confirmed the client's statement.

A fictional example with an intermediate company

The imaginary client “Faro Componenti” declares an individual as its beneficial owner. The attached document, however, shows part of the interest held by “Ponte Holding”, a company in another country. The reviewer does not yet know how that stage affects identification and cannot regard it as resolved simply because the final name was signed.

The operator opens a focused request concerning the relevant relationships and links the new documents to the chain. The competent function applies the appropriate criteria and records its reasoning, distinguishing verified connections from declared ones. This example gives no legal solution and does not claim a particular percentage determines the result: it illustrates how to keep the reasoning readable.

Close with reasons that can be reconstructed

The closing note should explain the criterion used, relevant sources and assessment date. If some information prevents completion, apply the appropriate rules and procedure. Do not describe the file as complete merely because every portal box has been filled in. A documented open issue is more informative to the next reviewer than an unexplained approval status.

Arrange review when relevant information arrives or the client's structure changes. Preserve continuity between the old and new reconstruction under applicable rules. A later reviewer should understand which stage changed without starting again from a folder of unreferenced documents. This also helps identify whether an earlier conclusion remains relevant or depends on information no longer current.

Sources and limitations

The beneficial ownership FAQs published by the Bank of Italy, developed with the Ministry of Economy and Finance and UIF, are the institutional source used for the relationship between the register and due diligence. The customer due diligence provisions should be consulted for their respective addressees alongside the current framework. No register access rule is inferred here from earlier practice.

To compare this method with a file connecting statements, documents and the operator's reasons, you can view Kyclara.