The Corporate Connect data export module bridges the gap between your US Bank commercial accounts and the enterprise systems that consume financial data. Export account balances, transaction histories, payment confirmations, and corporate card activity in five industry-standard formats: BAI2 for treasury workstations and ERP platforms, CSV for spreadsheet analysis and custom integrations, PDF for archival and distribution, MT940 for international subsidiaries operating on SWIFT-based systems, and OFX for accounting software. Automated SFTP delivery pushes files to your servers on a configurable schedule — daily balance reports at 7:00 AM, weekly payment summaries on Mondays, monthly reconciliation packages at period close.
Pre-built ERP connectors for SAP, Oracle, and NetSuite map Corporate Connect data fields to your chart of accounts, eliminating manual re-keying and reducing reconciliation errors. US Bank — FDIC insured and regulated by the OCC — retains exportable data for seven years in compliance with federal banking retention requirements.
Custom Reports Account Summary
Each format serves a different downstream system. Select the format that matches your integration requirements, or export the same data in multiple formats simultaneously.
| Format | Standard | Primary Use | ERP Compatibility | Includes Balances | Includes Transactions |
|---|---|---|---|---|---|
| BAI2 | ABA/BAI Version 2 | Treasury workstations, SAP, Oracle | Native ingestion | Yes — opening, closing, available | Yes — coded type, amount, reference |
| CSV | RFC 4180 | Spreadsheets, custom scripts, NetSuite | With field mapping | Yes — column per balance type | Yes — one row per transaction |
| PDF/A-1b archival | Distribution, print, audit documentation | Not for automated ingestion | Yes — formatted summary | Yes — formatted detail pages | |
| MT940 | SWIFT MT940 | International subsidiaries, SWIFT systems | International ERP platforms | Yes — opening/closing statement | Yes — SWIFT transaction codes |
| OFX | Open Financial Exchange 2.2 | QuickBooks, Xero, accounting software | Direct import | Yes — ledger and available | Yes — categorized entries |
BAI2 specifications maintained by Accredited Standards Committee X9. MT940 governed by SWIFT standards. FDIC insured institution.
SFTP delivery eliminates manual file downloads by pushing export files directly to your servers on a schedule you define. Corporate Connect uses SSH key authentication — no passwords traverse the network.
Configure SFTP delivery in the Data Export module by entering your server hostname, port number (default 22), target directory path, and uploading the Corporate Connect public SSH key to your server's authorized_keys file. Test the connection to verify authentication and write permissions before scheduling. Corporate Connect supports multiple SFTP destinations — send BAI2 files to your SAP server and CSV files to a different analytics server simultaneously. Each destination maintains its own connection profile, schedule, and delivery log. IP addresses for Corporate Connect SFTP outbound connections are published for firewall whitelisting.
For organizations with strict network security policies, Corporate Connect also supports SFTP over a VPN tunnel. Contact your US Bank relationship manager at +1-800-344-8758 for VPN configuration details.
Schedule exports at any frequency: every hour (for intraday balance feeds), daily (for prior-day balance and transaction files), weekly, monthly, or at custom intervals. The scheduler runs on US Bank infrastructure and accounts for banking holidays. File naming conventions use variables for date ({YYYY}, {MM}, {DD}), time ({HH}, {MI}), account number ({ACCT}), and format ({FMT}) — producing predictable file names that ERP ingest processes can match automatically. Compression options include ZIP and GZIP for large files. The delivery log records every file sent: timestamp, file name, size, checksum, and delivery status. Failed deliveries retry three times at five-minute intervals before alerting the administrator.
Pre-built connectors map Corporate Connect data to your ERP chart of accounts, enabling straight-through processing from bank to general ledger without manual intervention.
Corporate Connect delivers BAI2 files to SAP Bank Communication Management (BCM) via SFTP. SAP BCM parses the BAI2 file, maps transaction codes to SAP posting rules, and creates bank statement line items in FI-BL. Automatic matching against open items in accounts receivable and accounts payable completes the reconciliation. Exception items route to the SAP workflow for manual clearing. The integration supports multi-company code environments where each subsidiary has separate Corporate Connect accounts mapped to distinct SAP company codes. Configuration requires a one-time mapping session between your SAP basis team and US Bank implementation specialists.
Oracle Cloud ERP and Oracle E-Business Suite ingest Corporate Connect BAI2 or CSV files through Oracle Cash Management. The bank statement loader maps transaction types to Oracle transaction codes and creates cash entries for automatic reconciliation against receivables, payables, and general ledger journal entries. Oracle's Auto-Reconciliation engine matches by reference number, amount, and date. Unmatched items appear in the Oracle reconciliation workbench. For Oracle Cloud customers, Corporate Connect SFTP delivery integrates with Oracle Integration Cloud (OIC) for event-driven processing.
NetSuite imports Corporate Connect CSV files through the bank feed import utility or the SuiteScript-based bank statement parser. CSV field mapping aligns Corporate Connect columns with NetSuite transaction types, subsidiaries, and accounts. Automated matching reconciles imported transactions against open invoices, bills, and journal entries. For organizations using NetSuite SuiteBanking, the OFX export format provides direct connectivity. NetSuite's native bank feed rules categorize recurring transactions — payroll, rent, utilities — without manual tagging after the initial setup.
Every file exported from Corporate Connect is protected by multiple layers of encryption and access control throughout its lifecycle.
SFTP delivery encrypts the file transfer channel with AES-256 via SSH. Email delivery encrypts attachments with AES-256 and offers a secure download link alternative that expires after 72 hours. Manual downloads from the Corporate Connect portal travel over 256-bit TLS. Files staged on Corporate Connect servers before delivery are encrypted at rest with AES-256 and automatically deleted after 30 days. The encryption key management system is SOC 2 Type II audited and uses hardware security modules (HSMs) for key storage. These security controls satisfy the data protection requirements of the FDIC and OCC.
Data export permissions are granted per operator through the user management module. Administrators specify which operators can configure SFTP destinations, which can create export schedules, and which can download files manually. Every export action generates an audit log entry: operator ID, timestamp, IP address, format, accounts included, and delivery method. The audit trail is retained for seven years and available to internal compliance teams and external examiners. Dual authorization can be required for export configurations that include sensitive account data, ensuring that one operator creates the export and another approves it before delivery begins.
Corporate Connect data export feeds your ERP, treasury workstation, and accounting systems with accurate, timely financial data — eliminating manual downloads and re-keying. Call +1-800-344-8758 to configure SFTP delivery and ERP connectors for your organization.
Login Guide Contact a SpecialistAnswers about export formats, SFTP delivery, ERP integration, data retention, and encryption in Corporate Connect.
Five formats: BAI2 (treasury workstations, ERP), CSV (spreadsheets, custom scripts), PDF (archival), MT940 (international SWIFT systems), and OFX (QuickBooks, Xero). Each preserves full transaction detail and balance positions. See custom reports for format selection in scheduled reports.
In Data Export, enter your server hostname, port, directory path, and upload the Corporate Connect SSH public key. Test the connection, configure file naming with date/time variables, and set the delivery schedule. Multiple SFTP destinations are supported simultaneously.
Yes. Pre-built connectors deliver BAI2 files to SAP Bank Communication Management and Oracle Cash Management via SFTP. NetSuite imports CSV or OFX files. Field mapping aligns Corporate Connect data with your ERP chart of accounts for automated reconciliation.
90-day online data exports immediately. Archived data from 91 days to seven years is retrievable within one business day in BAI2, CSV, or PDF format. Federal banking regulations require seven-year retention. See transaction reporting for online search.
Yes. SFTP uses AES-256 via SSH. Email attachments use AES-256 encryption. Portal downloads use 256-bit TLS. Files at rest are encrypted with AES-256 and deleted after 30 days. US Bank is FDIC insured and SOC 2 Type II certified.