Why correspondent banks are finally standardising KYC exchange

Ask any compliance officer at a correspondent bank how many different KYC questionnaire formats land on their desk in a given month, and you'll rarely get a precise number — because nobody counts anymore. Each relationship bank has its own template, its own required annexes, its own idea of what "current" documentation looks like. Multiply that by dozens or hundreds of correspondent relationships, and the result is a back office built almost entirely around re-entering the same facts into different forms.

The problem isn't the regulation — it's the duplication

Firms subject to anti-money-laundering rules are required to know who they're dealing with and to keep that picture current. That obligation itself is not the bottleneck. The bottleneck is that every institution has historically built its own version of the same questionnaire, then exchanged it by email, one relationship at a time. The underlying due diligence requirement barely changes from bank to bank; the paperwork wrapped around it does.

This is the gap that a shared KYC Standard Questionnaire is designed to close — one regulator-aligned form, developed with the industry rather than by a single institution, that a client bank fills in once and shares electronically with every counterparty that needs it.

What changes when the questionnaire is shared, not duplicated

Standardisation shifts the work from re-drafting to reviewing. A client bank uploads its documentation once, to a repository it controls. Requesting banks no longer wait on an email reply; they access current data directly, in electronic format, ready to load into their own onboarding systems. When something changes on the client bank's side, every relationship bank connected to that record sees the update — nobody has to be told twice.

For the requesting bank

• One consistent format to review, regardless of which correspondent it comes from
• Confirmation that the data reflects the client bank's current documentation, not a snapshot from an old email thread
• No disruption to the requesting bank's own internal approval policies — the standard questionnaire feeds into them, it doesn't replace them

For the client bank

• A single questionnaire covers every participating counterparty, instead of one per relationship
• Full control over exactly which relationship bank can see which documents
• Ownership of the underlying data never moves — it stays with the bank that produced it

Standardisation also supports ongoing monitoring, not just onboarding

The other advantage of a shared framework is that it doesn't stop working once onboarding is complete. Because every counterparty is describing the same relationship in the same structure, it becomes far easier to flag when something material changes — a change in ownership, a shift in expected activity, a jurisdictional flag — and to route that change to everyone who needs to see it. That kind of proactive monitoring is usually organised around what's known as a Trigger Review Event, which we cover separately in our piece on building a proactive AML monitoring habit.

The direction of travel

None of this removes the underlying due diligence obligation — nor should it. What it removes is the duplicated effort of satisfying that obligation separately with every counterparty. As more correspondent banks connect to a shared exchange rather than maintaining parallel, bilateral paperwork, the standard questionnaire stops being one bank's convenience and starts being the industry's default.

For institutions evaluating whether to move away from email-based KYC exchange, the practical starting point is usually the same regardless of size: look at how many hours the compliance and onboarding teams currently spend re-keying data that already exists somewhere else in electronic form, and ask whether a shared repository would remove that step entirely. In most correspondent networks, the answer is yes.