SadaSend — Transactional Email API & Native Model Context Protocol (MCP) Server for AI Agents.
SWIFT MT940 & BAI2 Bank Statement Converter
Parse institutional corporate bank statements (.sta, .mt940, .bai) directly in your browser. Decode complex multi-line :61:/:86: narratives, map standardized BAI transaction codes, reconcile opening-to-closing ledger cash balances, and export to clean Excel CSV and QuickBooks.
| # | Value Date | Type & Code | Reference | Remittance & Description | Debit ($) | Credit ($) | Balance ($) |
|---|---|---|---|---|---|---|---|
| 1 | 2026-01-03 | NTRFBank Wire / Electronic Funds Transfer | NONREF INV-884102 | /EREF/INV-884102/PREF/ACME-GLOBAL/REMI/ENTERPRISE ERP SERVICES Q1 | — | $48500.00 | $293500.00 |
| 2 | 2026-01-05 | NTRFBank Wire / Electronic Funds Transfer | NONREF PAYROLL-TAX | /EREF/TX-0912/PREF/US-TREASURY/REMI/941 FEDERAL TAX DEPOSIT | $12450.20 | — | $281049.80 |
| 3 | 2026-01-08 | NTRFBank Wire / Electronic Funds Transfer | NONREF STRIPE-PAY | /EREF/STRIPE-88910/PREF/MERCHANT-SETTLE/REMI/CARD ACQUIRING BATCH 108 | — | $35000.00 | $316049.80 |
| 4 | 2026-01-12 | NTRFBank Wire / Electronic Funds Transfer | NONREF WIRE-OUT-LEASING | /EREF/HQ-LEASE-JAN/PREF/BOSTON-PROPERTIES/REMI/COMMERCIAL SUITE 1400 | $45000.00 | — | $271049.80 |
| 5 | 2026-01-15 | NTRFBank Wire / Electronic Funds Transfer | NONREF AP-SETTLEMENT | /EREF/PO-449102/PREF/VERTEX-LOGISTICS/REMI/SUPPLY CHAIN FREIGHT SETTLEMENT | — | $55000.00 | $326049.80 |
| 6 | 2026-01-20 | NCHKCheck Clearing | 1094 CH-1094 | /EREF/CHECK-1094/PREF/DATACENTER-EQUIPMENT/REMI/GPU SERVER HARDWARE | $28450.00 | — | $297599.80 |
| 7 | 2026-01-28 | FMSCBanking Maintenance / Service Charge | NONREF BANK-FEE | /EREF/ANALYSIS-FEE/PREF/CITIBANK-NA/REMI/GLOBAL CASH POOLING SERVICE CHARGE | $6000.20 | — | $291599.60 |
| 8 | 2026-01-30 | FMSCBanking Maintenance / Service Charge | NONREF WIRE-FEE | /EREF/FEE-WIRE/PREF/CITIBANK-NA/REMI/CROSS BORDER MT103 TRANSFER CHARGE | $250.00 | — | $291349.60 |
Automate SWIFT, ISO 20022 camt.053 & Host-to-Host Bank Feeds
Manual bank statement imports break at institutional scale. DataDaur architectures direct host-to-host SFTP and API integrations for Microsoft Dynamics 365 Finance, SAP S/4HANA, and Odoo — auto-matching 98%+ of customer remittances, vendor payouts, and currency hedges with zero manual keying.
SWIFT MT940 vs. BAI2 Banking Specifications
SWIFT MT940 (ISO 15022)
Used globally by European, Middle Eastern, and Asian international corporate banks (Citibank, HSBC, Deutsche Bank, Standard Chartered). Delivered as a tagged text message:
- :20: Transaction Reference Number (TRN)
- :25: Account Identification / IBAN
- :60F: Opening Balance (Mark, Date, Currency, Amount)
- :61: Statement Line (Value Date, C/D, Amount, Type, Ref)
- :86: Information to Account Owner (Remittance / EREF)
- :62F: Closing Balance (Final book balance)
BAI2 Cash Management Standard
The de facto treasury standard in North America created by the Bank Administration Institute, used by JPMorgan Chase, Bank of America, and Wells Fargo:
- Record 01: File Header (Sender, Receiver, Timestamp)
- Record 02: Group Header (Account Group, Currency)
- Record 03: Account Identifier & Summary Balances (010, 045)
- Record 16: Transaction Detail (Type Code, Amount in Cents, Ref)
- Record 88: Continuation Record (Appends remittance text)
- Record 49: Account Trailer with Control Hash Totals
How to use this tool
Select format or upload your statement file
Choose between SWIFT MT940 (.sta / .mt940) for international commercial banking or BAI2 (.bai / .txt) for US cash management feeds, or upload your statement file for automatic format detection.
Paste raw statement text or inspect the pre-loaded corporate preset
Paste raw statement text into the workbench or load institutional test presets (CitiDirect SWIFT MT940 or JPMorgan / BofA BAI2) to test field extraction.
Verify account identifier, statement period, and opening ledger balance
The parser extracts IBAN or bank account numbers, currency (USD, EUR, GBP), and opening balance from tag :60F: (MT940) or Record 03 / Type 010 (BAI2).
Inspect extracted statement lines, transaction type codes, and multi-line narratives
Review the interactive transaction grid with parsed dates, debit/credit indicators, standardized BAI codes (115 lockbox, 142 ACH, 475 check, 495 wire), and stitched :86: remittance details.
Confirm automated mathematical balance reconciliation
Verify that Opening Balance + Total Credits − Total Debits = Reported Closing Balance with an automated zero-variance green audit indicator.
Download Excel CSV with UTF-8 BOM, QuickBooks Online, or Treasury Audit Workpaper
Export formula-safe CSV with native Excel byte-order mark, QuickBooks / Xero compatible feeds, or print a formal single-page corporate cash reconciliation workpaper for internal audit.
Frequently Asked Questions
What is the difference between SWIFT MT940 and BAI2 bank statement formats?
SWIFT MT940 is the international standard (ISO 15022) electronic bank statement used globally across European, Asian, and cross-border commercial banking (CitiDirect, HSBC Net, Barclays, Deutsche Bank). It uses colon-delimited tags such as :60F: (opening balance), :61: (statement line), and :86: (transaction narrative). BAI2 is the North American cash management standard created by the Bank Administration Institute and used by US corporate banks (JPMorgan ACCESS, Bank of America CashPro, Wells Fargo Commercial). BAI2 uses comma-separated record types (01 file header, 02 group, 03 account identifier, 16 transaction detail, 88 continuation, 49 account trailer).
How do SWIFT MT940 :61: statement lines and :86: narrative tags work?
Field :61: contains structured transaction data: value date (YYMMDD), entry date, debit/credit indicator (C, D, RC, RD), transaction currency amount, 4-character transaction type code (such as NTRF for transfer, NCHK for check, FMSC for fee), and customer reference. Field :86: contains unstructured or structured remittance data (payee name, invoice numbers, end-to-end references ?20, customer references ?21). This tool stitches multi-line :86: descriptions directly to their preceding :61: statement line for complete audit traceability.
How do BAI2 transaction type codes distinguish debits from credits?
BAI2 assigns standardized numeric type codes to every transaction: Codes 100 to 399 represent credits (such as 115 lockbox, 142 ACH credit, 165 preauthorized ACH, 175 check deposit, 195 incoming wire, 301 commercial deposit), while Codes 400 to 699 represent debits (such as 455 ACH debit, 475 check paid, 495 outgoing wire, 501 Fedwire, 699 miscellaneous debit/fee). Summary balance codes (010 opening ledger, 015 opening available, 040 float, 045 closing ledger) establish opening and closing cash positions.
How does the mathematical bank balance reconciliation work?
The tool executes an automated cash reconciliation equation: Opening Balance + Total Credits − Total Debits = Computed Closing Balance. It then compares the computed closing balance against the reported closing balance parsed from tag :62F: (in MT940) or Record 49/045 (in BAI2). If the discrepancy is exactly zero ($0.00), the statement receives a Zero Discrepancy Audit Pass. Any variance indicates missing transaction lines, skipped continuations, or currency rounding issues.
Are corporate banking statements processed privately and securely?
Yes, 100% client-side. Parsing executes entirely in your browser using local JavaScript memory. Bank account numbers, company names, wire references, customer balances, and corporate cash flows are never transmitted to any server or third-party cloud. You can disconnect your internet connection and the parser will function with complete fidelity.
Explore Related Financial & Operations Utilities
Run end-to-end ERP reconciliation across purchasing, payroll, logistics, and job costing.