Pre-file FINTRAC checks
LCTR, STR, LVCTR, EFTR, and CDR field checks in your browser — before you submit the report yourself.
What we check
5017 enforced checks across these report types. Source and last-verified date are on each pack.
LCTR
711 enforced
Official source · last verified 2026-09-23
STR
1094 enforced
Official source · last verified 2026-09-23
LVCTR
699 enforced
Official source · last verified 2026-09-23
EFTR
1642 enforced
Official source · last verified 2026-09-23
CDR
871 enforced
Official source · last verified 2026-09-23
How it works
- Check one report or a small batch of filled LCTR, STR, LVCTR, EFTR, or CDR fields.
- Scan transactions: 24-hour cash-received clustering plus LCTR and EFTR thresholds from a transactions CSV.
- Filing deadline helper: estimated local 5-business-day EFTR clock and 15-calendar-day LCTR clock from a transaction scan; sourced 15-calendar-day CDR filing-guidance in the catalog (no casino CSV profile) — not a regulator filing clock.
- Reject decoder: Catalog ValidationRuleNumbers (LCTR, STR, EFTR, LVCTR) are not the same count as pack enforced checks. Plain English when we have the meaning.
We show our work
- Every rule lists its source.
- Everything we don't cover is listed too.
- Checked in your browser. Nothing is filed.
- FINTRAC administrative monetary penalties scale per violation under Bill C-12. These checks do not assess a penalty.
What we don't cover
- 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