Banks almost never explain why they close an account. A letter arrives. It is formal, brief, and gives very little away beyond the date by which the money must be moved elsewhere. There is no accusation. No concrete concern is identified. The decision is simply presented as final.
In thirty years of working with international structures, I have seen this happen to businesses that were entirely lawful, commercially real, and genuinely shocked. Their first instinct is usually to call a lawyer. That instinct is understandable. But in most cases, the problem is not legal. It is architectural.
When a bank's compliance team reviews a corporate client, it is not really reading the business itself. It is reading the structure around it.
It sees the legal entities: how many there are, where they sit, and whether those jurisdictions appear to make commercial sense. It sees the ownership chain: how control moves from individual to company, from company to subsidiary, and from there to the account in question. It sees the movement of money: which entity invoices, which entity receives, which entity pays, and whether those flows match the story the bank believes it has been given.
Most importantly, it sees the whole picture at once. It asks a very simple question: does this arrangement read as something coherent, or does it read as something assembled over time without any clear discipline behind it?
That difference matters more than many clients realise. From the inside, a structure often makes perfect sense. The owner knows why each company exists. The owner knows why one jurisdiction was chosen over another. The owner knows why funds move in a particular direction. But a bank does not see the history behind those decisions. It only sees the visible result.
And when that result is difficult to read, the bank does what institutions usually do in such situations: it becomes conservative.
Accounts are rarely closed because of one dramatic event. In my experience, banks usually react to an accumulation of signals. Any one of those signals might have been manageable on its own. The problem begins when several of them sit together and start to suggest a structure the bank no longer feels comfortable carrying.
The first pattern is the mixing of different risk profiles inside the same perimeter. I often see groups where ordinary commercial activity sits alongside cryptocurrency exposure, or where mainstream clients sit alongside higher-risk counterparties or more sensitive jurisdictions. Internally, this often reflects how the business developed in real life. But from the bank's side, it can look like a group in which different forms of risk are bleeding into one another without any clear boundary.
The second pattern is the presence of entities whose economic logic is not immediately visible. A holding company in an offshore jurisdiction may well have a rational explanation behind it. A subsidiary in a particular location may have been created for very sensible reasons at the time. But if those reasons are not legible from the outside, the bank is left with a structure that appears to contain components it cannot easily justify to itself. Most banks will tolerate complexity for only so long. Very few will tolerate complexity they do not understand.
The third pattern is the existence of a cryptocurrency layer that sits next to the structure rather than inside it. This is one of the most common situations I encounter. A client has a legitimate business, a functioning bank account, and then, somewhere adjacent to that, some crypto activity: a wallet, occasional dealings with a crypto counterparty, part of treasury held in digital assets, perhaps a founder who has started using crypto informally in parallel with the business. None of this is necessarily improper. But if that crypto element has no defined role in the wider architecture — if it is merely present, loosely connected, and poorly explained — it begins to colour how the bank reads everything else.
That is the point many clients miss. Banks do not always isolate one issue and judge it neatly on its own merits. More often, they read the structure as a whole. And once the overall picture begins to look opaque, confidence disappears quickly.
When a closure notice arrives, most clients reach for legal help first. That is understandable. The letter feels legal. The tone is formal. The decision looks like something that ought to be challenged through legal argument.
Sometimes legal advice is necessary. There are cases where documentation needs to be reviewed carefully or where the bank's conduct deserves scrutiny. But in the overwhelming majority of situations I have seen, the deeper problem lies elsewhere.
Usually, no law has been broken. No regulation has necessarily been breached. What has happened is simpler and more uncomfortable than that: the structure has stopped being readable to the bank, and the bank has responded to that unreadability by removing the relationship.
A lawyer can write a letter. A lawyer can review contracts, declarations, and compliance files. A lawyer can sometimes challenge procedure. But that is not the same thing as redesigning a corporate architecture so that it can be understood, quickly and clearly, by a bank's compliance function.
That is a different discipline.
The real question is not what a business is allowed to do. The real question is whether what has been built can still be understood by a cautious institution looking at it cold, with limited time, limited patience, and no appetite for ambiguity.
Clients often ask me what banks actually want to see. The answer is much simpler than they expect.
A bank wants to see that each entity has a visible role. It wants to see that the choice of jurisdiction connects to a business reason that can be explained in plain language. It wants to see that money moves between entities in a way that follows an intelligible logic. And where the structure contains higher-risk elements — cryptocurrency, less conventional jurisdictions, unusual counterparties, more sensitive geographies — it wants to see that these are separated properly from the banking relationships that need protection, and that the documentation reflects that separation.
This does not mean a business must become simplistic in order to be bankable. I have worked with genuinely complex groups: multiple jurisdictions, significant crypto exposure, different lines of business, layers of ownership, real international movement. Complexity itself is not the problem.
The problem is unreadable complexity.
There is a great difference between a structure that is sophisticated and a structure that looks as though nobody stopped to ask how it would appear from the outside. Banks can live with the first. They eventually lose patience with the second.
There is usually a moment before the closure letter arrives when the relationship has already started to change. Information requests become more frequent. KYC reviews begin taking longer. Questions arrive that were never asked before. The tone shifts, even if only slightly.
That is the moment that matters.
Not after the notice has arrived. Not after the account has been restricted or frozen. Not at the point where a replacement bank must be found in a hurry. The useful moment is earlier, when there is still time to stop and ask an uncomfortable but necessary question: what does this structure look like to somebody seeing it for the first time?
That is harder than it sounds. Owners of international businesses usually understand their own arrangements in intimate detail. They know the history, the compromises, the reasons, the sequence of decisions. Looking at the same structure through the eyes of a compliance officer — someone with no history, no trust, no context, and a list of risk indicators — requires a very different kind of discipline.
But that discipline is often the difference between a banking relationship that survives scrutiny and one that does not.
I would always prefer to help a client see the structure that way before the letter arrives. By the time the bank has stopped trying to understand and started trying to exit, the useful choices are usually much narrower.
Vladimir Shuvalov works with international businesses and private clients on corporate structure, banking acceptability, and cryptocurrency architecture from Nicosia, Cyprus.
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