TaxDo
Global Business Registry Check - Part of the TaxDo Global Tax Identity Infrastructure

Official Business Registry & Entity Search

Entity Search Across 120+ Official Company Registries, Worldwide

Search 120+ official company registries by name or registration number. Legal form, status, directors and beneficial owners returned in one structured response. Official registries, not aggregated databases. Legal form mapped to tax classification. Real-time API or batch.

See Coverage
TaxDo global business registry verification dashboard
120+Official Registries
120+Countries
Real-TimeLookup at Point of Query
Tier 1Authoritative Sources
OfficialSources
Registry Data

What the Registry Returns

Every lookup returns structured, machine-readable entity data from the official source of record — ready for entity classification, controlling person identification, and compliance decisioning.

Registry Lookup ResultVerified
Entity NameMeridian Capital Holdings GmbH
Registration NumberHRB 219847
Legal FormGmbH (Gesellschaft mit beschränkter Haftung)
Registration Date14 March 2019
StatusActive
Registered AddressKaiserstraße 42, 60329 Frankfurt am Main, Germany
DirectorsM. Richter (Geschäftsführer), S. Bauer (Geschäftsführer)
Beneficial OwnersM. Richter (68%), K. Vogt (32%)
Industry CodeNACE 64.20 — Activities of holding companies
Source: Handelsregister — Amtsgericht Frankfurt am MainTier 1 — Authoritative
Complete Data

Every Data Field a Registry Check Returns

Not a summary — the complete structured data set from the official source. Field availability varies by jurisdiction; TaxDo returns everything the official registry provides.

Entity Name

Core

Registered name and trading name where available. Exact name as recorded in the official registry.

Registration Number

Core

Company number, Handelsregisternummer, SIREN/SIRET, CIF, or jurisdiction-specific identifier.

Legal Form

Core

GmbH, Ltd, S.A., AG, LLC, SARL, B.V., or equivalent. The input for entity classification mapping.

Registration Date

Core

Date of incorporation or registration with the official registry. Key for entity age verification.

Status

Core

Active, Dissolved, Struck Off, In Liquidation, Dormant, or registry-specific status codes.

Registered Address

Core

Street, city, postal code, country. Official registered office as recorded. Feeds into jurisdiction determination.

Directors / Officers

Extended

Names, appointment dates, resignation dates. Starting point for controlling person identification.

Beneficial Owners

Extended

Where available — name, ownership percentage, control type. From AMLD registers, PSC, FinCEN. This field from official BO registers.

Share Capital

Extended

Registered share capital where recorded by the registry. Relevant for entity substance assessment.

Parent Company

Extended

Where recorded by the registry. Critical for group structure identification and related entity mapping.

Industry Classification

Extended

NACE, SIC, ISIC codes as recorded. Feeds into entity activity determination for Active vs. Passive NFFE classification.

Annual Filing Status

Extended

Where available. Confirms ongoing compliance with filing obligations. Missed filings signal dormancy or dissolution risk.

Why It Matters

Why Official Registry Data Is Non-Negotiable

Self-declared entity data is unreliable. Official registries provide the authoritative foundation for every compliance decision downstream.

Entity Classification Depends on Legal Form

Classification

Under CRS 2.0, DAC8, and FATCA, entity type determines the entire compliance path — which self-certification form, which reporting category, which exemptions apply. Incorrect entity data from unverified sources produces wrong classification at the root.

Wrong Entity TypeWrong Path

Controlling Person Identification

Look-Through

Passive NFFEs require look-through to controlling persons. Registry data provides the starting point — directors, officers, and beneficial owners from the authoritative record, not from self-declared forms that may omit or misrepresent ownership structures.

RegistryControlling Starting Point

Tier 1: Authoritative Source

Trust Hierarchy

Official registries are Tier 1 in the trust hierarchy — authoritative, government-issued data. Self-declared entity type is Tier 4. The OS always starts from the most authoritative source available and escalates only when registry data is insufficient.

Government RegistrySelf-Declaration
Classification Mapping

How Registry Legal Form Maps to Tax Classification

The legal form from the official registry is the starting input for entity classification under every regulatory compliance framework. This mapping determines reporting obligations, look-through requirements, and applicable exemptions.

