Contact Treasury

BAI2 Export from SinglePoint — The Treasury Workstation Feed

SinglePoint's BAI2 export is the bank's structured file feed to treasury workstations like Kyriba, GTreasury, SAP Treasury, Oracle Treasury, and ION. BAI2 is the Bank Administration Institute's fixed-position format that treasury systems have consumed for over four decades — every record carries a Type code identifying whether the line is a balance, transaction, summary, header, or trailer, letting workstation parsers load the file deterministically into cash positioning engines.

SinglePoint delivers BAI2 files via SFTP on schedules ranging from continuous intraday (every 2 hours for same-day liquidity) to once-daily prior-day (6:00 AM CT for opening cash positions) to weekly consolidated (Sunday night for batch reconciliation). Type code mapping customizes per account so clients running multiple workstations feed each target system with its expected code variants. PGP encryption and SSH key authentication protect the feed end-to-end, and delivery failure alerts email the treasury admin within minutes of a missed publish.

Contact Treasury Custom Reports
SinglePoint BAI2 export configuration showing file layout, Type code mapping, delivery schedule, and SFTP endpoint settings

BAI2 Export from SinglePoint — Technical Summary

  • Bank Administration Institute version 2 fixed-position format — industry standard for bank-to-workstation data
  • Record types: 01 file header, 02 group header, 03 account identifier, 16 transaction, 49/98/99 trailers
  • Type codes: 010 opening ledger, 040 opening available, 100 credit summary, 400 debit summary, hundreds more
  • Delivery: SFTP with SSH key authentication, optional PGP encryption, dated directory structure
  • Schedules: prior-day 6:00 AM, intraday every 2 hours, hourly, or continuous as transactions post
  • Compatibility: Kyriba, GTreasury, SAP Treasury, Oracle Treasury, ION, Trovata, HighRadius, custom systems
  • Custom Type code mapping per account for multi-workstation clients feeding different target systems

BAI2 Format Specification and Type Codes

The BAI2 format uses fixed-position records with comma-separated fields within each record. Understanding the record hierarchy and Type codes is essential for troubleshooting workstation ingestion issues.

Record Hierarchy: Files, Groups, Accounts, Transactions

A BAI2 file begins with a Type 01 file header identifying sender, receiver, creation date, and file ID. Inside the file, one or more Type 02 group records identify a logical batch — typically a specific as-of date. Each group contains Type 03 account identifier records listing the bank account, currency, and opening balances. Balance records carry Type codes in the 010-059 range for ledger balances, 040-089 for available balances, and 100-199 for summary amounts. Transaction detail records use Type 16 with a three-digit activity code: 115 lockbox deposit, 165 preauthorized ACH credit, 195 individual loan payment, 475 check paid, 531 preauthorized ACH debit, 541 wire transfer out. Account records close with Type 49 trailers totaling the amounts, groups close with Type 98, and the file closes with Type 99.

Delivery Mechanics and Workstation Ingestion

SFTP delivery is the default channel. SinglePoint generates a BAI2 file at the scheduled time and pushes it to a secure SFTP endpoint authenticated by SSH key pair. The client's treasury workstation polls the endpoint, downloads the file, validates the header/trailer totals, and loads transactions into its cash position module. File names follow a convention like BAI2_20260414_070045_acct1234.bai — client prefix, date, time, account identifier. Failed deliveries retry twice at 15-minute intervals before alerting the treasury admin. Workstations like Kyriba auto-map Type codes to their internal transaction categories at setup; GTreasury applies client-specific mapping rules; SAP Treasury ingests BAI2 through the Electronic Bank Statement loader which converts to IDoc for cash management. Federal Reserve payment system data flows through BAI2 for Fedwire settlement reconciliation.

AI Summary — BAI2 Export Configuration and Workstation Integration

