
Onboarding and compliance
·
Same banking group, two jurisdictions, two different answers
Why two arms of the same banking group ask different questions, what a credible onboarding file has to establish, and why remote applications stall rather than get refused.

Nicolas Michaux
Whatever form it takes, an onboarding process is trying to establish one thing: why does this entity exist here, and what does it actually do?
Everything else follows from that. A company incorporated in a jurisdiction where it has no staff, no premises, no local clients and no local suppliers will struggle to open an operating account there, regardless of how well the file is assembled — because the file cannot answer the question. Conversely, an entity with a clear commercial rationale, a director who can be met, and evidence of genuine local activity will clear requirements that look intimidating on paper.
This is why a request for a bank account is rarely just that. It is a request to be understood well enough to be accepted, and understanding takes material.
What a credible file establishes
Across markets and institutions, the substance of what has to be demonstrated varies far less than the forms suggest.
The structure, in full. The ownership chain from the operating entity to the ultimate beneficial owners, with intermediate holdings explained rather than merely listed.
The rationale for this entity, in this place. Not the group strategy — the specific reason this company was incorporated in this jurisdiction, expressed in terms a compliance officer can record.
The source of business. Where the money comes from, from whom, under what contracts. This is where files most often fail: not because the answer is problematic, but because it was never written down.
The expected flows. Currencies, volumes, counterparty countries, frequency. A file that says “international payments” invites questions. A file that says which currencies, to which countries, at what monthly volume, closes them.
Evidence of local activity. Contracts, invoices, employment, premises, a local director. Whatever exists — but something.
Most rejections are not decisions against the company. They are decisions not to spend more time establishing what the file failed to establish.
Why remote applications stall
An application filed from abroad by a foreign parent, with nobody on the ground to carry it, is at a structural disadvantage — not because the company is less creditworthy, but because the file has no advocate.
Compliance teams work through queues. A file that generates questions, and whose questions take a week to answer because of time zones and intermediaries, moves to the bottom of that queue. It is not refused; it simply stops processing. Meanwhile several markets still expect a director to appear in person for a first meeting, which turns a scheduling problem into a strategic one when a transaction has a deadline attached.
The companies that succeed here treat the trip as part of the process rather than an obstacle: one journey, several meetings, all prepared in advance, with the file complete before anyone boards a plane.
Sequencing matters more than persistence
Two habits separate applications that progress from applications that circle.
The first is to build the file before approaching anyone. A company that applies, is asked for something, produces it three weeks later, is asked for something else, and repeats, has not made four attempts — it has made one very slow attempt, and each round of questions lengthens the next. Anticipating what will be asked and answering it upfront is not extra work. It is the same work, compressed, at a point where it still influences the outcome.
The second is to approach more than one institution in parallel where the timeline matters. This is standard practice in structured transactions and unusual in ordinary account openings, though the logic is identical: a single application is a single point of failure, and if it fails at week eight, the alternative starts from week zero.
The part that is rarely said
Companies often assume that a difficult onboarding reflects something wrong with them. In our experience that is seldom the case. What it usually reflects is a mismatch: an entity approaching an institution whose appetite, licence or client profile was never suited to it, with a file assembled for a different audience.
Correcting that mismatch takes less time than persuading the wrong institution — and it is a far better use of a finance team’s attention than a fourth round of the same questions.

