RBC Express Data Export: BAI2, MT940, CSV & PDF Formats
RBC Express Data Export is the format engine that produces every file leaving the RBC Express portal. BAI2 version 2 with all Type Codes. MT940 SWIFT customer statement. MT942 intraday. CSV with configurable column mapping. XLSX with formulas preserved. PDF for archival. Native JSON through the API. One export engine across every channel.
Treasury workstations ingest BAI2. Kyriba expects MT940. ERPs want CSV with your chart of accounts column mapping. Auditors want PDF archives. RBC Express Data Export produces all of them from the same underlying transaction history — scheduled delivery to SFTP, HTTPS webhook, secure email or direct API pull. Encrypted in transit. Signed, versioned and retained for 7 years.
Sign In to Export Data Back to Reports
Supported Export Formats
Every format RBC Express Data Export produces meets the standards the downstream system expects — not a lightweight subset.
BAI2 Version 2
Full BAI2 specification with every Type Code required by treasury workstations (Kyriba, ION, GTreasury, SAP TRM, Oracle Treasury, Treasury Intelligence Solutions). Prior Day (file type 01) and Intraday (file type 02) both supported. RBC Express Data Export writes standard BAI2 record lengths and transaction detail summaries — no custom parsing on the receiving side.
MT940 / MT942
SWIFT MT940 customer statement for end-of-day balance and transaction reporting. MT942 interim transaction report for intraday positioning. RBC Express Data Export produces MT-format output valid against the SWIFT Category 9 (Cash Management) specification. Block 4 fields, field 61 transaction lines and field 86 information lines all populate per standard.
CSV / TSV / XLSX / PDF
CSV with configurable column mapping, quoting and delimiter. TSV for systems preferring tab-separated. XLSX with preserved formulas, conditional formatting and pivot tables from custom reports. PDF for archival with embedded fonts and accessibility tags. All four formats flow through the same RBC Express Data Export engine with consistent metadata.
Format to Use Case Matrix
Five common treasury and AP use cases mapped to the RBC Express Data Export format that fits.
| Format | Use Case | ERP Target | Refresh Cadence |
|---|---|---|---|
| BAI2 Prior Day | Treasury workstation ingestion | Kyriba, ION, SAP TRM | Daily 7:00am ET |
| MT940 | SWIFT-native cash management | GTreasury, Workday | Daily end-of-day |
| MT942 Intraday | Intraday positioning | Kyriba, SAP S/4HANA | Every 15 minutes |
| CSV with column mapping | AP ledger posting | QuickBooks, Sage 300, Dynamics 365 | Daily / per batch |
| PDF archival | Audit and compliance retention | DMS / records system | Monthly / on demand |
Delivery Channels
RBC Express Data Export meets your downstream infrastructure where it lives — not the other way around.
SFTP Pickup & ERP Connectors
SFTP is the dominant channel for BAI2 and MT940 into treasury workstations. RBC Express Data Export either pushes to your SFTP endpoint or hosts a dedicated RBC SFTP pickup directory per client. Native ERP connectors for SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365 Finance, Sage Intacct, QuickBooks Canada and Sage 300 (Accpac) bypass SFTP entirely — the connector maps to the ERP's native import API.
HTTPS Webhook & API
For modern cloud stacks, RBC Express Data Export POSTs JSON or MIME-encoded file content to your HTTPS webhook with TLS 1.3. Alternatively the direct REST API lets your system pull on a timer. API authentication uses OAuth 2.0 with mutual TLS on the highest-security tier. Rate limits and pagination align with current RBC Express platform guidance.
Feature Brief
- RBC Express Data Export = BAI2 v2, MT940, MT942, CSV, TSV, XLSX, PDF, native JSON API.
- Delivery via SFTP pickup, encrypted email, HTTPS webhook, REST API pull, ERP connector.
- Schedules from every 15 minutes to monthly; Canadian bank holiday aware.
- GL code mapping preserves chart of accounts; maintained by Company Administrators.
- Encrypted in transit (SSH / TLS 1.3 / PGP) and at rest (AES-256); retained 7 years with delivery metadata.
GL Code Mapping Inside Data Export
Map once. Every subsequent RBC Express Data Export output honours the mapping — no reclassification at month-end close.
Company Administrators open the mapping console from user management and bind RBC Express transaction types to client chart-of-accounts codes. Wire fees to one GL code. EFT originations to another. FX gain/loss to a third. Interest credits to a fourth. Bank fees to a fifth. The mapping is account-specific where needed and organisation-wide where appropriate. RBC Express Data Export emits mapped GL codes in BAI2 field 88, MT940 field 86 information lines, CSV columns and XLSX cells.
For multi-entity clients with subsidiary-specific charts of accounts, RBC Express Data Export applies the correct mapping per account automatically — the parent export contains consolidated detail while each subsidiary's BAI2 file carries its own GL codes. This is what month-end close teams mean by "clean posting file": RBC Express Data Export delivers it by default.