html
Banks rarely explain why they close an account. A letter arrives — formal, brief, offering little beyond a date by which funds must be transferred elsewhere. No allegation. No specific concern named. Just a decision, presented as final.
In thirty years of working with international structures, I have watched this happen to businesses that were entirely lawful, well-run, and genuinely surprised. The instinct is to call a lawyer. But the problem, almost always, is not legal. It is architectural.
When a compliance team reviews a corporate client, they are not reading the business. They are reading the construction around it.
They see legal entities — how many, where registered, why those jurisdictions. They see ownership chains — how control flows from person to entity to entity to account. They see financial flows — which direction money moves, between which legal entities, under what stated rationale. And they see the overall picture: whether all of these elements tell a coherent story, or whether they produce a mosaic that resists easy interpretation.
A business that makes perfect sense from the inside — where the owner knows exactly why each entity exists, why that jurisdiction was chosen, why money moves in that particular direction — can look entirely different from the outside. Banks do not have access to the history. They do not see the reasoning behind each decision. They only see the result.
And when the result is opaque, banks draw their own conclusions. Those conclusions are almost invariably conservative.
Over the years, I have noticed that accounts are rarely closed for one isolated reason. What actually triggers the decision is a convergence of signals — each of which, alone, might have been manageable. Together, they produce a picture that the bank decides it is not comfortable holding.
Mixed risk profiles within the same perimeter. A group that handles conventional trade alongside cryptocurrency transactions, or that has clients in ordinary commercial sectors alongside clients in higher-risk jurisdictions, often finds these activities sitting inside the same corporate structure. From inside the group, this is simply the reality of how the business developed. From the bank's compliance desk, it looks like elevated exposure that cannot be easily separated or explained.
Offshore entities without visible economic logic. Holding companies in jurisdictions with no obvious connection to where the business operates, or subsidiary structures whose function is not immediately apparent from the documents the bank holds, generate questions that most banking relationships cannot sustain indefinitely. A bank that cannot understand why a particular entity exists will eventually decide it does not want to find out.
A cryptocurrency layer that exists alongside the main structure rather than within it. This is the pattern I encounter most frequently. A client has a legitimate business, a sound banking relationship, and — separately — some cryptocurrency activity: a wallet, an occasional transaction with a crypto counterparty, perhaps a portion of working capital held in digital assets. None of this is problematic in itself. But if the crypto layer is not embedded in the corporate architecture — if it is simply adjacent, informal, without a defined role and a coherent explanation — it becomes a flag that colours how the bank reads everything else.
The first call most clients make after receiving a closure notice is to a lawyer. This is understandable. The letter feels legal. The situation feels as though it requires a legal response.
But in most cases I have observed, the underlying cause is not a legal failing. No law has been broken. No regulation has been violated. What has happened is that the structure became unreadable to the bank — and the bank responded to that opacity by removing the relationship.
A lawyer can write letters. A lawyer can challenge decisions where there are legitimate grounds. A lawyer can review documentation for compliance. What a lawyer cannot do is redesign the architecture of a corporate group so that it reads clearly to a bank's compliance function — because that is not a legal question. It is a structural one.
The question is not what you are permitted to do. The question is whether what you have built can be understood by someone who knows nothing about you and has perhaps fifteen minutes to form a view.
I am often asked what banks want to see. The answer is simpler than most people expect.
Banks want to see a structure where every element has a discernible role. Where the choice of jurisdiction connects to a business reason that can be stated in plain language. Where the flow of money between entities follows a logic that does not require detailed explanation to be understood. Where higher-risk activities — cryptocurrency, less conventional jurisdictions, more complex counterparty relationships — are separated from the banking relationships that need to be protected, and where that separation is reflected in the documentation.
None of this requires simplification. I have worked with groups of genuine complexity — multiple jurisdictions, significant crypto exposure, diverse business lines — where the banking relationships were stable and untroubled, because the architecture had been designed with legibility in mind from the beginning.
The difference is not what the business does. The difference is whether the structure around it can be read by someone who approaches it cold.
There is almost always a moment — usually some time before the closure notice arrives — when a client senses that something is becoming more difficult. Information requests become more frequent. KYC reviews take longer. Relationship managers begin asking questions they never asked before.
This is the moment to act. Not after the letter. Not when the account has already been frozen and another bank needs to be found urgently. At that earlier moment, when there is still time to look at the structure honestly and ask: what does this look like from the outside?
That question is harder to sit with than it sounds. Owners of international businesses understand their own constructions intimately. It is genuinely difficult to look at something you have built and see it as a stranger would — as a bank's compliance officer might, with no prior knowledge, no goodwill, and a checklist of risk indicators.
But that capacity — to step outside the structure and read it from the outside — is what determines whether a banking relationship survives scrutiny or does not.
I would rather help a client develop that perspective before the letter arrives than explain, after the fact, what the bank was responding to.
Vladimir Shuvalov is a legal and tax adviser with thirty years of experience in international corporate structuring, banking acceptability, and cryptocurrency architecture.
Thinking Globally — thinking-globally.com
Thinking Globally Consulting Limited
Registered in England & Wales · Company No. 17138834
128 City Road, London EC1V 2NX, United Kingdom
© 2026 Thinking Globally Consulting Limited · All rights reserved