1. Why Local Browser Parsing Matters for Sensitive Financial Statements
Corporate bank statements contain the highest-concentration financial intelligence a business owns: full IBANs, SWIFT/BIC routing codes, payroll amounts, supplier pricing, tax authority transfers, and daily liquidity balances. Uploading an .mt940, .sta, .ofx, or .qif export to a remote cloud converter hands that entire ledger to an external web server—creating immediate exposure under GDPR Article 32, SOC 2 vendor-risk rules, and internal CPA client-confidentiality mandates.
Adawaty Pro eliminates remote transmission completely by running its parser strictly inside your browser's isolated JavaScript sandbox. When you drop a statement into the upload zone, the HTML5 FileReader API reads the file into a temporary ArrayBuffer inside your local RAM. No POST request fires, no temporary file hits an S3 bucket, and no server access log ever sees your account number. When you export an .xlsx workbook via SheetJS or a UTF-8 BOM .csv via Blob URLs, the output file is synthesized directly on your CPU and handed straight to your browser's download manager. Closing the tab immediately frees the memory buffer.
2. Deep Dive into SWIFT MT940, OFX & QIF File Architecture
Banking exports fall into three distinct structural generations, each requiring its own tokenization rules to avoid dropped transactions or inverted signs.
SWIFT MT940 (ISO 15022 Corporate Cash Management)
Standard across European, MENA, and international treasury portals (BNP Paribas, ING, Deutsche Bank, Rabobank, Attijariwafa, HSBC), an MT940 file structures statements using colon-delimited field tags:
:20:— Transaction Reference Number assigned by the sending bank.:25:— Account Identification (typically IBAN or domestic branch/account number).:60F:/:60M:— Opening Balance encoded as[C|D][YYMMDD][ISO Currency][Amount with comma], e.g.,:60F:C261101EUR12500,00.:61:— Statement Line carrying Value Date (YYMMDD), optional Entry Date (MMDD), Debit/Credit mark (D,C,RD,RC), comma-decimal amount, 4-character SWIFT transaction type code (NTRFwire transfer,NMSCmiscellaneous,NCHKcheck), customer reference, and bank reference after//.:86:— Information to Account Owner (up to 6 wrapped lines of 65 characters each). SEPA-compliant banks embed structured subfields like/NAME/,/IBAN/, and/REMI/or German ZKA?20–?32codes inside:86:.:62F:— Closing Booked Balance used to verify thatOpening + SUM(:61:) = Closing.
:20:STMT20261122
:25:MA64011519000001205000534921
:60F:C261101EUR12500,00
:61:2611051105D1450,50NTRFINV-2026-884//BANKREF001
:86:/NAME/ATLAS LOGISTICS SARL/REMI/FREIGHT INVOICE 884
:62F:C261122EUR11049,50
OFX 1.x (SGML) vs. OFX 2.x (XML) & Quicken QIF
OFX (and Intuit's QFX variant) groups each posted entry inside <STMTTRN> blocks containing <TRNTYPE>, <DTPOSTED> (YYYYMMDDHHMMSS), signed <TRNAMT>, unique <FITID>, <NAME>, and <MEMO>. Legacy QIF opens with !Type:Bank or !Type:CCard and emits single-letter prefixed lines (D Date, T Amount, P Payee, M Memo) separated by caret (^) record terminators.
3. Step-by-Step Conversion & Reconciliation Workflow
- Load Your Statement: Drag your
.sta,.mt940,.940,.ofx,.qfx, or.qiffile into the dropzone above, or click one of the three Sample buttons to inspect live output immediately. - Verify Summary Control Totals: Check the four KPI cards (Detected Format, Transaction Count, Total Credits, Total Debits) against your bank portal's summary screen.
- Filter & Audit Rows Live: Type a vendor name, invoice reference, or date into the table search bar to isolate specific wires or fees before exporting.
- Export to Excel (.XLSX) or UTF-8 BOM CSV: Click Export Excel (.XLSX) for typed numeric columns and automatic formula readiness, or Export CSV (UTF-8 BOM) for direct import into Xero, QuickBooks, Sage, or Odoo.
4. Technical Format Comparison Table
| Attribute | SWIFT MT940 (.sta / .940) | OFX / QFX | Quicken QIF |
|---|---|---|---|
| Syntax Structure | Colon-tagged FIN blocks (:61:, :86:) | SGML (1.x) or strict XML (2.x) | Single-letter prefixes + ^ |
| Decimal & Date Style | Comma decimal, YYMMDD | Dot decimal, YYYYMMDD | Locale-dependent dates |
| Opening/Closing Balance | Mandatory (:60F: & :62F:) | Closing in <LEDGERBAL> | None |
| Primary Ecosystem | SAP, Odoo, Exact, Sage, EU/MENA corporate banks | QuickBooks, Xero, Chase, HSBC, Wise | Legacy Quicken, GnuCash, older credit unions |
| Best Export Target | Native .XLSX (preserves exact running balance) | .XLSX or UTF-8 BOM .CSV | .XLSX (verify date order first) |
5. Troubleshooting Common Parsing & Encoding Errors
- Excel Turns Arabic or French Payee Names into Garbled Symbols: Double-clicking a plain UTF-8 CSV on Windows triggers legacy Windows-1252 decoding. Always use our Export CSV (UTF-8 BOM) button—which inserts
0xEF 0xBB 0xBF—or download native.XLSX. - MT940 Multi-Statement Files (
:60M:/:62M:): Daily corporate SWIFT feeds sometimes concatenate 30 daily statements into a single.stafile using intermediate balances (:60M:/:62M:). Our parser collects every:61:/:86:pair sequentially across the entire file without stopping at the first:62M:boundary. - QIF Thousands Commas Inside Amounts: Some Quicken exports format amounts as
T1,250.00. Our QIF parser strips thousands separators cleanly before numeric conversion so totals never truncate at the comma. - Sign Inversions on Reversal Entries (
RC/RD): In SWIFT MT940, a credit reversal (RC) subtracts funds from your account (negative), while a debit reversal (RD) restores funds (positive). Always check the Running Balance column against your bank's:62F:closing figure to confirm exact parity.
Mapping SWIFT Transaction Type Identification Codes (:61: Subfield 6)
Every SWIFT MT940 :61: statement line embeds a 4-character transaction type code immediately after the numeric amount. Understanding these ISO 15022 codes lets treasury teams build automated Excel categorization rules via IF or XLOOKUP tables without reading every narrative line manually. The first character is almost always N (SWIFT transfer) or F (first advice), followed by a 3-letter instrument code: TRF denotes a domestic or SEPA wire transfer, CHG denotes bank fees and commissions, INT denotes interest credit/debit, CHK denotes check clearing, DDT denotes SEPA Direct Debit, and MSC denotes miscellaneous card or FX settlements.
When reconciling multi-entity corporate accounts in SAP, Odoo, Exact Online, or Sage 100, always verify two mathematical invariants after exporting to Excel: first, check that the closing cell of the Running Balance column equals the exact :62F: Closing Booked Balance printed on the bank's PDF statement; second, check for duplicate FITID values when overlapping OFX date ranges are combined across month boundaries. Keeping raw .sta, .ofx, and .qif originals archived alongside your reconciled .xlsx workbook gives external statutory auditors a verifiable trail from bank portal download to general ledger posting.
Frequently Asked Questions
How does SWIFT MT940 encode debit and credit directions inside the :61: statement line?
Tag :61: places a single-letter or two-letter debit/credit mark immediately after the entry date: 'D' means Debit (outgoing), 'C' means Credit (incoming), 'RD' is a Reversal of Debit (positive adjustment), and 'RC' is a Reversal of Credit (negative adjustment). Our parser applies the exact sign to each numeric amount before computing the running balance.
Why do European MT940 files use commas for decimals while OFX files use periods?
SWIFT FIN standards (ISO 15022) mandate a decimal comma inside :60F:, :61:, and :62F: numeric amounts (e.g., 1450,50). Open Financial Exchange (OFX) follows US dot notation (1450.50). Our parser normalizes both into true IEEE 754 floating-point numbers so Excel SUM() formulas work immediately.
What happens when an MT940 :86: narrative spans 4 to 6 wrapped lines?
SWIFT FIN limits individual lines to 65 characters, causing banks to wrap SEPA remittance details across multiple continuation lines without repeating :86:. Our tokenizer joins every non-tag continuation line until the next colon-prefixed tag (:61: or :62F:) so payee names and invoice numbers are never truncated.
Does this converter preserve Arabic, French, and German payee names when opening the CSV in Windows Excel?
Yes. Clicking Export CSV prepends the 3-byte UTF-8 Byte Order Mark (0xEF 0xBB 0xBF) so Windows Microsoft Excel decodes accented European and Arabic payee strings cleanly instead of falling back to Windows-1252 mojibake.
Can I parse OFX 1.02 SGML files that omit closing tags like ?
Yes. Many major banks still export OFX 1.x SGML where leaf elements have no closing tags (for example,
How is the Running Balance column calculated if an OFX or QIF file has no opening balance?
For SWIFT MT940 files, the running balance initializes from the exact :60F: (First Opening Balance) tag. For QIF and minimal OFX feeds lacking an opening balance tag, the running balance tracks cumulative net cash flow starting from 0.00 so you can reconcile net movement cleanly.
Are my IBAN numbers, corporate balances, and supplier names sent to any server?
Never. Parsing executes inside your browser's local JavaScript runtime via FileReader and TypedArrays. Even if you disconnect your internet after loading this page, the OFX, QIF, and MT940 conversion and XLSX export work identically.