SAMPLE Canada Business Registry PRO | 1.5M Verified Organizations + 564K Director/Officer ...

QuantLens Canada PRO v4.9 is a join-ready “entity backbone + people layer” bundle designed for KYC/compliance workflows, entity resolution (MDM), and relationship/graph analytics. It combines a nationwide organization master file with a high-coverage director/officer edge table keyed to BN9 identifiers, so you can reliably connect people-to-organization relationships without inflating your org master table.

What’s inside (PRO bundle)

1) Organization Master (RegistryCore v4.9)

1,503,599 rows (1,492,319 unique organizations)

Fields include registry identifiers, organization name, normalized location fields (city/province), and provenance/source fields.

Personnel names exist in the core file for a minority of orgs (~13.1% orgs have a personnel_name).

Not a contact/leads database: phone/email coverage is limited by design.

2) Director/Officer People Layer (BN9 Edges v5)

564,207 director/officer relationships

76,433 BN9 entities have at least one person edge

Coverage: ~91.3% of BN9 targets present in the CRA BN9 universe (83,711 BN9 targets)

Includes mapping tables to join safely:

Canonical mapping (recommended): 1 org target per BN9 for clean BI/compliance use

Expanded mapping: all possible org targets per BN9 for graph/entity-resolution workflows

Collision transparency: 11,376 BN9 values map to multiple org targets; a collision report is included.

Why buyers use this

KYC / Compliance enrichment: strengthen organization identity, add governance relationships (director/officer graph)

Entity resolution / MDM: deterministic org keys + provenance + joinable people edges

Graph analytics: org↔person networks, shared director analysis, ecosystem mapping

Risk & due diligence support: governance context from public filings (buyer must ensure permitted use)

Delivery & quality controls

Delivered as a ZIP with UTF-8 CSVs, QA reports, join examples, and SHA-256 checksums for integrity.

Deterministic keys (org_id/org_key) and documented join patterns (canonical vs expanded) reduce row-explosion risk.

Best practice: Use the canonical BN9 mapping for clean “one org per BN9” joins; use expanded mapping only when you explicitly want multi-target graph resolution.

Suitability :

Built for data engineering teams, compliance/KYC teams, fintech/regtech, BI teams, and analytics groups that need joinable registry-grade entity data plus governance relationships.