About

What this is

A pre-file data-quality gate. Checks run against transcribed, country-specific rules before you submit through the regulator. No case-data store, no database of reporting-entity contacts or locations, no portal login, no filing. Check one and Batch check are stateless: any FINTRAC on-file / uniqueness checks use a registry snapshot you paste or load as a local fixture in this session only. Reject log is optional and stays in this browser — hashes, finding counts, and statuses you type from FWR (formerly F2R) or other portal acknowledgements, never raw report bodies, not a filing archive.

What we do

• Pre-file checks against 5,017 published FINTRAC rules.
• Every rule lists its source.
• Everything we don't cover is listed too.
• Checked in your browser. Nothing is filed.
• Findings show pass, warn, or fail before you submit to the regulator yourself.

What we don't do

• We do not file reports.
• We do not log in to regulator portals.
• We do not give legal advice.
• We do not claim a filing will be accepted, or that you are compliant.
• Packs are AML Deck's interpretation of public regulator sources — always check official guidance. Official reporting: FINTRAC.

FINTRAC not covered

civic and municipal public holidays under Interpretation Act s. 35(1)(b) (city-council days; Natal Day NS and Gold Cup Parade Day PEI are not provincial statutes we can cite) and employer-specific closures, in the EFTR working-day count; FINTRAC CDR CAD-equivalent upper limit (341) after currency conversion — published API table has no exchangeRate field (valueInCanadianDollars is mutually exclusive with amount); rules that need a regulator data feed we don't have yet

How rule packs stay current

• Each pack lists its source URL and last-verified date.
• Every change is versioned with a dated changelog.
• You can sign up for change alerts on Rule Packs.

Why we built this

Small teams often fix formatting and cross-field slips by hand — or file, take a bounce, and scramble after the statutory clock has started. This tool catches those issues on your machine first. Report-pack validation does not start a filing clock. Scan Transactions can show a local countdown from dates in a transaction CSV when the profile has a verified clock (15 calendar days for LCTR and CTR; 5 working days for EFTR — nationwide public holidays applied; provincial statutory days and Boxing Day extras applied as our reading of Interpretation Act s. 35(1)(a), not FINTRAC's list; civic and municipal holidays and employer-specific closures not applied, including Natal Day NS and Gold Cup Parade Day PEI). CDR's 15-calendar-day window is sourced filing-guidance on the filing deadline helper (FINTRAC CDR page / PCMLTFR s. 132(3)); the transaction scanner does not start a CDR row.

What the packs cover

Covered means the check can fail locally. Coverage & limitations lists what is and is not checked. On Rule Packs, each pack shows enforced vs registry vs not-enforced counts.Submit production filings through FINTRAC; verify against official sources.

How it runs

Private for case data

Form and bulk check in the browser. No payload log. PII shows as [MASKED]; rules use the in-memory original. Page views may be counted — details on Privacy.

One engine

validateReport() powers Check One, Batch Check, and Sheets / Excel (subscription). See Pricing for free vs paid. Browser extensions are not built — see Integrations.

Conditional rules

Fields can become required or must-be-blank from other values. Browse every transcribed rule on Rule Packs.

Failures

Plain-language message, field path, rule ID, and remediation when the pack has it.

How packs are sourced

Transcribed from published FINTRAC API validation pages (LCTR, STR, LVCTR, EFTR, CDR). Packs are not live-synced. Production filings must still pass FINTRAC.

Official sources: LCTR rules, STR rules, LVCTR rules, EFTR rules, CDR rules.

Pre-file checks only — not legal advice. Verify against official regulator sources.

Questions — contact