> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/amlr/chapter-iv-beneficial-ownership-transparency-art.-51-68/51.md). # Art. 51 — Identification of beneficial owners for legal entities AMLR Article 51 — Identification of beneficial owners for legal entities. Regulation (EU) 2024/1624, Chapter IV — Beneficial ownership transparency. Beneficial owners of legal entities shall be the natural persons who:Control via other means as referred to in the first paragraph, point (b), shall be identified independently of and in parallel to the existence of an ownership interest or control through ownership interest. > **(a)**have, directly or indirectly, an ownership interest in the corporate entity; or > > **(b)**control, directly or indirectly, the corporate or other legal entity, through ownership interest or via other means. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.mica.wtf/amlr/chapter-iv-beneficial-ownership-transparency-art.-51-68/51.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.