Home
How to report
FAQ goAML
Submitting a report
Submit Web Report
Transactions
Transactions to be submitted

Transactions to be submitted

1. The reporting entity could not identify any suspicious transaction

Example 1: the client was mentioned negatively in the press, but the transactions recorded by the reporting entity are entirely normal.

Example 2: the request to enter into a business relationship was refused.

In this case, a Suspicious Activity Report (SAR) must submitted (see the User's guide ). Transactions do not need to be provided proactively, but must be supplied if requested by the FIU.

2. The reporting entity has identified one or several suspicious transactions

In this case, a Suspicious Transaction Report (STR) must be completed, containing the transactions history of the client’s account(s).

Unless there is a specific suspicion relating to earlier transactions, only transactions from the last two years must be provided.

The suspicion(s) relating to the transactions must be described in the “Reason for suspicion (summary)” field of the report (see the User's guide ) or attached as an annex.

3. Specific case: the client is the victim of a fraudulent transfer

This section applies only if the client is the victim of a fraudulent transfer. If the client is a suspect, please refer to section 2.

If the client is the victim of one or several fraudulent transfers, only the fraudulent transactions must be reported.

Examples: CEO fraud, fake invoice fraud, man‑in‑the‑middle attack.

Note: Bank fees (account maintenance fees, etc.) are generally not suspicious and therefore do not need to be reported.

Last update 08.06.2026