How to Record a Decision Not to File an STR in the UAE

When an AML alert identifies unusual customer activity or a potentially suspicious transaction, the compliance team must assess the available information and determine the appropriate next step. Some investigations may establish grounds for submitting a Suspicious Transaction Report (STR), while others may not support that conclusion after the available evidence has been reviewed.

However, closing an alert without submitting an STR should not mean leaving the decision unexplained. A clear decision record helps demonstrate what was investigated, which evidence was considered, who made the decision and why the case was closed without a report.

For UAE businesses, this documentation should form part of a structured AML investigation and decision-making process. The applicable requirements depend on the entity's sector and regulatory framework. Importantly, documenting a decision does not replace the obligation to report suspicious activity when the applicable reporting threshold has been met.

1. Identify the Case and Original Concern

The first step is to establish a clear link between the non-reporting decision and the original alert or internal referral.

The case record should identify:

• The internal alert or investigation reference.
• The date the alert was generated or concern was raised.
• The customer or relevant parties involved.
• The transaction or activity under review, where applicable.
• The original risk indicator or reason for investigation.
• The investigator and responsible compliance reviewer.

These details create a traceable record of why the case was opened.

For example, a transaction-monitoring alert may have been triggered because a customer's transfers differed from the activity expected under their customer profile. The record should identify the relevant transactions and explain what initially raised concern.

Avoid using a generic description such as “customer activity reviewed.” A future reviewer should be able to understand the original issue without reconstructing the entire case from separate systems.

2. Summarise the Investigation Performed

The decision record should briefly explain the steps taken to assess the original concern. It does not need to reproduce every investigation note, but it should identify the material checks and evidence that informed the conclusion.

Depending on the circumstances, the investigation may involve reviewing:

• Customer due diligence and know-your-customer records.
• The customer's expected business activity and transaction profile.
• Transaction histories, amounts, dates and counterparties.
• Invoices, contracts or other supporting commercial documents.
• Beneficial ownership information.
• Relevant internal alerts and previous case records.
• Customer explanations and whether they can be independently supported.
• Additional information obtained through appropriate internal checks.

The record should distinguish between verified facts, information provided by a customer and assumptions that remain unconfirmed.

If evidence is missing or an explanation cannot be verified, that limitation should be documented. The absence of supporting documentation does not automatically prove criminal activity, but neither should it automatically be treated as a reason to close a suspicious case without reporting.

The CBUAE's Guidance for Licensed Financial Institutions on Suspicious Transaction Reporting emphasises thorough investigations and adequately detailed records of the procedures performed.

3. Record the Evidence Supporting the Decision

A strong decision record explains which findings influenced the conclusion.

For each material issue, document the relevant evidence and its significance. This may include a verified commercial purpose, consistent transaction records, confirmed counterparty information or other facts that clarify the original alert.

Where possible, reference the supporting document, system record or investigation note instead of relying on an unsupported statement.

For example, an alert may concern a payment that appears inconsistent with a customer's usual transaction pattern. The investigation identifies a corresponding invoice and confirms that the payment amount and counterparty are consistent with the documented commercial transaction.

The reviewer should explain how those findings affect the assessment of the original concern. The existence of an invoice alone does not prove that the transaction is legitimate, and the conclusion must reflect all relevant circumstances.

A useful record distinguishes between:

• Verified findings: Facts supported by reliable evidence.
• Unresolved issues: Questions that remain unanswered.
• Risk indicators: Circumstances that may still raise suspicion.
• Assessment: The compliance professional's reasoned interpretation of the available information.

This approach makes the decision more transparent and easier to reassess if new information emerges.

4. Explain Why an STR Was Not Filed

The decision rationale is the central element of the record. It should explain why the evidence available at the time did not lead to an STR filing decision, where that conclusion is appropriate under the applicable rules.

The rationale should address:

1. What originally triggered the investigation.
2. What the investigation established.
3. Which evidence clarified or affected the original concern.
4. Whether any material red flags remain unresolved.
5. How the findings were assessed against the applicable reporting requirements.
6. Why the case was closed, retained for monitoring or escalated for further review.

Avoid statements such as “no suspicion found,” “customer explanation accepted” or “transaction approved” without supporting reasoning.

A more useful entry would describe the original concern, the checks performed, the verified findings and the reason those findings support the recorded decision. If uncertainty remains, the record should explain how it was evaluated and why further action is or is not required.

Important: A non-reporting decision must never be used to avoid a reporting obligation. Under the CBUAE framework, licensed financial institutions must report without delay when they have reasonable grounds to suspect that a transaction, attempted transaction or funds are linked to criminal proceeds or activity, regardless of the amount. Other reporting entities must follow the requirements applicable to their regulatory framework.

5. Record Who Made the Decision and When

A decision should be attributable to the person responsible for making it under the organisation's AML procedures.

Record the following, where applicable:

• Name or role of the investigator.
• Name or role of the compliance officer or MLRO responsible for the decision.
• Date of the final assessment.
• Internal review or escalation undertaken.
• Relevant internal policy or procedure.
• Any disagreement, additional review or outstanding action.

The record should distinguish the person who investigated the alert from the person who authorised the final decision, where those responsibilities are separate.

