Transaction Monitoring Without Software: A Guide for Small UAE Firms
Reviewed by Rajesh Kumar, Director and Founder · Last reviewed

UAE rules require every regulated business to monitor its customer relationships on an ongoing basis, but they do not require monitoring software. A small firm with a modest number of transactions can meet the duty with a documented manual process: record what normal activity looks like for each customer, define the red flags relevant to the business, review transactions against both on a set routine, investigate anything unusual, and keep a record of each review and its outcome. What inspectors look for is consistency and evidence, not technology. Software becomes worthwhile when transaction volumes make manual review unreliable.
Key takeaways
- Ongoing monitoring is mandatory; monitoring software is not.
- The duty is to check that transactions are consistent with what you know about the customer.
- A manual process needs four things: a customer profile, a list of red flags, a review routine and a record.
- Every alert needs a documented outcome: explained and closed, or escalated to the compliance officer.
- Review high-risk customers more closely and more often.
- Move to software when volumes grow to the point where manual review cannot be done reliably.
Is transaction monitoring software required in the UAE?
No. The obligation is to monitor, not to buy a system. Article 19 of Federal Decree-Law No. 10 of 2025 requires regulated businesses to apply customer due diligence and continuous monitoring procedures, with their scope set by risk. Article 8 of Cabinet Resolution No. 134 of 2025 describes what ongoing monitoring must include:
- scrutinising transactions throughout the relationship to make sure they are consistent with what the business knows about the customer, the nature of their activities and the risks they present, including the source of funds where necessary; and
- keeping due diligence documents and information up to date, with particular emphasis on high-risk customers.
Neither article mentions technology. The regulations also say that policies and controls should be proportionate to the nature and size of the business. For a real estate brokerage closing a few dozen deals a year, or a jeweller with a manageable number of qualifying sales, a disciplined manual process is proportionate. See our glossary entries on transaction monitoring and ongoing monitoring for the definitions.
When is manual monitoring enough?
There is no fixed number in the rules. In our experience, manual monitoring works when one person can realistically look at every transaction, or every customer's activity, within your review cycle. Signs that it still fits your business:
- transactions are counted in the tens or low hundreds each month, not thousands;
- each transaction is already handled by a person who knows the customer;
- customers are relatively few and their expected activity is easy to describe; and
- you have no real-time payment flows that would need screening before they complete.
If those stop being true, see the section on moving to software below.
How do you set up manual monitoring? Six steps
Step 1: Record what normal looks like for each customer
Monitoring compares what happens with what you expected. So at onboarding, record the purpose of the relationship and the expected activity: the type of transaction, typical value, frequency, payment method and where funds will come from. A short section on the customer file is enough. Without this baseline there is nothing to monitor against.
Step 2: Write down your red flags
Article 17 of the Resolution requires businesses to establish indicators that help identify suspicion and to keep them updated. Draw yours from your sector guidance and your own risk assessment. Common examples:
- payment from a third party with no clear connection to the customer;
- cash where a bank transfer would be normal, or several payments just below a reporting threshold;
- a transaction much larger than the customer's profile suggests;
- funds routed through, or a customer connected to, a high-risk country;
- money that arrives and leaves quickly with no commercial reason;
- a customer who is reluctant to explain a transaction or provide documents;
- a sudden change in how, or how often, the customer transacts; and
- an overpayment followed by a request for a refund to a different account.
Step 3: Build a simple monitoring log
A spreadsheet is fine. One row per transaction, or per customer per review period, with columns for the date, customer, risk rating, transaction details, payment method, whether it matched the expected profile, any red flag noted, the action taken, the reviewer and the review date.
Step 4: Set a review routine
Decide who reviews, how often, and write it into your procedures. A common approach for a small firm:
| When | What is reviewed | By whom |
|---|---|---|
| At each transaction | Does this fit the customer's profile? Any red flag? | The person handling the transaction |
| Monthly | All transactions in the log; any patterns across customers | Compliance officer |
| Quarterly | High-risk customers' activity and files | Compliance officer |
| At periodic review | The customer's whole relationship against their profile | Compliance officer |
Step 5: Investigate and decide
When something does not fit, look into it before the transaction completes if you can. Ask the customer for an explanation and supporting documents, taking care not to reveal any suspicion. Then record one of two outcomes: the activity was explained, with the reason, or it was escalated to the compliance officer, who decides whether to file a suspicious transaction report through goAML. Our explainer from suspicion to a goAML report shows the route.
Step 6: Keep the evidence
Keep the log, the notes of each investigation and the compliance officer's decisions for at least five years. An inspector will ask to see how a specific alert was handled, and a clear record is the only way to show it.

