Regulatory Reporting Services in the UAE
Registering on goAML gives your business access to the UAE Financial Intelligence Unit (FIU). Using it well is another matter. Which report type applies? Is this suspicious enough to report? What must the narrative say? How many days do you have to file a partial name match? What happens after you submit?
Our goAML reporting services help UAE reporting entities choose the right report, decide what to include and meet every filing deadline with confidence. We support your Compliance Officer through every stage of AML regulatory reporting, from recognising a reportable event to preparing a complete, clear report and keeping the records that prove it was handled correctly. Our team began by helping businesses register on goAML, so reporting is at the heart of what we do.
What Is goAML Reporting?
goAML reporting is the process by which UAE Financial Institutions, Designated Non-Financial Businesses and Professions (DNFBPs) and Virtual Asset Service Providers (VASPs) submit reports to the UAE Financial Intelligence Unit (FIU) through goAML, the FIU's electronic reporting system. Federal Decree-Law No. 10 of 2025 (FDL 10/2025), Article 18(1) requires suspicion reports to be submitted through the electronic system designated by the FIU or any other approved means, with all available data on the transaction and the parties. goAML reports cover suspicion-based reports, threshold and activity reports and sanctions name match reports, and each type has its own trigger and data requirements. goAML reporting services help a reporting entity choose the right report type, prepare complete content and meet every deadline.
Key Points at a Glance
The key points below summarise what UAE reporting entities need to know about goAML reporting and how our support helps at each stage:
- FDL 10/2025, Article 18(1) requires suspicious transactions to be reported without delay, regardless of value.
- goAML reports fall into three families: suspicion-based reports, threshold and activity reports and sanctions reports.
- The reporting decision belongs to your Compliance Officer under CR 134/2025, Article 22(2).
- Confirmed Name Match Reports (CNMRs) and Partial Name Match Reports (PNMRs) must be filed within five business days of the freezing, suspension or rejection measure.
- From 14 December 2026, a Postponement Suspicious Transaction Report (PSTR) must be filed within 24 hours where there is suspicion of both a criminal link and an imminent risk that the funds will be transferred, withdrawn or dissipated.
- Clear narratives and complete data reduce goAML report rejections and FIU follow-up.
- Our goAML support covers every stage, from escalation to record-keeping.
- Fees are charged at AED 550 (USD 150) per hour, based on the hours your case needs.
- 25+ regulatory reporting projects completed across 5+ sectors.
The Legal Duty to Report on FIU's goAML platform
The legal duty to report suspicious transactions in the UAE comes from Federal Decree-Law No. 10 of 2025 (FDL 10/2025), Article 18(1). FDL 10/2025, Article 18(1) requires Financial Institutions, DNFBPs and VASPs that suspect, or have reasonable grounds to suspect, that a transaction or funds represent proceeds of crime, or are related to or intended for use in a crime, to notify the FIU without delay and directly, regardless of value. The report must be detailed, contain all available data about the transaction and the parties, be submitted through the electronic system designated by the FIU or any other approved means and be followed by any additional information the FIU requests.
Cabinet Resolution No. 134 of 2025 (CR 134/2025), Articles 17 to 19 set out further rules on suspicion indicators, reporting and the prohibition on tipping off. CR 134/2025, Article 22(2) gives the Compliance Officer the duty to receive, examine and assess suspicious transaction information and to decide whether to notify the FIU or retain the matter with documented reasons, in full confidentiality.
Lawyers, notaries, other legal professionals and independent legal auditors are exempt from the reporting duty only where the information was obtained in circumstances subject to professional secrecy, under FDL 10/2025, Article 18(2). CR 134/2025, Article 18(2) explains these circumstances, such as assessing a customer's legal position, representing the customer before courts or in arbitration or mediation and giving a legal opinion on judicial proceedings.
goAML Report Types Explained
goAML report types in the UAE are not interchangeable, and each one has its own trigger and data fields. The table below lists the main goAML report types that UAE reporting entities file with the FIU, what each one is and when it applies. Selecting the wrong type is a frequent reason a report is questioned or rejected.
| Report | What it is | When it applies |
|---|---|---|
| STR | Suspicious Transaction Report | Suspicion of money laundering, terrorist financing or proliferation financing linked to a transaction or funds |
| SAR | Suspicious Activity Report | Suspicious activity or attempted transactions where no transaction was completed |
| PSTR | Postponement Suspicious Transaction Report | Suspicion of a criminal link plus an imminent risk that funds will be transferred, withdrawn or dissipated, filed within 24 hours (from 14 December 2026) |
| DPMSR | Dealers in Precious Metals and Stones Report | Cash transactions of AED 55,000 or more with individuals, and covered transactions of AED 55,000 or more with companies, which can include cash and wire transfers, by dealers in precious metals and stones |
| REAR | Real Estate Activity Report | Freehold property purchases and sales paid with physical cash of AED 55,000 or more in one or several payments, or paid with virtual assets or funds converted from virtual assets, filed by real estate brokers, agents and lawyers |
| HRC | High-Risk Country Transaction Report | In-scope cross-border banking or remittance transactions linked to a high-risk jurisdiction or party, where the mandatory transaction details are available |
| HRCA | High-Risk Country Activity Report | Reportable attempted in-scope transactions linked to a high-risk jurisdiction or party, where the transaction details are insufficient |
| CNMR | Confirmed Name Match Report | Freezing measures or rejected transactions after a confirmed sanctions match |
| PNMR | Partial Name Match Report | Suspended or rejected transactions where a sanctions match cannot be confirmed or ruled out |
Choosing the right goAML report type matters. Filing an STR where a SAR is appropriate, or the reverse, can lead to rejection or quality concerns.
Three Families of goAML Reports
goAML reports fall into three families, and each family is triggered in a different way. Suspicion-based reports depend on judgement, threshold and activity reports depend on transaction facts and sanctions reports depend on screening results. Knowing which family a case belongs to tells the Compliance Officer what must be filed and how quickly.
Suspicion-based reports
Suspicion-based goAML reports, namely Suspicious Transaction Reports (STRs), Suspicious Activity Reports (SARs) and PSTRs, depend on the Compliance Officer's judgement. There is no threshold: suspicion or reasonable grounds to suspect is enough, regardless of the amount. CR 134/2025, Article 18(1) also covers attempted transactions, so a deal the customer abandons can still require a report.
From 14 December 2026, UAEFIU Regulation No. 1 of 2026, Articles 1, 3, 4 and 19 require a reporting entity to file a Postponement Suspicious Transaction Report (PSTR) promptly, meaning within 24 hours, when it suspects or has reasonable grounds to suspect both a criminal link and an imminent risk of transfer, withdrawal or dissipation of the funds. An amount of AED 500,000 is an indicative criterion, with exceptions under Article 4, and is not a minimum filing threshold. FDL 10/2025, Article 5(1) allows the Chief of the FIU to suspend a suspicious transaction for up to ten working days.
Threshold and activity reports
Threshold and activity goAML reports, namely DPMSRs, REARs, HRCs and HRCAs, are triggered by transaction types, amounts or links to high-risk countries, as specified by the FIU and the relevant supervisory authority. Threshold and activity reports do not require suspicion. If the same transaction is also suspicious, the separate duty to file an STR or SAR under FDL 10/2025, Article 18(1) still applies.
Sanctions reports
Sanctions goAML reports, namely CNMRs and PNMRs, follow sanctions screening results. Under Cabinet Resolution No. 74 of 2020 (CR 74/2020), Articles 15 and 21 and the Executive Office for Control and Non-Proliferation (EOCN) Guidance on Targeted Financial Sanctions (TFS) of March 2026, a confirmed match requires freezing without delay, which CR 74/2020, Article 1 defines as within 24 hours of the listing decision, and a CNMR within five business days of the freezing measure, or of rejecting a prospective customer or transaction.
For an unresolved partial match involving an existing customer, the business must suspend without delay, keep the suspension in place pending EOCN instructions and file a PNMR within five business days of the suspension. For a prospective customer or counterparty, it must seek identification documents and, if they cannot be obtained within 10 business days, reject the transaction and file a PNMR within five business days of the rejection. CNMRs and PNMRs are sent to the EOCN and the relevant supervisor through goAML (EOCN Guidance, paragraphs 35 to 36, 42 to 44 and 49 to 51).
Businesses that focus only on STRs often miss threshold, activity and sanctions goAML reports altogether, and each missed report is a separate reporting failure.
Make sure you are filing every report your business is required to file.
Talk to us.
How Our goAML Reporting Services Work
Our goAML reporting services follow the life of a report, from the first internal alert to the final record on file. Each stage below can be used on its own for a single case or combined as ongoing support. The reporting decision and the submission always stay with your Compliance Officer and registered goAML users.
Reporting framework review
The reporting framework review is usually the starting point of our goAML reporting support. We review your goAML registration, users, reporting procedures and filing history to identify gaps. The review shows whether the right people can file, whether procedures reflect FDL 10/2025 and CR 134/2025 and whether past reports were complete.
Case assessment support
Case assessment support helps the Compliance Officer decide whether a potential reportable event must go to the FIU. When a potential reportable event arises and disclosure to us is lawful, with appropriate access arrangements in place, we help the Compliance Officer review the facts, the customer file and the red flags, and assess whether there is suspicion or reasonable grounds to suspect. The decision always remains with your Compliance Officer.
Report preparation
Report preparation for goAML covers the structured data each report type requires. We help prepare the report content: parties, accounts, transactions, identification details and supporting documents, organised according to the goAML report type. Complete and consistent data reduces the risk of the FIU rejecting the report or asking for more information.
Narrative drafting
Narrative drafting turns the facts of a case into a clear written explanation for the FIU. We help write a clear narrative explaining who was involved, what happened, when, where, how and why it is suspicious and what action your business took. Your Compliance Officer reviews and approves every narrative before it is submitted.
Quality review
Quality review is the final check on a goAML report before submission. We check each report for missing mandatory information, inconsistencies and common causes of rejection. The checks range from the wrong report type to missing or unreadable attachments.
Deadline tracking
Deadline tracking keeps time-bound goAML reports on schedule. We help you track deadlines for reports such as PSTRs (24 hours), CNMRs and PNMRs (five business days), and document the timeline for STRs and SARs. A documented timeline shows your supervisor that each suspicion was reported without delay, as FDL 10/2025, Article 18(1) requires.
FIU follow-up
FIU follow-up support helps you respond when the FIU asks for more about a report you have filed. We support responses to FIU requests for additional information and help you manage any instructions received. CR 134/2025, Article 18(1)(b) requires a prompt response to any FIU request for additional information.
Record-keeping
Record-keeping support makes sure every reporting decision can be evidenced to your supervisor. We help you keep a complete reporting file, including STRs and the reasons recorded for decisions not to report, in line with CR 134/2025, Articles 22(2) and 25(2). CR 134/2025, Article 25(2) requires records, including STRs, to be kept for at least five years. For records covered by Article 25(2), count the minimum from the latest applicable event, such as relationship termination, account closure, completion of an occasional transaction, completion of an inspection, completion of an investigation or issuance of a final court judgment.
Writing an Effective STR Narrative
The narrative is the part of a Suspicious Transaction Report (STR) or Suspicious Activity Report (SAR) that the FIU relies on most, because it explains why the data in the report is suspicious. A clear narrative lets the FIU understand the case without going back to the reporting entity for basic facts. A good STR narrative:
- Starts with a short summary of the suspicion
- Identifies all parties and their relationships
- Describes the transactions or activity with dates and amounts
- Explains the specific red flags, not just general concerns
- Records the customer's explanation, if one was given, and why it did not resolve the concern
- States the action taken by the business
- Avoids jargon and assumptions the FIU cannot verify
Tipping Off and Confidentiality
Tipping off means telling a customer or any other person, directly or indirectly, that a suspicious transaction report has been or is about to be filed, and UAE law prohibits it. FDL 10/2025, Article 24 makes information on suspicious transactions confidential, and FDL 10/2025, Article 29(1) punishes tipping off with imprisonment and a fine of not less than AED 50,000, or either penalty. CR 134/2025, Article 19(1) prohibits the business and its directors, officers and employees from disclosing a report to the customer or any other person. We help you design customer communications and internal access controls that keep reports confidential while allowing the business to manage the relationship.
Protection for Reporting in Good Faith
Protection for reporting in good faith comes from FDL 10/2025, Article 37(1), which shields reporting entities, their board members, employees and authorised representatives from criminal, civil and administrative liability for providing required information. The protection applies even if the reporter was not fully aware of the nature of the crime or whether it actually took place. It is lost only if it is proven that the report was made in bad faith with intent to harm others.
Why goAML Reports Get Rejected or Questioned
goAML reports are often rejected or questioned by the FIU for avoidable reasons. Each problem below either delays the report or prompts a request for more information. The most common problems in goAML reports are:
- Wrong report type selected
- Missing identification details for parties
- Inconsistent dates, amounts or currencies
- Narratives that do not explain the suspicion
- Attachments missing or unreadable
- Registration details or users out of date
Our goAML quality review is designed to catch wrong report types, missing data and weak narratives before submission.
Penalties for Reporting Failures
Penalties for goAML reporting failures in the UAE are both criminal and administrative. Under FDL 10/2025, Article 28, deliberately or through gross negligence failing to report a suspicious transaction is punishable by imprisonment and a fine of AED 100,000 to AED 1,000,000, or either penalty. Supervisory authorities can also impose administrative penalties under FDL 10/2025, Article 17(1), including warnings, fines of AED 10,000 to AED 5,000,000 per violation and revocation of the licence. Tipping off a customer about a report is a separate offence under FDL 10/2025, Article 29(1).
Who Needs goAML Reporting Support?
goAML reporting support is most useful for businesses that file often, face complex suspicion decisions or have had problems with past reports. The reporting duty applies to every Financial Institution, DNFBP and VASP, but the pressure points differ by sector. Typical clients include:
- Dealers in precious metals and stones filing DPMSRs
- Real estate brokers, agents and lawyers filing REARs
- Trust and company service providers and professional firms facing complex suspicion decisions
- VASPs and Financial Institutions with higher reporting volumes
- Financial Institutions and DNFBPs handling in-scope cross-border transactions linked to high-risk countries and filing HRCs or HRCAs
- Businesses with a new or part-time Compliance Officer
- Businesses that have received FIU queries or report rejections
Internal Escalation: The Step Before goAML
Internal escalation is the step between a staff member noticing something unusual and the Compliance Officer deciding whether to file a goAML report. Many goAML reporting failures happen at this stage, before the report is written. For example, a front-line employee spots a red flag but does not escalate it, or escalates it through a casual conversation that is never recorded. Our support includes designing an internal escalation process that works:
- A simple internal suspicion report form that staff can complete quickly
- Clear guidance on what to escalate and when
- A log where the Compliance Officer records every internal report received
- A documented decision for each case, whether to report to the FIU or not, with reasons
- Timelines so that decisions are made promptly and reports filed without delay
- Training so that staff know the process and understand tipping off
A documented internal escalation process gives the FIU better reports and gives your supervisor evidence that suspicions are handled consistently.
Threshold Reporting for DNFBPs
Threshold reporting for DNFBPs means filing Dealers in Precious Metals and Stones Reports (DPMSRs) and Real Estate Activity Reports (REARs). DPMSRs and REARs are the most frequent goAML filings for many DNFBPs, and both depend on accurate transaction records and customer identification.
DPMSR reporting for dealers in precious metals and stones
DPMSR reporting for dealers in precious metals and stones depends on who the counterparty is and how the transaction is paid. Dealers in precious metals and stones must track cash transactions of AED 55,000 or more with individuals and covered transactions of AED 55,000 or more with companies, which can include cash and wire transfers, under MoET Circular No. 8 of 2021 and MoET's March 2026 DPMS Guidance, section 1.4.1. The applicable FIU instruction should be checked before treating a domestic bank wire, exchange-house transfer or international wire as covered.
REAR reporting for real estate brokers, agents and lawyers
REAR reporting for real estate brokers, agents and lawyers depends on how a freehold purchase or sale is paid. Real estate brokers, agents and lawyers must identify freehold property purchases and sales paid with physical cash of AED 55,000 or more, in one or several payments, for REAR reporting. Payments in virtual assets, or with funds converted from virtual assets, are separate REAR triggers with no equivalent cash threshold stated, under MoET Circular No. 5 of 2022, MoJ Circular No. 14 of 2022 and MoET's 2026 Supplemental Real Estate Guidance. For both report types, we help you set up simple tracking registers, check that covered transactions are not missed and prepare reports correctly, so your goAML reporting stays complete and up to date.
Ongoing goAML Reporting Support
Ongoing goAML reporting support is available for businesses that want help beyond a single case. Ongoing support suits businesses with regular filings, a new Compliance Officer or a history of FIU queries. This support can be provided case by case or as part of a wider compliance support package that includes training, health checks and annual reviews.
What You Receive
Our goAML reporting services give your Compliance Officer practical outputs that can be used straight away and shown to your supervisor. The exact outputs depend on the scope agreed for your business. A typical engagement can include:
- A review of your goAML setup and reporting procedures
- Case assessment support for potential reports
- Prepared report content and narrative drafts for your Compliance Officer's approval
- Quality checks before submission
- Deadline tracking and FIU follow-up support
- Reporting templates, checklists and decision logs
- Training for your Compliance Officer on goAML reporting
File accurate goAML reports on time, every time.
Contact our team.
Engagement, Timeline and Fees
Engagement, timeline and fees for goAML reporting support are set for each case, because no two reportable events need the same amount of work. A single STR narrative takes far less time than mapping DPMSR requirements or reviewing whether HRC and HRCA reports apply. The sections below explain what we need from you, how the timeline is set and how fees are charged:
Information we need from you
Information needed for goAML reporting support starts with your requirement, such as the report you think applies, the deadline you face or the FIU query you have received. For the initial enquiry, share the report type and timing in general terms. Share identifiable case information or filed reports only where disclosure is lawful and the appropriate access arrangements are in place, given the confidentiality rules in FDL 10/2025, Article 24 and CR 134/2025, Article 19(1). Your Compliance Officer retains the reporting decision under CR 134/2025, Article 22(2), and your authorised users submit the report.
Timeline
The timeline for goAML reporting support is set by the agreed scope of work and service level agreement (SLA). Time-bound reports are planned around their filing deadlines: 24 hours for PSTRs and five business days for CNMRs and PNMRs. STRs and SARs are planned around the legal duty to report without delay. We confirm the timeline once we understand your requirement.
Fees
Fees for goAML reporting support are charged by the hour at AED 550 (USD 150) per hour. The total fee depends on the hours spent, which is driven by the number and type of reports, the volume of transactions and the complexity of the facts. Because the work is billed on time spent, you pay only for the support your case needs.
How to Get Started
Getting started with our goAML reporting support begins with understanding your requirement. Each step builds on the one before, so we understand your case before any work starts. The steps are:
- Contact our goAML team and tell us your requirement
- Share the report type and timing in general terms, and case details only where disclosure is lawful
- We assess the requirement and confirm which goAML reports apply
- We agree the scope of work, SLA and timeline with you
- We prepare and review the report content, and your Compliance Officer approves it and submits it through your goAML account
Our goAML Reporting Track Record
Our goAML reporting track record comes from hands-on work with UAE reporting entities across several sectors. The figures below summarise that work:
25+
regulatory reporting projects completed
5+
sectors served
10+
reporting mistakes avoided
Every engagement is built around the client's own facts and transactions, not reused templates.
Case study: separating PNMR and CNMR procedures
A goAML reporting case study from our work shows how the right sanctions procedure leads to the right report. A client needed to understand its Partial Name Match Report (PNMR) requirements when screening potential customers, and its existing procedure did not separate PNMRs from Confirmed Name Match Reports (CNMRs). We mapped the PNMR requirements for potential customers and set them out as a procedure separate from the CNMR procedure. The client was then able to pick the correct report and file it on time.
What our clients say about our goAML reporting services
Clients describe our work in their own words below:
"We took goAML Registration's regulatory reporting services and they helped us map our DPMSR requirements and file reports with the FIU. We are very happy with their services."
"We took their regulatory reporting services to evaluate HRC and HRCA applicability to us. They worked professionally and guided us through. Highly recommended."
Why Choose Our goAML Reporting Services
Our goAML reporting services are delivered by CAMS certified professionals. We have helped reporting entities register, set up users and file reports with the UAE FIU, and we understand the practical questions Compliance Officers face when a case lands on their desk. The team combines that hands-on knowledge with a clear understanding of current law, to help make every report timely, complete and well reasoned.
FAQs About goAML Regulatory Reporting
The FAQs below answer the questions UAE reporting entities most often ask about goAML reporting, from who decides to file to deadlines, penalties, fees and timelines. Each answer starts with the direct answer and cites the law where one applies:
Who decides whether to file an STR?
Your Compliance Officer. Under CR 134/2025, Article 22(2), the Compliance Officer assesses suspicious transaction information and decides whether to notify the FIU or retain the matter with documented reasons. We can support the assessment, but the decision always stays with the Compliance Officer.
Is there a minimum amount for filing an STR?
No. FDL 10/2025, Article 18(1) requires suspicious transactions to be reported regardless of their value. CR 134/2025, Article 18(1) applies the same rule to attempted transactions. A suspicion over a small amount must be reported in the same way as one over a large amount.
What is a PSTR in goAML?
A Postponement Suspicious Transaction Report (PSTR) is a mandatory report, from 14 December 2026, that must be filed within 24 hours where a reporting entity suspects both a criminal link and an imminent risk that the funds will be transferred, withdrawn or dissipated. After filing, the entity generally refrains from executing the transaction until three business days have passed without any FIU communication, or until the FIU authorises processing. Where the exception in Article 5(3) of UAEFIU Regulation No. 1 of 2026 applies, the PSTR is filed within two hours after execution with an explanation of why the transaction could not be held. A PSTR does not remove any separate STR duty (UAEFIU Regulation No. 1 of 2026, Articles 2(3), 5 and 6(3)). The FIU Chief's power under FDL 10/2025, Article 5(1) to order suspension for up to ten working days is separate from this initial three-business-day restriction.
What is the difference between an STR and a SAR?
Use the FIU's report instructions and the available transaction and account information to choose between a Suspicious Transaction Report (STR) and a Suspicious Activity Report (SAR). Suspicious activity or an attempted transaction may require a SAR. For the same transaction, choose the applicable report type, because CR 134/2025, Article 18(1) establishes the reporting duty, including for attempts, while the FIU materials explain which form to select.
How quickly must a CNMR be filed?
Within five business days of the freezing measure, or of rejecting a prospective customer or transaction. CR 74/2020, Article 15(2) requires any freezing measure to be notified within five business days of the freeze, and CR 74/2020, Article 1 defines the freeze without delay as within 24 hours of the listing decision. A PNMR is due within five business days of suspending an existing customer's transaction, or of rejecting a prospective customer after 10 business days without identification documents.
Is there a deadline for filing an STR in the UAE?
No fixed number of days is set for an STR. FDL 10/2025, Article 18(1) requires the FIU to be notified without delay, and CR 134/2025, Article 18(1)(a) requires notification immediately and without delay. Record the date the suspicion arose and the date the report was filed so you can show there was no delay.
What is the penalty for not filing an STR in the UAE?
Failing to report a suspicious transaction, deliberately or through gross negligence, is punishable by imprisonment and a fine of AED 100,000 to AED 1,000,000, or either penalty, under FDL 10/2025, Article 28. Supervisory authorities can also impose administrative fines of AED 10,000 to AED 5,000,000 per violation under FDL 10/2025, Article 17(1). Criminal penalties are imposed by the courts, while administrative penalties are imposed by the supervisory authority.
Can you submit reports on our behalf?
No. Reports are submitted through your goAML account by your registered users. We prepare and review the content and support your Compliance Officer throughout.
Can we tell a customer we filed a report?
No. Disclosing a report or suspicion to the customer may amount to tipping off, which is prohibited under CR 134/2025, Article 19(1) and punishable under FDL 10/2025, Article 29(1). We help you plan customer communications that manage the relationship without disclosing the report.
Do you help with HRC and HRCA reports?
Yes. We help you check whether a cross-border banking or remittance transaction is in scope and prepare High-Risk Country Transaction Reports (HRCs) and High-Risk Country Activity Reports (HRCAs). The UAEFIU goAML FAQs, Q42 to Q49, identify Financial Institutions and DNFBPs as the reporting entities, describe the qualifying jurisdiction or party connection, set no minimum amount and call for a three-working-day hold on covered transactions pending any FIU instruction. An HRC is used where the mandatory transaction details are available, and an HRCA for a reportable attempt where they are insufficient, so we check the current directions that apply to your business and transaction.
What if the FIU asks for more information?
You must respond. FDL 10/2025, Article 18(1) requires you to provide any additional information the FIU requests, and CR 134/2025, Article 18(1)(b) requires a prompt response. We help you gather and organise the information the FIU has asked for.
Should we keep records of decisions not to report?
Yes. The Compliance Officer should record the reasons for retaining a matter without reporting, as required by CR 134/2025, Article 22(2). CR 134/2025, Article 25(2) also requires records, including STRs, to be kept for at least five years, counted from the latest applicable event, such as relationship termination, account closure or a final court judgment.
How much does goAML reporting support cost?
Our goAML reporting support is charged at AED 550 (USD 150) per hour. The total depends on the hours spent, which depends on the number and type of reports, the volume of transactions and the complexity of the case. We confirm the scope of work with you before any work starts.
How long does goAML reporting support take?
The timeline depends on the agreed scope of work and SLA. Deadline-driven reports are planned around their filing deadlines: 24 hours for PSTRs and five business days for CNMRs and PNMRs. STRs and SARs are planned around the duty to report without delay. We confirm the timeline once we understand your requirement.
Is goAML reporting mandatory in the UAE?
Yes. FDL 10/2025, Article 18(1) requires Financial Institutions, DNFBPs and VASPs to report suspicious transactions to the FIU through the electronic system designated by the FIU or any other approved means. Threshold, activity and sanctions reports also apply where their triggers are met. Outside support is optional, but the reporting duty is not.
Can we handle goAML reporting ourselves?
Yes. Your Compliance Officer is responsible for the reporting decision, and your registered goAML users submit the reports. Outside support helps most when a case is complex, a deadline is close or past reports have been questioned by the FIU.