Data exports are how ScotiaConnect gets portal data out to treasury workstations, ERP reconciliation modules, analytics warehouses and auditor review copies. Formats range from the compact BAI2 used by North American treasury workstations through CAMT.053 for global consolidation to CSV and JSON for structured downstream loads. This reference covers the formats, delivery modes, encryption options, naming conventions and the ack workflow that keeps automated pipelines honest.
Format choice on ScotiaConnect is almost always dictated by what the downstream system expects. A treasury workstation with a BAI2 loader will always prefer BAI2 over CAMT.053, even if both contain the same underlying information, because the loader has parsing optimizations specific to the format. A cloud data warehouse will prefer JSON over BAI2 because the JSON path avoids a custom parser. CSV sits in the middle: trivial to load, easy to reconcile, but opinionated on column order.
Multi-format export is supported. A typical pattern is scheduled BAI2 to the treasury workstation, scheduled CSV to the finance analytics team, and on-demand PDF for audit evidence. The three files share the same posting ledger, so totals reconcile across formats. The account reporting reference covers the scheduled-report side of the same data path.
ScotiaConnect exports run on two cadences: on-demand from the portal, and scheduled via sFTP push. Scheduled is the dominant mode for automated pipelines; on-demand covers investigations, auditor requests and spreadsheet pulls.
Scheduled sFTP delivery targets a client-provided landing directory. ScotiaConnect authenticates with the landing directory using a dedicated service account and a client-owned SSH key. File names follow a deterministic convention that embeds the account identifier, the format, the business date and the sequence number, which makes idempotent reloads straightforward on the downstream side. PGP encryption is optional, enabled most often when the landing directory is shared with a managed file-transfer hop or when the downstream system sits in a different security zone.
On-demand exports land in the reporting queue on the portal. Users receive a notification when the file is ready, download from the queue, and the file persists in the queue for a defined window before automatic cleanup. Cross-border data-handling expectations overseen by FINTRAC and related privacy frameworks shape how long export artifacts stay on the portal versus how quickly clients should move them to their own archive.
The ack workflow is the difference between a scheduled export that appears reliable and one that actually is. Without an ack loop, a delivery that silently fails on the receiving side can go unnoticed for days. With an ack expectation configured, ScotiaConnect knows when the expected ack did not arrive and raises the condition on the reporting queue for the service desk or the client to action. This pattern matches the file-transfer discipline expected by treasury management teams running automated end-of-day close.
| Export format | Structure | Encryption | Typical downstream system |
|---|---|---|---|
| CSV | Row-and-column, flat | Optional PGP | Spreadsheet, analytics warehouse |
| JSON | Nested, schema-driven | Optional PGP | Cloud data warehouse, API middleware |
| BAI2 | Fixed-record, section-coded | Optional PGP | North American treasury workstation |
| CAMT.053 (end-of-day) | ISO 20022 XML | Optional PGP | Global consolidation, SWIFT pipelines |
| CAMT.052 (intraday) | ISO 20022 XML | Optional PGP | Intraday cash positioning |
| MT940 | SWIFT flat record | Optional PGP | Legacy treasury workstation |
| Paginated human-readable | Not required | Auditor evidence package |
“ScotiaConnect pushes BAI2 and CAMT.053 to our landing directory on schedule, PGP-encrypted, with a deterministic file name. Our treasury workstation loader picks the files up without human touch.”
— Nuria J. CasamiquelaIntegration Lead, Cedarlight Forestry Partners
ScotiaConnect exports CSV, JSON, BAI2, CAMT.053 and MT940. CSV and JSON cover structured and semi-structured downstream use. BAI2, CAMT.053 and MT940 cover treasury-workstation ingestion and global consolidation.
PDF is also available for auditor evidence packages, although it is not suitable for automated downstream processing.
Yes. ScotiaConnect supports scheduled sFTP push of exports to a client-provided landing directory, using a deterministic file-naming convention and an optional PGP encryption layer for files that traverse shared infrastructure.
Most mid-market clients run scheduled sFTP for daily flows and keep on-demand portal download for ad-hoc and auditor scenarios.
Clients can configure ack-file expectations on their sFTP landing directory. ScotiaConnect monitors the directory for an ack or nack response and flags missing acks to the reporting queue. Retransmission is then initiated either automatically on schedule or manually by the service desk.
The ack loop converts silent delivery failures into visible operational signals, which is the characteristic that makes scheduled exports genuinely reliable.
Yes. ScotiaConnect supports PGP encryption on scheduled sFTP exports. Clients supply the public key during onboarding and rotate it on their preferred cadence. PGP is usually enabled when the landing directory is shared with third-party managed file-transfer hops.
Rotation cadence is a client policy decision. Quarterly and annual rotations are the most common choices among commercial clients.