Skip to main content
Case Management is the investigation hub of the Didit Console. Every AML hit, flagged verification, or suspicious transaction can become a case your compliance team works from open to resolution, with a full audit trail.

Lifecycle

A case moves through exactly three statuses: Resolving a case requires a resolution: Every case also carries a priority (Low, Medium, High, default Medium) and an optional due date that drives SLA sorting and overdue flags.
There is no Under review, On hold, Pending approval, Critical severity, or case type axis. The lifecycle is deliberately fixed to keep analytics, SLAs, and permissions unambiguous across every case, regardless of how it was created.

One subject per case

Every case is anchored to exactly one user or one business. You cannot mix subjects on a single case, and you cannot attach a session, business session, or transaction that belongs to a different subject than the case, doing so returns a clear error. This keeps every case page focused: the subject card, risk overview, documents, and financial data all describe the same person or business the case investigates. To review a second entity, open (or create) a separate case.

Lists

Case Management has status tabs: Open, Awaiting user, Resolved, and All. Search matches subject name or ID, tag, case number, case title, linked session ID, and linked transaction ID, so you can paste in a session or transaction UUID and land directly on its case. Filter chips: Blueprint, Created, Source, Assignee, Tag, plus Add filter for Priority and Due. Columns: Created (date and creator), Case details (title), Status, Blueprint, Subject (name and ID), Subject tags, Assignee, Priority, and Due date, with more available behind horizontal scroll and column configuration.

Sort and SLA

Sort by Created at (default) or Due date. Sorting by due date surfaces overdue cases first; a case is overdue once its due date has passed while it is still Open or Awaiting user, shown with a red due chip.

Saved views

Save the current combination of filters and columns as a named view with Save view, switch between views with Select a view, and reset with Clear filters. Views are personal and persist the same way other console table preferences do.

Bulk actions

Select multiple cases to:
  • Assign to an officer. All selected cases must share the same blueprint, the console warns before submitting if they do not.
  • Set status to Awaiting user, Reopen, or Resolve (with a resolution and optional note). Each case is evaluated independently, so a case blocked by an incomplete checklist or a missing required note is reported individually without failing the rest of the batch.

Exports

The list menu offers two CSV exports, delivered through the Reports page:
  • All cases report, one row per case with status, resolution, priority, tags, linked transactions, and the last FIU report filed.
  • SLA report, per-case timing metrics: hours to assignment, hours to resolution, overdue, and SLA-met flags.

Tags

Add tags to a case from its header (Add tag) to group related investigations, or filter and search by tag from the list. Tag changes are recorded on the case timeline.

Creating cases

Every entry point: users, businesses, sessions, transactions, and automatic connectors.

Blueprints

Configure assignment, escalation, transfer, and the case page content.

Checklist

Gate resolution on required investigation steps.

4-eyes review

Maker/checker approval for sensitive resolutions.