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

Banking access is where the deal dies. In cross-border transactions involving counterparties from the Commonwealth of Independent States (CIS – the grouping of post-Soviet states, including Russia, Kazakhstan, Ukraine, Uzbekistan, Azerbaijan, Armenia, Georgia, Belarus, Kyrgyzstan, Moldova, Tajikistan and Turkmenistan), the question is rarely whether the underlying commercial relationship is legitimate. The question is whether the compliance file can demonstrate it, to the standard a Hong Kong correspondent bank or institutional counterparty will accept. When it cannot, the payment channel closes. The transaction stalls. The client begins to wonder whether the deal can happen at all.

An AML and source-of-funds file for a CIS counterparty, built to Hong Kong compliance standards and cross-referenced against the Anti-Money Laundering and Counter-Terrorist Financing Ordinance and the applicable United Nations sanctions regime, is the instrument that re-opens that channel. The file does not create legitimacy – it documents it, in the form and sequence a regulated institution needs to satisfy its own obligations.

This matter note sets out, in anonymised form, how one such file was constructed. It describes the constraint the client faced, the structure of the solution, the sequence of steps, and the lesson that travels across similar fact patterns.

The situation: a legitimate transaction without a usable paper trail

The client was an Asian trading group with an operating presence in Hong Kong and contractual relationships across several CIS states. The counterparty was a mid-sized commercial enterprise incorporated in one of the Central Asian CIS jurisdictions. The underlying transaction was the settlement of a substantial receivable – money owed under a supply contract that had run without difficulty for several years.

The problem was not the money itself. It was the gap between what the client knew about its counterparty and what the receiving bank required the client to prove. The bank's compliance team had raised a formal request: it needed a source-of-funds file covering the counterparty's beneficial ownership, the origin of the funds to be transferred, and the sanctions-nexus position. Without that file, the correspondent banking leg would not complete.

What did the client have? A copy of the commercial contract, some exchange of correspondence, and an invoice. That is a starting point, not a compliance file. The counterparty's corporate registry, while publicly accessible in principle, operated in a language the client's Hong Kong team could not use, and the documents it produced did not map cleanly onto the categories a Hong Kong-trained compliance officer would recognise.

This is a pattern our desk sees regularly. The commercial relationship is real, the funds are legitimate, but the evidentiary infrastructure that a regulated institution needs does not exist in a form the institution can process. The gap is documentary, not substantive.

What the governing rules required

Hong Kong's AML regime is set out in the Anti-Money Laundering and Counter-Terrorist Financing Ordinance (the AMLO). The Ordinance imposes customer due-diligence and ongoing monitoring obligations on financial institutions. It requires those institutions to identify and verify the beneficial owners of entities they deal with, and to satisfy themselves about the source of funds and source of wealth where risk indicators are present.

The relevant risk indicators here were geographic. CIS-origin funds carry elevated scrutiny in most compliance programmes, not because of any blanket legal prohibition, but because of the confluence of factors that financial institutions associate with that geography: sanctions exposure, politically exposed persons, the opacity of some corporate-registry systems, and correspondent-bank de-risking. None of these factors makes a CIS transaction impermissible. They make the compliance file harder to build and more important to build correctly.

Hong Kong implements United Nations sanctions and does not give domestic effect to the unilateral measures of other states. That is a legally material distinction. A payment that a US or EU institution might be unable to process for sanctions reasons may be entirely permissible through a Hong Kong channel, provided the UN-sanctions position is clean and the AMLO obligations are met. The file had to document both.

The United Nations Sanctions Ordinance was also relevant. It required confirmation that neither the counterparty nor its beneficial owners appeared on a UN-designated list, and that no designated entity or individual was connected to the transaction.

For a broader view of how our practice handles the intersection of sanctions posture and payment-channel compliance, the Sanctions & AML practice page sets out our approach.

The sequence above describes the standard position. Your matter turns on the specific documents, the jurisdictions actually engaged, and the order of steps – and that is where the route is won or lost.

For an assessment of your cross-border AML position, write to us at info@lockhartyip.com.

How was the file structured?

Building an AMLO-standard source-of-funds file for a CIS counterparty requires working backwards from the question the bank is actually asking. The bank needs to be able to complete its own risk assessment. The file should do the work for it.

The file was built in four layers.

The first layer was corporate identity. This meant obtaining, translating, and presenting the counterparty's constitutive documents – the equivalent of articles of association and the registry extract – alongside certified translations into English. The translations were accompanied by a brief explanatory note mapping the CIS jurisdiction's corporate forms to the categories a common-law compliance officer would recognise. What is called a "director" in that jurisdiction, what authority the general director holds, how the share register works – these were explained in plain terms.

