OFX to MT940 converter

OFX is what many banks and credit-card issuers export — and exactly the format European accounting packages will not read. Upload it and download a SWIFT MT940 that imports cleanly.

Upload your OFX file →

2 free conversions · no credit card required

OFX to MT940 in 3 steps

  1. Upload your OFX. Both a regular bank statement (STMTRS) and a credit-card statement (CCSTMTRS) are recognised. Amounts, dates and counterparties are parsed.
  2. Check the account and balances. A credit-card statement identifies the account by card number rather than IBAN. That number does not belong in an exported file, so StatementBridge substitutes a fictitious but valid account number and tells you it did.
  3. Download the MT940 file. The result follows the SWIFT standard and imports into Exact Online, Twinfield, AFAS, Moneybird, SnelStart and e-Boekhouden.

Where OFX files come from

Banks abroad

OFX is the common export format in the US and the UK. Dutch and Belgian packages expect MT940 or CAMT.053 instead.

Credit-card issuers

Card statements often arrive as OFX. Those use CCSTMTRS rather than STMTRS — both are supported.

Accounting software

Packages that export OFX let you move to one that expects MT940 without rekeying anything.

OFX 1.x or 2.x?

Only OFX 2.x (XML) can be read. If you see a message about OFX 1.x, export again as 2.x — see the questions below.

Prefer a different target format?

MT940 is not the only output. From the same OFX file you can also pick CAMT.053, Excel or CSV. If your package works with CAMT.053, choose that — it carries more structured fields than MT940 does.

Frequently asked questions

Which OFX versions are supported?

OFX 2.x, the XML-based version. OFX 1.x uses SGML rather than XML and cannot be read; if you get that message, re-export from your bank as OFX 2.x. Most banks offer both.

Does this work for credit-card statements?

Yes. Credit-card exports use CCSTMTRS and CCACCTFROM instead of STMTRS and BANKACCTFROM, and both are handled.

My OFX has a card number instead of an IBAN. What happens?

A card number is not a valid account identifier and does not belong in an exported file. A fictitious but format-valid account number is substituted, and the conversion tells you it did so. Change it if your accounting package expects a specific account.

Can I convert OFX to something other than MT940?

Yes. CAMT.053, Excel and CSV are available from the same upload. Prefer CAMT.053 if your package supports it — it carries more structured detail than MT940.

Will the MT940 import into my accounting package?

The output follows the SWIFT MT940 standard and is accepted by Exact Online, Twinfield, AFAS, SnelStart, Moneybird, e-Boekhouden, Yuki and Visma.