> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# FIU Reports & Templates

> Generate SAR, STR, CTR, and other FIU regulatory filings from a case or from the standalone Reports page, using reusable per-jurisdiction templates.

When an investigation concludes that activity must be reported to your Financial Intelligence Unit, generate the filing directly from case data, or from the standalone Reports page.

***

## Report types

| Code  | Report                              |
| ----- | ----------------------------------- |
| `SAR` | Suspicious Activity Report          |
| `STR` | Suspicious Transaction Report       |
| `CTR` | Cash Transaction Report             |
| `TTR` | Threshold Transaction Report        |
| `UTR` | Unusual Transaction Report          |
| `IFT` | International Funds Transfer Report |
| `CBR` | Cross-Border Report                 |
| `TFR` | Terrorism Financing Report          |

Every report renders in two formats: **goAML XML**, the UN-standard schema your FIU portal accepts, and a **PDF** for internal records and 4-eyes review.

## Report templates

A report template captures the parts of a goAML header that stay constant across your filings for a given jurisdiction and report type, so you are not re-entering them on every report:

* **Reporting entity ID** (`rentity_id`) and branch, the identifier your organization received from the FIU
* **Submission code** (electronic or manual)
* **Local currency code**
* Which optional blocks to include (reporting person, location, reason, action) via `enabled_fields`

Build templates from the Reports pill's **Templates** tab, one per jurisdiction and report type. A template is only usable once it passes validation, missing obligatory goAML fields are listed and block both saving an invalid template and creating a report from it.

## Creating a report

### From a case

1. Open the case and go to its **FIU reports** tab, shown when the blueprint's Reporting section is enabled.
2. Click **Create report**, pick a template (or leave it blank and fill fields manually), and optionally choose which of the case's linked transactions to include.
3. Didit auto-populates the draft: reporting entity details from the template, the case's subject, linked transactions, and a structured narrative.
4. Review the draft, then **Validate** to check obligatory goAML fields before finalizing.
5. **Finalize**. The goAML XML and PDF are generated, uploaded, and appear on the case's report list with download links for both files.

### From the standalone Reports page

The **Reports** pill also has a **Create report** button that works app-wide: pick a **case** and a **template**, both required, then follow the same validate and finalize flow. Use this when you are working from a queue of pending filings rather than from inside a specific case.

## Report lifecycle

| Status      | Meaning                                                                         |
| ----------- | ------------------------------------------------------------------------------- |
| `Draft`     | Editable, not yet validated                                                     |
| `Validated` | Passed obligatory-field validation                                              |
| `Finalized` | XML and PDF generated and stored; the report can no longer be edited or deleted |

### SAR narrative

SAR, STR, and TFR reports include a narrative structured around the 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 case data; edit any section before finalizing.

### Alert lifecycle

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

## Print case (separate from FIU reports)

**Print case**, in the case page's overflow menu, produces a full-case PDF independent of any FIU filing: case summary, subject, checklist state, notes, attached sessions and transactions, the event timeline, and the list of FIU reports on the case. Use it for internal audits or handoffs that need the whole investigation in one document, not a regulator-facing filing.

## Case exports

From the Cases list, queue two CSV reports (delivered through the [Reports page](/console/export-pdf-csv)):

* **All cases report**, status, resolution, priority, linked transactions, and the last FIU report filed per case.
* **SLA report**, per-case timing metrics.

## Related pages

<CardGroup cols={2}>
  <Card title="Cases" icon="folder-open" href="/console/case-management/cases">
    Lifecycle, lists, and bulk actions.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/console/case-management/analytics">
    Overview dashboard and case analytics.
  </Card>
</CardGroup>