
Regulated businesses across sectors face different warning signs: a bank sees unusual payment flows, a gold dealer sees cash buyers, a property broker sees opaque purchasers, and a crypto exchange sees wallet patterns. This guide explains how red flags differ from confirmed suspicion, sets out examples for banks, real estate and professional services, dealers in precious metals and stones (DPMS), virtual asset service providers (VASPs) and other designated non-financial businesses and professions (DNFBPs), and shows how to respond to a red flag and turn indicators into monitoring controls. Examples refer to UAE requirements where relevant and reflect the position as of October 2026.
What are AML Red Flags?
An AML red flag is an indicator that activity may be linked to financial crime and should be reviewed in the context of the customer and the transaction.
Red flag vs confirmed suspicion
A red flag starts a review, while suspicion is the conclusion reached when the review finds no reasonable explanation, and suspicion is what triggers a report to the financial intelligence unit (FIU).
| Aspect | Red flag | Suspicion |
| What it is | An indicator that something may be wrong | A reasoned conclusion that activity may be linked to crime |
| When it arises | At onboarding, during monitoring or from staff observation | After review of context, explanation and evidence |
| Action required | Review, gather information, document | Report to the FIU in line with local law, without tipping off |
| Standard of proof | None; it is a prompt | Reasonable grounds to suspect, not proof of crime |
In the UAE, suspicious transactions must be reported to the UAE FIU through goAML without delay once suspicion arises, under Federal Decree-Law No. 10 of 2025 and Cabinet Resolution No. 134 of 2025.
Customer, transaction and behaviour indicators
Red flags fall into three broad types, depending on whether they come from who the customer is, what the customer does or how the customer behaves.
| Type | Examples |
| Customer | Unclear beneficial ownership, adverse media, links to high-risk jurisdictions, business activity that does not match the licence |
| Transaction | Amounts just below reporting thresholds, rapid movement of funds, payments from unrelated third parties, round-sum transfers without commercial reason |
| Behaviour | Reluctance to provide information, unusual interest in reporting thresholds, frequent changes to instructions, use of intermediaries without reason |
Why a red flag needs context
A red flag must be read against the customer’s profile and the purpose of the transaction, because the same activity can be normal for one customer and suspicious for another.
Large cash deposits are expected from a supermarket but unusual for a salaried employee. Payments to a high-risk country may be normal for a trading company with documented suppliers there. Firms should never treat nationality, ethnicity or a sector as a red flag in itself, and should avoid relying on a single indicator. The combination of indicators, the customer’s explanation and the supporting evidence decides the outcome.
Front-line staff are often the first to notice behavioural red flags, such as a customer who seems to be following someone else’s instructions or who asks how to avoid reporting. Training should give staff sector-specific examples, explain how to escalate internally and remind them not to discuss suspicions with the customer. A simple internal reporting form, reviewed promptly by the compliance officer, turns these observations into documented cases.
AML Red Flags By Sector
Each sector faces typical red flags linked to how criminals misuse its products and services; the examples below are illustrative, not an exhaustive legal checklist.
| Sector | Example red flags |
| Banks and payment firms | Activity inconsistent with profile, unexplained third-party flows, rapid in-and-out movement, structuring |
| Real estate | Opaque buyers, cash or virtual asset payments, rapid resale at unexplained price changes |
| Professional services | Requests to use client accounts without a transaction, complex structures without purpose |
| DPMS | Cash purchases split below thresholds, unclear source of gold, suspicious documents |
| VASPs | Use of mixers, links to high-risk wallets, activity inconsistent with profile |
| Trust and company service providers | Nominee arrangements without reason, frequent ownership changes, unclear purpose of companies |
Banks and payment firms
Bank and payment firm red flags usually involve account activity that does not match the customer’s profile, unexplained third-party payments, rapid movement of funds and structuring.
- Turnover far above the expected level declared at onboarding.
- Many incoming payments from unrelated individuals followed by quick outgoing transfers.
- Cash deposits split across days or branches to stay below reporting thresholds.
- Frequent transfers to or from high-risk jurisdictions without a business reason.
- Round-sum transfers between related companies with no supporting invoices.
- Use of personal accounts for business activity, or business accounts with no operating expenses.
Our article on real-time transaction monitoring in the UAE explains how banks detect these patterns.
Real estate and professional services
In real estate and professional services, red flags centre on opaque ownership, unclear source of funds, unusual intermediaries and transactions without a clear commercial reason.
- Buyer acts through a company or third party with no explanation of who the beneficial owner is.
- Payment in cash, virtual assets or from accounts unrelated to the buyer.
- Purchase price significantly above or below market value without explanation.
- Rapid resale of property, sometimes between related parties.
- Lawyer or accountant asked to hold funds in a client account with no underlying service.
- Requests to set up complex company structures across several jurisdictions without a clear purpose.
In the UAE, real estate agents and brokers must file a Real Estate Activity Report (REAR) on goAML for purchases of freehold property involving cash payments of AED 55,000 or more, or payment using virtual assets or funds derived from them.
Dealers in precious metals and stones (DPMS)
DPMS red flags include unusual cash or high-value activity, inconsistent trade documents and unclear beneficial ownership or source of goods.
- Cash purchases split into amounts just below AED 55,000, the UAE threshold for cash transactions with DPMS.
- Customer cannot or will not explain the source of funds.
- Certificates of origin, refinery stamps or invoices that appear altered or forged.
- Supply chains routed through conflict-affected or high-risk areas.
- Payments from several third parties or offshore entities with no clear link to the buyer.
- Repeated requests for refunds or duplicate invoices after cash purchases.
UAE DPMS must report cash transactions at or above AED 55,000 with individuals, and qualifying transactions with legal entities, through a Dealers in Precious Metals and Stones Report (DPMSR) on goAML, separately from any suspicious transaction report.
Virtual asset service providers (VASPs)
VASP red flags include unusual wallet flows, use of anonymity tools, links to high-risk wallets and activity that does not match the customer’s profile or source of funds.
The FATF’s 2020 report on virtual asset red flag indicators groups them into six categories: technological features that increase anonymity, geographical risks, transaction patterns, transaction size and frequency, sender or recipient profiles, and source of funds or wealth.
- Funds received from mixers, tumblers or privacy-enhancing services.
- Deposits from wallets linked to darknet markets, scams or sanctioned parties.
- Many small deposits followed by one large withdrawal to an external wallet.
- Conversion between several virtual assets with no clear business purpose and at a loss.
- Customer profile, such as a student or retiree, inconsistent with high-value trading.
- Use of exchanges in jurisdictions with weak AML controls.
Other DNFBPs and trade sectors
Other DNFBPs and trade businesses face red flags linked to ownership, payments and trade documentation, which are covered in more depth in separate articles on shell companies, money mules and trade-based money laundering.
Trust and company service providers should watch for requests to act as nominee directors or shareholders without reason, frequent changes of ownership and companies with no apparent business. Trading companies should watch for invoices inconsistent with market prices or shipping records, and payments from third parties unrelated to the trade. Auditors and accountants should note transactions without business rationale and pressure to sign off unusual entries.
Every sector should also watch for indicators of terrorist financing and sanctions evasion, which can look different from money laundering. Terrorist financing often involves small amounts from legitimate sources, such as donations or salaries, sent to individuals or organisations in or near conflict zones. Sanctions evasion may involve front companies, last-minute changes to counterparties or vessels, transhipment through third countries or goods that could have military uses. Because the amounts can be small, these indicators depend more on screening, counterparty knowledge and staff awareness than on value thresholds.
File DPMSR, REAR and STR Reports From One Module
Regulatory Reporting supports the generation and submission of STR, SAR, CTR, DPMSR and REAR reports for financial and non-financial businesses.
What Should A Firm Do When It Spots A Red Flag?
When a red flag appears, the firm should review the customer and transaction context, decide whether suspicion exists, document the decision and escalate or report as required.
- Pause where appropriate. Hold the transaction if the law and policy allow, without alerting the customer to suspicion.
- Review the customer file. Check due diligence, risk rating, expected activity and previous alerts.
- Examine the activity. Look at the full pattern, linked parties and supporting documents.
- Seek an explanation. Ask for information or documents in a normal business manner.
- Decide. Conclude whether there is a reasonable explanation or whether suspicion exists.
- Escalate and record. Send the case to the compliance officer and document the reasons.
- Report and monitor. File a suspicious transaction report where required and apply enhanced monitoring.
Review customer and transaction context
The review should compare the activity with what the firm knows about the customer, including due diligence, expected activity, linked parties, documents and prior cases.
Useful questions include whether the activity fits the customer’s occupation or business, whether the source of funds is documented, who the counterparties are and whether similar alerts have been closed before. Screening results for sanctions, politically exposed persons and adverse media should be checked; our article on PEP and sanctions screening in the UAE explains these checks.
Escalate and document decisions
Every red flag review should leave a record of the evidence, reasoning, reviewer, outcome and next steps, whether or not the case is reported.
| Record element | Example |
| Trigger | Alert: three cash deposits of AED 50,000 in four days |
| Information reviewed | KYC file, account history, customer explanation, sales invoices |
| Analysis | Deposits match documented sales from the customer’s retail shop |
| Decision | No suspicion; alert closed |
| Reviewer and date | Analyst name, date; approved by team lead |
| Follow-up | Update expected activity in customer profile |
Consider monitoring and reporting
Depending on the outcome, the firm may apply enhanced monitoring, restrict the relationship or file a suspicious transaction report, following the rules of its jurisdiction.
Restrictions, filing duties and deadlines vary. In the UAE, a suspicious transaction report must be filed through goAML without delay, and staff must not tip off the customer. Separate threshold reports, such as DPMSR and REAR, are required regardless of suspicion. Our article on the UAE’s new AML law covers the 2025 changes.
Document Every Red Flag Review In One Case
Compliance Case Management creates cases automatically when risk thresholds are reached, supports AML investigations and generates analysis reports with a narrative of the steps taken.
How to Turn Red Flags Into Monitoring Controls
Red flags become monitoring controls when they are translated into defined scenarios, rules or review steps with a clear rationale, then tested and tuned over time.
From typology to rule or review scenario
A monitoring scenario defines the activity, customer segment, threshold, time window and the reason the pattern indicates risk.
| Red flag | Scenario element | Example rule (illustrative) |
| Structuring of cash | Segment: retail customers; window: 7 days | Three or more cash deposits between 80 and 99 per cent of the reporting threshold within seven days |
| Pass-through activity | Segment: personal accounts; window: 48 hours | More than 80 per cent of credits transferred out within 48 hours, with credits above AED 50,000 in the month |
| Unrelated third-party payments | Segment: DPMS customers | Payment for a purchase made by a party other than the buyer |
| High-risk wallet exposure | Segment: VASP customers | Deposit from a wallet flagged by blockchain analytics as high risk |
Some red flags, such as forged documents or unusual behaviour, cannot be automated and should be built into staff procedures and checklists instead.
Test effectiveness and false positives
Monitoring rules should be tested before and after deployment to check that they catch relevant activity without overwhelming analysts with false positives.
Back-testing runs a rule against historical data to see what it would have flagged. Case outcomes show which rules produce useful alerts and which mostly produce false positives. Thresholds should be calibrated to the firm’s customer base and reviewed periodically, with the reasons for changes documented.
Keep the typology library current
The list of red flags and scenarios should be updated with new cases, regulator guidance and emerging trends.
Sources include FIU strategic analysis reports, FATF typology studies, national risk assessments, regulator circulars and the firm’s own investigations. In the UAE, the Ministry of Economy issued circulars in 2025 on applying the 2024 National Risk Assessment, and the UAE FIU published strategic analysis on the misuse of precious metals. A named owner should review the library at least annually.
Turn Red Flags Into Monitoring Rules
Transaction Monitoring lets you set rules that flag unusual activity based on transaction size, frequency, location and other factors, with goAML-formatted reporting.
Worked example: reviewing a DPMS red flag
The case below is fictional and illustrative. A Dubai gold retailer, here called Souk Gold Trading, notices a pattern.
| Step | Finding (illustrative) |
| Red flag | A customer buys gold bars in cash on three consecutive days for AED 52,000, AED 53,500 and AED 54,000 |
| Context | Customer is a new walk-in buyer; no previous relationship |
| Linked transactions | Total AED 159,500 over three days; the purchases appear linked, so the threshold for CDD and DPMSR is exceeded |
| Explanation sought | Customer says the gold is a gift but declines to explain the source of cash |
| Decision | Compliance officer concludes there are reasonable grounds to suspect structuring |
| Action | CDD completed on the linked transactions, DPMSR filed, STR filed through goAML without delay, no disclosure to the customer |
Key Takeaways
- A red flag is a prompt to review, not proof; suspicion is the conclusion that triggers a report.
- Read every red flag against the customer’s profile and evidence, and never treat nationality or sector alone as a red flag.
- Each sector has typical indicators, from structuring in banks to split cash purchases in DPMS and mixer use at VASPs.
- Document every review, including those closed without a report.
- Translate red flags into tested monitoring scenarios and keep the typology library current.
Frequently Asked Questions About AML Red Flags
What counts as an AML red flag?
An AML red flag is any customer, transaction or behaviour indicator that suggests activity may be linked to money laundering or other crime, such as an unexplained source of funds, structuring, opaque ownership or activity inconsistent with the customer’s profile.
Which red flags apply to banks, DPMS, real estate and VASPs?
Banks watch for activity inconsistent with profile and rapid movement of funds. DPMS watch for split cash purchases and suspicious documents. Real estate firms watch for opaque buyers and cash or virtual asset payments. VASPs watch for mixers and high-risk wallets.
When does a red flag become a suspicion?
A red flag becomes a suspicion when, after reviewing the context, explanation and evidence, the firm has reasonable grounds to suspect the activity is linked to crime. Proof is not required.
How should red flags feed monitoring rules?
Translate each red flag into a scenario with a defined activity, segment, threshold and time window, test it on historical data, calibrate it to reduce false positives and review it as typologies change.
What are examples of AML red flags by industry?
Examples include structured cash deposits in banking, cash or virtual asset property purchases in real estate, split cash gold purchases for DPMS, mixer-linked deposits for VASPs and nominee requests for company service providers.
What are customer due diligence red flags?
Customer due diligence red flags include refusal to provide information, inconsistent or altered documents, unclear beneficial ownership, adverse media, and a stated business or occupation that does not fit the expected activity.
Catch Red Flags Before They Become Regulatory Findings
Book a demo to see how monitoring, case investigation and goAML reporting work together for your business.
