How to Handle Attempted Suspicious Transactions Under UAE AML Procedures
Suspicious activity does not always result in a completed transaction. A customer may attempt to transfer funds using unclear information, provide inconsistent documents, or try to proceed with a transaction that raises concerns during customer due diligence. Even when the transaction is stopped, the circumstances may still require careful assessment by the business's compliance team.
For regulated businesses and applicable Designated Non-Financial Businesses and Professions (DNFBPs) in the UAE, understanding how to handle attempted suspicious transactions is an important part of an effective anti-money laundering (AML) framework. Staff should know how to identify warning signs, preserve relevant records, escalate concerns internally, and determine whether a report to the UAE Financial Intelligence Unit through goAML may be required.
The correct response depends on the facts, the entity's obligations, and the applicable UAE requirements. A transaction being blocked or abandoned does not, by itself, establish money laundering. However, an unsuccessful transaction should not automatically be ignored.
What Is an Attempted Suspicious Transaction?
An attempted suspicious transaction is a proposed or initiated financial or business transaction that raises reasonable concerns about possible money laundering, terrorist financing, or other relevant financial crime, even though it does not proceed to completion.
Examples may include:
- A customer attempts to make a payment but cannot provide a credible explanation for the source or purpose of the funds.
- A customer submits documents that appear inconsistent or potentially falsified during verification.
- A person attempts to transfer funds on behalf of another party without a clear business reason.
- A customer repeatedly attempts transactions after earlier attempts were declined due to compliance concerns.
- A customer abandons a transaction immediately after being asked for additional information.
These situations are indicators for further review, not proof of wrongdoing. Businesses should consider the overall circumstances, customer profile, transaction purpose, available evidence, and applicable reporting requirements.
Why Businesses Should Review Attempted Transactions
Reviewing attempted activity can help compliance teams identify risks that may not appear in completed transactions. For example, repeated attempts to bypass verification controls may reveal weaknesses in a customer's explanation or suggest an effort to avoid scrutiny.
Ignoring unsuccessful transactions can also create gaps in the business's AML records. If similar activity occurs again, earlier attempts may provide important context for understanding the customer's behaviour.
A structured review process helps businesses maintain consistent decision-making, demonstrate how concerns were assessed, and identify whether additional customer checks or internal controls are needed.
Common Red Flags to Watch For
Compliance teams should consider the following warning signs when reviewing attempted transactions:
1. Inconsistent customer information
The details provided by the customer may conflict with identification documents, business records, ownership information, or previously supplied information.
2. Unclear transaction purpose
The customer may be unable or unwilling to explain why the transaction is being attempted, who will benefit from it, or how it relates to their stated business activities.
3. Unusual urgency or pressure
A customer may insist that a transaction must be processed immediately and discourage normal verification checks.
4. Repeated attempts to bypass controls
Repeatedly changing transaction details, using alternative parties, or resubmitting an instruction after rejection may warrant closer examination.
5. Unexplained third-party involvement
A proposed transaction may involve a person or entity whose relationship with the customer is unclear, particularly where the payment purpose or beneficiary cannot be reasonably explained.
No single indicator automatically proves suspicious activity. Staff should assess the facts collectively and follow the organisation's established AML procedures.
Steps to Handle Attempted Suspicious Transactions
1. Identify and Record the Attempt
Front-line staff should record the basic details as soon as a concern arises. This may include the date and time, customer identification details, proposed amount, payment method, intended beneficiary, transaction purpose, and reason the transaction did not proceed.
Where available, retain relevant transaction references, communications, submitted documents, and system records in accordance with the organisation's recordkeeping and data-protection procedures.
2. Apply Relevant Controls
Follow the organisation's approved procedures for pausing, declining, or otherwise handling the proposed transaction. Staff should not bypass verification requirements simply because a customer is applying pressure.
Any restriction or decision should be based on applicable legal requirements, internal controls, and the circumstances of the case. Staff should escalate uncertainty rather than make unsupported assumptions about the customer's intentions.
3. Escalate the Concern Internally
Refer the case to the designated compliance officer or Money Laundering Reporting Officer (MLRO), where applicable. The escalation should explain what happened, which indicators were identified, what checks were performed, and why the activity requires review.
A clear internal escalation process helps ensure that concerns are assessed consistently rather than decided informally by individual employees.
4. Conduct a Risk-Based Review
The compliance team should examine the attempted transaction alongside the customer's profile, expected activity, previous transactions, beneficial ownership information where relevant, and any available supporting documents.
The reviewer should distinguish verified facts from assumptions. If additional information is needed, follow the applicable customer due diligence and escalation procedures without improperly alerting the customer to a potential report.
5. Assess Whether Reporting Is Required
The MLRO or responsible compliance function should assess whether the circumstances meet the applicable threshold for reporting under UAE AML requirements. The fact that a transaction was not completed does not automatically remove reporting considerations.
Where reporting is required, the relevant report should be submitted through the appropriate UAE Financial Intelligence Unit reporting channel, including goAML where applicable. The organisation should follow current official guidance for the relevant report type and submission process.
Do not delay a required report merely because the proposed transaction was stopped. Equally, do not submit a report solely because a transaction failed; base the decision on the available facts and applicable requirements.
6. Maintain a Clear Audit Trail
Document the review, supporting evidence, internal escalation, decision rationale, and any follow-up actions. Records should show how the concern was assessed and why the organisation took a particular course of action.
Access to sensitive case information should be restricted to authorised personnel. Staff should also follow applicable confidentiality requirements and avoid unauthorised disclosure that could compromise an investigation or breach tipping-off restrictions.
The Role of goAML in Reporting Suspicious Activity
goAML is used by relevant reporting entities to submit reports to the UAE Financial Intelligence Unit. When an attempted transaction raises concerns, the responsible compliance team should determine whether a report is required and identify the appropriate report type under current official guidance.
A useful report should present the relevant facts clearly, including the attempted activity, parties involved, transaction details available, reasons for concern, and supporting information. If the transaction did not complete, the narrative should accurately explain that fact and describe the circumstances surrounding the attempt.
Businesses should avoid inventing missing details or presenting assumptions as established facts. Accurate information and a clear explanation of the concern support effective review by the relevant authorities.
Common Mistakes to Avoid
Businesses should avoid these common errors when handling attempted suspicious transactions:
- Ignoring unsuccessful attempts: A transaction that did not complete may still contain relevant indicators.
- Making decisions without documentation: Verbal discussions alone may not provide an adequate audit trail.
- Treating every failed transaction as suspicious: Technical errors, incomplete forms, or ordinary customer mistakes may have legitimate explanations.
- Delaying internal escalation: Front-line staff should know when and how to refer concerns to compliance.
- Revealing confidential reporting activity: Customer communications should be handled carefully under applicable confidentiality and tipping-off requirements.
- Using inconsistent procedures: Similar cases should be reviewed under a clear, documented framework while allowing for differences in risk and circumstances.
How Businesses Can Strengthen Their Procedures
UAE businesses can improve their handling of attempted suspicious transactions by training staff to recognise relevant red flags, maintaining clear escalation channels, and documenting both completed and unsuccessful activity where appropriate.
Periodic reviews can help identify recurring patterns, weaknesses in customer verification, and gaps in transaction monitoring. Organisations should also keep their AML policies aligned with current applicable UAE requirements and ensure that responsible personnel understand their reporting duties.
Where a business is uncertain about its obligations, it should consult current official UAE guidance or obtain advice from a suitably qualified AML compliance professional.
Frequently Asked Questions
Must every attempted suspicious transaction be reported in the UAE?
Not automatically. The organisation should assess the facts and determine whether reporting is required under the applicable UAE AML framework. An unsuccessful transaction can still raise reportable concerns, depending on the circumstances.
Should a business keep records if the transaction was cancelled?
Relevant records should be retained in accordance with applicable legal requirements and the organisation's recordkeeping procedures. These records may help explain the decision and provide context if similar activity occurs later.
Who should review an attempted suspicious transaction?
The case should follow the organisation's internal escalation process and be reviewed by the designated compliance officer or MLRO, where applicable. Front-line staff should record and escalate concerns rather than independently make complex reporting decisions.
Can an attempted transaction be relevant to a goAML report?
Yes, depending on the circumstances and applicable reporting requirements. The report narrative should clearly distinguish the attempted activity from any transaction that was actually completed.
What should staff avoid when dealing with the customer?
Staff should follow approved procedures, avoid unsupported accusations, and protect confidential information. They should not improperly disclose whether suspicious activity has been reported or whether a report is being considered.
Conclusion
Attempted suspicious transactions deserve a structured and evidence-based response, even when no funds or assets change hands. UAE businesses should record relevant details, apply appropriate controls, escalate concerns, assess reporting obligations, and maintain a clear audit trail.
A consistent process helps organisations identify potential financial crime risks while avoiding assumptions based solely on a failed transaction. By integrating attempted-transaction reviews into their wider AML procedures and following current UAE requirements, businesses can strengthen compliance and support accurate goAML reporting when required.