Dubai & Sharjah, UAE +971 4 422 1190 enquire@aonebiz.com Mon–Fri 09:00–18:00

Suspicious Transaction Reports in the UAE: When and How to File

When suspicion turns into a report, timing and discretion matter. Here is what to do, who decides and what never to say to the customer.

Based on the current AML frameworkCheck dates against official texts7 min readUpdated 21 October 2026

A suspicious transaction report, or STR, is a report to the UAE Financial Intelligence Unit that a regulated business files through goAML when it suspects, or has reasonable grounds to suspect, that funds are the proceeds of crime or linked to terrorist financing. It is filed without delay, and the customer must not be told.

STR and SAR

ReportUsed when
STR, suspicious transaction reportA transaction, or attempted transaction, raises suspicion
SAR, suspicious activity reportSuspicious behaviour with no transaction attached

Both go through goAML. See goAML registration step by step if you do not yet have an account.

What triggers a report

The test is suspicion based on the facts, not proof. Typical indicators are described in supervisor guidance and include:

  • A customer who avoids giving information or documents about ownership or the source of funds.
  • Payments that do not match the customer's profile or stated business.
  • Cash used in unusual amounts or patterns.
  • Payments from third parties with no clear link.
  • Pressure to complete quickly or to avoid normal checks.
  • Complex structures with no commercial reason.

No single sign proves wrongdoing. The compliance officer looks at the whole picture.

The internal process

  1. Staff flag. The employee writes down what they saw and sends it to the compliance officer using the internal form.
  2. Officer reviews. The officer gathers context from the customer file, prior transactions and any screening results.
  3. Decision. Either the officer documents why there are no grounds, or files a report.
  4. File on goAML. Complete the STR or SAR with the facts, parties and transactions.
  5. Keep records. Store the internal report, the decision and the filing confirmation.
  6. Follow FIU instructions. If the FIU asks for more information or gives directions on the account, follow them.

Timing

Guidance from supervisors says reports are to be filed without delay. We do not rely on a fixed number of days from secondary sources; a delay between suspicion and filing is itself something a supervisor will question. Record the date suspicion arose and the date of filing.

Tipping off

The customer must not be told that a report is being or has been filed. Commentary also warns that abruptly refusing the customer or ending the relationship can alert them. Do not discuss the report with colleagues who do not need to know, and do not mention it in customer emails. Seek guidance from the supervisor or FIU on how to handle a live transaction.

Who may file

The compliance officer usually files. Make sure a deputy can also file when the officer is away. See AML compliance officer duties.

Example

A bookkeeping firm learns that a new client intends to pay its invoices from three unrelated personal accounts abroad, though the client says it has no overseas business. The staff member records the facts and informs the officer. The officer asks the client for an explanation and documents; the answers do not fit. The officer files an STR the same day and does not tell the client. The file records the sequence.

Records to keep

  • The internal report and who made it.
  • The officer's review and reasons.
  • A copy of the goAML submission and acknowledgement.
  • Any correspondence from the FIU.

Mistakes to avoid

  • Waiting for proof before reporting.
  • Telling the customer.
  • No record of why a flag was closed.
  • Only the officer knowing how to use the portal.
  • Treating a one-off tick-box training as enough for staff to recognise suspicion.

Next step

Check your internal escalation form and a worked example are in your procedure. See AML compliance programme components and our goAML services.

Red flags by sector

SectorExamples of unusual activity
Real estateBuyer pays in cash or through unrelated third parties; quick resale at a different price; buying through a newly formed company with unclear owners
Precious metalsLarge cash purchases; customer unconcerned about price; requests to split payments
Accounting and auditClient asks for records that do not reflect the real transactions; unexplained cash; reluctance to disclose owners
Company servicesLayered structures across several jurisdictions with no clear business reason; nominees with no knowledge of the business

A red flag is a reason to look closer, not proof. The officer should record what was checked and why the activity was or was not reported.

What to put in the report

  • Who the parties are, with identification details you hold.
  • What happened: dates, amounts, accounts and how the funds moved.
  • Why you are suspicious, in plain words, linking the facts to the indicators.
  • What you did in response, for example requested information or paused the transaction.
  • Supporting documents the FIU may request.

A clear report is more useful to the FIU than a long one. Avoid opinions about guilt and stick to facts and reasoning.

After you file

Keep the confirmation, continue to monitor the customer, and follow any instruction from the FIU. Do not assume the matter is closed. If new facts arise, a follow-up report may be needed. Keep the customer file consistent with what you told the FIU.

A simple internal form

Give staff a one-page form with five questions: what did you see, when, who was involved, why does it seem unusual, and what documents do you hold. Route it only to the compliance officer. This keeps the reporting chain short and the information confidential.

Frequently asked questions

A report filed with the UAE Financial Intelligence Unit through goAML when a regulated business suspects, or has reasonable grounds to suspect, that funds relate to crime or terrorist financing.

An STR relates to a transaction or attempted transaction. A SAR relates to suspicious behaviour or activity with no transaction.

Supervisor guidance says without delay. Record when suspicion arose and when you filed.

No. Telling the customer is tipping off and should be avoided.

No. The test is suspicion or reasonable grounds, not proof.

Keep reading

Related guides

Talk to us

Get a clear answer in one short call

Tell us your situation and we will say what applies, what does not and what to do next.

  • Scoped first we agree what is in and out before any work starts.
  • Named consultant one person owns your file from the first call.
  • Plain-language advice you get a clear answer, not a list of options.
  • Records kept tidy working papers you can hand to the FTA or an auditor.
Scroll to Top