Free training Free 1-hour training on the new FINTRAC expectations under Bill C-12, followed by live Q&A. Available on-demand and virtually across Canada, or in person in the GTA.
BriteBase
Beneficial ownership

Beneficial Ownership Material Discrepancy Report: what changed under the PCMLTFA

Canadian reporting entities are now part of the feedback loop that keeps the federal beneficial ownership registry accurate. When a regulated firm obtains beneficial ownership information that materially conflicts with the registry, it has to report the discrepancy. The obligation is operational, ongoing, and enforceable through the Bill C-12 AMP regime.

By BriteBase Compliance Team · Published June 8, 2026 · 7 min read

The federal beneficial ownership registry is one half of Canada's response to FATF criticism of corporate opacity. The other half is the new requirement that PCMLTFA-regulated firms act as a feedback loop on the registry: when a reporting entity obtains beneficial ownership information that materially conflicts with what is in the registry, the entity has to file a Material Discrepancy Report. The point is to make the registry self-correcting and to put the real-world signal regulated firms see into the system that law enforcement, FINTRAC, and other government users rely on.

This article covers what the Material Discrepancy Report is, when the obligation triggers, what counts as "material", how to file, the common pitfalls, and what BriteBase does to operationalise the requirement.

What is the Material Discrepancy Report?

The Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA) already required reporting entities to obtain and verify beneficial ownership information on corporate customers. The amendment that introduced the Material Discrepancy Report obligation added one more step: a regulated entity has to compare the beneficial ownership data it obtains against the public federal beneficial ownership registry. Where the comparison reveals a material discrepancy and the discrepancy cannot be resolved, the entity has to file a report.

The mechanism is borrowed from the EU's Fifth Anti-Money Laundering Directive (5AMLD), which introduced the "obliged entities report discrepancies" model for member-state UBO registries. Canada's version is operationally similar: regulated firms become a feedback loop, not a passive consumer of registry data.

The public-policy point of the obligation is straightforward: the registry is only as useful as the information it contains. Corporate filings are self-reported; bad actors are the ones least likely to disclose. Regulated firms see the real-world signal when a corporate customer turns up with documentation that does not match the registry. Forcing those firms to surface the mismatch closes the loop.

When does the obligation trigger?

The obligation runs continuously through the customer relationship. It triggers at three distinct points.

1. Onboarding

When a corporate customer is onboarded, the entity gathers beneficial ownership information using its usual KYC process. That information has to be compared against the public registry record (where one exists) before the relationship goes live. If there is a material discrepancy and it cannot be resolved at onboarding, the report goes in within the prescribed window.

2. Periodic refresh

Risk-based refresh of beneficial ownership data is already a PCMLTFA expectation. Each refresh becomes a new opportunity for discrepancy. A previously matching record may now disagree with the registry; a new beneficial owner may have appeared; an ownership percentage may have crossed the disclosure threshold. The discrepancy check is part of the refresh, not a parallel workflow.

3. Triggering events

Material changes in customer behaviour, ownership announcements, news flow, sanctions screening hits, or transaction monitoring escalations can all surface fresh beneficial ownership information. Where that new information conflicts with the registry, the obligation triggers again. This is the hardest category to operationalise, because the trigger is implicit rather than calendar-driven.

What counts as "material"?

"Material" is a working term, not a numeric threshold. Three categories are clearly material and one category is clearly not.

Material

  • Different individuals. The customer's BO information names a person not in the registry, or omits a person who is listed in the registry. This is the most common material discrepancy.
  • Different ownership percentages, especially across a disclosure threshold. If the customer says individual X holds 30% but the registry shows 12%, the difference matters because it crosses the line at which disclosure is required.
  • Different control rights. The customer's BO information identifies a controller who is not listed in the registry, or vice versa. Control rights without an ownership percentage are still in scope.

Not material

  • Administrative variance. Spelling variants, address differences (especially for individuals who have moved), dated phone numbers, or differences in title (CEO vs President) are typically not material on their own. They become material if they obscure identity.

The materiality assessment is itself part of the file. An examiner will read a decision that the difference was not material, and will expect to see the reasoning written down, not implied.

The filing workflow

Operationally, the Material Discrepancy Report obligation breaks into six steps. Each step has to leave a documentary trace.

  1. Obtain BO information from the customer. Through KYC, the existing onboarding workflow, or refresh. The information has to be sourced, not assumed.
  2. Pull the registry record. The federal BO registry record for the corporate customer is captured at the same time as the customer-provided BO data, with a date-stamped copy retained in the file.
  3. Compare and decide. The comparison happens, materiality is assessed, and the decision is logged. A non-material discrepancy is documented with reasoning. A material discrepancy that cannot be resolved with the customer becomes a reportable event.
  4. Attempt resolution with the customer. Before filing, a regulated entity is generally expected to attempt to resolve the discrepancy through a follow-up with the customer. The customer may have updated their corporate filings, the registry may be stale, or the customer's documentation may be wrong. This step often closes the file without a report.
  5. File within the prescribed window. Where the discrepancy persists, the report is filed within the regulatory window. The window's exact length is defined in regulation; treat it as a hard deadline, not a target.
  6. Close the loop in the file. Date filed, report identifier, customer notification (where required), and the disposition of the file. The next time a refresh runs, the prior discrepancy and its outcome should surface automatically.

Common pitfalls

