How to automate goAML reporting for STRs and SARs

Updated: 2 days ago
Filing a suspicious transaction report through goAML rarely fails because the compliance team missed the suspicion. It fails, or takes days longer than it should, because someone has to re-key customer, account and transaction data from three systems into a long web form, and one wrong field gets the report rejected.
You can automate goAML reporting for most of that work: collecting the data, mapping it to the goAML XML schema, validating it, and keeping the audit trail. What you cannot automate is the decision to report.
This guide explains how to automate goAML reporting, where that line sits, how goAML accepts reports, how to build the workflow step by step, and what the UAE Financial Intelligence Unit expects.
goAML Reporting Automation Key Takeaways |
|
|
|
|
|
|

What is goAML, and what does automating it actually mean?
goAML is the software that many Financial Intelligence Units (FIUs) use to receive and analyse suspicious transaction reports (STRs), suspicious activity reports (SARs) and other filings. It was developed by the United Nations Office on Drugs and Crime (UNODC).
Automating goAML reporting means your own systems prepare the report in the structure goAML expects, so that analysts review and approve a pre-filled, validated report instead of typing one from scratch.
Two things follow from that definition.
First, goAML is the FIU's system, not yours. Each FIU configures its own report types, mandatory fields, lookup codes and rejection rules. A report that passes validation in one country can be rejected in another.
Second, automation happens before the portal. goAML is the destination. The work of automating sits in your case management, transaction monitoring and customer data, and in how cleanly those connect to the reporting format.

Which parts of goAML reporting can be automated?
Data assembly, formatting, validation and record-keeping can be automated.
The judgement about whether activity is suspicious, the narrative that explains why, and the final sign-off should stay with a person, normally the MLRO or compliance officer. Technology can draft and check. It should not decide.
Stage | Can it be automated? | What stays human |
Detecting unusual activity | Yes: transaction monitoring and screening alerts | Tuning rules and thresholds |
Investigating the alert | Partly: evidence gathering, linked parties, history | Assessing context and reaching a conclusion |
Deciding to report | No | The MLRO's decision and its rationale |
Populating persons, entities, accounts and transactions | Yes: mapped from KYC and core systems | Spot-checking accuracy |
Writing the reason for suspicion | Partly: a draft from case notes | Editing, completing and owning the narrative |
Generating and validating the XML | Yes | Resolving exceptions |
Submitting to the FIU | Depends on the channels your FIU offers | Authorising the submission |
Tracking status, FIU queries and audit trail | Yes | Responding to FIU requests |
A useful test: if a step is about moving or formatting data, automate it.
If it is about forming or explaining a suspicion, support it with technology but keep a named person accountable.

How does goAML accept reports?
goAML accepts reports through web forms completed manually in the portal, or as XML files that follow the goAML schema and are uploaded to the portal.
UNODC also describes offline XML submission, and some FIU deployments list a business-to-business (B2B) upload feature. Which of these channels is available to you depends on how your FIU has configured its system.
Web forms suit low volumes. An analyst logs in, selects a report type, and enters every party, account and transaction by hand. This is where most manual effort and most errors come from.
XML upload is the foundation of automation. Your system produces a file that conforms to the FIU's XSD (the schema definition), and the portal validates it on upload. The UAE Central Bank's guidance for licensed financial institutions notes that goAML has an XML schema for filing batches of STRs.
There is also a middle route worth knowing about. Several FIUs allow an XML file to be loaded into the web form to pre-fill it, so the analyst reviews and completes a report instead of typing it. For a small team, this alone removes most of the re-keying.
In practice, "automated goAML reporting" usually means automated XML generation with a human approval step, not a system that files reports unattended.

How to automate goAML reporting step by step
This is an example workflow, not a mandatory regulatory procedure. Your FIU's technical documentation always takes precedence.
Get the FIU's current technical package. Download the XSD schema, schema documentation, lookup tables, sample XML files and rejection rules for your jurisdiction. Check the version: goAML 5.0 introduced changes such as hybrid reports that combine transactions and activity, and FIUs update their schemas periodically.
Map your data to the goAML model. goAML structures a report around persons, entities, accounts and transactions, with roles linking them. List every mandatory field per report type and identify which internal system holds it. The gaps you find here, such as missing passport country, incomplete signatory details or free-text transaction purposes, are the real project.
Fix data quality at source. If onboarding does not capture a field the STR requires, no reporting tool will invent it. Close the gap in KYC and KYB data collection so that the report can be populated from records you already hold.
Connect the report to the case. The report should be generated from the AML investigation case, pulling in the alert, the customer profile, the linked accounts and the selected transactions. Re-keying between a case tool and a reporting tool defeats the purpose.
Draft the narrative, then have an analyst own it. A structured draft built from case notes saves time. The final description of who, what, when, where and why the activity is suspicious needs a person who understands the case.
Validate before you submit. Run the file against the XSD and the FIU's business rules. Some FIUs publish an offline validator and written rejection rules; the goAML portal also includes a validator. Catching an error before submission is far cheaper than handling a rejection after it.
Build in approval and segregation of duties. The MLRO or an authorised deputy approves each report before it leaves the organisation. Record who drafted, who reviewed, who approved and when.
Test in the FIU's test environment where one exists. Some FIUs require it. Luxembourg's FIU, for example, asks reporting entities to submit representative XML files in its training environment and wait for approval before uploading XML in production.
Track what happens after submission. Log the acceptance or rejection, the FIU reference, and any follow-up request arriving through the goAML Message Board. Link all of it back to the case.

