For decades, large international banks have positioned themselves as gateways to the global financial system. Their pitch is straightforward: one partner, global reach, consistent service. For multinational corporates, the appeal is obvious - simplify banking by consolidating relationships.
But beneath the branding, the idea of a truly “global” bank starts to unravel.
The limitation is not ambition or scale. It is jurisdiction.
Banks do not operate across borders in the way technology companies or logistics networks do. They expand into countries, but once there, they become subject to local rules - rules that define, often in granular detail, what services they can provide, how they provide them, and to whom.
What emerges is less a single institution and more a network of locally regulated entities, loosely stitched together under a common name.
That distinction matters.
A corporate working with a global bank across Europe, Asia, and the Americas might expect a consistent experience. Instead, they encounter variation at almost every layer. A payment setup that works seamlessly in the Netherlands may require adjustments in the United States. A liquidity structure available in London may not be permitted in Mumbai. Even something as routine as onboarding can turn into a multi-country exercise, with separate documentation, timelines, and approval processes for each jurisdiction.
In some cases, the gaps are subtle. A bank may offer ISO 20022 payment formats globally, but local implementations differ. Files accepted in one country may fail in another not because the standard changed, but because interpretation did. Error handling, cut-off times, and processing logic follow local conventions, not global ones.
In other cases, the limitations are more explicit.
Take liquidity management. In theory, a multinational corporate should be able to centralise cash across accounts worldwide, optimising funding and reducing idle balances. In practice, that depends heavily on where the cash sits. European markets allow relatively sophisticated pooling structures, including notional pooling across entities. Move into markets like China or India, and those structures quickly encounter restrictions. Capital controls, regulatory approvals, and tax considerations can prevent funds from being moved freely or at all.
The result is a familiar problem for treasury teams: cash that exists, but cannot be used.
Payments tell a similar story. While a global bank may offer local payment capabilities in dozens of countries, it does not always control the full chain. In markets where it lacks direct access to domestic clearing systems, it relies on local correspondent banks. For the corporate client, this dependency is largely invisible until something goes wrong. Delays, additional fees, and reconciliation issues emerge, often without clear transparency into where in the chain the problem occurred.
In certain regions, even data becomes fragmented. Regulatory regimes increasingly require financial data to be stored and processed locally. For global banks, this means that account information, transaction data, and reporting cannot always be fully centralised. A corporate attempting to build a real-time, global view of its cash position may find that some pieces simply cannot be integrated in the same way as others.
And then there are the markets where global banks are only partially present or absent altogether.
In parts of Africa, Southeast Asia, and Latin America, even the largest international banks rely on partnerships with domestic institutions. In these cases, the “global” relationship effectively stops at the border, and the corporate is pulled back into the very fragmentation it was trying to avoid.
None of this is accidental. It reflects the underlying structure of the financial system.
.svg)
Banking is, at its core, a nationally regulated industry. Governments retain control over their financial systems for reasons that go beyond efficiency: monetary policy, financial stability, capital controls, and oversight. These priorities impose boundaries that even the largest banks cannot cross.
The consequence is a persistent gap between how corporates operate and how banks are structured. Corporates expand internationally and expect their infrastructure to scale with them. Banks expand internationally but remain constrained locally.
This is why even the most sophisticated multinationals rarely rely on a single banking partner. They build networks—combining global banks for reach, regional banks for depth, and local banks for access. Integration becomes their responsibility.
And that is where a different type of solution has started to emerge.
Rather than trying to replace banks or force uniformity where it cannot exist, platforms like Cobase sit above this fragmented landscape and act as an integration layer. They connect to multiple banks—global and local, across channels such as SWIFT, EBICS, APIs, and host-to-host, and standardise how corporates interact with them.
In that model, the complexity of dealing with multiple banking entities does not disappear, but it is absorbed. Payment formats are converted automatically to meet bank-specific requirements. Differences in file structures, validation rules, and communication protocols are handled centrally. Data coming back from banks—balances, transactions, statuses is normalised into a consistent format.
The effect is not that a corporate suddenly has a “global bank.”
It is that it gains a single, controlled interface across many banks.
This distinction is subtle, but important. The fragmentation remains at the infrastructure level where it is dictated by regulation and market structure but it is no longer fully exposed at the operational level.
In that sense, the role of integration shifts. It moves away from trying to find the one bank that can do everything, toward building a layer that can manage many banks as if they were one.
The “global bank,” then, is less a reality than an abstraction.
What corporates increasingly build instead is their own version of it—on top of the system as it actually exists.
