Matter note: an AML and source-of-funds file for the UAE counterparty

When a cross-border transaction stalls at the banking stage, the problem is rarely the deal itself. It is the file. For a Hong Kong group contracting with a UAE-based counterparty, the Anti-Money Laundering and Counter-Terrorist Financing Ordinance sets out what must be established about a customer or a counterparty – and a correspondent bank's own compliance desk will apply its own overlay on top of that. The gap between "we know who this is" and "we can demonstrate who this is, in a form the bank will accept" is where deals die.

An AML and source-of-funds file (a structured compliance dossier demonstrating the identity, beneficial ownership, source of wealth and source of funds of a counterparty) is governed principally by the Anti-Money Laundering and Counter-Terrorist Financing Ordinance, with supplementary standards drawn from the Financial Action Task Force recommendations and the relevant regulators' AML guidelines. Where the counterparty is UAE-incorporated, the file must also address the UAE's own anti-money laundering regulatory environment, which has evolved considerably since the UAE's removal from the FATF grey list in 2024. The matter described below illustrates how the sequencing of that file – not the underlying commercial relationship – determined whether the transaction could proceed.

This note covers the situation and the constraint, the cross-border issue and the route chosen, the sequence and the point at which the matter turned, and the transferable lesson for advisers handling similar mandates.

The situation: a Hong Kong principal, a UAE counterparty, and a stalled payment

A mid-market trading group incorporated in Hong Kong had contracted with a UAE counterparty for the supply of industrial goods. The transaction was straightforward on its face: a commercial sales agreement, a purchase price denominated in US dollars, a payment mechanism through a Hong Kong correspondent bank. The counterparty was a UAE limited liability company (an LLC, the standard form of UAE private commercial entity, analogous to a private company in common-law systems) with a short operational history and a structure that included a holding layer in a Gulf-based free zone.

The Hong Kong bank declined to process the payment. The stated reason was a request for additional customer due diligence documentation on the UAE counterparty, specifically around the identity of the ultimate beneficial owner (UBO) – the natural person who ultimately owns or controls the entity – and the source of the funds being used to make payment on the other side of the transaction. The bank did not allege wrongdoing. It applied its standard compliance review before releasing funds through the correspondent chain.

The window was narrow. The commercial contract included a payment deadline. A missed deadline risked triggering a force majeure clause on the UAE side and, in turn, a dispute over whether the Hong Kong group had performed its payment obligation. The compliance problem had become a contractual risk, and it was becoming more acute by the day.

In our cross-border AML practice, this pattern – a stalled correspondent bank, a hard deadline, and an incomplete counterparty file – appears with regularity. The underlying cause is almost always the same: the file was assembled to satisfy the internal KYC process of the Hong Kong contracting entity, not the standards of a correspondent bank processing an international dollar payment.

The cross-border issue: two regulatory environments, one file

The compliance obligation on the Hong Kong side is framed by the Anti-Money Laundering and Counter-Terrorist Financing Ordinance, which requires that a regulated institution (a bank, broker, or other licensed entity subject to the Ordinance) conduct customer due diligence including beneficial ownership verification. The bank processing the payment was the regulated institution; the Hong Kong trading group was its customer. The UAE counterparty was a third-party payee – but a payee about whom the bank needed to be satisfied before it would release the funds.

Correspondent banking adds a second layer. The Hong Kong bank was clearing through a US correspondent. That correspondent's own compliance programme – operating under its home-state AML rules – imposed a further overlay. The result was a file requirement driven by three regulatory environments simultaneously: Hong Kong, the UAE, and the intermediary jurisdiction through which dollars settle.

The UAE side presented its own dynamics. The UAE's Federal Decree-Law on Anti-Money Laundering and the rules issued by the UAE's regulatory authorities impose UBO disclosure obligations on UAE companies. Since the UAE's removal from the FATF grey list, its domestic AML infrastructure has deepened, and international correspondent banks have updated their country-risk assessments accordingly. That is, on balance, a positive development – but it means the file must reflect current UAE UBO registry standards, not the older assumptions that shaped some internal KYC templates still in use by trading groups.

The structural complexity here was real. The UAE counterparty's holding layer sat in a free-zone entity. Free-zone companies in the UAE operate under their own licensing and governance frameworks, distinct from mainland UAE commercial law. UBO disclosure obligations apply, but the documentary evidence required to prove that ownership chain to a non-UAE bank often requires a more detailed explanation than the registry extract alone provides.

The route chosen: file architecture before re-submission

The Hong Kong group's initial instinct was to re-send the documents already provided. We advised against this. Re-submitting the same file to the same compliance desk, without addressing the identified gaps, typically prolongs the delay rather than resolving it. The bank had already reviewed the materials. What was needed was a structured file that answered, in sequence, each of the questions the bank's compliance team had either raised explicitly or was likely to raise next.

We mapped the file against the bank's publicly stated customer due diligence standards and the relevant AML guidelines applicable to the bank's Hong Kong operations. The gaps were identifiable: the UBO chain had not been documented to the natural-person level, the free-zone holding entity had not been explained in terms a compliance officer unfamiliar with UAE free-zone structures would recognise, and the source-of-funds narrative – the explanation of where the payment funds originated – was absent.

The file architecture we built had four components.

First, a corporate structure diagram tracing the ownership chain from the UAE LLC through the free-zone holding entity to the natural-person UBOs, with each layer identified by jurisdiction of incorporation, governing law, and the documentary evidence available to substantiate it.

