Bank statement CSV or OFX won't import into your accounting software
Last reviewed 2026-09-19
Every bank exports slightly differently: different date formats, amounts with currency symbols, brackets or trailing minus signs, decimal commas, and separate Debit and Credit columns. Accounting software wants one consistent format, and it rejects or mis-reads rows that do not match.
Messages you might see
- “Import failed: invalid date or amount format”
- “Unrecognised columns in statement file”
- “OFX/QFX file could not be parsed”
Why it happens
- Dates in more than one format inside one file.
- Amounts written with symbols, brackets, trailing minus or decimal commas.
- Debit and Credit in separate columns instead of one signed Amount.
- Duplicate rows from overlapping exports, or a malformed OFX/QFX file.
Try this first (free, no tool needed)
- Open the file and compare a few rows with the format your software's import help asks for.
- Re-download the statement for a shorter period, to avoid overlap and duplicates.
- Check your regional settings: a decimal comma versus a decimal point changes every amount.
If that didn't work
These tools run in your browser. Your file is read and repaired on your own device and is never uploaded.
Bank Statement CSV/OFX/QFX Reconciler
Finds the date, description, amount, debit, credit and balance columns, rewrites every date in one format, turns amounts into plain signed numbers, merges Debit and Credit into one Amount and removes or flags duplicate rows. It also repairs OFX/QFX files. Identical same-day transactions with different balances are kept. Check the totals against your statement afterwards.
Open Bank Statement CSV/OFX/QFX ReconcilerCommon questions
How do I check it didn't lose a transaction?
Compare the row count and the closing balance with your bank's statement after cleaning.
Is my file uploaded anywhere?
No. The tool runs as a program inside your own browser, so the file is read and repaired on your device and never sent to a server.