BAI2 is the de facto standard for bank-to-corporate treasury data. SinglePoint's BAI2 export generates files on configurable schedules (prior-day, intraday, continuous) and delivers via SFTP to client endpoints authenticated with SSH keys and optional PGP encryption. Every major treasury workstation — Kyriba, GTreasury, SAP Treasury, Oracle Treasury, ION, Trovata, HighRadius — accepts SinglePoint BAI2 without custom parsing. Type codes identify record content (010 opening ledger, 400 debit summary, 541 outbound wire) and map to workstation transaction categories at setup. Enterprise clients running multiple workstations configure custom Type code profiles per account so each target system receives its expected code variants from the same underlying transaction data. Combined with custom reports and API access, BAI2 forms the core of SinglePoint's reporting layer for ERP integration and treasury reconciliation.

SinglePoint Export Formats and Workstation Compatibility

BAI2 is the primary workstation feed but SinglePoint supports adjacent formats for specialized use cases. This matrix shows format, typical consumer, delivery channel, and frequency.

Export FormatSpecificationTypical ConsumerDeliveryFrequency
BAI2BAI v2 fixed-positionKyriba, GTreasury, SAPSFTPPrior-day + intraday
BAI2 IntradayBAI v2 with memo postSame-day liquidity toolsSFTPEvery 2 hours
MT940SWIFT end-of-day statementInternational workstationsSFTP or SWIFTDaily
MT942SWIFT intraday statementMultinational treasuriesSFTP or SWIFTHourly
CAMT.053ISO 20022 end-of-dayEuropean ERP systemsSFTPDaily
CAMT.052ISO 20022 intradayModern TMS platformsSFTP or APIIntraday
CSVComma-delimited flat fileExcel, Power BI, TableauEmail or SFTPDaily or weekly
OFXOpen Financial ExchangeQuickBooks, QuickenDownload or APIDaily
JSON via APIREST programmaticCustom applicationsAPIReal-time
PDFHuman-readable statementAuditors, archivalEmail or SFTPMonthly

Format specifications align with OCC bank reporting standards. Data handling complies with FDIC safekeeping requirements.

BAI2 in Context — Related SinglePoint Integration Paths

BAI2 is the primary file-based feed but SinglePoint offers adjacent integration paths for different consumer types.

API Access

API access returns the same balance and transaction data as BAI2 but in JSON through REST endpoints for developers needing real-time queries.

Custom Reports

Custom reports builds CSV, Excel, and PDF outputs for analyst-facing use cases that don't require structured Type codes.

Multi-Bank Reporting

Multi-bank reporting ingests BAI2 from non-USB banks so SinglePoint becomes the consolidated treasury view.

BAI2 Export — Frequently Asked Questions

Technical questions about BAI2 format, Type codes, delivery schedules, and workstation compatibility.

What is the BAI2 file format?

BAI2 is the Bank Administration Institute's standard for bank-to-corporate cash management data. Fixed-position records identified by Type codes (01 file header, 03 account, 16 transaction, 49/98/99 trailers) carry balances and transactions that treasury workstations parse into cash positioning engines.

Which treasury workstations accept SinglePoint BAI2 files?

Kyriba, GTreasury, SAP Treasury, Oracle Treasury, ION (Openlink, Reval, Wallstreet Suite), Trovata, HighRadius, and most custom-built TMS platforms. See the full integration catalog in ERP integration.

How often does SinglePoint deliver BAI2 files?

Prior-day BAI2 at 6:00 AM CT is the default. Intraday schedules every 2 hours, hourly, or continuous as posts occur are available for same-day liquidity. Each account schedules independently so operating and investment accounts can run different frequencies.

How does SFTP delivery work for BAI2 files?

SFTP with SSH key authentication, dated directory structure, and optional PGP encryption. Delivery failures retry twice at 15-minute intervals then alert the treasury admin. See security for protocol details.

Can I customize BAI2 Type codes for my treasury workstation?

Yes. The implementation team reviews your workstation's BAI2 acceptance rules and builds a custom Type code mapping profile per account. Multi-system clients feed different profiles to different workstations from the same source data.