Registry Legal Form
CRS Classification
FATCA Classification
CARF Classification
Compliance Implications
GmbH, Ltd, LLC, S.A., B.V.
Active NFFE (if trading)
Active NFFE or Passive NFFE
Non-CASP entity — Reportable User if transacting
If classified as Passive NFFE, controlling person look-through required. Ownership structure must be identified and reported.
Bank, Credit Institution, Kreditinstitut
Financial Institution
FFI (Reporting or Deemed Compliant)
Excluded CASP (if not providing crypto services)
Must have GIIN. Different reporting track from NFFEs. Separate due diligence procedures apply.
Fund, SICAV, UCITS, Investment Company
Investment Entity (FI)
Investment Entity (FFI)
Reporting CASP if holding crypto on behalf of clients
Classified as Reporting FI. All account holders / equity interest holders are reportable. GIIN required.
Foundation, Trust, Stiftung
Depends on activity test
Passive NFFE or Exempt
Reportable User — look-through to controlling persons
Must assess whether passive or active. If passive, controlling persons (settlor, trustee, beneficiary, protector) must be identified.
Government Entity, Sovereign Body
Excluded from reporting
Exempt Beneficial Owner
Excluded from CARF reporting
No reporting obligation. Excluded from account holder due diligence requirements.
Crypto Exchange, Custodian, Wallet Provider
Financial Institution (if meeting criteria)
FFI or NFFE (depends on activity)
Reporting CASP — full due diligence and reporting
Under CARF, legal form determines whether the entity is a Reporting CASP, Excluded CASP, or non-CASP. Registry data confirms whether the entity is licensed, regulated, and operating as a crypto-asset service provider.
Sole Proprietorship, Einzelunternehmen
Individual treatment
Individual treatment
Individual Reportable User
Reported under individual rules, not entity rules. TIN and residence of the individual apply.

Classification is never mechanical. Legal form is the starting input — activity tests, income composition, and management location determine the final classification. The OS handles this end to end.

Beneficial Ownership

Beneficial Ownership Data from Official Registers

Where jurisdictions maintain official beneficial ownership registers, TaxDo returns BO data as part of the registry check. Coverage varies — TaxDo returns what the official registry provides and flags where BO data is unavailable.

European Union

EU AML Beneficial Ownership Registers

Anti-Money Laundering Directives require all EU member states to maintain beneficial ownership registers. TaxDo connects to national BO registers across EU jurisdictions. Registers include name, date of birth, nationality, ownership percentage, and nature of control. Access rules vary — some public, some restricted to obliged entities.

27 Member States
United Kingdom

Persons with Significant Control (PSC)

Companies House maintains the PSC register — publicly accessible, free, and comprehensive. Covers individuals and relevant legal entities with significant control (25%+ shares, 25%+ voting rights, or right to appoint/remove directors). Updated as part of annual confirmation statement filings.

Public & Free
United States

Corporate Transparency Act — FinCEN BOI

The Corporate Transparency Act established a federal beneficial ownership registry administered by FinCEN. Reporting companies must disclose beneficial owners (25%+ ownership or substantial control). Access restricted to authorized users — law enforcement, financial institutions with customer consent, and regulators.

Restricted Access
Other Jurisdictions

Varying Levels of BO Disclosure

Australia, Canada, Singapore, and other jurisdictions have varying beneficial ownership disclosure requirements. Some maintain central registers; others require disclosure at the entity level. Coverage continues to expand globally as AML regulations tighten. TaxDo returns available BO data and flags jurisdictions where it is not yet accessible.

Coverage Expanding
Regulatory Mandate

Why Registry Verification Is Mandatory

Every major tax and compliance framework requires entity verification from authoritative sources. Self-declaration alone is insufficient — official registry data is the foundation of accurate entity classification.

CRS 2.0

Entity Classification for Common Reporting Standard

Must classify entities as Active NFFE, Passive NFFE, Financial Institution, or other defined categories. Official source verification required — self-declaration alone does not satisfy due diligence obligations. Incorrect classification triggers wrong reporting track and potential controlling person look-through failures.

DAC8 / CARF

Crypto-Asset Entity Classification

DAC8 extends CRS-style entity classification to crypto-asset service providers, while CARF requires CASPs to verify the legal structure of every entity counterparty. Registry data determines whether an entity is a Reporting CASP, Excluded CASP, custodial wallet provider, exchange, fund, or unregulated entity — and prevents wrong reporting tracks entirely.

FATCA

Chapter 4 Classification Across All FATCA Categories

FFIs must classify account holders across all FATCA entity categories — Reporting FFI, Deemed-Compliant FFI, Exempt Beneficial Owner, Active NFFE, Passive NFFE. Passive NFFEs trigger controlling person look-through. Official entity data required for defensible classification.

DAC7

Platform Operator Seller Verification

