The name is often read as "go anti money laundering". UNODC titles the product "goAML (Anti-Money-Laundering System)", and its goAML pages do not spell out the "go", a prefix shared with goCASE and goPRS in the goPortfolio suite. The other misreading is a single UN database. Each FIU runs its own installation, customized to local requirements, and the software is governed jointly by member states and UNODC.
What is goAML?
goAML is software developed for FIUs, one of UNODC's strategic responses to money laundering and terrorist financing, built by its IT service with its global program against money laundering (GPML). Inside the FIU it takes reports from receipt through analysis to intelligence for law enforcement.
A reporting firm sees one part: goAML Web, the FIU's platform for registration, reports and messages. For the firm, goAML is the last step of filing a SAR or STR, after the suspicion, the decision and the sign off. UNODC's goAML site counts over 70 member states and over 500,000 active users (November 2026).
A goAML report that fails the schema check or is rejected has not been filed: Malta's FIAU says such a report is not considered submitted, and South Africa's FIC gives no extra time to fix it, so the clock that started with the suspicion keeps running while the XML is corrected.
How is a report filed in goAML?
Picture an illustrative Maltese money transfer firm that suspects one cash transfer abroad. Under the FIAU's XML specification 13.1, the transfer has a From side and a To side: the sender, a customer, is "my client", the recipient "not my client", and with no account both are person elements. The upload belongs to one reporting entity and carries one report type, here an STR.
UNODC's goAML services page lists three routes in: web forms on the FIU's goAML website, XML upload through the portal and offline XML, such as email attachments. Malta's FIAU offers registered firms the first two.
Luxembourg's CRF, in its 2026 guidelines, strongly recommends that regular or bulk filers export straight from their own systems to XML. complead, formerly Sanction Scanner, submits SAR, STR and CTR filings directly to FinCEN, MASAK, FINTRAC and FIUs on goAML; a person on the firm's team reviews and signs before submission.
Which report types does goAML take?
UNODC's standard set covers suspicious transaction or activity reports, cash transaction reports (in the US, the currency transaction report), electronic funds transfer reports including international transfers, and list based reports, such as hits on lists of known terrorists.
Malta's FIAU has its own report types, among them STR and SAR, terrorism financing and PEP versions of each, call for action reports (CFAR and CFATR) on links to non reputable jurisdictions, a suspected cash restriction breach report, a pending transaction report (TRN) and an additional information report (AIF). UNODC built the additional information feature so an FIU can ask for follow up data, such as a transaction history, which arrives in XML.
How does goAML registration work?
Registration comes before the first report. Under the CRF's guidelines, a Luxembourg firm first registers as a reporting entity on goAML Web and names at least one compliance officer. Once the CRF approves, the ID in its confirmation email lets other staff register as users under the entity. Access needs a LuxTrust certificate, the CRF's filing page adds.
Malta requires every subject person to register before reporting anything. Luxembourg's training environment takes its own registration, and the CRF does not consider reports sent there. Steps differ by FIU, so each FIU's own site is the guide.
Which FIUs use goAML?
| FIU | System | How reports go in | Source |
|---|---|---|---|
| UAE Financial Intelligence Unit | goAML | STRs, SARs and other report types through the FIU's goAML portal | FIU home page, capture of 1 November 2026 |
| Malta, FIAU | goAML since June 2020 | Web reports or XML upload, after registration | FIAU reporting page and rejection rules, December 2025 |
| Luxembourg, CRF | goAML only | Online form or XML upload, with a LuxTrust certificate | CRF filing page, 1 September 2026 |
| Kuwait, KwFIU | goAML, required for all reporting entities | STRs through the platform | Central Bank of Kuwait guidance for banks, May 2025 |
| Portugal, UIF | goAML from 13 April 2026 | Suspicious transaction reports straight into the portal | UIF notice, 16 March 2026 |
| South Africa, FIC | goAML, its registration and reporting system | Web reports and batch XML | FIC goAML Notice 04A, 10 November 2020 |
| United Kingdom, UKFIU at the NCA | SAR Portal, not goAML | SARs through the SAR Portal | NCA SAR page |
| United States, FinCEN | BSA E-Filing, not goAML | Financial institutions file only electronically through BSA E-Filing | FinCEN filing information |
Which FIUs take reports on goAML (as of November 2026).
UNODC shows the countries using goAML on a map image with no text list, so the table holds FIUs that name goAML on their own pages. The UK and the US run their own systems: UK reporters file SARs through the NCA's SAR Portal, and US institutions file through FinCEN's BSA E-Filing System.
Why are goAML reports rejected?
| Rule | What the FIAU checks | Field | Note |
|---|---|---|---|
| R1 | At least one indicator each for amount, predicate offense, its location and product | Report indicators | Plus at least one reason for suspicion indicator; location not needed when the offense is "Unknown" |
| R3 | Every transaction has exactly two parties | From and To sides | Multi party transactions are not accepted |
| R4 | Local currency is EUR | currency_code_local | XML uploads; a foreign amount keeps its own code and the day's rate |
| R5 | A non client's account names at least one entity or signatory | t_entity or signatory | The account holder's name as the firm has it |
| R6, R7 | No post dated transaction and no zero amount | date_transaction, amount_local | Post dated payments are not accepted on submission |
| R10, R11 | Date of birth filled in, never 01/01/1900 | Involved person | R11 covers clients in transaction reports |
| R12 | Nationality of clients given, not "UNKNOWN" | Involved person | Not applied to remote gaming |
| R13 to R15 | Reason for suspicion, internal reference, supporting documents | reason, entity_reference, attachments | R13 exempts AIFs; specification 13.1 requires a reason in every XML report |
| R16 | Report key of the earlier report on AIF and TRN reports | fiu_ref_number | The key comes on the message board |
Why goAML reports bounce: one FIU's published rejection rules (FIAU Malta, December 2025).
A report passes two gates. The first is the schema: an XML upload with structural errors shows "Failed Validation", a status web reports never get, because the web form always gives them a correct structure. The second is the FIU's business rules: automated rules flag a report, and the FIAU's screening officer can reject it with the reason, marking it "Rejected". UNODC builds the same intake check into goAML, which returns invalid data for correction.
The table is Malta's set. South Africa's FIC applies its own goAML schema and business rules, and asks firms to pre validate batches in house instead of using goAML as the test.
How is a rejected goAML report fixed?
At South Africa's FIC, a submitted report cannot be changed, and the fix depends on the route. A rejected web report is reverted to the drafts, corrected along the reasons on the message board and submitted again; filing a new one would create a duplicate. A rejected batch is corrected in the original XML, with the old Report ID in the fiu_ref_number field and a comment on each transaction describing the fix. Malta's schema has an optional field, prev_rejected_ref_number, for the earlier report's reference. The FIC allows no extra time for any of it.
Where does goAML sit in an AML program?
goAML ends the reporting duty, and the compliance officer named at registration owns it. Seven habits keep reports moving:
- Register before the first suspicion. Malta and Luxembourg require it.
- Keep officers and users current. The CRF expects working access.
- Test in the training environment. Reports there do not count.
- Map client data to the fields that bounce. Malta checks date of birth, nationality and account holders.
- Pre validate XML in house. The FIC is not the test.
- Keep every report key. AIF and TRN reports and fixes cite it.
- Read the message board. Rejection reasons and report keys arrive there.
Which goAML dates mattered in 2026?
- 1 January. Luxembourg's CRF replaced its feedback form on each report with a quarterly feedback report, sent through the goAML message board.
- 12 January. Malta's XML specification 13.1 took effect and made the report's reason field mandatory.
- 13 April. Portugal's UIF moved suspicious transaction reports onto its new goAML portal, where obliged entities and sector authorities now file directly.
- 15 September. The CRF's new guidelines applied in Luxembourg, replacing those of 6 January 2026; the main change is new deadlines for answering the CRF's requests for information, and reports still go only through goAML.
What has to be in the report itself before any FIU, on goAML or not, can act on it? A clean upload proves only the format. The facts, the narrative and the reason for suspicion have to stand in the suspicious activity report itself, whatever portal carries it.
Related terms
- Currency transaction report. A US filing to FinCEN when one person's cash transactions top $10,000 in a business day; goAML's standard list calls the type a cash transaction report.
- Electronic funds transfer. A transfer begun at a terminal, phone or computer that tells an institution to debit or credit an account; UNODC lists EFT reports, international transfers included, among goAML's standard types.
- MLRO. The officer who takes in staff suspicions of money laundering and decides which ones reach the authorities.