FINTRAC publishes reject/warning tables for LCTR, STR, and LVCTR. Here is how those pages become local rule packs — and where registry checks stop.
FINTRAC’s API validation pages list field IDs, rule types, actions, and messages — including codes such as 324 (contact on file) and 997 (RE-unique report reference). They are the closest thing Canada publishes to a machine-readable reject catalogue for API reporters.
What local engines can enforce
- Presence, format, lists, numeric ranges, and most cross-field when-clauses from the published text.
- Within-report uniqueness for transaction references where transcribed.
- Completing-action disposition + amount gates once compiled into arrayAny conditions.
What needs RE data
Contact/location “on file” and RE-wide uniqueness are FINTRAC-side knowledge. This product evaluates them against an optional RE registry snapshot you paste on Form or Bulk. Without a snapshot, those rules do not silently count as covered.