Offshore Transfers
In a Nutshell
- Offshore transfers trigger STR and SAR obligations when the choice of destination is motivated by jurisdictional opacity rather than legitimate commercial purpose.
- HRC (High-Risk Country Transaction Report) is relevant when an offshore transfer involves a FATF black-listed jurisdiction at the transaction level.
- HRCA (High-Risk Country Activity Report) is relevant when broader business activity or customer relationships involve FATF black-listed countries across an ongoing pattern.
- All four report types may apply simultaneously to a complex offshore transfer scheme; the STR obligation arises first from reasonable suspicion.
- The STR filing obligation under Cabinet Resolution No. 134 of 2025, Article 18 has no minimum value; reasonable suspicion from the transfer routing or beneficial ownership analysis is the sole trigger.
Offshore transfers are among the most complex money laundering typologies for compliance teams to navigate because the activity is distributed across multiple jurisdictions, correspondent chains, and corporate layers, all of which are designed to obscure the origin of the funds. The goAML reporting obligations that arise from offshore transfer activity depend on what the transfer involves: the jurisdictions it passes through, the beneficial ownership structures behind it, and whether the routing reflects genuine commercial purpose or deliberate opacity.
Applicable goAML Report Types: STR, SAR, HRC, and HRCA
Four goAML report types are potentially relevant to offshore transfer activity:
STR (Suspicious Transaction Report)
The STR is filed when a completed or attempted offshore transfer creates reasonable suspicion of money laundering, terrorism financing, or other financial crime risk. No minimum value applies. A transfer to an offshore entity in a secrecy jurisdiction, routed through two intermediary banks, whose stated purpose cannot be verified against the customer’s declared business, creates STR-level suspicion regardless of the transfer amount. The obligation under Article 18 of Cabinet Resolution No. 134 of 2025 is to file without delay once suspicion is identified.
SAR (Suspicious Activity Report)
The SAR is filed when offshore transfer-related suspicious behaviour is identified outside a specific completed transaction. This includes a customer refusing to explain the beneficial ownership structure behind an offshore counterparty, an entity providing conflicting information about the purpose of recurrent offshore payments, or the identification of a nominee arrangement during ongoing CDD review that suggests a deliberately obscured offshore relationship.
HRC (High-Risk Country Transaction Report)
The HRC is filed when an offshore transfer involves a transaction with a country classified by FATF as high-risk and subject to a call for action (black-listed). The HRC is a transaction-level report; it covers the specific payment that passes through or terminates in the black-listed jurisdiction. The filing trigger is the involvement of a FATF black-listed country, independently of whether any additional suspicious indicators are present.
HRCA (High-Risk Country Activity Report)
The HRCA is filed when broader business activity or customer relationships involve FATF black-listed countries across an ongoing pattern rather than a single transaction. When a correspondent banking relationship, a corporate customer’s operating structure, or a trust vehicle’s jurisdiction of administration involves a FATF black-listed country as a sustained element of the business relationship, the HRCA captures the activity-level exposure that the HRC does not cover at the transaction level.
Are You Managing Offshore Transfer Risk Without Delay?
The STR obligation arises from reasonable suspicion, with no minimum value threshold, so timing and documentation matter.
Relevance Assessment: When Each Report Type Applies to Offshore Transfers
← scroll to see full table →
| Offshore Transfer Scenario | Applicable Report Type(s) |
|---|---|
| Transfer to an offshore secrecy jurisdiction with no verified commercial purpose; beneficial ownership unclear | STR (suspicion-driven; file without delay) |
| Transfer routed through a FATF black-listed country as a transit or destination jurisdiction | HRC (transaction-level) + STR if suspicion also present |
| Customer relationship involving ongoing activity connected to FATF black-listed jurisdictions across multiple transactions or entities | HRCA (activity-level) + STR if suspicion present |
| Customer refuses to explain purpose of offshore transfers; nominee structure identified during CDD but no completed transaction yet | SAR (suspicious activity without completed transaction) |
| Complex offshore transfer chain involving black-listed country transit, nominee corporate structure, and unverifiable beneficial ownership | STR + HRC + HRCA all may apply simultaneously |
Filing Sequence When Multiple Report Types Apply
Where an offshore transfer triggers both an STR and an HRC, both reports must be filed through goAML. The STR arises from reasonable suspicion under Article 18 of Cabinet Resolution No. 134 of 2025 and must be filed without delay. The HRC arises from the involvement of a FATF black-listed jurisdiction and is filed as a separate report covering the transaction-level high-risk country exposure. The HRCA covers the broader activity or relationship pattern where the customer’s ongoing business involves a black-listed jurisdiction.
Filing one report does not satisfy the obligation to file the others. Each report type covers a distinct dimension of the risk: STR covers suspicion, HRC covers transaction-level country risk, HRCA covers activity-level country risk. Compliance teams should document which report types were considered for each offshore transfer event and which were filed, with the rationale.
Correspondent Banking and SWIFT Chain Opacity
A significant proportion of offshore transfers involving UAE institutions move through correspondent banking chains in which the institution processing the payment sees only the correspondent bank’s SWIFT message, not the underlying customer of the offshore respondent institution. This structural opacity means that the UAE institution may be processing an offshore transfer without visibility into the beneficial owner behind it.
The STR obligation requires that when an institution suspects, based on the available information, that a transfer may involve money laundering, it files without delay. Correspondent chain opacity that makes it impossible to verify the beneficial owner does not remove the STR obligation; it may itself be the suspicious indicator that triggers it.
STR Narrative Requirements for Offshore Transfer Cases
The goAML STR narrative for an offshore transfer case must include: the full routing path of the transfer including all intermediary institutions and jurisdictions; the stated purpose of the transfer and the analysis of whether it is consistent with the customer’s declared business; the beneficial ownership structure behind the offshore counterparty and the extent to which it was verifiable; the specific indicators that created the suspicion conclusion; and the time period covered by the analysis. The FIU uses STR narratives to build financial intelligence pictures; a narrative that covers only the transaction without addressing the routing chain and beneficial ownership analysis provides limited utility.
Are Your Offshore Transfers Raising Red Flags?
Offshore transfers can trigger STR obligations when routing, ownership, or destination jurisdiction suggests opacity rather than a clear business purpose.
Register on goAML for Offshore Transfer Reporting
Managing STR, HRC, and HRCA reporting obligations for offshore transfer activity requires goAML registration and a reporting programme that distinguishes between suspicion-driven obligations and country risk-driven obligations. Contact goAML Registration for advisory support on offshore transfer reporting workflows.
Frequently Asked Questions
No. The HRC is triggered by FATF black-listed jurisdictions (those subject to a call for action), not grey-listed jurisdictions. Transfers involving grey-listed jurisdictions are a risk factor that may contribute to an STR suspicion assessment, but they do not independently trigger an HRC. Transfers involving FATF black-listed jurisdictions trigger an HRC regardless of whether additional suspicious indicators are present.
The HRCA should be filed when the exposure to a FATF black-listed jurisdiction is an ongoing relationship or activity characteristic rather than a single transaction. If a customer’s entire business model involves regular dealings with entities in a black-listed jurisdiction, the HRCA captures that activity-level exposure. The STR is filed in addition if any of those dealings create reasonable suspicion of money laundering. The two reports address different dimensions and are not substitutes for each other.
The STR obligation arises at the point at which the compliance team reaches a reasonable suspicion conclusion, not at a specified stage in the transaction lifecycle. If suspicion is identified before the transfer is executed, the institution should consider whether to proceed, and should file the STR without delay. If suspicion is identified post-execution, the STR must be filed without delay from that point. Tipping off the customer by returning funds or notifying them of a review before the STR is filed is a criminal offence under Article 29 of Federal Decree-Law No. 10 of 2025.