The second layer was beneficial ownership. This was the most substantive exercise. The counterparty's ownership structure ran through two intermediate holding entities before reaching the natural persons who ultimately controlled the business. Each holding entity required its own documentation. Each natural person required identity verification and a search against UN-sanctions and politically-exposed-persons lists. One of the intermediate entities was incorporated in a third CIS jurisdiction, which introduced a second registry system and a second translation requirement.

The third layer was source of funds. This required tracing the origin of the receivable. The file documented the underlying supply contracts, the history of the commercial relationship, the pattern of prior settlements, and the bank statements showing that the receivable had accumulated over the course of ordinary trading activity. The narrative tied the documentary evidence to the amount in question and explained the timeline in terms a compliance officer could follow without further inquiry.

The fourth layer was the sanctions-nexus position. This comprised a documented UN-sanctions search against all named individuals and entities in the chain, a brief analysis of the applicable UN-sanctions resolutions relevant to the jurisdiction pair, and a written conclusion on the Hong Kong-law position. The conclusion noted explicitly that Hong Kong does not give domestic effect to unilateral measures and that the question to be answered was UN-sanctions status only.

The sequence and the turning point

The file was presented to the bank's compliance team not as a collection of documents but as a structured memorandum. That distinction matters. A compliance officer reviewing a folder of foreign-language documents with no explanatory thread must do the analytical work themselves. A structured memorandum does that work and presents conclusions the officer can rely on and record.

The bank's first response asked three follow-up questions. Two of them concerned the beneficial-ownership chain at the intermediate-entity level. One concerned the source of a capital contribution that appeared in the counterparty's balance sheet.

The capital contribution was the turning point. On its face, it looked like an injection of funds from a third party with no obvious connection to the counterparty's trading activity. In isolation, it was potentially a red flag. The file had not addressed it because the initial document review had not surfaced it as a live issue.

Working through the client and the counterparty, it emerged that the contribution had been made by a parent-company shareholder as part of a refinancing exercise several years earlier. The parent company was documented, the shareholder was already in the beneficial-ownership chain, and the refinancing had a commercial rationale that was straightforward to explain. The supplemental note documented the connection, presented the relevant corporate resolutions, and explained the commercial background.

The bank accepted the supplemental note. The payment was released.

The turning point was not the discovery of a problem. It was the recognition that the compliance file must anticipate the question behind the question. A bank's compliance team will not simply confirm that the documents are present. It will look for anything that does not fit the narrative. The file needs to close those gaps before they are raised, or be constructed in a way that allows gaps to be closed quickly when they are.

If an earlier filing or compliance submission produced an adverse or stalled result, a second read can identify the structural error and the routes still open. Write to info@lockhartyip.com to discuss the position.

The transferable lesson

Three points travel from this matter to similar fact patterns.

First, the compliance file is not a disclosure exercise – it is a risk-assessment exercise done on behalf of the institution. The goal is not to hand over documents and wait. The goal is to produce a file that allows the institution's compliance officer to close their own file with confidence. That means anticipating the questions, explaining the foreign-law concepts, and mapping the ownership and funds trail in a way that is legible to a common-law-trained reviewer.

Second, CIS-origin files have specific structural challenges that need to be planned for at the outset. Registry systems vary significantly across CIS jurisdictions. Some are well-organised and produce documents in forms that translate cleanly. Others require more interpretive work. Corporate forms do not always correspond to their common-law equivalents. Beneficial-ownership chains often run through multiple intermediate jurisdictions, each with its own documentation requirements. Politically-exposed-person searches need to be adapted to the political landscape of each jurisdiction, not applied by rote from a global list. These are manageable challenges – but they need to be managed, not discovered mid-process.

Third, the Hong Kong / CIS cross-border interface has a specific legal characteristic that can be used to a client's advantage: Hong Kong's sanctions posture. Because Hong Kong implements UN sanctions and does not apply the unilateral measures of other states, there is a category of transactions that cannot move through a US-dollar correspondent channel but can move lawfully through a Hong Kong channel. That is not a circumvention strategy. It is a straightforward consequence of the applicable legal rules. Recognising it, and documenting the position correctly, is part of the compliance work.

For comparison with the approach taken in a related matter involving an offshore holding structure, see our matter note on the Cayman Islands counterparty file. For the approach to sanctions due-diligence in a deal context, see the BVI sanctions due-diligence matter note.

Related practices

Related practices

• Sanctions & AML – source-of-funds, counterparty due diligence, and compliance file construction
• Holding Structures – offshore and Hong Kong holding entity review for AML-sensitive transactions

Speak with Lockhart & Yip

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

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