Product

For Developers

Resources

Company

Product

For Developers

Resources

Company

Blog

The Hidden Cost of Choosing the Wrong KYB Data Provider

Author

Joy Green

Updated

The wrong KYB data provider costs compliance teams operational problems. Stale company data sends analysts back to redo checks, pushes extra document requests onto your customers, and can leave you paying a second vendor to correct the first. And if you've signed a multi-year contract, you're stuck with it. 

Company data can often be the first step in a compliance workflow, so all the subsequent steps build upon the initial data that’s surfaced, from ID verification to sanctions screening. If your KYB data is incorrect in the first place – stale or inaccurate or both – it affects the whole chain, sending errors cascading through the workflow.

I have had first-hand experience of how bad data breaks the whole KYB flow because I started life as a CeMAP-qualified mortgage broker. I was running checks daily, onboarding remote customers, relying on KYC and KYB platforms. Now, I work with partners and clients all over the globe, all with different models, different use cases, and different customers within that, and varying risk appetites.

Why does KYB database data go stale?

Commercial databases aggregate data from, often, hundreds of different sources, refreshing them over time. Most of the big commercial databases hold a wide range of KYB data: company registry data, PEPs, sanctions, and adverse media.

Commercial databases are useful when the registries don’t store much data, as they pull from other sources. However, the freshness of their data varies significantly by jurisdiction and entity type.

Every refresh costs the vendor money, so they prioritise the data that most customers search for. Large companies and popular jurisdictions are refreshed regularly. Smaller companies, and those in less popular or hard-to-reach jurisdictions, are updated less often because the commercial return is lower, and their data is sometimes months or years out of date.

In a regulated setting, the database model is challenging. As Kyckr found in its 2026 report on British AML fines, low-quality KYB data is materially linked to 68% of regulatory fines. If a regulated business gets audited and they can't tell the auditor when that data was updated, or where it came from, they run the risk of falling foul of regulators.

For a fuller comparison of live registry data and KYB databases, see our guide to live company registry data.

How does stale company data break the KYB onboarding process?

It doesn’t catch newly incorporated businesses

Many KYB databases hold little data on newly incorporated businesses, particularly those in less popular jurisdictions. This doesn’t reflect the operational reality of a fast, digital economy. If you're an online marketplace like Amazon, your customers might register their business on a Monday and want to start trading on a Wednesday – as soon as their business is active. If a database hasn't been refreshed since last month, you're not going to be able to verify that. This leads to discrepancies between what the customer tells you and what the database holds, forcing onboarding analysts to request additional documentation from the customer. Does the customer like it? Absolutely not.

Your team screens the wrong person

Outdated databases don’t consistently catch company changes – their status, shareholders, registered addresses, or directors. This causes teams to conduct further checks – ID, adverse media, sanctions screening – on the wrong person. They assign the incorrect risk level and don’t notice the danger. But the team only realises further down the line, when they must redo the process. The risk doesn’t sit with the KYB database. The liability sits with you.

What happens when you're locked into the wrong KYB data provider? 

Stale data causes inefficiencies in the onboarding process, increasing the workload of compliance teams, while burdening customers with friction. 

One of my clients is a law firm that uses Kyckr to correct the inaccurate data from a global KYB database vendor. When they pull data from the vendor and notice a gap between what the customer said and what the database holds, they use Kyckr to pull company profiles in real time.

They know that this isn’t the most optimal solution, as they’re duplicating their work and slowing down the onboarding process. But they don’t have a choice. They signed a huge, multi-year contract with the database vendor in question, so they’re stuck with it.

Operationally, this produces an inconsistent workflow. The finance team gets involved, seeing two billing accounts for two invoices – all for the same customer, and with no set fee. And, while the cost of duplication is high, it's difficult to define, as it differs per customer. How do they even know the cost of onboarding per customer?

This law firm is not an outlier among regulated firms of all types. Kyckr's recent report on the state of business banking onboarding found that the share of businesses asked for additional documents or information after applying rose from 51% in 2020 to 91% in 2026.

Independent research points the same way. Sumsub's European KYB Benchmark Survey 2026, which polled 154 compliance and risk professionals, found that 99% had run into incomplete or unreliable company records.

Is a multi-vendor KYB workflow better than a single provider?

Isn't that what the law firm is doing? No. The law firm pays two vendors for the same job and uses the second to correct the first. That's a duplication. A multi-vendor workflow gives each vendor the job it does best and routes each check to the right one.

I don't think it's ever a case of “pick one or the other”. Many platforms spread their risk by relying on as many accurate, reliable sources as possible. A lot of the partners I work with don’t just work with Kyckr; they also work with Dun & Bradstreet, Creditsafe, or Moody's so their solution waterfalls where it's strongest.

They need Kyckr because they need current, independent, and auditable data. But if Kyckr lacks rich data because of a gap in the corporate registry record, those vendors fill the gaps.

This allows compliance teams to have best-in-breed vendors at every step: Kyckr for the registry data layer, and other vendors for PEPs, ID verification, and sanctions screening, enabling them to build a bespoke workflow that caters to the risk level of their customer base. And, when things change, they can adapt their workflow to the change, and not be locked in with a single, end-to-end vendor.

The model isn’t without pitfalls. You end up with six contracts and six pricing mechanisms, but the alternative is to rely on a single vendor. And the minute you're unhappy with one element of the single-vendor service, you're forced to unpick everything.

How should you route KYB checks across vendors?

As the head of compliance at a large, second-hand marketplace told me last week, “The minute there’s an outage, we can’t onboard a customer, and we can’t afford them dropping off.”

They have a multi-vendor workflow as a result, to ensure a consistent onboarding experience for their customers. Kyckr is used across all jurisdictions. But where the registry record is thin, they default to database vendors.

What should you check before signing a KYB data contract?

Before you sign, ask six questions.

  1. Will they put the refresh frequency for each jurisdiction you onboard from into the contract, rather than an average across all of them?

  2. Does every record show its source and the date it was retrieved?

  3. Will they let you test a sample of your own recent customers, including the hard jurisdictions, before you sign?

  4. What’s the minimum commitment, and what happens if your volumes drop?

  5. What does it cost to leave early?

  6. If you leave, can you take your records and audit trail with you?

The cheapest vendor on paper can be the most expensive one to be stuck with. 

Author

Joy Green

Joy Green

Senior Partnerships Manager

Joy builds and manages strategic partnerships across the compliance and onboarding ecosystem. She works with partners that support regulated entities such as banks, payment providers and fintechs, helping them embed trusted registry data into their verification and onboarding workflows. Joy brings extensive industry experience from Thirdfort and other partnerships roles across the onboarding space, with a strong understanding of identity, compliance and customer onboarding challenges.

Join 200M+ companies already verified through Kyckr.

Join 200M+ companies already verified through Kyckr.

Join 200M+ companies already verified through Kyckr.