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 is trying to answer one 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 that the compliance officer can grasp, document in their internal records, and defend to their own management if the relationship is ever questioned.
When a compliance officer cannot answer the question — when the structure is opaque, when the ownership chain requires extensive explanation, when the source of funds is unclear, when the purpose of key entities cannot be stated simply — they are 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 look for obscuration. By making complexity legible: explaining it in terms that the compliance officer can understand, document, and defend.
A banking narrative is not a marketing document. It is not a pitch. It is a structured explanation of four things that every compliance review will seek to understand, whether it asks for them explicitly or not.
Who you are and what the business does. This sounds obvious — and it is the element most often handled badly. A description of the business that is too vague ("international consulting and investment") tells the compliance officer nothing useful and raises more questions than it answers. A description that is too detailed buries the essential information under complexity. The right description is a paragraph: what the business does, for whom, and where. Specific enough to be credible. Concise enough to be remembered.
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 — and the overall logic has never been assembled into a single coherent explanation. A compliance officer looking at a multi-entity group spanning three jurisdictions needs to understand why it is structured that way. Not the full history. A simple statement: what role each key entity plays, why those jurisdictions were chosen, and how the structure reflects the actual business model.
How money moves and why. The flow of funds between legal entities is often the element that generates the most questions in a banking review. Intercompany transactions, management fees, dividends, loans — each of these is a legitimate mechanism, but each requires explanation if it is to be understood rather than questioned. The narrative should describe the principal flows in plain language: where revenue is generated, how it moves through the structure, and what the logic is behind each significant intercompany transaction.
What the cryptocurrency layer is and how it fits. If there is a crypto element — and increasingly there is — it needs its own explanation within the narrative. Not a technical description of how the cryptocurrency works. A business description: what digital assets the group holds or transacts, why, within what framework, and how that activity relates to the conventional operations that the bank is primarily financing. An explanation that treats cryptocurrency as a normal element of a modern business — which it is — rather than something that requires special justification.
A banking narrative is only as strong as its consistency. And consistency is harder to achieve than it sounds, because a corporate group typically has multiple touchpoints with a bank — the account opening documentation, the KYC questionnaire, the responses to information requests, the conversations between relationship managers and company representatives — and these touchpoints are often handled by different people at different times.
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 by the 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 conversation.
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.
The remedy is simple in principle and demanding in practice: 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 who fills in 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 break down 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 explain from the existing documentation. It is not, at that stage, 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 to provide as much documentation as possible. Both instincts are wrong. Speed, without care, produces responses that are inconsistent with earlier documentation. Volume, without structure, buries the relevant information under material that is not responsive to the actual question.
The right response to an information request is a narrative response: one that identifies what the bank is actually asking — which is usually not what the letter literally says, but what underlying concern prompted the question — and addresses that concern directly, with documentation that supports rather than contradicts the explanation.
This requires someone who understands both the business and the bank's perspective — who can read an information request the way the compliance officer who wrote it intended it to be read, and construct a response that resolves the concern rather than generating new ones.
The banking narrative is not a document you produce once and file. It is a living description of the business — one that needs to be updated as the business changes, as new entities are added, as the cryptocurrency layer evolves, as banking relationships are added or replaced.
A business that maintains its narrative as an ongoing discipline — that reviews and updates its standard account of itself whenever something material changes — has a significant advantage over one that reconstructs the narrative from scratch each time a banking question arises. The advantage is not only operational, though it is that too. It is reputational: a client who presents a consistent, detailed, and up-to-date account of their business at every banking interaction is a client who looks managed. And a client who looks managed is a client a compliance officer can be comfortable with.
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 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