Skip to main content
When transactions are flagged by rules, Didit creates alerts that can be organized into cases for structured investigation. Cases group related alerts and transactions, track investigation progress, and maintain an audit trail.
Case management is console-only. There is no public alert- or case-CRUD API. Analysts triage, assign, and resolve cases from Case Management in the Business Console. See alerts for the alert lifecycle in detail.

Case types

Each case is categorised by the type of investigation:
TypeDescription
TRANSACTION_MONITORINGInvestigation triggered by transaction rule matches or alerts
AMLAML-specific investigation (sanctions hits, watchlist matches)
BUSINESS_REVIEWReview of a business entity’s verification or activity
VERIFICATION_REVIEWReview of a user verification session
DUPLICATESInvestigation of potential duplicate entities or sessions
GENERALGeneral-purpose case for any compliance matter

Alerts

Every time a rule matches a transaction, an alert is created. Alerts can also be created manually by analysts or by external providers.

Alert sources

SourceDescription
RuleAutomatically created when a transaction rule matches
ProviderCreated by an external AML or blockchain analytics provider
ManualCreated manually by an analyst from the console

Alert statuses

StatusDescription
OPENNew alert, not yet reviewed
INVESTIGATINGAn analyst is actively working on this alert
AWAITING_USERAdditional information is needed from the user
PENDING_SARUnder review for a Suspicious Activity Report filing
SAR_FILEDA Suspicious Activity Report has been filed
RESOLVEDInvestigation complete — no further action needed
DISMISSEDAlert reviewed and determined to be a false positive

Cases

A case is an investigation container that links together related alerts and transactions for a structured review workflow.

Case workflow

Triage

Review incoming alerts in the Transactions section of the console. Group related alerts into a new case or add them to an existing case.

Assign

Assign the case to an analyst for investigation. Track assignment and response times for SLA monitoring.

Investigate

Analysts review the linked transactions, user verification history, AML screening results, and any attached evidence. Add internal notes and document findings.

Resolve

Close the case with a resolution — escalate to SAR filing, dismiss as false positive, or take action (e.g., block the user, decline future transactions). The resolution is logged in the audit trail.

Creating a case

Cases are created from the Business Console:
  1. Navigate to Transactions and select one or more flagged transactions
  2. Click Create Case and provide a title and description
  3. Set the severity and priority
  4. Link the relevant alerts and transactions
  5. Assign to an analyst

Case properties

PropertyDescription
TitleShort description of the investigation
Case typeType of investigation (see case types above)
SeverityLOW, MEDIUM, HIGH, CRITICAL
PriorityLOW, NORMAL, URGENT
StatusOPEN, UNDER_REVIEW, AWAITING_USER, ON_HOLD, RESOLVED
Assigned toAnalyst responsible for the investigation
Linked alertsAlerts included in the case
Linked transactionsTransactions associated with the investigation
EvidenceDocuments, screenshots, or files attached to the case
TypologiesSAR typology codes relevant to the investigation
Due dateDeadline for completing the investigation
NotesInternal comments and findings from the investigation

Resolution

When a case is resolved, the analyst selects a resolution type:
ResolutionDescription
FALSE_POSITIVEInvestigation determined the activity was legitimate
VALID_THREATConfirmed suspicious or fraudulent activity
APPROVEDActivity reviewed and cleared for processing
DECLINEDActivity rejected after investigation
OTHERCustom resolution with analyst notes
The resolution, along with any closing notes, is immutable once set and forms part of the compliance audit trail.

Transaction notes

Analysts can add notes to individual transactions at any time. Notes include:
  • The note text
  • The analyst who wrote it (name and email)
  • Timestamp
  • Optional metadata
Notes are visible to all team members with transaction access and form part of the audit trail.

Analytics

The Transactions overview in the console tracks analyst performance including:
  • Average alert resolution time
  • Alerts resolved per analyst
  • Alert-to-case conversion rate
  • Open alert backlog by status

Next steps

Alerts

Alert lifecycle, sources, and SAR workflow.

Console

Full console walkthrough.

Statuses

All status machines.