Platform operators must verify seller entity type, registration status, legal existence, and tax registration before reporting. DAC7 requires authoritative registry data to confirm the seller’s jurisdiction, legal form, and reporting obligations across sole traders, partnerships, corporations, and other entity structures.

KYB / AML

Anti-Money Laundering Entity Verification

AML regulations across jurisdictions require entity verification from authoritative sources during onboarding. AMLD in the EU, Bank Secrecy Act in the US, and equivalent frameworks globally all mandate verification of entity legal existence, ownership structure, and registration status.

E-Invoicing

Entity Verification for Compliant Electronic Invoicing

Peppol, Italy’s SDI, India’s GST e-invoicing, and emerging mandates in France, Germany, and Poland require entity verification and registration validation before invoices can be exchanged. Registry data confirms legal entity existence and registration status for compliant invoice routing.

Data Source Matters

Official Registry vs. Commercial Aggregator

The source of entity data determines whether your compliance classification is defensible. Aggregated commercial data is supplementary — not authoritative.

Data Source
Data Freshness
Regulatory Acceptance
Entity Classification
Beneficial Ownership
Compliance Focus
Cost of Error
Commercial Aggregators
Compiled from multiple sources, scraped, or licensed
Updated periodically — days or weeks of lag
Supplementary only — Tier 3 data
May include outdated legal form data
May be outdated, incomplete, or compiled from proxies
General business intelligence / credit scoring
Misclassification → wrong reporting track
TaxDoRegistry + Verification
Direct government / chamber of commerce connection
Real-time at point of query
Meets CRS / DAC8 / FATCA due diligence requirements — Tier 1
Authoritative legal form for defensible classification
From official BO registers (AMLD, PSC, FinCEN)
Regulatory compliance entity classification (CRS, DAC8, FATCA)
Authoritative classification → defensible reporting
Applications

Where Registry Verification Is Required

Entity verification is not a single-use check. It feeds into every compliance workflow that depends on knowing what the entity actually is. See how it works for global enterprises, manufacturers and payment platforms.

Regulatory Compliance

Entity classification for CRS 2.0, DAC8, and FATCA self-certification. Legal form from the registry determines Active vs. Passive NFFE, Financial Institution, and reporting category.

Know Your Business (KYB)

Verify counterparty legal existence, registration status, and beneficial ownership during entity onboarding. Confirm the entity is who it claims to be before account opening.

E-Invoicing Entity Verification

Verify entity registration and tax identification for compliant electronic invoicing. Registration data feeds into VAT and GST validation workflows.

CARF Crypto Entity Classification

CARF requires CASPs to verify institutional counterparties before reporting. Registry data determines whether a wallet holder is an individual, trust, fund, or regulated entity — and whether the counterparty qualifies as a Reporting CASP with its own due diligence obligations.

Counterparty Classification for Tax Reporting

Classify counterparties before CRS/FATCA self-certification or DAC7 seller reporting. Registry data confirms vendor status, validity, and entity type to pre-fill the right form and determine obligations before the first transaction.

Shell Company & Classification Monitoring

Detect shell companies, dormant entities, dissolved companies, misrepresented legal forms, and status changes — dissolution, strike-off, address changes, director changes — that affect CRS/FATCA entity classification, controlling person look-through requirements, and annual reporting obligations.

Format Reference

Business Registries by Country

Real-time connections to official government business registries. Each jurisdiction maintains its own register with distinct naming, data fields, and access rules — TaxDo normalizes them into a single response.

UKCompanies HouseDEHandelsregisterNLKvK (Kamer van Koophandel)FRInfogreffe / RCSESRegistro MercantilITCamera di CommercioATBundesamt für JustizBECBE / BCEDKCVR (Central Business Register)FIPRH (Patent & Registration Office)NOBrønnøysundregistreneSEBolagsverketIECRO (Companies Registration Office)CHSwiss Commercial RegistryPLKRS (National Court Register)ATFirmenbuch
+29 More
Integration

Built for Infrastructure-Level Integration

Registry verification embeds directly into onboarding, compliance, and monitoring workflows through a production-grade API.

REST API

Standard RESTful endpoints. Single lookup or batch. Versioned, documented, rate-limited.

JSON Response

Structured JSON with typed fields. Machine-readable entity data for downstream decisioning.

Batch Processing

Portfolio-level verification. Submit thousands of entities for parallel registry lookups.

Webhook Notifications

Real-time notifications on lookup completion, status changes, and monitoring alerts.

Business Registry FAQ

Questions from Compliance Teams

We will respond to you at any time
Just you need to use our help center or contact us

