> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.idenfy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# AML Monitoring
> Set up and manage continuous AML monitoring with daily sanctions, PEP, and adverse media screening for individuals and companies in the iDenfy dashboard.
## Monitoring vs. Single Check
AML Monitoring performs a **recurring daily check** on a subject — scanning them against PEP, Sanctions, and Adverse Media databases every 24 hours for as long as monitoring is active. A single AML check runs once and returns results immediately.
You can also start monitoring directly from any completed AML check result (within an ID verification or a standalone AML check) by clicking **Add Monitoring** at the bottom of the finding.
***
## Creating AML Monitoring
There are two ways to start monitoring a subject.
### From the AML Monitoring List
Navigate to **AML Verifications** → **AML Monitoring** and click **New Monitoring** in the top right corner.
A pop-up window will appear. Fill in the subject's details:
### From a Verification Window
Open any ID verification, then click **View AML** in the toolbar at the bottom of the page. A dropdown appears with two options:
* **Add to monitoring** — opens the monitoring creation pop-up pre-filled with the subject's details from the verification
* **Check AML** — runs a one-time AML check instead
Using **Add to monitoring** from a verification is the fastest way to enrol a verified subject — their name, nationality, and date of birth are carried over automatically.
### Fields
| Field | Required | Description |
| ----------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Type** | Yes | `Person` or `Company` |
| **Full name / Company name** | Yes | For persons, enter the full name as a single combined field |
| **Date of birth** | No | Persons only. Improves match accuracy by narrowing results to the correct age range |
| **Nationality / Country** | No | Improves screening accuracy by filtering results to the relevant jurisdiction |
| **Gender** | No | Persons only. `Male`, `Female`, or `Other` |
| **AML Tags** | No | Up to 5 custom tags (max 100 characters each) for filtering and organising the monitoring list. Configured in [AML Settings](/guides/dashboard/settings/anti-money-laundering-aml#aml-monitoring-tags) |
| **Auto monitoring extension** | No | Extends the 365-day monitoring period automatically each year. Enabled by default — each renewal costs one credit |
All monitoring entries use the AML matching thresholds, filters, and dataset configuration set in your [AML Settings](/guides/dashboard/settings/anti-money-laundering-aml). These cannot be adjusted per-entry at creation time.
Adverse Media monitoring cannot be enabled on its own — it requires PEP & Sanctions screening to be active on your contract.
***
## Filtering the Monitoring List
The monitoring list has two tabs — **Person** and **Company** — to switch between individual and business records. If a subject is not visible, confirm you are on the correct tab.
Use the **sort dropdown** to order results:
| Option | Description |
| ---------------------------------------- | ----------------------------------------------- |
| Check date newest / oldest | Order by when the monitoring record was created |
| AML check date newest / oldest | Order by the last PEP & Sanctions screening run |
| Adverse media check date newest / oldest | Order by the last adverse media screening run |
***
## Monitoring Results
Opening a monitoring record shows three sections: the search parameters the record was created with, the current monitoring status, and all matched profiles (findings).
### Search Parameters
Displays the subject details and screening configuration used for this monitoring record. The top row shows:
* **Full name** — the monitored subject's name
* **Address or nationality** — country code used in screening
* **Date of birth** — if provided at creation
Expand the row to see the full configuration:
| Field | Description |
| ---------------------- | ------------------------------------------------- |
| **Matching threshold** | Minimum similarity score used (e.g. 95%) |
| **Birth year range** | DOB range applied to narrow results |
| **PEP tier** | Which PEP tiers were included (Tier 1, 2, 3) |
| **PEP status** | PEP CURRENT, PEP FORMER, PEP LINKED |
| **Sanctions status** | SAN CURRENT, SAN FORMER |
| **Datasets** | Screening databases included (e.g. PEP, SAN, RRE) |
| **Sanction databases** | Any sanction lists excluded from screening |
***
### Monitoring Status
Summarises the current state of the monitoring record:
| Column | Description |
| ------------------- | ----------------------------------------------------------------------------------------------- |
| **Review status** | `Flags found` if at least one unresolved match exists; `Clear` otherwise |
| **Monitoring ID** | Unique identifier for this monitoring record |
| **Client ID** | Your internal reference, set at creation |
| **Status set by** | The user who last changed the status |
| **Status set at** | When the status was last changed |
| **Comment** | Optional review note |
| **AML tags** | Tags assigned to this record for filtering |
| **Check date** | The date of the most recent update to the finding (e.g., new evidence or changes to sanctions). |
| **Expiration date** | When monitoring expires (365 days from creation unless auto-renewed) |
***
### Found Matches
Each matched profile row shows the following columns:
| Column | Description |
| -------------------------- | -------------------------------------------------------------------------- |
| **Full name** | Matched entity's name, with alias match shown as a badge if applicable |
| **Date of birth** | Matched entity's date of birth |
| **Address or nationality** | Country associated with the matched profile |
| **Datasets** | Which screening databases flagged this profile (e.g. `SAN CURRENT`, `POI`) |
| **Match score** | Confidence score (0–100) for the name match |
| **Status** | Set to **True positive** or **False positive** to review the finding |
| **Comment** | Add an internal note to the finding |
| **Delete** | Permanently hide the profile from this monitoring record (see below) |
Each monitoring entry displays up to 30 findings.
Clicking a matched profile row opens the full profile viewer. See [AML Profiles](/guides/dashboard/aml/aml-profiles) for a description of all tabs and fields.
### Reviewing and Resolving Findings
**True positive** — confirms the finding as a genuine match. The monitoring record stays in Alert until all findings are resolved.
**False positive** — marks the finding as not relevant to the monitored subject. The finding is hidden from view. However, if the screening provider updates the underlying record (detectable by a changed update date), the profile may reappear on the next daily check — marking as False Positive is not permanent suppression.
**Delete (trash icon)** — permanently removes the profile from this monitoring record. The profile ID is added to the record's hidden list and filtered out on every subsequent daily check, even if the screening provider updates the record. Use this when the profile is definitively not the monitored subject.
If you added a subject to monitoring from an AML check, any findings you already resolved in that check are carried over automatically. Only new findings detected after monitoring started require review.
Resolving findings does **not** automatically change the monitoring status from Alert to Active. After dismissing false positives, a manager must manually click **Start** on the monitoring record to re-evaluate the remaining findings and restore Active status.
### Other Actions
**Page header:**
* **Delete results** — removes all current findings from this monitoring record (the monitoring record itself remains active and continues daily screening)
* **Download PDF** — exports the full monitoring record as a PDF for audit and compliance purposes
**Bottom toolbar:**
* **Auto renewal** — toggles automatic extension of the monitoring period each year; each renewal consumes one credit
* **Logs** — shows a full audit trail of status changes and screening events for this record
* **History** — previous screening runs and rechecks
* **Comments** — internal notes left by managers on this record
* **Recheck** — manually triggers a new screening run outside the daily cycle; consumes one credit
* **Update monitoring** — saves any pending changes to the record (active when edits are unsaved)
* **Stop monitoring** — disables further checks for this subject; can be restarted at any time