What does the UAE require for goAML reporting?
In the UAE, financial institutions, DNFBPs and virtual asset service providers report suspicions to the UAE FIU through goAML. The current framework is Federal Decree-Law No. (10) of 2025 and its implementing regulation, Cabinet Resolution No. (134) of 2025.
The reporting obligation applies without delay and regardless of the amount involved. The UAE launched goAML in June 2019 and was the first GCC country to do so.
Registration comes first. Guidance for licensed financial institutions says newly licensed firms should register on goAML immediately after obtaining their licence and keep the registration active.
Which report types exist on the UAE goAML portal?
Report | Purpose |
STR (Suspicious Transaction Report) | New suspicion involving one or more transactions |
SAR (Suspicious Activity Report) | New suspicion about activity or behaviour where there is no transaction to report |
AIF / AIFT (Additional Information File, without/with transactions) | Supplementary information linked to a previously filed STR or SAR |
RFI / RFIT (Request for Information, without/with transactions) | Response to an FIU request |
HRC / HRCA (High-Risk Country Transaction / Activity Report) | Transactions or activity connected to listed high-risk jurisdictions |
DPMSR (Dealers in Precious Metals and Stones Report) | Sector report for qualifying DPMS transactions |
REAR (Real Estate Activity Report) | Sector report for qualifying real estate transactions |
FFR / PNMR (Funds Freeze Report / Partial Name Match Report) | Targeted financial sanctions matches and freezing measures |
Which of these apply to you depends on your sector and supervisor. A bank, a real estate broker and a gold trader do not file the same set.

Secure Compliance Software for Real Estate
Manage property transactions, legal documents, and stakeholder verifications from a single, intuitive platform backed by the most AI technology.
What does this mean for automation in the UAE?
Four points from the Central Bank's STR guidance for licensed financial institutions shape how you design the workflow.
Choose the right report type in the logic, not by habit. STR and SAR are different report types with different data sections. Your workflow should select the type based on whether transactions are being reported.
Attachments are part of the report. The guidance treats supporting documents, such as KYC records, ID copies, account opening forms and transaction receipts, as mandatory. Automation should assemble the evidence pack along with the data.
Reasons for Reporting must match the suspicion. Filers select one or more Reasons for Reporting from a menu. The guidance warns that selecting reasons unrelated to the actual suspicion hinders FIU analysis and can lead to repeated clarification requests. Do not default these values.
You cannot edit an accepted report. Once a report is submitted and accepted, missing or incorrect information cannot be amended; a supplementary report is filed instead. That makes pre-submission validation more valuable than any speed gain.
Tipping off remains prohibited throughout. Access to report drafts and case data should be restricted to those who need it, and the automation should not trigger customer-facing communications.
Read also: UAE data residency for KYC data
Do other GCC countries use goAML?
Not uniformly. goAML is the UAE's reporting channel, but you should not assume the same system, schema or report types apply elsewhere in the Gulf.
Each FIU chooses its own platform, and even FIUs that use goAML configure it differently.
Country | FIU | Reporting channel |
UAE | UAE Financial Intelligence Unit | goAML, since 2019 (official sources) |
Kuwait | Kuwait Financial Intelligence Unit (KwFIU) | goAML. The FATF’s 2024 mutual evaluation recorded paper-based filing while goAML was being implemented; KwFIU now operates a goAML portal for STR filing. See our guide to AML compliance in Kuwait. |
Qatar | Qatar Financial Information Unit (QFIU) | Secondary sources indicate QFIU uses its own reporting system, not goAML. Confirm with QFIU |
Saudi Arabia | Saudi Arabia Financial Intelligence Unit (SAFIU) | Reports go to SAFIU; confirm the filing channel and format with SAFIU and your supervisor |
Bahrain, Oman | National FIUs | Not verified in this research. Confirm with the national FIU |
If you operate in several Gulf markets, design your reporting around a single internal case and data model with a separate output mapping per FIU. That way, a schema change in one country does not break reporting in another.
What goes wrong when goAML reporting is automated badly?
Most failures come from data quality and over-automation, not from the XML itself. The common ones:
Schema drift. The FIU updates its XSD or lookup codes and the generator is not updated, so files start failing validation.
Valid but wrong. A file passes technical validation while carrying the wrong party role, a default country, or a placeholder value. The FIU receives a report that is harder to analyse.
Template narratives. Identical boilerplate reasons for suspicion across reports tell the FIU nothing and invite follow-up requests.
Wrong report type. Filing an STR where a SAR applies, or missing a separate sector or high-risk country report that the same case also triggers.
Automating the decision. Reports generated and filed because a rule fired, with no investigation behind them. This produces defensive over-reporting and no record of human judgement.
A weak audit trail. No record of who approved the report, or of why a case was closed without one. The decision not to report needs documenting too.
Most of these failures trace back to the same two causes: fragmented data and missing review steps. Azakaw brings KYC, screening, transaction monitoring and case management into one compliance workflow, so the customer record, the alert and the investigation are already connected before anyone drafts a report.

