Build UAE goAML STR/SAR (XML)

Skill: Convert suspicious-activity case data into a goAML STR/SAR report

Region: United Arab Emirates (الإمارات العربية المتحدة) Category: AML / regulatory — goAML (FIU) Does: Takes a suspicious-activity case and assembles the goAML XML report — a Suspicious Transaction Report (STR) or Suspicious Activity Report (SAR) — that UAE reporting entities submit to the Financial Intelligence Unit (FIU) at the Central Bank (CBUAE) through the goAML portal. Spec: UNODC goAML XML schema (~v5.x) as adopted by the UAE FIU

goAML is the UNODC anti-money-laundering reporting platform used by the UAE FIU (and many FIUs worldwide — so this pattern also applies to Germany's FIU and others). Reporting entities (banks, exchange houses, DNFBPs, etc.) must register on goAML and file STRs/SARs (and other report types: FFR, DPMSR, etc.) when they suspect money laundering or terrorist financing. The element structure below follows the goAML report schema.

When this applies

• A reporting entity that knows or suspects that funds/transactions relate to proceeds of crime or terrorist financing must file an STR (transaction-based) or SAR (activity-based) without tipping off the subject, promptly upon forming the suspicion.
• Other goAML report types exist (e.g. high-value dealer reports); this skill covers the STR/SAR core.

Structure (goAML report → XML)

report
  rentity_id, rentity_branch          reporting entity ID + branch (FIU-assigned)
  submission_code (E = electronic), report_code (STR / SAR)
  entity_reference, FIU_ref_number
  reason                              the suspicion narrative / grounds
  action / reporting person          the compliance officer submitting
  transaction (for STR) — repeating:
     transactionnumber, date, amount_local (AED), transmode
     t_from / t_from_my_client        originator (account/person/entity)
     t_to   / t_to_my_client          beneficiary (account/person/entity)
  activity (for SAR)                  involved parties + accounts without a completed transaction
  involved parties:
     person: name, DOB, nationality, ID document(s) (Emirates ID/passport), address
     account: institution, account number, currency
     entity: name, registration, address
  goods_services / addresses          as applicable

Data rules

• STR vs SAR: an STR is built around one or more transactions (with from/to parties and amounts); a SAR reports suspicious activity/parties where a transaction may not have completed — choose the right report_code and populate the matching block.
• Identify all involved parties fully: persons (name, DOB, nationality, ID documents), accounts (institution, number, currency), and entities (registration) — weak party identification is the main quality failure.
• The reason/narrative is central: clearly state the grounds for suspicion (the indicators, the unusual pattern, why it's inconsistent with the customer profile) — factual and specific.
• Amounts in AED (with original currency where relevant); transaction dates and modes (transmode) coded per the schema.
• No tipping-off: the report is confidential to the FIU; do not disclose to the subject.
• Validate against the FIU's goAML schema version and the portal's accepted code lists before upload; the FIU returns an acknowledgment/reference.

Worked example (STR — outline)

report: rentity_id=98765, report_code=STR, submission_code=E, FIU_ref=...
reason: "Multiple structured cash deposits just under the reporting threshold over 5 days,
         inconsistent with the customer's declared business; rapid transfer out to a high-risk
         jurisdiction." (grounds for suspicion)
transaction 1: date 2025-05-10, amount_local 45,000 AED, transmode = cash deposit
   t_from_my_client: person — Ali Hassan, DOB 1988, nationality ..., Emirates ID ...
   t_to_my_client:   account — Bank X, AE.. IBAN
reporting person: MLRO (compliance officer)

Emitted as the goAML STR XML and uploaded to the FIU goAML portal.

Validation checklist

• Correct report_code (STR vs SAR) and reporting-entity ID/branch; current FIU goAML schema version
• Transaction block (STR) with from/to parties and amounts, or activity/party block (SAR), populated correctly
• All involved persons/accounts/entities fully identified (IDs, DOB, nationality, account details)
• Reason/narrative states specific, factual grounds for suspicion
• Amounts in AED (+ original currency where relevant); dates and transmode coded per the schema
• Confidentiality preserved — no tipping-off of the subject
• Schema-validated against the FIU's accepted version/code lists; submitted via the goAML portal; acknowledgment retained

Last updated: 2026-05-31 — the goAML schema version and FIU code lists change; confirm the current goAML schema, report types/codes, and submission rules against current UAE FIU / CBUAE goAML guidance before use. (The same goAML pattern applies to other FIUs, e.g. Germany.)