Organisations should also establish clear escalation arrangements for cases involving significant unresolved concerns, conflicting evidence or disagreement about the appropriate response.

The objective is to demonstrate accountability and a consistent decision-making process, not simply to show that someone changed an alert's status to “closed.”

6. Maintain a Traceable and Confidential Audit Trail

The decision record should be stored with, or clearly linked to, the underlying investigation evidence.

Effective recordkeeping practices include:

• Using a unique case reference across related documents.
• Recording the date and author of material case updates.
• Retaining investigation notes and supporting evidence.
• Restricting access to authorised personnel.
• Maintaining version history where available.
• Recording the reason for any subsequent change in the decision.
• Applying the retention period required by the relevant legal and regulatory framework.

Confidentiality is essential. Staff should follow applicable restrictions on disclosure and tipping off, as well as the organisation's information-security procedures.

A controlled case-management system can help maintain these records, although a spreadsheet may be suitable for limited tracking if appropriate access, security and audit controls are in place.

7. Define Follow-Up Actions and Reassessment Triggers

Closing a case without filing an STR does not necessarily mean the customer or activity should never be reviewed again.

Further information may change the original assessment. Examples include a new transaction pattern, a material change in the customer profile, newly identified counterparty information or evidence that contradicts an earlier explanation.

Where appropriate, record:

• Whether continued or enhanced monitoring is required.
• Which unresolved issues need further attention.
• Who is responsible for the follow-up.
• The next review date or event that should trigger reassessment.
• The conditions that require escalation.
• The outcome of any later review.

If new information establishes grounds for reporting, the organisation must address its reporting obligation promptly under the applicable framework. An earlier non-reporting decision should not delay a required report.

Follow-up arrangements should be proportionate to the risk and consistent with the entity's AML policies and regulatory obligations.

8. Common Weaknesses in Non-Reporting Decision Records

UAE businesses should review their procedures for the following documentation problems.

Generic explanations: A short statement such as “alert closed” does not explain the basis for the decision.

Missing evidence references: The record describes findings but does not identify the documents or system records that support them.

Unverified customer explanations: The decision relies on what a customer said without evaluating the available supporting information.

Unresolved concerns left unexplained: Material inconsistencies are omitted or ignored rather than assessed.

Unclear decision ownership: The record does not identify who made or reviewed the final decision.

No reassessment process: The case is permanently closed even though new information could materially change the risk assessment.

Inconsistent case records: The rationale in the case-management system conflicts with investigation notes or supporting documents.

Treating documentation as a substitute for reporting: A detailed internal record does not remove an obligation to submit an STR when the relevant reporting threshold has been reached.

Periodic quality reviews can help identify these weaknesses and improve the consistency of decision-making across the compliance team.

9. Checklist for Recording an STR Non-Reporting Decision

Before closing a case without submitting an STR, the responsible reviewer can use this checklist:

• The original alert and case reference are recorded.
• The transaction or activity under review is clearly identified.
• The investigation steps are summarised.
• Material evidence is referenced and retained.
• Verified findings are distinguished from assumptions.
• Remaining concerns and evidence limitations are documented.
• The reason for the decision is specific and evidence-based.
• The decision-maker and decision date are recorded.
• Required internal review and escalation procedures have been followed.
• Monitoring and reassessment actions are assigned where necessary.
• Confidentiality and access controls are applied.
• Records are retained in accordance with applicable requirements.

This checklist is an internal control aid, not a substitute for the requirements of the competent regulator.

Frequently Asked Questions

Must a UAE business document a decision not to file an STR?

The precise requirements depend on the applicable legal and regulatory framework. Some frameworks expressly require reasons for not reporting to be recorded in specified circumstances. Businesses should confirm their regulator's requirements and maintain clear records of investigations and reporting decisions.

Who should approve an STR non-reporting decision?

The responsible person should be identified under the organisation's approved AML procedures and applicable regulatory requirements, typically involving the designated compliance officer or MLRO. Escalation arrangements should address cases where significant concerns remain unresolved.

What should the decision record contain?

It should identify the original concern, investigation performed, material evidence, assessment of unresolved issues, rationale for the decision, responsible reviewer, decision date and any required follow-up.

Can a closed AML alert be reopened?

Yes. If new information materially changes the assessment, the case should be reassessed under the organisation's procedures. Any reporting obligation arising from that reassessment must be addressed promptly.

Does a decision not to file an STR mean the customer presents no AML risk?

No. A decision about a specific alert is not necessarily a conclusion that the customer presents no ongoing risk. Customer risk assessments and monitoring should continue as required by the applicable framework and the organisation's procedures.

Conclusion

Recording a decision not to file an STR is an important part of a structured AML investigation. The record should explain the original concern, evidence reviewed, reasoning behind the conclusion, responsible decision-maker and any follow-up required.

For UAE businesses, the aim is to maintain a clear and traceable record that supports accountability and allows the decision to be reassessed when circumstances change. Good documentation supports compliance governance, but it must never replace a report required by law or the relevant regulator.

GoAMLUAE.com supports businesses seeking to strengthen their goAML reporting processes and AML compliance arrangements. Organisations should ensure that their procedures reflect the requirements applicable to their sector and competent authority.