Beyond the F2R portal. Built for the way banks actually file.
Every reporting entity faces the same choice: submit one report at a time through the F2R web portal, or bulk-submit via the FINTRAC batch-submission API. EasyLoad sits on top of the batch channel — giving you machine-to-machine power without the developer overhead.
A browser-based portal where compliance officers key in each report by hand. Designed by FINTRAC for organisations with low to moderate reporting volumes — typically real-estate brokers, small MSBs, dealers in precious metals, and casinos with under ~100 reports per month.
Machine-to-machine submission of hundreds of reports in one signed batch — wrapped in a compliance-officer-friendly dashboard. EasyLoad is built for banks, large MSBs, securities dealers, life insurers and casinos filing at scale, where the F2R portal is no longer the cheapest option.
EasyLoad ingests transactions from your core in one simple CSV format — drop the file into a watched folder, push it to our SFTP endpoint, or let us pull it on a schedule. EasyLoad takes it from there: validate, map, build the F2R JSON, and submit it directly to FINTRAC. No core-system replacement, no analyst re-keying, no manual portal sessions sitting between your ledger and the regulator.
Pick whichever delivery mechanism your IT team can stand up fastest. The downstream pipeline is identical regardless of how the file lands.
Drop the CSV into a watched SFTP folder on our perimeter. The ingest worker fires within seconds of file-close, validates UTF-8 encoding, header signature and row count, then archives the file under a content hash. Tenant-isolated chroot, key-based auth only — the simplest mode to start a pilot with.
Your core POSTs the CSV (multipart or raw) to a per-tenant HTTPS endpoint behind mTLS. The same validators run on arrival, and a synchronous 202-Accepted comes back with a job ID your core can persist for downstream reconciliation. Best when your network team prefers outbound HTTPS over SFTP.
EasyLoad reaches out on a schedule — every 15 minutes, hourly, or end-of-day — and pulls the latest CSV from your SFTP server or a REST endpoint your team exposes. Idempotent fetch keyed on filename + checksum, so a re-run never produces duplicate FINTRAC reports. Useful when the source system can only emit files on its own cadence.
Most reporting entities still type each STR · LCTR · EFT · CDR into the F2R web portal field by field — one record, one browser session, no audit memory. EasyLoad rides FINTRAC's batch-submission channel instead, giving your AML desk machine-to-machine throughput without anyone touching XML, JSON or the FINTRAC developer kit.
Past 50 reports a month, the portal stops being the cheap option. 1,000 STRs through the portal burns roughly 330 officer-hours per quarter; the same workload through EasyLoad lands in hours, not weeks. Officers stay in charge — they review, sign, and submit from the dashboard.
Ingest from your core or message bus. Schema-check every record against the live F2R rules. Officer review and supervisor sign-off in the dashboard. JSON build to the regulator's wire format. Direct send into the F2R API with idempotent retries and signed acks.
Every step is parallelisable and journalled. Loop time collapses from days to minutes — and the bounce rate drops from the industry's ~12% portal average down to under 0.1% on EasyLoad.
LCTR cash totalled across branches and channels per client over a rolling 24 hours — the portal sees one record at a time, EasyLoad sees everything. Bank of Canada rates pulled at the cut-off and applied uniformly with conversion lineage. STR narratives pre-drafted by the rule engine against indicator-of-ML patterns; officers review and refine instead of typing from blank.
Every edit, view, sign, send and FINTRAC ack is hashed and journalled with officer attribution. When an inspector arrives, the evidence pack on any batch exports as a signed ZIP: feed → schema check → JSON → ack → chain hash. No hunting through inboxes, no shared-drive notes, no gaps that become findings.
Eight reasons compliance desks abandon the portal — each one a daily friction that EasyLoad removes outright.
Strict ISO codes, postal patterns, SIN masking, date formats. One typo and the batch comes back — hours later, sometimes overnight.
LCTR rules need cash totalled across branches per client over 24 hours. The portal sees one record at a time; cross-branch totals slip through.
Submit, wait, partial rejection, hunt for the bouncing record, re-key, resubmit. A 30-day STR clock evaporates in two cycles.
Submitted records sit in a table, but who edited which field, when, and why lives nowhere outside an officer's notepad. Inspectors will ask.
Senior eyes on every STR before send. Past 100 STRs a month, approval becomes the throughput cap — not the analysts.
Manual BoC rate lookups create inconsistencies that look like structuring to FINTRAC, even when the officer was just inattentive.
Pulling the evidence on a single batch from the portal, the inbox approval thread, and a shared drive takes days — and missing pieces become findings.
FINTRAC publishes Administrative Monetary Penalties — and the company name. Recent actions cite deficient STR procedures and late filings.
Walk the numbers through at scale and keystroke pain compounds — an entire compliance crew vanishes into portal sessions for two solid work-weeks every quarter.
Each officer eats roughly 82 hours — about ten working days — on portal sessions alone. That's an 8-hour day, every weekday for two solid weeks, on nothing but typing into a browser form.
Bottom line: two full work-weeks of an entire AML desk — gone, every quarter — to portal typing. On bad quarters it stretches to three. Annualised, that's 8–12 work-weeks per team before a single LCTR or EFT report is even started.
Avg STR bounce rate: ~12% industry average
Time per batch: 4–8 hours officer + 1–2 hours supervisor
STR bounce rate: < 0.1% (99.9% acceptance)
Time per batch: 15 min officer + 30 sec supervisor sign-off
EasyLoad consolidates collection, validation, generation and submission of FINTRAC reports into one inspectable pipeline — purpose-built around the F2R schema and PCMLTFA obligations.
Pulls transactions from core banking, payment rails or ledger systems, then classifies each event by report type (STR, LCTR, EFT, CDR).
Every record runs against the live F2R schema in-flight — missing fields, format breaks, prohibited values and duplicates surfaced before send.
Machine-to-machine delivery into FINTRAC. No PDF uploads, no portal copy-paste. Idempotent retries, signed acks, audit IDs preserved.
Workspaces designed by AML practitioners. Bulk-edit, transaction-level review, status feed, one-click resubmission of corrected records.
Lower audit cost, higher adherence rate, faster STR turnaround, measurable drop in F2R bounces — every metric visible on the ops dashboard.
Every event hashed, journalled and traceable. Who edited what, when, why, what FINTRAC returned — built for regulator-on-site review.
Plan on 10–14 business days end-to-end. Discovery and core-system mapping fill days 1–3, sandbox credentials and JWT secrets land by day 4, the first F2R submission flows through the sandbox by day 7, and UAT plus cut-over close at day 14. A dedicated implementation engineer pair-works with your team throughout.
Either way. EasyLoad is certified against the F2R API for direct delivery — your reports stay inside the EasyLoad → FINTRAC channel. For teams still on the portal, EasyLoad also produces a fully-compliant JSON file you can upload by hand. We recommend the API path for any volume above ~50 reports per day.
EasyLoad runs the 24-hour rolling total per PCMLTFA rules — combining cash transactions across branches, channels and currencies per client. FX conversion uses Bank of Canada rates at cut-off and is applied uniformly to close any threshold-gaming surface. The aggregation logic is configurable per institution from the operations dashboard.
Three connection modes are supported: (1) direct database read with allow-listed credentials, (2) message-bus subscription (Kafka, RabbitMQ, MQ-Series), or (3) SFTP / API push from the core. Most banks pick option 2 or 3. The mapping from your transaction schema to the F2R schema is set once during onboarding.
EasyLoad parses the rejection acknowledgement, surfaces the bouncing fields against the originating transaction in the dashboard, and queues the record for officer review. Once corrected, a one-click resubmission goes through with the trail intact — original submission, edit history, FINTRAC ack — all linked.
Yes. The same engine serves Schedule-1 banks and small money-service businesses; what differs is the connection mode and the seat count. Smaller MSBs typically run in SFTP-feed mode with 2–3 seats; larger banks use direct database or message-bus integration with 30+ seats and SSO.
We'll push a real submission through our sandbox using realistic test data — usually within a week of the first call. No canned slides, no recorded demos.
Book a Live Demo