> For the complete documentation index, see [llms.txt](https://docs.trustform.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustform.io/guide/onboarding-and-reviewing/kyc-aml-checks/monitoring.md).

# Monitoring

## Overview

Monitoring automatically screens all client accounts marked as Active – including the applicant and all related entities. Once monitoring is enabled, Trustform continuously checks for new sanctions, PEP, or adverse media matches and instantly notifies you if anything changes.

{% hint style="info" %}
All detected matches appear in the Monitoring tab. If needed, you can also view linked context via the Associations tab.
{% endhint %}

## View Monitoring Results

{% stepper %}
{% step %}

#### Open the Monitoring tab

Go to **Monitoring** in the top navigation panel to access the list of all relevant persons and entities.\
The table shows the name, entity type, number of potential matches (hits), number of confirmed matches (true matches marked by the user), and the current screening status.

<figure><img src="/files/dyWItJW2iKMWFavwsjL9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Click the entity name to open its monitoring details

Here you can see:

* In the **Monitoring** tab, all detected matches and previous activity. You can set the match status and leave comments on each result.

<figure><img src="/files/id1IGVFWJOFj3UsfaaXL" alt=""><figcaption></figcaption></figure>

* In the **Associations** tab, all accounts in the system linked to this person or company. For example, if a match is found for a director, you will see which company and which client account they are associated with.

<figure><img src="/files/Ambvm4FZlQMPNTzrPAkD" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Open an individual match for full details

In the **Monitoring** tab, click a **specific matc**h to view detailed information.

<figure><img src="/files/yeQ9dSRamtz0QlUoHYvW" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Review the resolts&#x20;

Here you can see:

* **Key info** — provides general information about the match and the sanctions source data.
* **Adverse media** — shows results from open media sources, with direct links to the original articles.

Click **Download certificate** if you need to export a PDF file confirming the monitoring result.

<figure><img src="/files/QNE7AH7jqubbc8hQ6Vhb" alt=""><figcaption></figcaption></figure>

{% endstep %}
{% endstepper %}

## Overall status logic for searches

A single search may contain multiple results (hits), and each hit can have a different status. The **overall search status** is automatically determined based on the statuses of all hits according to the following logic:

* **No hits in the search** → *No potential match*
* **At least one hit with status "Potential"** → *Potential match*
* **No "Potential match", but at least one "True positive" (including Approve/Reject)** → *True positive*
* **All other cases** → *No match*

*Note: If a search has the status **Potential match**, it means that the search contains at least one result that has not yet been reviewed.*


---

# 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:

```
GET https://docs.trustform.io/guide/onboarding-and-reviewing/kyc-aml-checks/monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.