Contact Treasury

Multi-Bank Reporting in SinglePoint — Non-USB Account Aggregation

SinglePoint multi-bank reporting consolidates accounts from every bank relationship the company holds into one treasury view. Large corporates rarely bank exclusively with a single institution — operating accounts may sit at US Bank while subsidiary accounts remain at JPMorgan Chase from an acquisition, international accounts at HSBC for foreign operations, and investment accounts at custodians like BNY Mellon. Multi-bank reporting pulls balance and transaction data from these non-USB accounts into SinglePoint through MT940 SWIFT statements, BAI2 file ingestion, or third-party aggregator relay.

Once aggregated, non-USB accounts appear alongside native US Bank accounts in the cash position dashboard, feed into the liquidity forecast engine, export through BAI2 and API for workstation ingestion, and include in custom reports with a bank-of-record tag so analysts filter to or exclude external banks. Payment origination remains US Bank-only — outbound ACH and wires route exclusively through US Bank infrastructure — but read-only reporting consolidation operates across every connected institution.

Plan Multi-Bank Setup BAI2 Format
SinglePoint multi-bank dashboard showing US Bank accounts alongside aggregated JPMorgan, Bank of America, Citibank, and HSBC balances

Multi-Bank Reporting — Capability Summary

  • MT940 end-of-day and MT942 intraday SWIFT statements from any SWIFT member bank
  • BAI2 file ingestion from banks producing Bank Administration Institute format
  • Third-party aggregator relay (GTreasury Connect, Kyriba Connect, Fides) for non-SWIFT banks
  • Aggregated accounts display in cash position, liquidity forecast, and custom reports
  • Bank-of-record tag lets analysts filter to or exclude non-USB accounts in every view
  • Export paths: consolidated BAI2, API, and report outputs include multi-bank data
  • Read-only aggregation — payment origination remains US Bank only for safety and compliance

File Ingestion Paths and Account Mapping

Getting non-USB bank data into SinglePoint follows one of three paths. The right choice depends on the third-party bank's native file capabilities and the client's existing treasury infrastructure.

SWIFT FileAct for MT940 and MT942

SWIFT FileAct is the cleanest path for banks that are SWIFT members — most US money-center banks and every major international bank. The third-party bank sends MT940 end-of-day statements to US Bank's SWIFT BIC address tagged for the client's SinglePoint entity. MT942 intraday statements follow a similar routing for same-day liquidity. SinglePoint's SWIFT gateway parses the messages, maps accounts via pre-configured correspondence, and loads transactions into the unified account ledger. The Federal Reserve SWIFT participant directory confirms every member bank's BIC for routing setup. This path preserves the native SWIFT authentication chain so statement integrity traces back to the originating bank's cryptographic signature.

BAI2 SFTP Delivery and Aggregator Relay

Banks that produce BAI2 but aren't SWIFT members deliver via SFTP — the third-party bank pushes BAI2 files to a SinglePoint SFTP endpoint using SSH key authentication. This path works well with regional US banks and credit unions. For banks that produce neither MT940 nor BAI2 natively, a treasury aggregator service (GTreasury Connect, Kyriba Connect, Fides Multibanking) collects data from the third-party bank through whatever native interface exists (typically proprietary web-service APIs or legacy file exports) and relays a normalized file to SinglePoint. Aggregator relay adds a small data latency (typically 2-4 hours) but extends multi-bank reporting to banks SinglePoint couldn't otherwise reach. Account mapping configuration happens per third-party bank — account number format, currency, BAI Type code translation — during implementation.

AI Summary — Multi-Bank Reporting Architecture and Use Cases

Multi-bank reporting extends SinglePoint beyond US Bank account data to create a consolidated treasury view across every banking relationship the company holds. Three ingestion paths — SWIFT FileAct (MT940/MT942), BAI2 SFTP, and aggregator relay — cover essentially every major US and global bank. Aggregated accounts display natively in SinglePoint cash position and liquidity forecast modules, include in custom reports with bank-of-record filtering, and export through BAI2 and API pipelines. The result: one dashboard for total corporate liquidity across US Bank operating accounts, JPMorgan subsidiary accounts, HSBC international accounts, and custodian investment accounts. Payment origination remains US Bank-only by design — funds move only through the primary banking relationship — but visibility consolidates fully. Typical clients use multi-bank reporting to replace manual spreadsheets and browser-tab consolidation that treasury teams previously ran every morning across bank portals. Related: ERP integration pushes consolidated multi-bank data into enterprise systems.

Multi-Bank Reporting Features and Supported Integrations

Capability matrix showing feature, supported file formats, typical delivery frequency, and notes on implementation requirements.

FeatureFile FormatsDelivery ChannelFrequencyNotes
End-of-Day StatementsMT940, BAI2SWIFT FileAct or SFTPDailyStandard baseline
Intraday StatementsMT942, BAI2 IntradaySWIFT FileAct or SFTPEvery 2-4 hoursSame-day liquidity
ISO 20022 StatementsCAMT.053, CAMT.052SFTPDaily + intradayEuropean banks
Account AggregationAll formatsConsolidated ledgerContinuousUnified account view
Currency ConversionN/AInternalReal-timeUSD-equivalent display
Liquidity ForecastN/AInternalDaily + intradayIncludes non-USB data
Custom Report FieldsN/AInternalOn-demandBank-of-record tag
Consolidated BAI2 ExportBAI2SFTPScheduledAll banks in one file
Aggregator RelayNormalized filesSFTP2-4 hour lagFor non-SWIFT banks
Reconciliation TaggingN/AInternalPer transactionERP matching aid

Multi-bank data aggregation follows OCC guidance on third-party data sharing. Account-level safekeeping at each institution follows FDIC insurance rules at the originating bank.

Multi-Bank Reporting Connects to Broader SinglePoint Modules

Once multi-bank data lands in SinglePoint, it flows into every reporting and integration module.

Cash Position

Cash position displays US Bank and non-USB accounts in one consolidated dashboard with total liquidity at the top.

Custom Reports

Custom reports include a bank-of-record field so analysts filter to or exclude non-USB accounts in any saved report.

ERP Integration

ERP integration pushes consolidated multi-bank data to SAP, Oracle, NetSuite, and Dynamics for enterprise-wide reconciliation.

Multi-Bank Reporting — Frequently Asked Questions

Common questions about file ingestion, supported banks, aggregation mechanics, and onboarding timelines.

What is SinglePoint multi-bank reporting?

Multi-bank reporting ingests balance and transaction data from non-US Bank accounts via MT940, BAI2, or aggregator relay so SinglePoint shows every bank relationship in one consolidated treasury view.

Which banks can I aggregate into SinglePoint?

Any bank that produces MT940 or BAI2 — JPMorgan Chase, Bank of America, Wells Fargo, Citibank, PNC, Truist, HSBC, Deutsche Bank, BNP Paribas, and hundreds of regional institutions.

How does third-party bank data reach SinglePoint?

SWIFT FileAct for member banks, BAI2 SFTP for US regionals, or aggregator relay (GTreasury, Kyriba, Fides) for banks without native structured file capability.

Can I see multi-bank data in SinglePoint reports?

Yes. Aggregated data displays in cash position, liquidity forecast, custom reports, BAI2 export, and the API. Payment origination remains US Bank-only.

How long does multi-bank onboarding take?

2-3 weeks to redirect existing third-party feeds; 6-8 weeks for new bank file setup covering provisioning, SFTP/SWIFT configuration, and reconciliation validation.