---
title: "From 22 registers to one clean answer – Elucidate"
description: "How the Elucidate Bank & Firm Directory turns 22 registers from 13 authorities into one dataset of 80,347 active institutions: one taxonomy for many words, one entry per registration, identifiers before names, and a date on every value. On video."
url: https://elucidate.co/blog/from-22-registers-to-one-clean-answer
---

[Home](https://elucidate.co/) [Blog](https://elucidate.co/blog) [Compliance](https://elucidate.co/category/compliance)

From 22 registers to one clean answer: what makes public financial data usable

[Compliance](https://elucidate.co/category/compliance)

# From 22 registers to one clean answer: what makes public financial data usable

Public registers are open, but they are not ready to use. Here is what it takes to turn 22 of them, and Swift's BIC directory, into one answer that people and AI agents can rely on.

[Data](https://elucidate.co/tags/data)

[Technology](https://elucidate.co/tags/technology)

[Regtech](https://elucidate.co/tags/regtech)

[AML](https://elucidate.co/tags/aml)

[Elucidate team](https://elucidate.co/author/elucidate-team)

Nov 7, 2026

 ·

5

 min read

## Introduction

Regulators publish a great deal. Payment institutions, e-money issuers, money service businesses and crypto-asset service providers all appear on public registers, free to download. Open, however, is not the same as usable. Each register has its own format, its own vocabulary and its own idea of what a row is—and none of them was designed to be read next to the others.

The Elucidate Bank & Firm Directory reads 22 of these registers, from 13 authorities covering 37 countries, alongside Swift’s BIC directory. The result is one dataset of 80,347 active institutions in 231 countries (registers retrieved between 24 September and 5 November 2026; BIC data as at 24 October 2026). The video shows four of the steps in between.

How the directory turns 22 registers and Swift’s BIC directory into one answer. Figures as at the dates on screen.

## One activity, many words

Registers describe the same activity in different words. A firm that sends money for its customers is an “authorised payment institution” in London, a “major payment institution” in Singapore and a “money transmitter” on FinCEN’s list in the United States. The words are not interchangeable: the first two are prudential licences, with capital and safeguarding requirements; the third is a registration with an anti-money laundering supervisor.

So every firm in the directory gets one of three levels—prudential licence, small-firm registration or AML registration only—and the level is set firm by firm, not register by register. One register can hold several levels: on the FCA’s payment services register, 430 active firms hold a prudential licence and 509 a small-firm registration (register as retrieved on 25 September 2026). Read from the register’s name alone, one group or the other would be wrong.

## One row per premises

HMRC’s register of supervised businesses lists every premises separately. Post Office Limited alone has 6,693 rows, all under one registration number (HMRC’s register as retrieved on 24 September 2026). Counted naively, that is 6,693 institutions. In the directory, it is one: rows are collapsed to one entry per registration, with the trading premises behind it.

The same discipline applies elsewhere. The European Banking Authority records a firm’s history as a sequence of authorisations and withdrawals, so current status is read from the whole sequence, not from the latest field.

## Identifiers before names

Names are where datasets go wrong. As our post on [“Which Citibank?”](https://elucidate.co/blog/which-citibank-names-are-not-identifiers) showed, 3,993 names in the directory are each carried by more than one entry (as at 6 November 2026). So records are joined on identifiers: a register firm and a BIC holder become one institution only when they share a Legal Entity Identifier (LEI). Of the 36,546 institutions that hold a BIC and the 44,705 entries on registers, 904 are joined this way—shown once, with both records.

## Nothing deleted, every value dated

Registers forget. A cancelled licence disappears from the next download; a BIC that Swift stops listing is simply absent from the next edition. The directory keeps them: 8,746 inactive institutions remain, marked inactive, with their dates. When a register changes a value, the old one stays in the record’s history. And every value names its source and the date it was retrieved.

This matters more, not less, when the reader is a machine. An AI agent that cannot tell a current licence from one withdrawn last year—or cannot say where a fact came from—will produce a confident answer that no compliance file can accept. Clean data, for an agent, means three things: one vocabulary, one entity per real-world institution, and a source and date on every fact.

## Where Elucidate can help

The directory is free to search, and every step above is documented in its [methodology](https://elucidate.co/directory/methodology): each register, its publisher, what we take from it and how it is matched. Agents can query the same data through our [MCP server](https://elucidate.co/for-agents#mcp), with the source and date attached to each answer. Elucidate is certified to ISO/IEC 42001, the standard for AI management systems, and ISO/IEC 27001.

Clean identification is where due diligence starts, not where it ends. For banks and payment firms that need to assess risk, the [Elucidate FinCrime Index (EFI)](https://elucidate.co/directory/score) is an independent score of the financial crime risk of banks and payment firms—comparable to a credit risk rating, applied to financial crime.

Public data is a public good only when it can be used. Making it usable is the work.

See how the directory is built

Every register, its publisher, what we take from it and how often, and how institutions are matched: the directory's methodology, in one page.

[Read the methodology](https://elucidate.co/directory/methodology)

Related Content

[Compliance](https://elucidate.co/category/compliance)

[Beyond the BIC: why we built one directory for banks and regulated payment firms](https://elucidate.co/blog/beyond-the-bic-bank-and-firm-directory)

The data behind the Elucidate Bank & Firm Directory—Swift's BIC directory, GLEIF and 22 regulator registers—how we standardise and link it, what it does not show, and why an identification layer is only useful if it is current.

[Compliance](https://elucidate.co/category/compliance)

[Ask an agent: who is this counterparty? What AI agents need from institution data](https://elucidate.co/blog/ask-an-agent-who-is-this-counterparty)

A recorded session with the Elucidate directory's MCP server, on video: what an agent asked, what each tool returned, and the three properties that make institution data usable by AI agents—identifiers, provenance and stated limits.

[Compliance](https://elucidate.co/category/compliance)

[Who reads the directory? A week of machine traffic](https://elucidate.co/blog/who-reads-the-directory)

A week of elucidate.co's request logs, 22 to 28 October 2026, in shares: who asks for the directory's pages, which AI crawlers read it, what an assistant fetching a page for someone means, and why every page has a Markdown twin. On video.