Home / Wiki / E / Electronic Bank Statement

Electronic Bank Statement

Trade Finance and B2B PaymentsUpdated 17 Nov 2026
Share

An electronic bank statement is a structured, machine-readable file in which a bank reports the balances and transactions on a client's accounts. Unlike a PDF or paper bank statement, it is designed to be loaded straight into an accounting, enterprise resource planning (ERP) or treasury management system, where it drives reconciliation, cash application and cash positioning without retyping.

Companies receive these statements through a range of channels, from bank portals and SWIFT to direct host-to-host links and APIs. The main formats are BAI2 in the United States, SWIFT MT940 and MT942 messages used worldwide, and the newer ISO 20022 cash management messages camt.052, camt.053 and camt.054. Many large firms receive statements from dozens of banks in several formats at once.

01

Formats in use

The common formats differ in origin and in how much detail they carry:

  • BAI2. A comma-delimited file format developed by the Bank Administration Institute and long used by US banks for prior-day and current-day balance and transaction reporting, with numeric type codes for each kind of entry.
  • SWIFT MT940 and MT942. The MT940 is the customer statement message for end-of-day balances and transactions; the MT942 is an interim transaction report sent during the day. Both are text messages with tagged fields and limited room for remittance information.
  • ISO 20022 camt messages. The ISO 20022 family uses XML. The camt.052 account report carries intraday information, camt.053 is the end-of-day statement, and camt.054 notifies individual debits and credits, often used for detailed collection or batch breakdowns.

Banks also offer local and proprietary formats, such as country-specific files in some European markets, and a variety of CSV exports for smaller clients.

02

Intraday and end-of-day reporting

End-of-day statements, sometimes called prior-day reports, give final booked balances and all entries for the business day. They are the authoritative source for accounting and for bank reconciliation. Intraday reports, delivered at intervals during the day or close to real time, show transactions as they are booked and expected value-dated items. Treasury teams use intraday data for cash positioning, deciding funding and investment moves before bank cut-offs, while relying on end-of-day files for the official record. Balances in intraday reports can change, so systems treat them as provisional.

03

Role in reconciliation and cash application

Once a statement is loaded, the receiving system matches each line with expected items: outgoing payments already recorded, card settlements, customer receipts and bank charges. Codes and references on each entry are translated through bank statement mapping rules into ledger postings. Receipts with enough remittance information pass straight to cash application, while unmatched items go to exception queues. High automatic match rates in automated reconciliation depend on statement quality: complete references, consistent codes and correct value dates.

The ISO 20022 formats help here because they carry structured fields for the end-to-end reference of a payment, the ultimate payer and payee, and detailed remittance data, as well as a standard bank transaction code structure organised by domain, family and sub-family. Older formats often truncate such data or place it in free text, which forces matching engines to rely on pattern rules.

04

Migration to ISO 20022

SWIFT and the wider industry are moving cross-border payments and reporting from MT messages to ISO 20022 MX messages. For corporate statements the shift is gradual. Many banks now offer camt.053 alongside MT940, and some markets have made ISO 20022 reporting the norm, while many corporates still receive MT940 or BAI2 files because their ERP and treasury systems are built around them. Moving to camt formats usually requires rebuilding mapping tables and testing reconciliation rules for each bank, so firms often run both formats in parallel for a period. The pace depends on each bank's product plans and on the client's own systems rather than on a single industry deadline.

05

Practical issues

Common problems with electronic statements include missing files, duplicate deliveries, balances that do not roll forward from the previous day, and format versions that change after a bank upgrade. Treasury and IT teams therefore monitor file receipt each morning, check opening and closing balance continuity, and keep a record of each bank's implementation guide. Good multi-bank connectivity and standardised formats reduce these issues and make it easier to build reliable balance reporting and cash visibility across a group.

Last updated 17 Nov 2026
Share this entry

Ref 1310000200