Five operational mistakes account for most examination findings on this obligation.

  • Treating it as a one-time check. The obligation is continuous. A program that performs the check at onboarding but not at refresh or at trigger events will fail the test of "reasonably designed, risk-based and effective" under Bill C-12.
  • No documented materiality assessment. A non-material conclusion that is not written down looks indistinguishable from a missed obligation. The reasoning is the artefact.
  • No date-stamped registry record in the file. A registry record pulled today and compared to BO information pulled six months ago is a near-useless comparison. The two timestamps need to be close, and both retained.
  • Customer follow-up handled by email and forgotten. If the resolution step lives in inboxes, the obligation lives in inboxes. The workflow tool should track the open item to closure.
  • Spreadsheet-based reconciliation. A growing book of corporate customers cannot be reconciled to the registry by hand. The discrepancy check has to live in the same system as KYC and screening.

How this fits with examiner posture under Bill C-12

The new statutory standard under Bill C-12 is reasonably designed, risk-based and effective. The Material Discrepancy Report obligation is exactly the kind of process where the new standard bites. A program that performs the check at onboarding and never again may have a policy that looks reasonable on paper but does not produce outcomes. An examiner now asks: how many Material Discrepancy Reports has the firm filed this year, in proportion to the book of corporate customers? A zero-report year on a large book is itself a flag.

This connects to the wider enforcement pattern. The home-page enforcement summary shows 84 published AMP actions between November 2020 and May 2026, totalling more than CAD $239.5 million. Beneficial ownership and KYC failures are the universal common thread across the cited violations. The Material Discrepancy Report obligation is the operational extension of those long-standing failures.

How BriteBase operationalises the obligation

The discrepancy check is built into the AML Operating Platform's corporate-customer onboarding flow. When BO information is captured, the platform pulls the registry record, runs the comparison, surfaces material differences for review, captures the materiality decision, and tracks any resolution step with the customer. If a Material Discrepancy Report has to be filed, the report is generated from the same record and submitted in the required format, with the closing-the-loop step (date filed, identifier, disposition) saved back to the customer file. The cadence for refresh and the trigger events that re-run the check are configured once and inherited by every corporate customer the firm onboards.

For programs that have to retrofit the obligation against an existing customer book, BriteBase's Special Projects bench handles the backfill: pulling current registry records, running the comparison, working through the materiality decisions, and filing reports on the records that need them. The Advisory Services bench is the right path for the prior question of when an existing book is large enough that a backfill should be sequenced over months rather than completed in one pass.

FAQ

What is a Beneficial Ownership Material Discrepancy Report?

It is the obligation, under PCMLTFA amendments tied to Canada's federal beneficial ownership registry, for designated reporting entities to notify the relevant authority when the beneficial ownership information they obtain on a corporate customer materially conflicts with the information held in the public registry. The purpose is to make the registry self-correcting: regulated entities act as a feedback loop on registry accuracy.

When does the obligation trigger?

Once a reporting entity has obtained beneficial ownership information on a corporate customer (at onboarding, refresh, or in the course of a transaction), it must compare that information against the relevant public beneficial ownership registry. Where the comparison reveals a material discrepancy that the entity cannot resolve, the entity has to file a Material Discrepancy Report within the time prescribed by regulation. The obligation runs continuously through the relationship, not only at onboarding.

What counts as material?

A material discrepancy is one that affects the identity, ownership stake, or control rights of a person listed in the public registry, or one that suggests the registry omits a person who should be listed. Minor administrative differences (spelling variants, alternative addresses, dated contact information) are typically not material; differences in named individuals, ownership percentages crossing the disclosure threshold, or undisclosed controllers typically are. The reporting entity has to document its reasoning either way.

Who has to file?

The obligation applies to designated reporting entities under the PCMLTFA, including financial entities, money services businesses, real estate brokers, securities dealers, and other captured industries. The exact scope is defined in regulation and continues to evolve as PCMLTFA-captured industries expand. Title insurers, mortgage companies, and cheque cashing and factoring firms newly brought into the PCMLTFA reporting tent are also captured.

What information goes into the report?

Identifying information for the corporate customer, the registry record reviewed, the specific discrepancy identified, the supporting beneficial ownership information the entity obtained, the steps taken to resolve the discrepancy with the customer, and the conclusion. The standard is to make the report self-contained: a reviewer should not need additional context to act on it.

What if the customer disputes the discrepancy?

The reporting entity is generally expected to attempt to resolve the discrepancy with the customer before filing. If the customer updates their corporate filings, the registry may catch up and the discrepancy disappears. If the customer disputes the entity's understanding of beneficial ownership, the entity has to decide whether to credit the explanation or file anyway. The decision and reasoning go into the file.

What are the consequences of not filing?

Failure to file a Material Discrepancy Report when required is a PCMLTFA violation enforceable through the Administrative Monetary Penalty regime. Under Bill C-12, AMP ceilings per violation rose roughly forty times. Beneficial ownership failures are also a high-frequency examination finding, particularly in real estate brokerages, and the Material Discrepancy Report obligation is now part of the same examiner's checklist.

Back to all resources

Reading is useful. A conversation is faster.

Book a call and we'll tell you, plainly, where your program stands against Bill C-12 and what to fix first. No retainers. No hourly rates.

Prefer to talk now? Call 905-218-7088 or email info@britebase.ca