Somewhere around the second week of due diligence, a founder who has spent months rehearsing the growth story gets a request that has nothing to do with growth at all.
Someone in the data room wants to know why the KYC file for the Dublin entity doesn’t match the one for Singapore. Why cash sits in six accounts across four banks with no single view of the total. Why onboarding took six weeks in one market and four months in another, for reasons nobody quite remembers.
None of this shows up in the pitch deck. All of it shows up in the data room, usually somewhere between the term sheet and the wire hitting the account, right when the founder has the least appetite for surprises.
That’s the part founders tend not to see coming: banking structure due diligence is already underway by the time anyone in the deal notices it’s happening. The structure that got built quietly, deal by deal, market by market, while the business was busy growing, is now sitting under the same scrutiny as the revenue numbers. However, unlike revenue, it wasn’t designed to be looked at.
What Banking Structure Due Diligence Actually Tests
It’s no surprise that diligence has always gone deeper than the headline metrics. Investors and acquirers aren’t just underwriting what a business earns, they’re underwriting how it actually operates, because operational mess is a decent proxy for risk the numbers won’t show you.
Banking is one of the clearest windows into that; it’s where a company’s cross-border banking reality lives. It’s also one of the few places where the gap between “we operate in twelve markets” and “we can prove exactly how” becomes visible in about ten minutes of questions.
Why This Hits Sooner Than Founders Expect
The timing is what makes cross-border banking genuinely tricky for these companies, not just inconvenient.
Companies in the innovation economy don’t wait until they’re big and well-resourced to go international. They internationalise early, often while still lean, often before finance has caught up with the rest of the business.
A Series B company might already be banking in five or six countries, each relationship opened by whoever needed an account at the time, with a different bank, different compliance standards, and a different onboarding experience.
That’s not mismanagement, as each account was usually opened for a perfectly good reason at the time: a new subsidiary needed a local current account, a payroll provider only worked with one particular bank, or a customer insisted on paying in-market.
Nobody sat down and designed a group-wide banking structure because nobody had the time, and honestly, nobody was asking for one yet.
That’s just what growing fast across borders looks like from the inside. But it means that banking due diligence on the structure usually starts at exactly the moment the structure is least ready to be examined.
What Fragmentation Looks Like in the Data Room
What does that cross-border banking fragmentation actually look like once someone starts asking? A few things, consistently.
Compliance and KYC records that don’t line up market to market, so what should be one straightforward answer turns into three separate explanations. No consolidated view of liquidity, meaning nobody can say with confidence how much cash the group actually has on a given day without a spreadsheet built specifically for the question. Reconciliation is still done manually, which is fine until someone asks how quickly the finance team could produce a clean cash position under pressure.
Then we have onboarding histories with gaps: an account opened in one country in three weeks, the same process taking four months somewhere else, with no clear reason why.
None of these individually sink a deal, and most diligence teams have seen versions of all four before. It’s seeing them together, in the same data room, from the same company, that turns them into a pattern someone flags to the investment committee.
The Cost of Fixing It Under Pressure
The expensive part isn’t fixing any of this; it’s fixing it under pressure. A founder trying to explain a fragmented banking structure mid-diligence is doing so at the worst possible time, with the least leverage, in front of an audience actively looking for reasons to slow down or reprice.
It pulls management attention away from the actual negotiation and towards questions that should have been closed out months earlier. Worse, it plants a small, specific doubt: if the banking is this disorganised, what else hasn’t been tidied up?
That doubt doesn’t need to sink a valuation to matter. It just needs to give the other side one more reason to push on price, extend the timeline, or add a condition that wasn’t on the table before.
Do the same work before anyone’s asking, and it disappears as a talking point entirely. The fix costs roughly the same either way – do it early, and it’s just good housekeeping, do it late, and it’s a live liability in someone else’s negotiation.
Why This Isn’t a Software Problem
This is where the instinct to reach for a piece of software usually kicks in, but it’s the wrong instinct.
A dashboard that stitches together six separate banking relationships after the fact doesn’t fix the underlying problem; it just gives you a slightly better view of it. The fragmentation is still there underneath.
What actually resolves it is coordinated banking across markets: institutions operating to shared standards, consistent onboarding, and governance that holds the whole structure together, so the local expertise in each market plugs into something coherent rather than sitting there as six separate relationships that happen to share a logo on the group chart.
The better question is whether those banking relationships are coordinated with each other, or whether each one is just fine on its own, leaving the group without anything coherent.
A raise or an exit is the first time anyone senior looks closely at how the business actually runs day to day. Banking is one of the clearest places that shows up, whether the company is ready for it or not.
Getting There Before Anyone Asks
The founders who come through diligence cleanly on this front aren’t the ones with the most banking relationships. They’re the ones whose independent banks were coordinated before anyone went looking, so there was nothing left to explain.
Getting there isn’t about doing more banking. It’s about getting the banking you already have to work as a single coherent structure rather than a collection of separate ones.
There’s a version of this story that plays out for the banks, too.
The mid-tier and regional independent banks serving these companies are usually the ones best placed to spot the gap long before a raise is on the horizon. They’re also in a position to fix it while it’s still a low-stakes conversation rather than a diligence item. The banks that can offer that coordination early tend to keep the mandate when the company scales past them. The ones that can’t, they tend to find out about the fragmentation at the same time the investors do.
However, that’s a conversation for another day. Focusing on the founder sitting across from a diligence team right now, the point is simpler. Do the work before the data room opens, because it’s far easier to have the conversation on your own terms than theirs.
This is the argument for a governed network rather than a stitched-together one: independent banks operating to shared standards, so a client’s cross-border banking structure holds together the moment someone senior finally looks at it. IBOS exists to make that coordination possible before banking structure due diligence becomes a bottleneck, not after. To talk through what that looks like for your business, get in touch with Manoj Mistry.