> 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-iii-customer-due-diligence-art.-19-50/42.md).

# Art. 42 — Specific provisions regarding politically exposed persons

AMLR Article 42 — Specific provisions regarding politically exposed persons. Regulation (EU) 2024/1624, Chapter III — Customer due diligence.

1. In addition to the customer due diligence measures laid down in [Article 20](/amlr/chapter-iii-customer-due-diligence-art.-19-50/20.md), obliged entities shall apply the following measures with respect to occasional transactions or business relationships with politically exposed persons:
   1. obtain senior management approval for carrying out occasional transactions or for establishing or continuing business relationships with politically exposed persons;
   2. take adequate measures to establish the source of wealth and source of funds that are involved in business relationships or occasional transactions with politically exposed persons;
   3. conduct enhanced, ongoing monitoring of those business relationships.
2. By 10 July 2027, AMLA shall issue guidelines on the following matters:
   1. the criteria for the identification of persons known to be close associates;
   2. the level of risk associated with a particular category of politically exposed person, family member or person known to be a close associate, including guidance on how such risks are to be assessed where the person is no longer entrusted with a prominent public function for the purposes of [Article 45](/amlr/chapter-iii-customer-due-diligence-art.-19-50/45.md).


---

# 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-iii-customer-due-diligence-art.-19-50/42.md?ask=<question>&goal=<endgoal>
```

`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.
