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

# Report Activity

> Start reporting suspicious activity using Sigma

<Note>
  You have to create a reporting entity and reporting agent before you can start
  generating reports. See [how to create reporting entity and reporting
  agent](../getting-started/)
</Note>

### Suspicious Activity Reports (SAR)

Use a SAR when the concern is broader than a single transaction. This report type
is designed for patterns of behaviour, suspicious conduct, or activities that may
indicate money laundering, terrorism financing, or other financial crime.

Unlike CTR, FTR, and STR, the SAR workflow focuses on the **parties involved in
the activity**, the **investigation carried out**, and the **indicators** attached
to the case.

## Create a SAR report

1. Go to **Reporting → All Reports**
2. Click **Generate Report**
3. Select **Suspicious Activity Report (SAR)**
4. Choose your data source
5. Complete the selection or upload step
6. Review the details and click **Create Report**

After the report is created, Sigma opens the report page where you complete the remaining sections.

The SAR report page is structured to help you document the suspicious activity in
stages, so that reviewers can understand who is involved, what happened, and why
the activity is reportable.

## Complete the report

### General Information

Fill in the report details:

* **Filing name**
* **Reporting entity**
* **Reporting agent**
* **Submission code**
* **Report code**
* **Currency code**
* **FIU reference**
* **Report date**
* **Reason for reporting**

You can also create a new reporting entity or reporting agent directly from this section if needed.

This section defines the filing itself. Review it carefully before moving to the
activity details, because the filing metadata carries through the rest of the
review and export process.

### Activity

Use the **Activity** section to add the parties involved in the suspicious activity.

Each entry on this section represents an **Activity Party**. Use **Add Activity
Party** when more than one person, account, or entity is involved.

For each activity party, provide:

* **Country**
* **Significance (0-10)** with the available options `Not significant`, `Significant`, and `Very significant`
* Whether the party is suspected
* **Party type**
* **Reason for reporting**

Depending on the selected party type, Sigma asks for more details:

* **Person**: first name, middle name, last name, and one or more emails
* **Account**: bank name, account number, and either bank code or SWIFT
* **Entity**: business name, incorporation number, country code, and area of business

Use **Add Activity Party** to add more than one party.

Capture enough detail for each party so the reviewer can understand both the
party's role in the activity and why that party is relevant to the report.

### Investigations

Use the **Investigations** section to record actions taken during your review.

You can add multiple investigative actions and remove any that are no longer needed.

Use this area to document the steps your team took before escalating the SAR,
such as internal checks, case review actions, or supporting inquiries.

### Indicators

Use the **Indicators** section to add the indicators that apply to the report.

Indicators help classify the suspicious behaviour and provide extra context for
internal review and downstream filing.

### Attachments

Upload supporting files in the **Attachments** section.

Attachments added to a SAR belong to the report itself rather than to individual transactions.

New uploads may appear as **save report to view** until the report is saved.

Use attachments for supporting evidence such as internal case notes, supporting
documents, or related files that help explain the suspicious activity.

## Review flow

Once the report details are complete, you can move the report through the normal review flow:

* **Save Report** while you are still working
* **Submit for review** when the report is ready
* **Approve Report** or **Reject Report** during review
* **Revert to draft** if the report needs more updates after review
* **Export XML File** after the report has been reviewed

### Status progression

* **Draft**: The SAR is still being prepared
* **Pending review**: The SAR has been sent for internal approval
* **Reviewed**: The SAR is approved and ready for export
* **Rejected**: The SAR has been returned for correction and resubmission

Use **Audit Trail** on the report page whenever you need to review the report's
change history or approval activity.