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

# Compliance and Monitoring Tab

> Navigate the compliance and monitoring tab in iDenfy to review audit logs, AML statuses, blocklist matches, and monitoring subjects.

* [Comments & Audit Logs](#Compliance\&MonitoringTab-Comments\&AuditLogs)
* [ Compliance Information (AML)](#Compliance\&MonitoringTab-ComplianceInformation\(AML\))
* [Automation Statuses](#Compliance\&MonitoringTab-AutomationStatuses)
* [ Blocklist Statuses](#Compliance\&MonitoringTab-BlocklistStatuses)
* [ Monitoring Subjects](#Compliance\&MonitoringTab-MonitoringSubjects)
* [ Troubleshooting & Support](#Compliance\&MonitoringTab-Troubleshooting\&Support)

### Comments & Audit Logs

These two cards provide a chronological history of the case.

* **Comments:** An internal notebook for your team. Use this to leave notes about manual verifications or decisions.
* **Action:** Type in the text box at the bottom and click **Comment** to add a note.
* **Audit Logs:** A read-only system record that tracks every action, including automated system checks (e.g., "\[AUTOMATION] Done website audit") and user actions (e.g., "\[DemoUser] Added comment").

***

### Compliance Information (AML)

This section breaks down the screening results for every person and company involved (Directors, Shareholders, UBOs).

* **No flags:** The entity passed screening against sanctions and watchlists.
* **Flags found:** Potential matches were found (e.g., Adverse Media, PEPs).
* **Action:** Click **View AML** or **View Adverse media** next to a name to review and resolve the match.

***

### Automation Statuses

This card details the result of every automation rule configured for your workflow.

**Understanding Rule Statuses**

| Status              | Meaning                                                                                     |
| ------------------- | ------------------------------------------------------------------------------------------- |
| COMPLETED           | Rule ran successfully and returned a result.                                                |
| FAILED              | Rule encountered an error during execution.                                                 |
| SKIPPED             | Rule didn't apply (conditions not met).                                                     |
| BLOCKED             | A previous rule with a "BLOCK" action already denied the company, so this rule did not run. |
| INSUFFICIENT\_FUNDS | The partner account does not have enough credits to run this specific check.                |

Understanding Rule Actions

Each rule is configured with an "Action" that dictates what happens if the rule is triggered:

| Action      | Consequence                                                                       |
| ----------- | --------------------------------------------------------------------------------- |
| DO\_NOTHING | Informational only. The check runs, but the company is not flagged automatically. |
| FLAG        | The company is flagged for manual review.                                         |
| BLOCK       | The company is automatically denied.                                              |

***

### Blocklist Statuses

This section shows exactly which data fields were cross-referenced against your internal blocklists.

**Check Results**

| Status  | Meaning                                                                            |
| ------- | ---------------------------------------------------------------------------------- |
| CHECKED | The field contained data and was successfully validated against blocklist rules.   |
| SKIPPED | The field was empty or missing in the company profile, so it could not be checked. |

What gets checked?

The system attempts to screen the following data points if they are present:

* **Company Info:** Name, Registration Number, Country, City, Address, Postcode, Activity Code, Domain.
* **Applicant Info:** Name, Email, Phone, Personal Number, IP Address.
* **Persons (UBO/Rep):** Nationality, Country of Residence.

### Monitoring Subjects

Enroll specific entities into ongoing monitoring to detect future changes in their status (e.g., appearing on a sanctions list next month).

* **Add from the list:** Select entities already known in this application.
* **Create new:** Add a new entity manually.

***

### Troubleshooting & Support

Quick answers to common questions about this tab:

1. **Why are blocklist fields showing "SKIPPED"?** This means the company data is incomplete. If a field (like "Postcode") is empty in the application, the blocklist cannot check it.
2. **Why are multiple automation rules "BLOCKED"?** An earlier rule in your workflow (one with a **BLOCK** action) has already denied the company. To save resources, the system stops running subsequent rules.
3. **What does "INSUFFICIENT\_FUNDS" mean?** The automation failed because the account lacks the credits required for that specific third-party check. Credits must be topped up to run these rules.
4. **Why wasn't the company flagged even though the automation ran?** Check the rule's **Action** setting. If it is set to **DO\_NOTHING**, the rule will complete successfully without generating a flag, regardless of the finding.
