Federal corporations in Canada use an eight-digit corporation number, though the fields that matter in diligence work sit much deeper in the registry payload. Corporations Canada exposes status history, annual filing state, registered office details, director appointments, and continuance events that often appear later in cached commercial datasets.
That gap shows up fast when you are tracing a financing vehicle across provinces or checking whether a reporting issuer still exists before settlement. We have seen dissolved CBCA entities remain marked active in internal systems for weeks after the federal register changed state.
What the federal register returns
Corporations Canada covers entities incorporated under the Canada Business Corporations Act. Through OpenRegistry MCP, the usual flow starts with search_companies and then moves into get_company_profile.
A basic search call looks like this:
{
"tool": "search_companies",
"arguments": {
"jurisdiction": "CA",
"query": "Maple Leaf Holdings"
}
}
The response includes the federal corporation number together with the legal name recorded by Corporations Canada. That number becomes the stable reference for later checks.
get_company_profile returns the current federal profile and keeps upstream registry fields inside jurisdiction_data. For Canadian diligence work, these are usually the fields people care about:
corporationNumberbusinessNumbergoverningLegislationstatusstatusDateannualFilingsregisteredOfficeAddressdirectorMinimumdirectorMaximumcontinuanceDate
The corporation number and CRA business number get mixed up constantly in onboarding documents. They are not interchangeable. The corporation number identifies the entity on the CBCA register. The business number belongs to the CRA tax system.
Director data is often more detailed than people expect from a public register. get_officers exposes director names, appointment dates, and service addresses where the registry publishes them.
Example:
{
"tool": "get_officers",
"arguments": {
"jurisdiction": "CA",
"company_number": "1234567-8"
}
}
Continuance history is easy to miss during M&A screening. Canadian entities move between provincial and federal regimes more often than internal entity-resolution systems expect. We ran into this while tracing an Ontario corporation that later continued under the CBCA. Same legal name. Older internal records still treated the federal registration as a separate entity.
Annual filing state is another useful signal. An overdue annual return does not mean immediate dissolution, though it often tells you where the file is drifting. Treasury and credit teams usually care more about whether the legal shell can still execute agreements than whichever industry description appears in the profile.
Where the register stops
Corporations Canada is not a beneficial ownership register.
Canada has expanded transparency obligations in recent years, including the federal Individuals with Significant Control regime under the CBCA. Public disclosure still remains narrower than many compliance teams expect. The federal register should not be treated as a complete UBO source comparable to internal KYC records held by financial institutions.
OpenRegistry also does not layer interpretation onto the registry response. The MCP server returns upstream data exactly as provided by the source authority. No ownership graphing is attached to the output. No sanctions enrichment either.
Historical state has limits as well. Requests hit the live register directly. If a director resigns today and the filing is processed, the current response reflects that latest state instead of a stored historical snapshot.
Document availability varies. Some filings expose retrievable source documents through fetch_document. Others return little beyond filing metadata.
Working with filings and documents
Federal filing history becomes useful during IPO preparation or debt issuance reviews because you can compare amendments against disclosure drafts and board materials.
A filing query looks like this:
{
"tool": "list_filings",
"arguments": {
"jurisdiction": "CA",
"company_number": "1234567-8"
}
}
Depending on the entity, the register may return annual returns, articles of amendment, continuance filings, dissolution notices, or director changes.
If a filing exposes a retrievable source document, fetch_document can pull it directly.
{
"tool": "fetch_document",
"arguments": {
"jurisdiction": "CA",
"document_id": "filing-2024-09-18-001"
}
}
That direct registry path matters during audit disputes. A reviewer can trace the exact filing used in a diligence decision instead of relying on copied summaries from the legacy paid databases.
Cross-border checks get messy quickly
Canadian corporate structures regularly split operations across federal and provincial registrations. A CBCA corporation may still maintain extra-provincial registrations in British Columbia or elsewhere.
That creates matching problems during counterparty screening.
OpenRegistry currently covers federal Canada alongside British Columbia and Northwest Territories registries. The MCP interface stays consistent even though the underlying registries behave differently.
A typical compliance workflow looks something like this:
- Search the federal CBCA entity.
- Pull current directors and filing state.
- Search provincial registries for matching legal names.
- Compare addresses against incorporation dates.
The workflow sounds straightforward. It still catches real problems. One recurring lending issue is a dissolved federal corporation remaining marked active inside internal CRM systems because a provincial registration stayed open.
Issuer verification work is usually blocked by stale data rather than missing data. Overnight exports from aggregator platforms can lag behind the official register when director appointments or dissolution filings change during the day.
The OpenRegistry MCP server gives AI assistants direct access to the live registry response instead of a warehouse copy normalised weeks earlier. Teams building KYB tooling around CBCA entities can inspect the raw filing state directly at openregistry.sophymarine.com/mcp
Top comments (0)