Dutch KVK numbers use eight digits, yet the Handelsregister also issues separate establishment identifiers for branch locations. That trips people up during KYB reviews because a single legal entity can operate from multiple registered sites, each with its own address record.
In Dutch onboarding flows, the Chamber of Commerce register is usually the first registry lookup after sanctions screening. We use it to confirm incorporation status, directors, trading names, insolvency indicators, and branch structure before ownership review starts.
OpenRegistry serves the Netherlands register live through MCP. Queries hit KVK directly rather than stale aggregator exports. The returned jurisdiction_data preserves the original Dutch field names and payload layout, which makes audit sampling easier when analysts need to walk a field back to the source entry.
Fields that matter during Dutch KYB checks
Dutch entities create odd edge cases around trade names and establishments. A marketplace merchant may present itself under a commercial brand that barely resembles the statutory company name. KVK records usually contain enough detail to reconcile both.
A typical get_company_profile response for an NL lookup can include:
kvkNumberrsinlegalFormtradeNamesbusinessActivitiesvisitingAddressmailingAddressestablishmentsregistrationDatecurrentStatus
The rsin field matters during tax reconciliation and public-sector matching because it functions as the fiscal identity number for many Dutch entities. During enhanced due diligence, we often compare the RSIN against VAT-linked invoices or onboarding documents supplied by the customer.
tradeNames deserves careful review too. Dutch SMEs often operate under several commercial names. Some aggregator datasets flatten those into one text blob. That creates avoidable mismatches during sanctions screening or adverse-media review.
Officer lookups help with operational verification. get_officers can expose director names, appointment dates, authority structures, and registered roles pulled from KVK records. Useful when checking whether the person signing onboarding paperwork can actually bind the entity.
What you will not get from KVK
The Netherlands restricted access to parts of its ownership data after the CJEU C-601/20 ruling on public UBO registers. Public access to the Dutch UBO register was suspended, so standard company lookups should not be treated as a broad beneficial ownership source.
That becomes a genuine limitation in AML investigations involving layered holding structures. You can still establish incorporation status and management structure through KVK, though beneficial ownership evidence may require regulated access channels or customer-supplied documentation.
OpenRegistry does not bypass restricted datasets. If KVK limits access to a record or connected register, the MCP response reflects the same restriction.
Historical snapshots are another gap. Every request runs live against the registry of record. If your audit policy requires point-in-time evidence retention, you need to store retrieved payloads internally.
Filing depth varies by entity type as well. Smaller Dutch private companies may publish far less financial detail than larger reporting issuers. Risk-scoring systems should account for that instead of assuming identical filing coverage across all entities.
Querying KVK through MCP
Most onboarding flows begin with a company name search. We usually search both the statutory name and the supplied trading name because Dutch retail and logistics merchants often lead with branding rather than the registered entity name.
{
"tool": "search_companies",
"arguments": {
"jurisdiction": "NL",
"query": "Mollie B.V."
}
}
Once the entity is identified, pull the register profile directly.
{
"tool": "get_company_profile",
"arguments": {
"jurisdiction": "NL",
"company_number": "30204462"
}
}
Officer checks usually follow.
{
"tool": "get_officers",
"arguments": {
"jurisdiction": "NL",
"company_number": "30204462"
}
}
If the register exposes filing metadata for that entity type, list_filings can highlight dormant periods, restructuring events, or governance changes that deserve manual review.
Dutch onboarding quirks
The Netherlands produces fewer formatting problems than some European registers, though a few operational quirks appear repeatedly.
Branch structures matter. One Dutch legal entity can maintain several establishments with separate operating addresses. Payment processors sometimes flag fulfilment centres or warehouse locations as onboarding mismatches even when the establishment is properly registered.
Legal form handling matters too. Dutch entities use structures such as B.V., N.V., stichting, vereniging, and coöperatie. Governance rules differ between them. Ownership visibility does as well.
Cross-border structures appear often. Dutch holding companies frequently sit inside wider EU groups involving Belgium, Luxembourg, or Cyprus. OpenRegistry currently serves several connected European jurisdictions, which helps when tracing relationships across onboarding chains.
Direct registry retrieval also changes the audit trail. Instead of citing an aggregator record refreshed months earlier, analysts can reference the underlying KVK result retrieved during onboarding. That distinction matters when regulators ask how a merchant's legal existence or director structure was verified on a specific review date.
OpenRegistry exposes the Dutch registry through a free MCP endpoint at https://openregistry.sophymarine.com/mcp
Top comments (0)