Twelve parts
What is KYB orchestration?
KYB orchestration is a control layer that sits between your business and the many company registries, corporate-data providers, UBO sources, and screening vendors you need to verify a company and the people behind it. It decides, in real time, which source to query for each jurisdiction, in what order, and what to do when a source has no record or is unavailable. Rather than hard-wiring one KYB data vendor into onboarding and living with its coverage gaps, you route each entity through a configurable workflow that can waterfall across sources for coverage, fail over when a registry is down, resolve the same company across conflicting records, and log every step once.
It is the KYB sibling of identity verification orchestration, and the plumbing rhymes: routing, waterfall, failover, and one audit trail appear on both sides. The difference is the subject. A person largely carries a passport and a face; a company is a legal fiction whose truth is distributed across national registers with no shared format, and whose owners can be deliberately obscured. So the registry-fragmentation and UBO discovery problems are KYB-specific, and they change what orchestration has to do.
If you are new to the underlying discipline, start with what KYB is. This page is about the architecture that makes KYB work at scale across many countries and many sources.
Common misconception
The most common misconception
KYB orchestration is just KYC orchestration for companies.
The plumbing rhymes, but the data problem is harder. An individual carries a passport and a face; a company's truth is scattered across national registers that share no format, and its owners can be deliberately hidden behind layers of holding companies. Registry fragmentation and UBO discovery are the KYB-specific problems, and they are exactly what orchestration exists to solve for businesses.
Why business data is fragmented (no single vendor covers the world)
Verifying a business is not one lookup. It is: confirm the entity legally exists and is active (the company register); confirm its registered details, directors, and status; discover and verify its ultimate beneficial owners (UBOs), often through layers of holding companies across borders; and screen the entity, its directors, and its UBOs against sanctions, PEP, and adverse-media lists. Each step draws on different data, and that data lives in different places. Four structural facts make a single source insufficient.
Every country has its own register, and they are inconsistent
Registers range from fully open, such as UK Companies House, to closed systems accessible only to registry officials, such as the British Virgin Islands or Alberta. The market reports that only about half of company registers offer a public API. Some charge for filings, some are free; some do not collect shareholder information at all, and some list only founding shareholders. Freshness varies enormously: some registers update only on a company's filing cycle rather than in real time, and one US state (California) has been cited as updating on a roughly 24-month lag. Cross-border KYB is hard precisely because registration, ownership disclosure, and reporting standards differ by jurisdiction, and registry accessibility and accuracy differ with them.
No single vendor covers the world
Coverage claims among leading providers diverge because each stitches together a different subset of the world's registers. Figures cited across the market include 300-plus registry integrations in around 100 to 120 countries (Kyckr), 300-plus jurisdictions (Vespia), 400-plus official registries across 200-plus countries (Global Database), and 500-plus local registers (Know Your Customer). The takeaway is not any single number; it is that every vendor draws a different map, so any one of them leaves gaps somewhere. Attribute these as vendor and marketing figures, not authoritative counts.
Beneficial-ownership data is scattered and contested
UBO information is the hardest part of KYB, because owners hide behind layered holding companies, nominee directors, trusts, and shell entities across multiple jurisdictions, and many registers show only declared or direct ownership and depend on company self-reporting. On top of that, the register landscape itself is in flux (see the section on 2025 to 2026 below): the EU's public UBO registers were curtailed by the Court of Justice in 2022, and the US has, for now, exempted domestic companies from beneficial-ownership reporting entirely. A single UBO source is therefore never a complete or stable picture.
Single vendor equals single point of failure
If the one wired-in KYB provider is down, cannot read a given jurisdiction, or returns no record, the applicant is simply blocked. The evidence is stark: legacy KYB platforms automatically clear only around 30 percent of verifications, pushing roughly 70 percent to slow, costly manual review (Sayari). And a name match against a registered entity name is not the same as verifying who actually owns and controls it. Orchestration replaces brittle single-source wiring with a coordination layer that combines sources per jurisdiction, fails over when one is unavailable, resolves conflicting records, and logs everything once.
Common misconception
A name match is not verification
A name match against the register verifies the business.
It confirms that an entity of that name exists. It does not confirm who owns and controls it, which is what regulators now require. Fraudsters moved to layered ownership structures precisely because they defeat name matching, so the bar has shifted from existence to ownership resolution.
How KYB orchestration works (the mechanism)
The concepts are the same as KYC-side orchestration, but the subject is a legal entity and its owners, which changes each one. A business-verification request enters a routing engine, which sends each part of the check to the best source per jurisdiction, waterfalls to the next source when one has no record, fails over to an alternative when a source is down, resolves the returning records to one real-world entity, and writes every source queried, every result, and every decision to a single audit trail.
- Routing (best source per jurisdiction). The engine picks the right register or data provider for the country of incorporation, because the best source for a German GmbH is not the best source for a Delaware LLC or a Singapore Pte Ltd. This turns per-market coverage differences from a weakness into a design decision.
- Verification waterfall (coverage). Sources are ordered. If the first has no record of the entity, or returns only a name match rather than confirmed ownership, the query cascades to the next until one satisfies the requirement. This lifts overall match and pass rates above what any single register achieves. The cost, as with KYC waterfalls, is added latency and per-query expense, so a governed waterfall decides when to cascade rather than always querying everyone.
- Failover and resilience (uptime). Government registers go down, and some vendors keep offline registry backups precisely so verification does not stall during an outage. Orchestration routes automatically to an alternative source when the primary times out or errors, which is a distinct job from waterfalling for coverage.
- UBO discovery by combining sources. Because no register alone reveals a layered ownership chain, orchestration assembles the beneficial-ownership picture by cross-referencing multiple sources (company registers in several jurisdictions, corporate-hierarchy data, and shareholder filings) to unwrap holding companies within holding companies, spot nominee arrangements, and trace up to the natural persons at the top.
- Entity resolution and deduplication. The same company appears differently across registers and datasets (name variants, transliterations, different identifiers, stale addresses). Entity resolution matches, links, and deduplicates those records so the platform treats one real-world business as one entity, avoids onboarding it twice, and can follow ownership chains reliably. Poor resolution means missed links or false matches, which is exactly the KYB failure mode.
- One audit trail across all vendors. Every source queried, every record returned, and every decision is captured in a single evidence record, so a regulator can be shown why a given entity and its owners were cleared, escalated, or rejected, no matter how many vendors were involved.
Note
A waterfall is not always better
An uncontrolled cascade tries everyone, which inflates cost and latency. The value is in deciding when to cascade, per market, against a cost and latency budget, not in cascading everything. Failover for uptime and waterfall for coverage are two different jobs, and a good platform lets you configure them separately.
Key terms (defined for businesses, not individuals)
Each concept has a KYC counterpart, but the subject is an entity spread across national registries rather than a person with a passport, which changes how it works.
- Verification waterfall (cascade): an ordered fallback across data sources to maximise coverage and match rate. For businesses, the sources are company registers and corporate-data providers per jurisdiction, and a pass can require confirmed ownership rather than just a name match.
- Least-cost routing: sending each query to the cheapest source that can satisfy it, and only escalating to more expensive sources when needed, so coverage does not mean paying every vendor for every check. This is the KYB analogue of cost-aware routing in KYC orchestration.
- Failover (resilience): automatic rerouting to an alternative source when a register or vendor is down or errors, so onboarding does not stall. Government registers going offline makes this a first-class concern in KYB, not an afterthought.
- Entity resolution: matching, linking, and deduplicating records that refer to the same real-world business across multiple sources. Where an individual is anchored by a date of birth, the business analogue is a stable identifier such as a registration number or a Legal Entity Identifier (LEI), the G20-backed ISO 17442 standard whose reference data ties an entity to its official name, registered address, and country of formation.
- UBO discovery: tracing ownership and control through layered structures to the natural persons who ultimately own or control the entity. It is the hardest KYB task, and combining sources is what makes it tractable.
Common misconception
Orchestration does not replace your data vendors
An orchestration platform replaces my KYB data providers and registers.
No. It coordinates them. The registers and data providers still supply the underlying data, and orchestration cannot exceed their quality. If a country's register is closed, stale, or thin, orchestration combines what exists, but it cannot invent the missing data.
The buyer objections orchestration answers
Most KYB buying questions reduce to four objections: coverage, resilience, auditability, and vendor lock-in. The table sets a single-vendor KYB stack, a do-it-yourself multi-vendor build, and an orchestration platform side by side against each.
| Concern | Single-vendor KYB | DIY multi-vendor | Orchestrated KYB |
|---|---|---|---|
| Coverage | Inherits one vendor's map of the world; whatever it does not cover becomes your gap. | You can add sources, but you write and maintain the routing per jurisdiction yourself. | Routes to the best register per country and waterfalls across sources, so coverage exceeds any single map. |
| Resilience | The vendor is a single point of failure; an outage blocks the applicant. | Failover is possible, but you build and test the retry and rerouting logic. | Automatic failover to an alternative source when a register is down, kept separate from coverage waterfalls. |
| UBO discovery | Limited to that vendor's declared or direct ownership view; layered chains slip through. | You cross-reference sources by hand or in bespoke code, which is slow and brittle. | Combines registers, corporate-hierarchy data, and filings to trace ownership to the natural persons. |
| Audit trail | One vendor's logs, in one vendor's format. | You stitch logs together across providers, with gaps where formats differ. | One immutable record of every source, result, and decision across all vendors. |
| Vendor lock-in | Switching means re-integrating; the wiring holds you to the vendor. | Lower lock-in, but the integration and maintenance burden sits with your engineers. | Best-of-breed behind one integration; add or swap a source without re-plumbing onboarding. |
Note
Do you need KYB orchestration?
The signals that tip the balance: you verify businesses across multiple countries with different registers; pass rates are low or manual-review volume is high; register outages have blocked legitimate applicants; UBO discovery is manual and misses layered owners; or compliance needs one provable record across every vendor. A single-market, single-source, low-volume flow may not need a platform.
The beneficial-ownership register landscape in 2025 to 2026
The defining feature of the current moment is that the beneficial-ownership register landscape, the very data KYB depends on, is fragmenting and in active flux across the three major blocs. That instability is the single strongest argument for orchestration: if you cannot rely on any one register being open, current, and complete, you must be able to combine and switch sources.
European Union: public registers curtailed, then re-regulated
On 22 November 2022 the Court of Justice of the European Union ruled that the provision giving the general public access to beneficial-ownership information was invalid, holding that unrestricted public access was a serious interference with the rights to private life and data protection under Articles 7 and 8 of the Charter. Many member states suspended or restricted public access to their UBO registers in response, while access was preserved for those with a legitimate interest and for journalists and civil-society organisations working on anti-money-laundering. A data source many teams had relied on became patchier overnight. The EU AML package then re-regulated the area: the Anti-Money Laundering Regulation (AMLR, Regulation (EU) 2024/1624), applying from 10 July 2027, defines beneficial ownership uniformly at a threshold of 25 percent or more, requires richer national registers interconnected via the BORIS system, and obliges firms to identify, verify, and consult central registers. The Commission may, after an assessment due by 10 July 2029, set a lower threshold by delegated act, capped at 15 percent for higher-risk sectors. (AMLR article-level detail should be confirmed against EUR-Lex before quoting verbatim.)
United Kingdom: register reform and mandatory identity verification
The UK is tightening the integrity of Companies House under the Economic Crime and Corporate Transparency Act (ECCTA). Identity verification for company directors and people with significant control (PSCs) became mandatory from 18 November 2025, phased over roughly 12 months, and Companies House estimates 6 to 7 million individuals are affected. Companies House gained powers to query suspicious filings and impose civil penalties up to 10,000 pounds for false information. This matters for KYB because the UK PSC register has historically depended on self-declaration, so until the reform fully beds in, teams cannot assume PSC data is verified.
United States: domestic beneficial-ownership reporting removed (for now)
The Corporate Transparency Act (CTA) required companies to report beneficial ownership to FinCEN, then went through extraordinary turbulence: a nationwide injunction was reinstated by the Fifth Circuit on 26 December 2024, the Supreme Court stayed that injunction on 23 January 2025, and on 21 March 2025 FinCEN issued an interim final rule (published 26 March 2025) that removed the reporting requirement for US companies and US persons, exempting all domestically formed entities and leaving obligations only on certain foreign entities. For KYB, the anticipated US federal UBO register is, for domestic companies, effectively empty, so US beneficial ownership must again be assembled from state registries and third-party data, which is precisely a multi-source, orchestration-shaped problem. (CTA status is fast-moving; re-verify against FinCEN at publish.)
The latest trends
Six directions are reshaping KYB in practice.
- From name matching to ownership resolution. The bar has moved from verifying that an entity of a given name exists to verifying who owns and controls it, because fraudsters shifted to layered structures designed to defeat name matching. Sayari reports that deterministic beneficial-ownership resolution roughly doubles fraud-detection accuracy on obfuscation cases and lifts automation from around 30 percent to around 55 percent. Orchestration across registers is what feeds that resolution.
- Company plus UBO in one orchestrated flow. Modern platforms run entity verification and UBO identity checks in a single orchestrated workflow rather than as siloed steps, with no-code layers to cut manual burden. This is the KYB expression of the KYC no-code workflow trend.
- Resilience as a feature. Because government registers go offline, offline registry backups and automatic failover are marketed as core KYB features rather than nice-to-haves.
- Perpetual KYB. Company facts change (directors, ownership, status, sanctions exposure), so the direction is event-driven re-verification rather than periodic manual refresh, the KYB analogue of perpetual KYC.
- Standard identifiers as the resolution anchor. The LEI (ISO 17442, G20-backed) and national registration numbers are increasingly used as the stable key that entity resolution matches on across sources, reducing the ambiguity that plagues name-only matching.
- Regulatory fragmentation raises the value of orchestration. With EU registers restricted, the UK verifying identities from late 2025, and US federal UBO reporting removed for domestic entities, no single register is reliably open, current, and complete, so the ability to combine and switch sources is now a compliance necessity, not an optimisation.
How AI helps KYB orchestration
Used defensively, AI is what turns a KYB orchestrator from a router into an investigator. The hardest KYB task, unwrapping layered ownership across jurisdictions, is exactly where AI helps: cross-referencing multiple registers and datasets, following ownership chains, and flagging where the trail goes cold offshore, into a nominee, or into a trust. Machine learning matches, links, and deduplicates entity records across sources using identifiers, addresses, and hierarchy rather than name alone, which is where most missed links and false matches are eliminated. And the same pre-classification that helps individual screening applies to the multiple screening hits a single business generates across the entity, its directors, and its UBOs.
AI on the defender’s side
Where Zenoo's AI genuinely applies
Zenoo runs 10 specialised AI agents plus an automated pipeline on top of the data you connect, never as a substitute for the register or vendor that supplies it. The KYB Researcher returns a structured compliance dossier of 50-plus fields in under 60 seconds, versus 2 to 4 hours of manual research. The Full KYB Pipeline takes end-to-end KYB onboarding from 3 to 5 business days down to under 30 minutes, and by cross-referencing 6 data sources typically discovers 2 to 4 times more persons (directors and beneficial owners) than a manual process, which is orchestration plus AI applied to the layered-ownership problem. Adding a new registry or data provider takes under 1 hour versus a traditional 4 to 6 months, with AI-generated field mappings in under 30 minutes at 85 to 90 percent first-pass accuracy. Checks run in parallel (4 parallel checks in about 3.4 seconds), and the Marketplace exposes 240-plus check types at the Enterprise tier, including KYB and company data. Platform-wide, investigation time drops from an industry benchmark of 22 hours to 12 minutes, with roughly a 95 percent reduction in false positives typically within 90 days.
How AI is abused against KYB
The same technology raises the stakes. AI lowers the cost of manufacturing corporate facades and defeating shallow checks, and the defensible answer is combining sources and resolving ownership across them rather than trusting any single register.
- Layered-ownership obfuscation, now cheaper to build. Fraudsters deliberately construct chains of holding companies, nominee directors, and shell entities across jurisdictions to defeat name-matching KYB. Company formation is cheap and fast in many jurisdictions, so building a plausible corporate facade is within reach of ordinary fraud operations.
- Synthetic and shell businesses. The synthetic-identity playbook used against individual KYC extends to businesses: fabricated or repurposed entities with just enough real registry footprint to pass a shallow existence check but no genuine beneficial owner behind them.
- Exploiting the register gaps. Every jurisdiction where ownership is self-declared, stale, or unverified is an opening. The UK's move to mandatory PSC identity verification from November 2025 is a direct response to abuse of a self-declared register, and the current US domestic UBO gap is exactly the kind of blind spot bad actors route through.
- Deepfakes at the human layer of KYB. UBO verification ultimately requires confirming the natural persons behind the entity, and that identity step is under the same generative-AI attack as consumer KYC, so a business can be legitimate on paper while its owner onboarding is a synthetic or deepfaked person.
AI as the threat
Why this favours orchestration
Because a business can be manufactured on paper and its owner faked at the identity step, no single register or single check holds. The defensible posture is combining multiple sources to resolve ownership, and routing the human identity step to the specialist liveness and deepfake detectors, which is exactly what orchestration provides. It combines and routes; it is not itself the detector.
Where Zenoo fits (honestly)
Zenoo is a KYC, KYB, and AML orchestration platform: your registers and vendors plus Zenoo, never instead of them. It does not publish a company register, and it does not replace your KYB data providers or the registers themselves. You still choose and pay for the sources; Zenoo coordinates them and applies AI to the work around the data.
In practice, Zenoo routes a business-verification request to the best register or data provider per jurisdiction, waterfalls for coverage, and fails over when a source is down, so you are not locked to one vendor's map of the world, and new sources connect in under 1 hour versus a traditional 4 to 6 months. UBO discovery is where orchestration plus AI earns its place: the Full KYB Pipeline cross-references 6 data sources and typically surfaces 2 to 4 times more persons than manual research, taking end-to-end KYB from 3 to 5 business days to under 30 minutes, and the KYB Researcher returns a 50-plus-field dossier in under 60 seconds. Records from multiple sources are resolved to one entity, and every source, result, and decision is captured as an immutable audit event (32 event types across 8 categories) inside the Compliance Hub, which is exactly what a fragmented multi-vendor KYB stack lacks and what AMLR-era supervision will expect. That answers the four objections directly: coverage through waterfall across registers, resilience through failover, auditability through one trail across vendors, and vendor lock-in through best-of-breed behind one integration. Specialised AI agents also assist re-verification as company facts change, the perpetual-KYB direction. All figures here come from Zenoo's metrics registry; only Maples is a publishable named Zenoo customer.
Honest scope
Where Zenoo does not solve the problem
Zenoo does not make a closed or stale register open or current; orchestration combines what exists, and it cannot exceed the underlying data quality. It does not remove the legal obligation to identify and verify UBOs and consult central registers; it speeds the work, but a human still owns the decision. It cannot, by itself, defeat a deepfaked or synthetic person at the UBO identity step; that is the job of the IDV and liveness vendors it orchestrates. And per Zenoo's rules, integration status defaults to activate unless data confirms a pre-built connector, with no vendor-viability or unattributed claims.
What the future looks like
Several directions look settled enough to plan around.
2027 is the EU pivot. The AMLR applies from 10 July 2027 with a harmonised 25-percent-or-more UBO threshold, richer national registers, and BORIS interconnection. Non-EU firms will benchmark against it, and orchestration layers will branch on which register, under which access regime, applies to a given entity.
Continued fragmentation, not consolidation. With EU public access curtailed, the UK bedding in identity verification, and US domestic UBO reporting removed, KYB teams will keep assembling ownership from multiple sources per jurisdiction for the foreseeable future. That is the structural tailwind for orchestration.
Ownership resolution becomes the standard. The shift from roughly 30 percent to roughly 55 percent automation and deterministic resolution becomes the baseline expectation, and orchestration across registers is what feeds it. Perpetual KYB. Periodic manual refresh gives way to event-driven re-verification of entity status, directors, ownership, and screening exposure, mirroring perpetual KYC. Identifiers as connective tissue. Wider LEI adoption and standard registration numbers make cross-source entity resolution more reliable over time.
Where this fits, honestly
From reading about it to running it.
KYB fragments across national registers, UBO sources, and screening vendors, which is exactly what orchestration is for. Zenoo coordinates the best-of-breed registers, corporate-data providers, and UBO sources you choose behind one integration: routing to the best source per jurisdiction, waterfalling for coverage, failing over when a register is down, and writing everything to one immutable audit trail. AI agents assist UBO discovery and ongoing monitoring on top of the data you connect. Your registers and vendors plus Zenoo, never instead of them.
A live Compliance Hub with fictional data. Nothing you do is saved.
