Statement file fixer
Drop an OFX, QFX, QBO, QIF or CSV file to find out exactly why it won't import — and get a repaired copy.
What this tool checks
The fixer enforces the same rules real importers do: the OFX declaration header, SGML/XML escaping, date formats, numeric amounts, unique transaction ids, file truncation, QIF type headers and record separators, CSV delimiters, column alignment and byte-order marks. Repairs are deterministic — when a fix would require guessing, the finding says so instead of corrupting your data silently.
Why we never see your file
Bank statements are sensitive. This page ships the repair engine to your browser as JavaScript; the analysis happens on your device and the repaired file is generated there too. There is no upload endpoint at all — verify it in your browser's network tab, or load this page, go offline, and run the fixer in airplane mode.
Common reasons a file is rejected
- Quicken error OL-221-A when importing a QFX file
- QuickBooks: not a valid Web Connect file
- YNAB says the file is empty (0 transactions)
- GnuCash QIF import finds no transactions
- Invalid OFX file: the six defects that cause it
- Transactions missing after a Quicken or YNAB import
- CSV import: columns shifted, merged, or misaligned
- Statement file cut off mid-download (truncated OFX/QFX)
- Quicken will not import QIF into a bank account
- QuickBooks says the QBO file is for another account