Skip to main content
When a transaction monitoring investigation concludes that activity must be reported to your Financial Intelligence Unit (FIU), you can generate the regulatory filing directly from the case — no manual re-typing of transaction data.

Report types

CodeReport
SARSuspicious Activity Report
STRSuspicious Transaction Report
CTRCash Transaction Report
TTRThreshold Transaction Report
UTRUnusual Transaction Report
IFTInternational Funds Transfer Report
CBRCross-Border Report
TFRTerrorism Financing Report
Every report is produced in two formats:
  • goAML XML — the UN-standard schema accepted by FIU portals in 50+ jurisdictions, ready to upload.
  • PDF — a Didit-styled report for your internal records, audits, and four-eyes review.

Generate a report from a case

  1. Open Case Management and select the investigation case.
  2. Go to the FIU Reports tab and click Generate report.
  3. Pick the report type and the FIU jurisdiction (2-letter country code).
  4. Didit auto-populates the draft from the case: the linked transactions, parties, amounts and currency, triggered rules and alerts, typologies, and a structured narrative.
  5. Review the draft, then click Validate fields — obligatory goAML fields (reporting entity ID, submission code, local currency, action taken, transactions, submission date) are checked before generation.
  6. Click Finalize report. The goAML XML and PDF are generated and stored on the case; download either one at any time.
The reporting entity ID is the identifier your organization received from the FIU when registering for goAML. Set it once per report — validation blocks finalization until it is present.

SAR narrative

For SAR/STR filings the PDF includes a narrative structured around the FinCEN “five Ws”: who is conducting the activity, what instruments are involved, when and where it took place, why it is suspicious, and how it occurred. Didit drafts each section from the case data; you can edit every field before finalizing.

Alert lifecycle

Finalizing a SAR, STR, or TFR automatically moves the case’s transaction alerts from Pending SAR to SAR filed, keeping the alert queue in sync with your filings.

Automatic drafts

Case blueprints support a Reporting toggle. When enabled, every case created from that blueprint starts with a pre-populated draft report of the configured type and jurisdiction — useful when a rule always escalates to a filing.

Case exports

From Case Management you can also queue two CSV reports (delivered through the Reports page):
  • All cases report — one row per case with status, resolution, priority, linked transactions, total amounts, and the last FIU report filed.
  • SLA report — per-case timing metrics: hours to assignment, hours to resolution, overdue and SLA-met flags.
Both exports respect the read:cases permission, cover up to 10,000 cases per file, and appear alongside your other exports in the Reports page.