8 min read · Updated Sep 2026 · Text & developer tools
Excel to MT940: Convert XLSX Financial Data to MT940 Online Free
Free Excel to MT940 converter to generate bank-format MT940 statements from spreadsheet data, in your browser. Private, no uploads, no sign-up.
When Systems Demand the Bank's Format
Some platforms, banks and treasury systems only accept MT940. Converting Excel data to MT940 packages a spreadsheet into the tagged statement format they require.
Columns and rows become the codes downstream parsers expect, preserving every date, amount and reference exactly.
ChooseTools builds MT940 from Excel locally in your browser with full control over field mapping.
How to Convert Excel to MT940
From working table to coded file:
Upload a workbook laid out with the expected columns — date, amount, description, balances — map the fields, and generate the MT940 text ready to deliver. The preview confirms tag placement before download.
Generation is local, keeping financial records sealed on your machine throughout the process.
Field Mapping Makes the Difference
Correct mapping of dates, amounts and references determines whether an MT940 is accepted or rejected by the receiving system.
The converter walks you through assigning columns to tags with clear labels so you match each field confidently.
Deliverables validate against standard rules, not just generate raw text that might fail downstream.
MT940 Tag Structure Explained
Every MT940 file follows a strict tag hierarchy. The :20 tag carries a unique statement reference that identifies this particular export. The :25 tag names the account in IBAN or bank-local format, so the receiving system knows which account the transactions belong to.
Balance tags :60M and :62M bookend the transaction list with opening and closing figures. Each contains a credit-or-debit indicator, the date, a currency code and the amount. Accurate balances are mandatory because reconciliation software validates that the closing balance of one statement matches the opening balance of the next.
Individual transactions live in :61 lines with a compact date, amount and reference layout, while the :86 tag provides the free-text narrative. Matching each :61 with its :86 narrative keeps descriptions aligned with the correct line item, preventing the kind of orphaned entries that confuse auditors.
For Testing and System Integration
Development teams produce sample statements to test importers and reconciliation engines without waiting for actual bank exports.
Treasury teams export statements for partner banks in their dialect when onboarding new accounts or upgrading integration modules.
One workbook, many compliant outputs, saving hours of manual formatting across multiple test cycles.
Handling Multi-Currency and Statement Periods
Companies operating across borders often maintain accounts in multiple currencies. Each currency requires its own statement block with the correct currency code in the balance tags. The converter generates separate statement sequences for each currency found in the workbook, keeping them properly delimited.
Statement period dates determine the :60M opening balance date and the :62M closing balance date. Getting these right matters for automated reconciliation, which compares closing and opening balances across consecutive statements to detect gaps or missing transactions.
Reference numbers in the :20 tag should follow your bank's convention, whether sequential, date-based or account-scoped. A consistent reference scheme makes it simpler to trace statements back to their source workbook when auditors ask questions months later.
Standard Syntax, Zero Guesswork
Tags, field positions and line lengths follow the standard automatically so the output is valid without manual review.
No manual brace-counting or tag surgery remains once the converter applies the formatting rules.
Accurate imports begin at the source, reducing the back-and-forth with bank support teams.
Common Pitfalls and How to Avoid Them
Date formatting is the most frequent source of rejection. MT940 requires YYMMDD without separators, but spreadsheets often store dates in locale-specific formats. The converter normalizes dates automatically, so a column of March 15 entries becomes 230315 in every :61 and balance line.
Missing or extra spaces in free-text :86 narratives cause parsers to misalign transaction details with their descriptions. The tool trims and pads narrative fields to the expected width, preventing the subtle spacing errors that surface only when the receiving bank processes the file.
Encoding mismatches between the spreadsheet and the MT940 output can corrupt non-ASCII characters in descriptions. The converter ensures UTF-8 consistency throughout, so Arabic, accented Latin and other scripts survive the round trip intact.
Private Financial Generation
Bank-grade data stays on your machine through local processing, with no intermediate servers or cloud storage involved.
No upload, no account, no watermark — across platforms and operating systems.
Statements are built, not exposed, maintaining confidentiality from creation to delivery.
MT940 in the Financial Suite
Combine with MT940 to Excel, MT940 from text and CSV exports for full coverage of statement workflows.
Everything is free and browser-native, requiring no installation or subscription.
Spreadsheets speak banking fluently once the conversion is complete.
Frequently asked questions
Which columns must the Excel file have?
Date, amount and description are essential; balance and reference fields map according to your bank's requirements.
Can the converter handle different field arrangements?
Yes. Interactive field mapping adapts the generated MT940 to your spreadsheet's layout.
Is the conversion private?
Yes. Everything runs locally in your browser with no uploads or accounts.
What date format does the output use?
MT940 dates follow the YYMMDD format without separators. The converter normalizes spreadsheet dates automatically.
Can I generate statements for multiple currencies?
Yes. The tool detects different currency values in your data and creates separate statement blocks with the correct currency code.
Will the output pass bank validation?
The converter checks tag structure, balance consistency and field lengths against standard MT940 rules before generating the file.