Second, a source-of-wealth narrative (an account of how the UBOs accumulated the capital behind the entity) supported by independent documentary evidence: audited accounts where available, and a coherent chronological account of the business activity that generated the relevant wealth. This is the element most often absent from files assembled under time pressure.

Third, a source-of-funds statement (a specific account of the origin of the funds used to pay in this particular transaction, distinct from the general source-of-wealth question), with bank statements and business records tracing the payment funds to an identifiable commercial origin.

Fourth, an explanatory memorandum addressed to the bank's compliance desk, written in the register of a compliance professional rather than a legal pleading, that placed the UAE free-zone structure in context, noted the applicable UAE UBO disclosure regime, and drew the reader's attention to the specific evidence in the file that answered each identified question.

The sequence mattered. Presenting the memorandum first, before the supporting documents, allowed the compliance desk to read the file as an organised narrative rather than a document dump. This is a consistent finding across the cross-border files our desk has prepared: a well-sequenced file is processed faster than a comprehensive but unordered one.

The turning point: substance over volume

The bank had received, in prior rounds, a substantial volume of documentation. The turning point was not adding more documents. It was the explanatory memorandum and the source-of-funds chain.

The compliance desk raised one further query after the re-submission: a request for clarification on the relationship between two entities in the UAE structure that shared a common name but appeared to be legally distinct. This was a legitimate question. The file had not addressed it because the Hong Kong group had not, until that point, identified it as a potential point of confusion.

We prepared a short supplemental note addressing the two entities – their incorporation dates, their respective roles, and the reason both appeared in the corporate documents. The query was resolved within the bank's standard review cycle. The payment was released before the contractual deadline.

The lesson here is precise: correspondent bank compliance desks are not trying to prevent legitimate transactions. They are trying to satisfy their own regulatory obligations. A file that makes that task straightforward – by answering the likely questions before they are asked, and by explaining what is unfamiliar rather than assuming familiarity – will almost always move faster than one that is technically complete but practically difficult to review.

If an earlier compliance submission has stalled or produced a request for further information, a second read of the file can identify the structural gap before re-submission. For a considered view on your matter, contact our Sanctions & AML practice at info@lockhartyip.com.

The transferable lesson: what the UAE counterparty file must address

Several elements of this matter recur across the cross-border AML files our desk handles. They are worth setting out for the adviser encountering this position for the first time.

The UBO chain must reach a natural person. A file that stops at the LLC or the free-zone holding entity is incomplete. The bank needs to know who, in the end, owns and controls the structure – and it needs documentary evidence, not a representation alone.

Free-zone structures require explanation. UAE free zones operate under distinct regulatory regimes. A compliance officer in Hong Kong, Singapore, or a European clearing centre may not be familiar with the governance documents applicable to a DIFC, ADGM, or JAFZA entity, for example. The file should explain the structure rather than assume the reader will look it up.

Source of wealth and source of funds are different questions. Both must be answered. A file that addresses one but not the other will generate a follow-up request. Preparing both at the outset saves the additional cycle.

The explanatory memorandum is not optional. Banks receive large volumes of documentation. A memorandum that guides the compliance desk through the file – identifying what each document is, what question it answers, and where in the file it sits – is the single most effective tool for accelerating review.

Timing matters in two directions. A file submitted under acute contractual deadline pressure is more likely to be re-submitted in an unstructured form. Building the file correctly before the first submission is almost always faster than correcting a deficient file after the bank has already reviewed and queried it. Where a deadline is already close, the most efficient path is a single, complete, well-sequenced re-submission rather than a sequence of supplemental responses to successive queries.

For advisers handling related CIS-counterparty files or preparing a compliance review before contracting with an offshore entity, the approach is consistent: see our guide on AML and source-of-funds files for CIS counterparties and our guide on compliance review before contracting with a Cayman Islands entity.

Common objections: what foreign counsel sometimes get wrong

There is a recurring assumption among advisers unfamiliar with correspondent banking compliance that a clean corporate structure – legitimate shareholders, no adverse regulatory history, proper incorporation documents – is sufficient to satisfy an AML review. It is not. The compliance desk is not reviewing the structure for legality. It is reviewing the file for completeness and coherence.

A second assumption is that once a bank has processed a payment for a counterparty, future payments in the same relationship will proceed automatically. This is not the position. Correspondent banking compliance reviews can apply to each payment instruction, and a bank's risk assessment of a counterparty may change as country-risk frameworks are updated. The UAE's removal from the FATF grey list has, on balance, reduced country-risk friction for UAE counterparties – but the file obligation does not disappear.

A third assumption, and perhaps the most consequential, is that the compliance obligation rests solely with the bank. In practice, the contracting entity – the Hong Kong group, in this case – bears a practical interest in the outcome because the payment stall creates contractual risk for the group, not for the bank. The bank can decline to process. The group faces the consequences of non-payment. This asymmetry means that managing the AML file is in the commercial interest of the Hong Kong contracting party, not merely a regulatory formality for the bank.

In our cross-border practice, we regularly advise Hong Kong groups and their in-house teams on preparing counterparty files that anticipate the bank's compliance requirements rather than reacting to them. The earlier the file is built into the contracting timeline, the lower the risk of a payment-stage stall.

Related practices

• Sanctions & AML – counterparty compliance, source-of-funds files, and AML documentation
• Corporate Counsel – cross-border contracting and governance for international groups

Speak with Lockhart & Yip

For a scoped view of your matter, contact info@lockhartyip.com. Discuss your matter →

Related

• Sanctions Aml
• Aml Source Funds File Cis Counterparty Cis Guide 2
• Compliance Review Before Contracting Cayman Islands Entity Cayman 4

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@lockhartyip.com.