Skip to main content

​
Comments and 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”), user actions (e.g., “[DemoUser] Added comment”), and client actions taken through a request update link. Client actions include “Form re-submitted without changes” when the client submits the form without editing anything.

​
Editing and Deleting Comments

You can edit or delete comments you wrote, as long as you still have permission to add comments. Comments written by other team members can’t be changed.
  • An edited comment is marked (edited).
  • A deleted comment no longer appears anywhere: the comment list, the findings summary, the company details, PDF reports and exports.
  • Adding, editing and deleting a comment is recorded in the Audit Logs and included in the PDF report. Earlier versions of an edited comment are kept for audit purposes but are not shown in the dashboard.
Comments on AML findings, opened with View AML or View Adverse media, can’t be edited or deleted.

​
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 Understanding Rule Actions Each rule is configured with an “Action” that dictates what happens if the rule is triggered:

​
Blocklist Statuses

This section shows exactly which data fields were cross-referenced against your internal blocklists. Check Results 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 and 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.