Sceau

Knowledge centre

UBO discrepancies: what to do when declaration, register and evidence disagree

How to treat mismatches between client declarations, ownership charts, official register extracts and supporting documents.

Executive summary

UBO records must be reconciled, not merely collected.Discrepancies require review, remediation and dated evidence.Official extracts, client declarations and ownership documents should be compared in one place.

UBO work is not finished when a client fills in a form. The office must understand who ultimately owns or controls the client, compare declarations against evidence, and handle discrepancies instead of burying them in the file.

In Belgium, offices often consult the UBO register under their own access rights and then keep the extract as evidence. But official register data is only one layer. It must be reconciled against corporate documents, shareholder registers, control rights, nominee indicators and client explanations.

The most important discipline is to separate facts from conclusions: what the client declared, what the register showed, what documents support, what differs, who reviewed it and what remediation or EDD followed.

Who this applies to

This guide is for offices onboarding companies, foundations, partnerships, trusts, nominee structures or any client where ownership and control are not obvious.

  • Corporate clients with layered ownership
  • TCSP and nominee structures
  • Real-estate buyers with holding companies
  • Client declarations that differ from register data
  • EDD files involving control without simple ownership

Legal and supervisory context

The Belgian UBO register is an important source, but it does not replace professional scrutiny. The office still needs to understand ownership and control and explain what it did when records do not line up.

Discrepancies can be innocent, stale or serious. The compliance value comes from recording the mismatch, asking the right follow-up questions and deciding whether remediation, EDD or refusal is needed.

What the office must actually do

The office should convert the legal requirement into a repeatable workflow with named owners, dated records and a clear review route.

  • Identify declared UBOs and control rights.
  • Record official register consultation.
  • Upload corporate documents and shareholder evidence.
  • Compare names, percentages, dates and control routes.
  • Ask for remediation or explanation.
  • Escalate unresolved or suspicious discrepancies.

What good evidence looks like

A good file shows the graph, the source of each ownership fact, the discrepancy, the office’s follow-up and the final accountable conclusion.

Common mistakes supervisors find

  • Treating a register extract as automatically correct.
  • Ignoring control rights below ownership thresholds.
  • Failing to record stale register data.
  • Not reconciling nominee or TCSP structures.
  • Closing onboarding while discrepancy tasks remain unresolved.

Practical checklist

  • Collect declaration.
  • Consult register under office rights.
  • Upload extract.
  • Map ownership and control.
  • Compare evidence.
  • Raise discrepancy task.
  • Record remediation, EDD or refusal conclusion.
How Sceau operationalizes this
  • Captures UBO declarations and official extracts.
  • Builds ownership graph evidence.
  • Diffs declared and evidenced UBO data.
  • Raises discrepancy and EDD tasks.
  • Ledger-seals the consultation and reconciliation outcome.

FAQ

Is the KBO the same as the UBO register?

No. KBO/BCE is the company register. UBO data is a separate beneficial-ownership register workflow.

Can Sceau access the UBO register in its own name?

No. The office consults under its own rights or mandate; Sceau records and reconciles the result.

What if the register is wrong?

Record the discrepancy, request correction or explanation, and decide whether the risk requires EDD, refusal or ongoing monitoring.

Official references

From knowledge to compliance

Reading is a start. Sceau turns these obligations into a workflow that runs itself and proves itself.

Book a demo