> For the complete documentation index, see [llms.txt](https://docs.elkyc.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elkyc.com/home/build-verification-flows/verification-steps/aml.md).

# AML

The AML Step enhances security and compliance by monitoring user profiles for potential money laundering activities. Users have the option to enable or disable ongoing monitoring as needed.

* Add `AML check` step into the flow canvas at the appropriate position in the flow.
* Click on `AML check` to open its configuration options.
* Toggle on or off the `ongoing monitoring feature`.
* Set the periodicity for ongoing monitoring (e.g., daily, weekly, monthly).
* Take `data from questionnaire` - a checkbox that allows the system to reuse data collected earlier in the flow via a questionnaire. When selected, relevant user-provided data is automatically populated into this verification step.
* `Verification validity period` - defines how long the **verification result** remains valid after it has been successfully completed. Once the validity period expires, the user must complete the verification step again.

<figure><img src="https://1111746725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3YdYFOUPi8bWAiBfJgPb%2Fuploads%2FPPAohc4J7if2K0YuEgkm%2FScreenshot%202026-01-01%20at%2018.21.16.png?alt=media&amp;token=3989f7c4-d88f-4769-a2a0-49efecb762a3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The AML step operates seamlessly in the background without requiring any actions from the end user. It conducts ongoing monitoring autonomously to enhance security and compliance.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.elkyc.com/home/build-verification-flows/verification-steps/aml.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.