When a business prepares for a banking review — a new account application, a KYC refresh, or a response to an information request — the instinct is to gather documents. Certificates of incorporation. Ownership charts. Financial statements. Contracts with key counterparties. The assumption is that the bank wants evidence, and that evidence takes the form of paper.
This assumption is partially right and substantially incomplete.
A bank does want evidence. But evidence, on its own, does not determine the outcome of a banking review. What determines the outcome is whether the evidence tells a coherent story — and whether the person presenting it can articulate that story clearly, consistently, and without contradiction.
In thirty years of working with international structures, I have watched businesses with impeccable documentation lose banking relationships they should have kept. And I have watched businesses with genuinely complex structures maintain those relationships without difficulty. The difference, in almost every case, was not the quality of the documents. It was the quality of the narrative.
A compliance officer reviewing a new client — or conducting a periodic review of an existing one — is trying to answer a single question: do I understand this business well enough to be comfortable with the relationship?
Comfort, in this context, is a precise concept. It does not mean that the business is simple. Complex businesses bank successfully everywhere. It means that the complexity is intelligible — that there is a logic to it the compliance officer can grasp, record in their internal files, and defend to their own management if the relationship is ever questioned.
When that question cannot be answered — when the structure is opaque, when the ownership chain requires extensive explanation, when the purpose of key entities cannot be stated plainly — the compliance officer is not comfortable. And a compliance officer who is not comfortable does not approve relationships. They escalate them, delay them, or decline them.
The banking narrative is the mechanism by which you make a compliance officer comfortable. Not by obscuring complexity — that approach fails, because compliance officers are trained to notice obscuration. By making complexity legible: explaining it in terms that can be understood, documented, and defended.
There are four things every banking review will seek to understand, whether it asks for them explicitly or not.
The first is who you are and what the business does. This sounds obvious — and it is the element most often handled badly. I have seen businesses describe themselves as "international consulting and investment" and then be genuinely surprised when the bank asks for clarification. A description that vague tells the compliance officer nothing useful and raises more questions than it answers. A description that is too detailed buries the essential information. What is needed is something in between: a clear paragraph that says what the business does, for whom, and where. Specific enough to be credible. Concise enough to be remembered.
The second is why the structure is organised as it is. This is the element that most businesses have never articulated — because it has never needed to be written down before. The structure grew organically. Each decision made sense at the time. But the overall logic has never been assembled into a single explanation that someone outside the business could actually read.
I have sat with owners who could spend an hour explaining, with perfect coherence, exactly why each entity in their group exists and why each jurisdiction was chosen. The explanation was genuinely convincing. But it existed only in conversation. The moment the owner left the room, the compliance officer was left with documents that told a different story — or no story at all. That gap is where banking relationships begin to break down.
The third is how money moves and why. Intercompany transactions are the element that generates the most questions in any banking review. Management fees, dividends, intercompany loans, royalties — each is a legitimate mechanism, but each requires explanation if it is to be read as normal rather than questioned as suspicious. The narrative should describe the principal flows plainly: where revenue is generated, how it moves through the structure, and what the logic is behind each significant intercompany transaction.
The fourth is what the cryptocurrency layer is and how it fits. If there is a crypto element — and increasingly there is — it needs its own place within the narrative. Not a technical description of blockchain mechanics. A business description: what digital assets the group holds or transacts, why, within what framework, and how that activity connects to the conventional operations the bank is primarily engaged with. An explanation that treats cryptocurrency as a normal feature of a modern business — which it is — rather than something that requires special pleading.
A banking narrative is only as strong as its consistency. And consistency is harder to achieve than it sounds.
A corporate group typically has multiple touchpoints with a bank over time: the account opening, the KYC questionnaire, responses to information requests, conversations between relationship managers and company representatives. These interactions are often handled by different people at different times, each doing their best, none of them working from a shared and agreed account of the business.
The result, in many cases, is a set of explanations that are individually plausible but collectively inconsistent. The ownership chart submitted at account opening shows a structure slightly different from the one described in a later KYC response. The business description given informally by a relationship manager contradicts, in minor but detectable ways, the description in the formal documentation. The explanation of a cryptocurrency element offered in response to an information request does not quite match what was said during the original account opening.
A compliance officer who notices these inconsistencies does not usually conclude that they are innocent. They conclude that the client does not have a clear picture of their own business — or that different versions are being presented to different audiences. Either conclusion damages the relationship.
This is also, I have come to understand, a harder problem to solve than it first appears. Owners of complex international businesses are usually very close to the detail. They know every element of the structure intimately. What they find difficult — what almost everyone finds difficult — is stepping back far enough to see how the business looks to someone encountering it for the first time, with no shared history and no goodwill. That distance is not natural. It has to be deliberately cultivated.
The practical remedy is straightforward: before any banking interaction, the narrative needs to be agreed and documented internally. Everyone who speaks to the bank on behalf of the company — the owner, the CFO, the legal adviser, the person completing the KYC questionnaire — needs to be working from the same account of the business. Not a script. A shared understanding of what the business is, why it is structured as it is, and how the key elements are to be described.
The moment at which banking narratives most commonly fail is not the initial account opening. It is the information request.
An information request — a letter from the bank asking for additional documentation or explanation — is, in most cases, a signal that the compliance function has encountered something it cannot resolve from the existing documentation. It is not yet a decision. It is a question. And the quality of the answer determines whether the relationship continues.
The instinct, when an information request arrives, is to respond quickly and provide as much documentation as possible. Both instincts are usually wrong. Speed without care produces responses that are inconsistent with earlier documentation. Volume without structure buries the relevant information under material that does not address the actual concern.
The right response is a narrative response: one that identifies what the bank is actually asking — which is rarely what the letter literally says, but rather what underlying concern prompted it — and addresses that concern directly, with documentation that supports the explanation rather than complicating it.
This requires someone who can read an information request the way the compliance officer who wrote it intended it to be read. And then construct a response that closes the concern rather than opening new ones.
There is a version of the banking narrative that businesses build once, file somewhere, and forget. That version is almost useless.
A business changes. New entities are added. The cryptocurrency layer evolves. Banking relationships are replaced or extended. The structure that was accurately described eighteen months ago may bear only a partial resemblance to what exists today. And when a bank review arrives — as it always does — the documentation describes a business that no longer quite exists, and the narrative explains a structure that has quietly moved on.
A business that treats its narrative as a living document — one that is reviewed and updated whenever something material changes — has a significant practical advantage. It does not have to reconstruct its account of itself under pressure. It does not have to reconcile contradictions between what it said a year ago and what is true today. When a banking question arises, the answer is already there.
But the deeper benefit is not operational. It is reputational. A client who presents a consistent, current, and clearly articulated account of their business at every banking interaction is a client who looks managed. And a compliance officer who is dealing with a client who looks managed is a compliance officer who can be comfortable.
The deepest function of the banking narrative is not to answer questions. It is to prevent them from arising. A structure that is clearly explained, consistently described, and properly documented does not generate information requests — because the compliance officer already has the answers. They are in the narrative. They were there from the beginning.
That is what it means to build a structure for legibility. Not to simplify what is genuinely complex. To ensure that complexity, wherever it exists, comes with an explanation already attached.
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