What does a monitoring record need to show?
| Field | Why it matters |
|---|---|
| Customer and risk rating | Shows monitoring is scaled to risk |
| Transaction date, amount, method | Lets the transaction be reconstructed |
| Expected activity | The baseline the transaction was compared with |
| Red flag or mismatch noted | Shows the reviewer applied the indicators |
| Enquiries made and documents obtained | Shows the concern was investigated |
| Outcome and reason | Closed with explanation, or escalated |
| Reviewer and date | Shows who decided and when |
A record that says only "reviewed, no issues" for every transaction carries little weight. Short, specific reasons carry a lot.
How should monitoring differ by risk?
The regulations expect more monitoring where risk is higher. For high-risk customers, including politically exposed persons, increase the degree of monitoring and look for patterns that need closer scrutiny. In a manual process that means reviewing every transaction individually, reviewing the relationship more often, and having the compliance officer, not only front-line staff, look at the activity. For low-risk customers, a lighter periodic review may be appropriate. Our article on enhanced due diligence explains the wider set of measures.
What about sanctions screening?
Screening is a separate duty and applies whatever your size. Customers, beneficial owners and counterparties must be screened against the UAE Local Terrorist List and the UN Consolidated List at onboarding and again whenever the lists change. Doing this by hand is possible for a very small customer base, but it is the first task most firms automate because the lists change frequently and every customer has to be rechecked. See cleared once is not cleared always.

When should you move to software?
Consider it when one or more of these applies:
- the reviewer cannot get through the transactions within the review cycle;
- you are finding issues late, after transactions have completed;
- your customer base is large enough that rescreening after each list update is a burden;
- you have added products, branches or payment channels that create more data than a spreadsheet can handle; or
- your supervisor or an independent review has raised monitoring as a weakness.
Software does not remove the need for judgement: it produces alerts that a person still has to review and decide on. Our AML software selection guide for DNFBPs explains what to look for, and our explainer on whether AI can replace the MLRO covers the limits.
What are the common mistakes?
- No record of expected activity, so there is nothing to compare transactions with.
- Monitoring only for large amounts and missing patterns of smaller payments.
- Reviewing transactions but keeping no evidence that it was done.
- Closing alerts with no stated reason.
- Treating all customers the same, whatever their risk rating.
- Leaving monitoring entirely to the compliance officer when front-line staff see the transactions first.
- Forgetting that suspicion must be reported whatever the amount.
Official sources
The requirements above are taken from the texts below. Check your supervisor's own guidance for sector-specific expectations.
- Federal Decree-Law No. 10 of 2025, published on the Central Bank of the UAE Rulebook
- Cabinet Resolution No. 134 of 2025, included in the CBUAE rulebook compilation (PDF copy hosted by Adventant)
Where Adventant fits
Adventant designs monitoring processes that fit the size of the business. For smaller firms we set up the customer profiles, red-flag list and monitoring log and train staff to use them. Where volumes justify it, we run screening and customer monitoring on your behalf or implement AML software.
Tell us your sector and transaction volumes and we will suggest a proportionate approach.
Set up monitoring that fits your businessFrequently asked questions
Is transaction monitoring software mandatory in the UAE?
No. The rules require ongoing monitoring of customer relationships, proportionate to the size and nature of the business. They do not require software. A documented manual process can meet the duty where transaction volumes are modest.
What is manual transaction monitoring?
Reviewing transactions by hand against each customer's expected activity and a list of red flags, on a set routine, and recording the review and its outcome, usually in a spreadsheet log.
How often should transactions be reviewed?
At the time of each transaction by the person handling it, with a periodic review by the compliance officer, commonly monthly, and more frequent review of high-risk customers. Set the frequency in your procedures according to your risk.
What should I do if a transaction looks unusual?
Ask the customer for an explanation and supporting documents without revealing any suspicion, record what you find, and either close the matter with the reason or escalate it to the compliance officer, who decides whether to file a suspicious transaction report.
Do DNFBPs such as real estate brokers need to monitor transactions?
Yes. Ongoing monitoring applies to all regulated businesses, including DNFBPs. For a broker it means checking that each deal and payment fits the customer's profile and looking for red flags such as third-party or cash payments.
When does a small business need monitoring software?
When manual review can no longer be done reliably: volumes are too high to review in time, issues are found late, or rescreening after sanctions list updates has become a burden.