What Is a MASAK Suspicious Transaction Report (STR), and How Does the Process Work Step by Step?

A suspicious transaction report (STR) is the report an obliged party files with MASAK when there is any information, suspicion or reasonable grounds to suspect that a transaction carried out or attempted with or through it is related to money laundering or the financing of terrorism. The report must be filed without delay, and within 10 business days at the latest, from the moment suspicion arises.

What Is a Suspicious Transaction, and What Is the Threshold?

A suspicious transaction is one where there is any information, suspicion or reasonable grounds to suspect that the assets involved were obtained illegally or are used to finance terrorism.

Three points are critical here:

• There is no monetary threshold. Under Article 4 of Law No. 5549, no fixed monetary threshold applies to suspicious transaction reporting; information, suspicion or reasonable grounds to suspect are sufficient. A small transaction can also be reportable.
• Certainty is not required. The threshold is suspicion, not proof. The obliged party is expected to pass on the suspicion, not to prove an offence. Assessment is MASAK’s job.
• Attempts are covered too. Transactions that were not completed, that the customer abandoned or that the institution rejected are also reportable. A rejected transaction should, for exactly that reason, not go unreported.

Who Is Obliged to Report?

Obliged party groups are defined by Law No. 5549 and the Regulation on Measures Regarding Prevention of Laundering Proceeds of Crime and Financing of Terrorism. The main ones are: banks and participation banks, payment and electronic money institutions, capital markets brokerage firms, portfolio management companies, insurance and pension companies, financial leasing and factoring companies, authorised exchange offices, crypto asset service providers, PTT, notaries, self-employed professionals and businesses in certain trade sectors.

Crypto asset service providers are likewise obliged to report suspicious transactions to MASAK within 10 business days at the latest, and immediately where delay would be detrimental.

Obliged parties must also appoint a compliance officer and establish internal training and internal control systems. An STR is the output of this structure — not a standalone form-filling exercise.

The STR Process Step by Step

• Detection. Suspicion arises from two sources: an alert generated by the automated transaction monitoring system, or direct observation by staff (branch, call centre, operations). If the second source is not run systematically, everything outside the monitoring system’s rules becomes invisible.
• Internal reporting. The staff member who notices the suspicion passes it to the compliance unit according to internal procedure. The date and time of this step must be recorded; this is where the clock starts.
• Review and assessment. The customer’s profile, transaction history, declared line of business and the economic rationale of the transaction are assessed together. At this stage, sanctions and PEP screening, adverse media screening and ownership structure analysis provide supporting data.
• Compliance officer decision. The compliance officer decides whether a report will be filed. If the decision is negative, its rationale is also recorded — auditors ask why alerts were not reported.
• Reporting. Reports are, as a rule, filed electronically through the MASAK Online system; in mandatory cases such as system failures, paper-based reporting is possible.
• Recording and retention. Documents underlying the report, review notes and decision records are retained. Under the Law, documents and records must be kept for eight years.
• Continued monitoring. A report does not automatically end the customer relationship. If the relationship continues, the customer is placed under enhanced monitoring and a new report is filed if fresh suspicion arises.

The Confidentiality Obligation: The Tipping-Off Ban

Obliged parties may not disclose to anyone, including the parties to the transaction, that they have filed or will file a suspicious transaction report with MASAK. Even where special laws contain provisions to the contrary, no information about those who filed a suspicious transaction report may be given to third persons, institutions or organisations other than the courts.

Operationally, this ban means: the customer cannot be told "your transaction is on hold because it was reported to MASAK", the report cannot be cited as the reason for an account restriction, and internally the information is limited to those who need to know. A breach of confidentiality is a violation in its own right, separate from failing to report.

Does Filing an STR Automatically Stop the Transaction?

A suspicious transaction report and the postponement of a transaction are different mechanisms.

Article 19/A of Law No. 5549 governs the power, under the relevant conditions, to suspend transactions for seven business days or not to allow them to be carried out. Filing a report therefore does not, on its own, mean an automatic stop decision for every transaction. Postponement and other measures must be assessed separately within their own conditions and procedures.

Consequences of Failing to Report

Breach of the suspicious transaction reporting obligation is subject to an administrative fine. There are three separate types of violation to watch for:

• Not reporting at all — failing to report even though suspicion was identified
• Reporting late — failing to submit the report within the legal deadline even though a decision to report was made; this is a separate violation
• Breaching confidentiality — disclosing that a report has been or will be filed

Audits examine not only the reports filed but also the rationale for alerts that were generated and closed. Saying "an alert came up, we reviewed it, we did not report it" is not enough; the rationale for the decision must be on record.

Four Challenges in Practice

Alert Volume

In a monitoring system with a high false positive rate, the compliance team loses genuine suspicion in the noise. The problem usually stems from single, fixed thresholds; thresholds that do not differ by customer segment produce either too many alerts or too many misses.

Scattered Data

If customer profile, transaction history, sanctions screening results and ownership information sit in different systems, every review turns into manual data gathering. Most of the 10-business-day window is spent here.

No Deadline Tracking

In many institutions the date of internal reporting is not systematically recorded. A deadline that is not recorded cannot be managed, nor proven in an audit.

Weak Rationale Records

The rationale for unreported alerts is kept as free text, scattered across places. This is the area that causes the most problems in audits.

Support Your Review Processes with Datactive AML & KYC

Datactive AML & KYC supports compliance teams’ review processes with transaction monitoring, scenario and alert management, relationship analysis and case management capabilities.

Assessing transaction activity together with customer and connection information helps place individual alerts in a wider context. Structuring the review and report preparation processes, in turn, supports a more consistent operational flow.

Contact us to take a closer look at Datactive AML & KYC and assess your institution’s needs.

This content has been prepared for general information purposes. The reporting obligations applicable to your institution should be assessed against current legislation by authorised legal/compliance teams.