You should have your reporting entity and agent configured in Reporting →
Preferences before creating reports. See Getting Started
guide CTR, FTR, and STR Reports
This page covers the three transaction-based NFIU reports you can create in
Sigma.
| Report | When it is used |
|---|
| CTR (Currency Transaction Report) | For large cash deposits or withdrawals that meet the reporting threshold |
| FTR (Funds Transfer Report) | For high-value or cross-border fund transfers that must be reported |
| STR (Suspicious Transaction Report) | For individual transactions that raise suspicion of money laundering, terrorism financing, or other financial crime |
Create a transaction report
- Go to Reporting → All Reports
- Click Generate Report
- Select one of these report types:
- Choose a data source
- Complete the selection or upload step
- Review the selected records
- Click Create Report
For transaction reports, Sigma’s wizard takes you through Report type, Data source, Select transactions, and Review details.
During the review step, confirm that the report type, selected rows, and source
data are correct before creating the report. Once created, Sigma opens the
report page for the remaining reporting details.
Choose a data source
Transaction reports can be created in these ways:
- Transaction Monitoring or CSV upload
- Retrieve from your server
Transaction Monitoring or CSV upload
Use this option when the transactions are already available in Sigma, or when you
want to supplement them with rows from a CSV template.
Typical use cases include:
- Select transactions from the list in Sigma
- Filter by date range
- Search before selecting rows
- Add more transactions with Upload CSV
- Review a combined set of selected transactions and uploaded rows before creating the report
This is usually the fastest option when your compliance team is already working
from Sigma’s transaction views.
Retrieve from your server
Use this option when you want to upload a CSV of transaction IDs and let Sigma retrieve the transaction details from your saved API connection.
This is useful when the transaction references are available in Sigma’s report workflow, but the full transaction details live in your own system.
In this flow, your CSV contains transaction identifiers only. Sigma then uses
your saved Manual API Connection to fetch the transaction payload before the
report is created.
Review and continue
Before the report is created, Sigma shows a review step where you can confirm the rows you want to include.
After you click Create Report, Sigma opens the report page so you can complete the report details.
Complete the report
Fill in the report details:
- Filing name
- Reporting entity
- Reporting agent
- Submission code
- Report code
- Currency code
- FIU reference
- Report date
- Reason for reporting
If needed, you can also create a new reporting entity or reporting agent directly from this section.
This section is the core filing metadata for the report. It is where you confirm
who is filing, what type of filing is being created, and the reporting context
for the selected transactions.
Transactions
On the report page, you can:
- Review the selected Transactions
- Expand each transaction to view the full details
- Confirm the originator and beneficiary details attached to each transaction
- Check that the records match the report type you selected
This is especially important for FTR and STR filings, where the full context of
the transaction often determines whether the report is complete.
Investigations
Use this section to record the investigative actions taken on the transactions being reported.
Add each action separately so your reviewers can see what checks were performed
before the report was sent for approval.
Indicators
Use the Indicators section to search available indicators and add the ones that apply to the report.
Indicators help describe why the transaction is reportable and give reviewers
more context during internal approval.
Attachments
Upload supporting files for each transaction.
New uploads may appear as save report to view until the report is saved.
Use attachments for any supporting evidence your reviewer or regulator may need,
such as internal investigation records or supporting transaction documents.
For direct CSV upload, Sigma expects the exact template headers below in the same order:
transactionnumber,transaction_description,date_transaction,transmode_code,amount_local,type,comments,to_funds_code,to_country,to_institution_name,to_account_number,to_institution_code,to_account_name,to_currency_code,to_client_number,to_iban,from_funds_code,from_country,from_institution_name,from_account_number,from_account_name,from_currency_code,from_institution_code,from_swift,from_iban,from_sort_code,from_institution_country,from_client_number
| Header | Description |
|---|
transactionnumber | Your internal transaction reference or unique ID |
transaction_description | Narrative or description associated with the transaction |
date_transaction | Transaction date and time |
transmode_code | How the transaction was conducted |
amount_local | Transaction amount in the local currency |
type | Transaction type or reporting classification code |
comments | Additional transaction notes or narrative context |
to_country / from_country | Country codes for the receiving and sending sides |
to_institution_name / from_institution_name | Financial institution names for both sides of the transaction |
to_account_number / from_account_number | Account numbers for the receiving and sending sides |
to_institution_code / from_institution_code | Institution or bank codes where available |
to_currency_code / from_currency_code | Currency codes used on each side of the transaction |
from_swift | SWIFT code for the sending institution where applicable |
to_iban / from_iban | IBAN values where applicable |
from_sort_code | Sort code for the sending institution where applicable |
to_client_number / from_client_number | Client references where available |
Key field groups
- Transaction details:
transactionnumber, transaction_description, date_transaction, transmode_code, amount_local, type, comments
- Beneficiary / receiving side: all
to_* columns such as to_country, to_institution_name, to_account_number, and to_currency_code
- Originator / sending side: all
from_* columns such as from_country, from_institution_name, from_account_number, and from_institution_code
Keep all template columns present even when some optional values are blank in your workflow.
Use a plain numeric value in amount_local without currency symbols or comma
separators.
Keep the transaction date in a machine-readable date-time format and use the
exact header names from the Sigma template.
API integration for CSV enhancement
If your CSV contains transaction IDs but not the full transaction details, you can configure Sigma to automatically fetch the missing data from your own API. Sigma calls your endpoint with the transaction IDs from the CSV and merges the response into the report.
To configure this:
- Go to Reporting → Preferences → General
- Open API connection settings
- Enter your endpoint URL, authentication method, and any required headers
- Use Test connection with a sample transaction ID
- Save the connection once the test succeeds
- Return to the report wizard and choose Retrieve from your server
- Upload a CSV containing transaction IDs only
See the full API integration setup in Manual Reporting →
If you use Retrieve from your server, upload a CSV containing transaction IDs only.
Review flow
Once the report details are complete, you can:
- Save Report
- Submit for review
- Approve Report or Reject Report during review
- Revert to draft if more changes are needed after review
- Export XML File after the report has been reviewed
Status progression
- Draft: The report is still being prepared and can be edited
- Pending review: The report has been sent for internal approval
- Reviewed: The report is approved and ready for export
- Rejected: The report was sent back for correction and resubmission
Use Audit Trail on the report page whenever you need to review the history of
changes or approval activity on the report.
