FINTRAC audit prep: from binder to workflow

Every managing broker knows the feeling. The examination notice arrives, and somewhere between the deal files, the shared drive, and three retired admins’ inboxes sits the evidence you now have weeks to assemble: identification records, receipt-of-funds records, review sign-offs, training logs. None of it is missing, exactly. All of it is scattered.

That scatter is the real cost of FINTRAC compliance for most brokerages. The obligations themselves — verify identity, keep prescribed records, file the required reports, run a documented program — are demanding but knowable. FINTRAC publishes sector guidance that describes them in detail. What turns them into a fire drill is when the records are created informally and reconstructed formally.

How records scatter on a live deal

Consider what actually happens on a busy deal. An agent photographs a driver’s licence and texts it to the office. The deposit arrives by e-transfer and someone notes it in a spreadsheet. The conveyancer asks whether the third-party determination was done, and the answer lives in somebody’s memory. Each step happened; almost none of it landed as a structured record at the moment it happened.

Audit preparation is then archaeology. Staff dig through email threads to prove work that was genuinely done, and the brokerage pays for the same compliance twice — once to do it, once to evidence it.

The brokerage pays for the same compliance twice — once to do the work, once to evidence it.

The workflow inversion

The workflow alternative inverts the order: build the record as the work happens, and examination prep becomes a report you run rather than a project you staff. In practice that means a few specific things:

• Every deal starts with a compliance checklist generated from its deal type, so nobody decides from scratch what diligence applies.
• Identification is captured into the deal record at intake — who was verified, by which method, when, and by whom.
• Funds events create structured records when money moves, not at month end.
• Reviews are submitted and signed off in a queue with timestamps, so "who approved this and when" has a recorded answer.

None of this changes what FINTRAC requires. It changes the marginal cost of proving it — from hours per file to minutes per report.

What an examination typically asks for

It helps to know what the request usually looks like before it arrives. While every examination differs, FINTRAC’s published material and the experience of brokerages that have been through one point to a recognizable document set:

• The compliance program itself — written policies and procedures, the risk assessment, and evidence they are current.
• Training records: who was trained, on what, when.
• The results of the program’s periodic effectiveness review.
• A sample of transaction files, with the identification, receipt-of-funds, and determination records each one should carry.
• Any reports filed — and the internal trail behind decisions not to file.

Read that list again with the workflow lens: every line is either a standing document your compliance officer maintains, or a query over records — if the records were structured when created. The sample of transaction files is where binder-based brokerages lose weeks, and where workflow-based brokerages run an export.

The second-order benefit: review quality

There is a benefit brokerages notice after a quarter or two: review quality improves. When the review queue shows aging and status, items stop dying silently in inboxes. Compliance officers spend their attention on judgment calls — the unusual transaction, the incomplete identification — instead of on chasing paper. The examiner conversation changes in the same way: from "give us three weeks" to "here is the report, and here is the queue it came from."

The same records also serve the program’s own hygiene. The periodic effectiveness review that a compliance program requires is far easier to conduct honestly when the reviewer can see completion rates, aging, and exception patterns instead of interviewing staff about what usually happens. Weak spots surface as data — a deal type whose checklists chronically stall, an office whose reviews age past SLA — while they are still internal findings rather than examination findings.

What software does and does not do

A caution worth stating plainly, because software vendors routinely blur it: no platform makes a brokerage compliant. Your compliance officer owns the program. Your policies define the work. FINTRAC’s guidance — not any vendor’s marketing, including ours — defines the requirements. What a system of record changes is whether the evidence of your compliance exists as a coherent set or as an archaeology site.

If you want the obligations themselves in plain language, start with the educational overviews in our compliance hub — they cite the official FINTRAC sources to rely on. And if the workflow approach sounds like the missing piece, that is what OpSphere DealFlow is built around: checklist templates by deal type, SLA-timed review queues, deposit and receipt records, and locked deal history. The examination notice will still arrive. The difference is what happens in the hour after you read it.