Reports built on connected data
See how Azakaw keeps customer data, screening results, alerts and investigations in one place, so every report starts from a complete record.
What should you look for in goAML reporting software?
Look for a tool that generates reports from your investigation cases, keeps pace with your FIU's schema, validates before submission, and enforces human approval.
Converters that turn a spreadsheet into XML solve the formatting problem but leave the re-keying in place.
Questions worth asking a vendor:
Which FIUs and schema versions do you support today, and how quickly do you update after a schema change?
Does the report populate from the case, customer and transaction records, or does someone still enter data?
Which report types are covered beyond STR and SAR?
Is validation run against both the XSD and the FIU's business rules?
Can we configure maker-checker approval and restrict who sees report drafts?
How are attachments, FIU references and follow-up requests stored against the case?
Is submission by XML upload, or through another channel the FIU has approved?
Where technology like azakaw fits
The reporting step is only as good as the data and decisions that feed it. When onboarding, screening, transaction monitoring and case management sit in separate tools, the STR becomes a manual reconciliation exercise at the worst possible moment.
azakaw brings KYC, KYB, screening, risk scoring, transaction monitoring and case management into one compliance workflow, so that the customer, the alert and the investigation are already connected when a report is needed.
azakaw's regulatory reporting is fully aligned with goAML requirements, so the reports your team prepares follow the structure the FIU expects.

From alert to regulatory report
Bring KYC, screening and transaction monitoring into one compliance workflow, so the data behind every report is already connected.
Frequently asked questions
Is goAML registration mandatory in the UAE?
Reporting entities need a goAML registration to file reports with the UAE FIU, and supervisors expect it to be in place and active. Licensed financial institutions are told to register immediately after licensing, and the Ministry of Economy and Tourism states that registration is mandatory for the DNFBPs it supervises.
What is the difference between an STR and a SAR on goAML?
An STR reports a suspicion that involves transactions, and the report carries the transaction details. A SAR reports suspicious activity or behaviour where there is no transaction to include, for example, an attempted transaction that never completed. Definitions vary by FIU, so check local guidance.
How quickly must an STR be filed in the UAE?
UAE law requires reporting to the FIU without delay once suspicion is formed. Sector guidance may add detail. Treat any fixed number of days quoted by third parties as something to verify against the current law, the implementing regulation and your supervisor's guidance.
Can goAML reports be submitted through an API?
It depends on the FIU. UNODC describes web forms and XML upload as the standard channels, and some deployments list a B2B upload feature. Ask your FIU which channels it has enabled and whether you need approval before using them.
Can AI write the STR narrative?
AI can produce a first draft from case notes and structured data, which saves time. The analyst and MLRO remain responsible for accuracy and completeness, and the narrative should reflect the specific facts of the case, not generic wording.
Do we need to keep a record of reports we decided not to file?
Keeping a documented rationale for closing an alert without reporting is widely treated as good practice and is what supervisors typically look for in a review. Check your supervisor's record-keeping requirements for the specific obligation.
Automating goAML reporting: where to start
Automating goAML reporting is less about the XML file and more about what feeds it. The format can be generated in seconds. What takes time is finding the customer data, the transactions and the evidence, and getting them into a shape the FIU will accept.
That is why the order matters. Fix data quality at source, connect the report to the investigation case, validate before you submit, and keep a named person accountable for the decision and the narrative. Automate the assembly. Keep the judgement human.
For teams in the UAE, the detail to remember is that an accepted report cannot be edited. Getting it right the first time is worth more than filing it a few minutes faster.
For teams working across the Gulf, check each FIU’s reporting channel and schema before assuming that one setup covers every market.
Done well, automation gives the MLRO back the time that re-keying used to take, and gives the FIU a report it can use.
Automating goAML reporting - Video
Related articles:
Sources
United Nations Office on Drugs and Crime (UNODC), goAML Services
UNODC, UNODC publishes landmark release goAML 5.0
UAE Financial Intelligence Unit, UAEFIU Launches goAML Platform in Partnership with UNODC (June 2019)
Central Bank of the UAE Rulebook, How to Submit an STR and Other Report Types
Central Bank of the UAE Rulebook, STR guidance for licensed financial institutions: report types and amendments to submitted reports
UAE Ministry of Economy and Tourism, Register in goAML
FATF, Mutual Evaluation Report of Kuwait (2024)
Cellule de Renseignement Financier (FIU Luxembourg), XML developments for STR and SAR
NOTE: This content is provided for general informational purposes and does not constitute legal or regulatory advice. Reporting obligations, report types and goAML technical requirements vary by jurisdiction, sector and supervisor, and they change over time. Organisations should consult the applicable legislation, their FIU's current technical documentation and qualified legal or compliance professionals where necessary.






