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,246 published FINTRAC, FinCEN, and AUSTRAC rules.
• Every rule lists its source.
• Everything we don't cover is listed too.
• Checks run in your browser. We do not file.
• 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 FIU Ready's interpretation of public regulator sources — always check official guidance. Official reporting: FINTRAC, FinCEN, AUSTRAC.

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

FinCEN not covered

DOEP; FBAR; SDTM; filing/submission; acknowledgement handling

AUSTRAC not covered

AUSTRAC Online structural schemas need an Australian reporting-entity login, so we haven't copied those rule lists; draft SMR XML (not used until final)

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 deadline radar (FINTRAC CDR page / PCMLTFR s. 132(3)); the MSB scanner does not start a CDR row. AUSTRAC v1 is threshold-only and does not invent a TTR countdown.

What the packs cover

Covered means the check can fail locally. On Rule packs, each pack shows enforced vs registry vs not-enforced counts. Production filings must still pass the regulator.

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 FinCEN Attachment A (document-level CTR/SAR/Form 8300) plus local BSA batch envelope checks when Bulk XML looks like EFilingBatchXML (offline xmllint --schema uses vendored ISM/CVE + schema-valid fixtures) and a Travel Rule checklist pack (FTR — not a BSA EFTR form); FINTRAC API validation pages (LCTR, STR, LVCTR, EFTR, CDR) including threshold/MD/aggregation compilers and a soft IR2020 Iran-signal warning; and AUSTRAC AML/CTF Rules (TTR, SMR, IFTI-E as EFT-equivalent, IFTI-DRA Chapter 17 identity). CDR CAD-equivalent upper limit (341) after conversion stays not_enforced — the published API table has no exchangeRate field. The 15-calendar-day CDR filing clock is sourced filing-guidance (FINTRAC CDR page / PCMLTFR s. 132(3)), not an API reject. Stateless: FINTRAC on-file / RE-unique checks need a local RE registry snapshot (no DB, no live registry API). Full IR2020 origin/bound determination and login-gated AUSTRAC Online XSDs are not fully encoded. Does not file — production filings must still pass the regulator.

Official sources: LCTR rules, STR rules, LVCTR rules, EFTR rules, CDR rules, CTR XML guide, SAR XML guide, Form 8300 XML guide, Travel Rule recordkeeping (31 CFR 1010.410), AML/CTF Rules 2025 Part 9, 2007 Rules Chapter 16 (IFTI).

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

Questions — contact