A business registry check verifies an entity’s legal existence, registration status, legal form, directors, and beneficial owners against official government and chamber of commerce registries. Unlike aggregated databases or commercial data providers, a direct registry check returns authoritative, Tier 1 data from the original source of record — the same data regulators rely on.

Under CRS 2.0, DAC8, and FATCA, entity type determines the entire compliance path — which self-certification form applies, which reporting category the account falls into, and which treaty benefits or exemptions are available. Incorrect entity classification from unverified data creates systemic compliance failures across the entire reporting chain.

TaxDo connects to 120+ official company registries across 120+ countries, including Companies House (UK), Handelsregister (Germany), KvK (Netherlands), Infogreffe (France), Registro Mercantil (Spain), Camera di Commercio (Italy), SEC EDGAR (US), State SOS registries (all 50 US states), ACRA (Singapore), ASIC (Australia), and dozens of national and provincial registries across Europe, the Americas, Asia-Pacific, and Middle East & Africa. All sources are government or chamber of commerce registries.

A TIN validation confirms the format and issuance status of a Tax Identification Number against the issuing tax authority. A business registry check verifies the entity itself — its legal form, registration status, directors, beneficial owners, and registered address against the official company registry. Both are required for complete entity due diligence under CRS 2.0 and DAC8.

CRS 2.0 and DAC8 require institutions to classify entities accurately — Active NFFE, Passive NFFE, Financial Institution, or other defined categories. This classification determines reporting obligations, look-through requirements for controlling persons, and applicable exemptions. Registry data provides the authoritative legal form and status needed for accurate entity classification at the point of onboarding.

CARF introduces entity classification requirements specific to the crypto-asset ecosystem. Reporting CASPs must determine whether an institutional counterparty is itself a CASP, an exchange, a custodial wallet provider, a fund holding crypto assets, or an unregulated entity. The legal form and registration status from the official registry are the authoritative inputs for this classification — they determine whether the counterparty falls within or outside the CARF reporting perimeter, and whether look-through to controlling persons is required for entity accounts.

Where beneficial ownership data is available in official registries, TaxDo returns it as part of the registry check. EU member states require beneficial ownership registration under AMLD. The UK provides PSC data through Companies House. The US Corporate Transparency Act established a FinCEN beneficial ownership registry. Coverage varies by jurisdiction, and TaxDo flags where BO data is unavailable.

Registry lookups are real-time. Results return within seconds for most registries, enabling entity verification at the point of onboarding rather than in batch remediation cycles. The API supports both single lookups and batch processing for portfolio-level verification across thousands of entities.

A registry check returns the complete entity record from the official source: entity name (registered and trading names), registration number, legal form, registration date, status (Active, Dissolved, Struck Off, In Liquidation), registered address, directors and officers with appointment dates, beneficial owners where available (name, ownership percentage, control type), share capital, industry classification (NACE, SIC, ISIC codes), parent company, and annual filing status. Exact field availability varies by jurisdiction and registry.

All EU member states require beneficial ownership registers under the Anti-Money Laundering Directives (AMLD). The UK provides Persons with Significant Control (PSC) data publicly through Companies House. The US established a beneficial ownership registry through the Corporate Transparency Act via FinCEN. Australia, Canada, and Singapore have varying levels of BO disclosure requirements. Coverage continues to expand globally as AML regulations tighten.

TaxDo queries official registries in real-time at the point of lookup — there is no cached or periodically updated database. Data freshness reflects what the official registry holds at the moment of the query. This is fundamentally different from commercial aggregators that compile and cache data with days or weeks of lag between updates.

Yes. The API supports batch processing for portfolio-level verification. Submit thousands of entities for parallel registry lookups across multiple jurisdictions simultaneously. Batch results include the same structured data as single lookups, with completion webhooks for asynchronous processing workflows.

KYB (Know Your Business) is a broader compliance process that includes entity verification, beneficial ownership identification, sanctions screening, and risk assessment. A business registry check is the foundational step within KYB — verifying the entity’s legal existence and details against official sources. TaxDo provides the registry verification layer that feeds into your wider KYB workflow.

Commercial aggregators compile data from multiple sources and cache it in proprietary databases. TaxDo connects directly to official government and chamber of commerce registries — the authoritative source of record. This means real-time data at point of query (not periodically updated), Tier 1 regulatory acceptance for CRS/DAC8/FATCA compliance, and authoritative entity classification rather than supplementary data.

Every Entity Classification Starts With Official Registry Data

Verify entity registration, legal form, and beneficial ownership through 120+ government registries — in real time, at the point of onboarding.