Account reporting on ScotiaConnect

Account reporting is the quiet backbone of ScotiaConnect. Prior-day, same-day and intraday files let treasury teams reconcile yesterday, position today and signal tomorrow, all without leaving the commercial banking portal. This reference collects the formats, delivery windows and integration notes treasury staff ask about in the first months of ScotiaConnect use, with pointers into the wider reporting silo for exports, alerts and API-driven retrieval.

Three reporting windows that matter

Short version. ScotiaConnect treats reporting as three distinct windows: prior-day for reconciliation, same-day for end-of-day position, and intraday for active cash management. Each window has its own file, its own cut-off and its own typical consumer downstream.

Prior-day reporting is the file that lands before the treasury analyst opens the laptop. It captures every posted transaction from the previous business day, summarizes opening and closing balances and produces a BAI2 record that treasury-workstation systems ingest automatically. On ScotiaConnect, prior-day Canadian-dollar reporting is typically available before 06:30 ET, with US-dollar prior-day files following shortly after. Treasury teams treat this file as the single source of truth for reconciliation against internal ledgers.

Same-day reporting is a consolidated snapshot at a published cut-off, generally tied to the rail's final clearing window. On ScotiaConnect the same-day file closes out the business day in a single transmission and is used for end-of-day tie-out, audit evidence and next-morning staging. Intraday reporting, the third window, refreshes multiple times through the day. It gives cash-management teams the granular view needed for concentration moves, FX funding decisions and large outgoing wire timing. See transaction history for the ad-hoc look-back companion to these scheduled files.

Formats the portal produces

Reporting basics

BAI2 remains the dominant North American format for prior-day and same-day reporting on ScotiaConnect. CAMT.053 is the ISO 20022 end-of-day statement used for global consolidation; CAMT.052 handles intraday. MT940 stays available for legacy treasury workstations. CSV and PDF cover the human-readable end of the spectrum.

Format choice usually follows the downstream consumer. A treasury workstation such as Kyriba, GTreasury or Reval will expect BAI2 for North American accounts and CAMT.053 for global accounts. ERP reconciliation modules inside SAP, Oracle and NetSuite generally accept BAI2 directly or through a lightweight mapping layer. Spreadsheet-based reconciliation and auditor requests tend to pull CSV. PDF output is used for signatory review and for regulatory evidence packages.

ScotiaConnect generates every format from the same underlying posting ledger, which keeps the totals consistent across formats. A reconciliation mismatch between BAI2 and CSV is almost always a filter difference, not a data difference. See the Canadian prudential supervisor's OSFI guidance for expectations around reporting reliability at federally regulated institutions.

Delivery channels and cut-offs

Short version. ScotiaConnect delivers reporting through two primary channels: scheduled sFTP push to a client landing directory, and on-demand download from the portal reporting queue. Both are authenticated and both use the same underlying files.

Scheduled sFTP is the dominant delivery mode for clients with treasury workstations. ScotiaConnect pushes the file to a client-provided sFTP landing directory using deterministic file naming, so the downstream loader can pick it up without human intervention. PGP encryption is optional and is typically turned on when the landing directory is shared or when the file will traverse a third-party managed file-transfer hop. On-demand download is the usual mode for spreadsheet reconciliation, auditor requests and one-off investigations.

Cut-off windows vary by rail and currency pair. Canadian-dollar prior-day files land first, followed by US-dollar prior-day and then multi-currency CAMT.053 end-of-day files. Intraday refreshes are keyed to Lynx and Fedwire cycles, so a Lynx-cycle posting will appear in the next intraday CAMT.052 within minutes. Treasury calendars built against ScotiaConnect should always anchor to the published cut-offs rather than observed delivery times, since intermittent clearing delays do occur.

Reporting format matrix

Short version. The table maps each ScotiaConnect reporting format to its cadence, its typical downstream consumer and the delivery channel most commonly used for that combination.
FormatCadenceTypical consumerDelivery channel
BAI2 (prior-day)Once per business day, early AMTreasury workstation, ERP reconciliationScheduled sFTP push
BAI2 (same-day)End-of-day snapshotTreasury workstation, internal auditScheduled sFTP push
CAMT.053 (end-of-day)Once per business dayGlobal treasury consolidationScheduled sFTP or portal
CAMT.052 (intraday)Multiple intraday refreshesCash positioning, FX fundingScheduled sFTP push
MT940Once per business dayLegacy treasury workstationScheduled sFTP push
CSVOn demand or scheduledSpreadsheet reconciliationPortal download
PDFOn demandSignatory review, audit evidencePortal download

From the treasury floor

“The prior-day BAI2 feed from ScotiaConnect drops into our treasury workstation before any analyst is at their desk. By the time the morning stand-up starts, reconciliation is already clean and exceptions are queued.”

— Kofi A. BoahenTreasury Analyst, Westbluff Pharmaceuticals

Frequently asked questions

Short version. These five questions cover formats, prior-day timing, delivery automation, the intraday versus same-day distinction, and retention inside the portal.
What reporting formats does ScotiaConnect produce?

ScotiaConnect produces BAI2 for prior-day and same-day balance reporting, CAMT.053 for end-of-day statements, CAMT.052 for intraday statements, MT940 for legacy treasury-workstation consumption, plus CSV and PDF for human-readable use.

Format availability is consistent across Canadian-dollar, US-dollar and most major foreign-currency accounts. The underlying posting ledger is shared, so totals will match across formats for the same reporting window.

How soon is the prior-day BAI2 file available?

Prior-day BAI2 for Canadian-dollar accounts is typically available before 06:30 ET. US-dollar accounts usually land before 07:00 ET. Delivery can be scheduled over sFTP or pulled from the ScotiaConnect reporting queue.

Occasional delays follow upstream clearing events, so treasury calendars should anchor to the published cut-off rather than a historical delivery time.

Can I automate daily reporting delivery?

Yes. ScotiaConnect supports scheduled sFTP push to a client landing directory, with a deterministic file-naming convention and an optional PGP encryption layer. Clients can also pull files from the portal on a schedule using their treasury workstation.

Most mid-market clients adopt scheduled push for prior-day and intraday reporting, and keep on-demand download for ad-hoc CSV pulls and auditor requests.

How does intraday reporting differ from same-day?

Intraday reporting on ScotiaConnect updates multiple times during the business day, capturing new postings as they occur. Same-day reporting is a consolidated snapshot at a defined cut-off. Intraday is used for active cash positioning; same-day is used for end-of-day tie-out.

Teams running real-time FX funding decisions rely on intraday CAMT.052; teams running reconciliation against internal ledgers rely on same-day BAI2.

How long is reporting history retained inside ScotiaConnect?

Account reporting history is retained inside ScotiaConnect for seven years on most commercial profiles, matching standard Canadian record-keeping expectations. Clients should still archive files to their own environment for independent retrieval.

Independent archiving protects against portal-side changes and supports audit scenarios that require the file to be produced outside the originating banking system.