Parsing SWIFT MT940 tags, FinTS ?20–?33, and SEPA codewords
Corporate treasury teams and European bookkeepers frequently receive .sta or .mt940 files that dump counterparty names, IBANs, and payment references into a single unstructured :86: block. Parsing those structured tags locally turns raw bank text into clean columns ready for ledger reconciliation.
Extracting :61: lines, German ZKA subfields, and /IBAN/ tags
The parser reads :60F: and :60M: opening balances, :61: transaction lines, :62F: and :62M: closing balances, and :86: narrative blocks across .sta, .mt940, .940, .txt, and .zip archives up to 25 MB per file. It decodes both German ZKA ?00 to ?63 subfields (including EREF+, SVWZ+, MREF+, CRED+, and ABWA+) and slash-delimited SWIFT SEPA tags (/IBAN/, /NAME/, /REMI/, /EREF/), aligned with European Central Bank SEPA Payment Integration Overview.
If your bank has already switched to XML reporting, you can convert ISO 20022 camt.053 XML bank statements into spreadsheets using the companion XML converter.
Splitting batch bookings and choosing booking versus value dates
Keep Split batch bookings into individual transactions enabled to break collective SEPA payroll or supplier batches into separate ledger rows. Toggle Export value date instead of booking date whenever your cash-flow model tracks interest valuation dates rather than bank posting dates.
The preview table renders the first 300 transactions for fast inspection, while the final download always exports 100% of loaded entries. Multi-file .zip bundles containing daily statements merge into one chronological export.
If a loaded statement includes multiple accounts or sequential days, the parser groups transactions cleanly without dropping :86: continuation lines. Each row retains its transaction code (txCode), bank reference, and extracted SEPA mandate ID where present.
Exporting CSV, Excel, QuickBooks, Xero, OFX, and QBO formats
Accounting platforms expect strict column headers, date formats, and signed amount conventions. Every CSV export follows the delimiter and quoting rules of IETF RFC 4180 Common Format for CSV Files so commas inside remittance descriptions never shift columns.
For OFX and QBO (QuickBooks Web Connect) downloads, pick Checking / current, Savings, or Credit card under Account type. QBO files also embed the Intuit bank ID (default 3000) required by QuickBooks Desktop import wizards.
| Save as format | File extension | Key columns or structure | Best accounting target |
|---|---|---|---|
| CSV with SEPA columns | .csv |
IBAN, BIC, EndToEndId, MandateId | ERP imports and treasury audits |
| Excel workbook | .xlsx |
Typed amounts and ISO dates | Spreadsheet review and pivot tables |
| CSV for QuickBooks | .csv |
Date, Description, Amount | QuickBooks Online CSV upload |
| CSV for Xero | .csv |
Date, Amount, Payee, Description | Xero bank statement import |
| OFX | .ofx |
Standard Open Financial Exchange | Xero, Sage, Lexoffice, QuickBooks |
| QBO Web Connect | .qbo |
OFX + Intuit bank ID (default 3000) | QuickBooks Desktop Web Connect |
When you need to convert PDF bank statements rather than .sta files into QuickBooks Desktop format, use the dedicated PDF bank statement to QBO Web Connect converter.
How are MT940 RC and RD reversal entries and balances verified?
Every statement is checked by comparing the :60F: opening balance plus total credits minus total debits against the :62F: closing balance within a 0.01 rounding tolerance. During this calculation, MT940 reversal marks RC (reversal of credit) are applied as debits and RD (reversal of debit) as credits so storno postings reconcile accurately.
Handling RC and RD storno signs against :60F: and :62F:
Standard C and D marks record normal credits and debits, whereas RC and RD reverse an earlier entry without flipping the original transaction sign. Checking the summary’s Balances verified or Balance mismatch indicator catches truncated .sta downloads before you import them into your general ledger.
Transitioning from legacy MT940 to ISO 20022 camt.053
Across the eurozone, EUR-Lex Regulation (EU) No 260/2012 on SEPA and ISO 20022 drives the long-term shift from legacy SWIFT MT940 messages toward structured ISO 20022 XML (camt.053). When preparing outbound vendor transfers from reconciled balances, you can prepare ISO 20022 pain.001 payment files from validated IBANs.
CSV formula safety, browser privacy, and accounting scope
Bank statement exports contain sensitive supplier IBANs, employee salaries, and customer payment references. Everything parses inside your browser with 0 bytes sent over the network, and CSV cells starting with formula triggers are sanitized automatically.
Sanitizing remittance fields and keeping IBANs off remote servers
Unescaped leading =, +, -, or @ characters in remittance text can trigger spreadsheet formula injection when opened in desktop software. Exporting as an .xlsx workbook following the Library of Congress Office Open XML (.xlsx) Format Description or sanitized CSV keeps text literals inert.
Tip: Before exporting to QBO or OFX, check the Account IBAN and Opening balance / Closing balance summary to confirm all multi-day
.stafiles loaded in sequence.
Informational scope for bookkeeping and tax reconciliation
This converter is an operational formatting utility and does not constitute certified accounting, audit, or tax advice. Always verify imported bank balances, VAT treatments, and statutory retention rules with a qualified accountant or local tax authority. To validate bank routing codes on international transfers, check the SWIFT / BIC format checker.
Because statement files are processed locally in browser memory, closing the tab clears all IBANs, amounts, and remittance descriptions immediately. You can safely convert confidential payroll runs and supplier ledgers offline once the page has loaded.