INSIGHTSPUBLISHED · 2026-08-25

Before answering a bank compliance request, build an evidence matrix

Turn every question from the reviewer into one row: what is being asked, what proves it, what is still missing and who owns the answer.

Insight brief

Turn the bank email into an evidence matrix before writing the answer.

Every reviewer question should map to a proposition, supporting record, relevant amount/date/account, translation need and unresolved professional dependency.

01 · Why it matters

Ad hoc email replies create multiple narratives. A matrix creates one controlled vocabulary for the transaction and makes gaps visible before documents are submitted.

02 · Who should care
  • People answering an active Canadian bank compliance request
  • Clients with property, inheritance or business funds connected to Ukraine
  • Accountants and advisers organizing evidence for a financial institution
03 · Practical next move
  1. Copy every bank question exactly.
  2. Separate facts from evidence and professional interpretation.
  3. Use one vocabulary for dates, currencies, counterparties and transaction type.
  4. Send the smallest complete indexed package that closes the identified gaps.
Full note

The context behind the brief.

Read this section for the underlying reasoning and operational detail. Where a rule can change, use the dated source trail rather than treating the article as permanent authority.

01

Context

Bank compliance requests become difficult when the client answers them as an email conversation instead of a file. One department asks where the money came from, another asks for ownership evidence, a third requests tax records, and several slightly different explanations begin circulating. The risk is not only missing documents. It is inconsistency between narratives.

An evidence matrix turns the request into an operational object. Copy each bank question exactly. Next to it, record the proposition the bank is trying to verify, the document or record that proves it, the relevant amount/date/account, any translation requirement and whether a professional explanation is still needed.

02

Separate facts, evidence and interpretation

A sale agreement is evidence of a transaction. A bank statement is evidence of a movement of money. A tax return or payment record may support the treatment of that transaction. A cover letter is not a substitute for any of those records; its job is to connect them so the reviewer does not have to infer the chronology.

Where an issue genuinely requires legal, accounting or tax analysis, identify that dependency explicitly. Do not disguise an unresolved professional question inside confident wording. A transparent package is easier to update when the bank asks a follow-up question and reduces the chance of contradicting an earlier explanation.

03

Use one transaction vocabulary everywhere

Names, dates, currencies, counterparties and transaction labels should remain consistent across the cover note, translations and supporting records. If the Ukrainian contract calls the event a property sale, a later bank explanation should not casually characterize it as a family transfer or business payment. If currencies differ because of conversion, show the conversion instead of leaving the reviewer to guess why the amounts changed.

The strongest package is usually smaller than the client expects. It is indexed, chronological and responsive to the questions actually asked. Extra documents belong only when they close a real evidentiary gap.

Editorial note

This publication is an operational/editorial note rather than a current-rule bulletin. If a real file reaches a government, bank, notary, registry or other change-sensitive step, confirm that step against the current competent source.

Have a Canada ↔ Ukraine file behind this topic?

Send the real situation. We’ll map the operational route and separate what is stable from what needs current verification.

Start a Case →