When KYC becomes a paper trail instead of a risk assessment

Sophie Njagi, CEO EQWIRE examines why more paperwork doesn’t always mean better KYC

When a business is asked for another document during onboarding, it is reasonable for its owner to ask why. If the answer is “we ask everyone for that”, I think the payments firm should be asking itself some questions too.

With the FCA exploring more proportionate KYC in its 2026/27 work programme, payments firms have an opportunity to reconsider what their checks actually achieve. Its April findings on customer due diligence highlighted where some firms had failed to establish the purpose and intended nature of customer relationships. For me, that raises a fundamental question about whether collecting more information is helping us understand customers any better.

There will always be information we must collect and circumstances that warrant further investigation. But collecting more can become a way of managing our own uncertainty without improving our understanding of the customer.

An organisation can have a substantial file on a business and still struggle to explain how it makes money, why it sends funds to particular countries or what activity it expects through the account. My concern is that the reassurance of a completed checklist can obscure gaps that become consequential once the customer starts transacting.

That understanding gives the other information its meaning. Knowing who owns a company is essential, but understanding its business model and expected payment flows helps us assess whether subsequent activity is credible.

If you consider a hypothetical UK consultancy with transparent ownership and predictable domestic payments. Once ownership has been reliably established, an explanation of its contracts and expected receipts might resolve remaining questions. Another copy of an already verified ownership document would need a reason of its own.

A business with layered ownership and complex cross border flows presents different questions. Further investigation into control, the origin of funds and their commercial purpose may be necessary. Both require proper due diligence and the additional evidence should follow the questions we need to answer.

The consequences follow the customer

If onboarding never establishes what normal activity should look like, monitoring teams inherit that uncertainty. When a payment triggers an alert, they may have to reconstruct an understanding that should already be available, creating further requests and additional work.

I would like to see leaders ask which information gathered during onboarding actually informs subsequent decisions. There should be a clear connection between what a firm knows about its customer, its risk assessment and how it monitors the relationship.

Judgement needs leadership support

Judgement can feel harder to defend than a uniform process as asking everyone for the same additional evidence creates an easily recognisable record; deciding a request is unnecessary requires someone to explain their reasoning and accept responsibility.

Yet a risk based framework depends on that ability, supported by training, escalation routes, documented decisions and independent assurance.  An invoice could explain a payment inconsistent with a customer’s stated activity. Another statement covering a period already reviewed might be justified by a discrepancy, but without an identifiable concern it can consume everyone’s time without improving understanding. I would want a team to feel confident challenging that request and a manager willing to listen.

More information brings more responsibility

Financial documents can reveal personal details about directors and shareholders, creating responsibilities for security, access and retention. The ICO’s data-minimisation guidance requires personal information to be sufficient, relevant and limited to what is necessary. Financial-crime record-keeping obligations still apply, but firms should be able to justify what they collect.

This also affects trust as a business owner may accept a demanding question when its relevance is explained; repeated requests for information already supplied can suggest nobody has properly considered their application. As automation accelerates onboarding, these decisions become more important and whilst technology can identify duplication and flag discrepancies, an unnecessary request gains nothing from being issued instantly.

Before investing in another layer of automation, I would want to understand which decisions it improves. A completed file should leave us able to explain the customer’s business and the risks we are accepting. If we cannot, we need to identify what remains unclear before asking for more.