File tool
QBO & OFX file validator
Find the exact reason a file won't import into QuickBooks, Quicken, or Xero.
Paste the file or pick it from your computer — nothing is uploaded. If you only have a PDF statement, convert it to OFX first.
Choose The Right Tool
Have a PDF statement?
Convert it to OFX for Quicken, GnuCash, Moneydance, or anything else that reads OFX.
Open PDF to OFX →Heading into QuickBooks?
Turn a spreadsheet export into a QBO Web Connect file, with the field mapping explained.
Open CSV to QBO →Want the transactions categorised too?
Upload the statement and get categorised spending and subscriptions, not just a reformatted file.
Analyze a statement PDF →Free tool
Check a QBO, OFX, QIF, IIF or CSV file
Paste the contents or pick the file. The format is detected automatically and only the checks relevant to it are applied.
Paste the file, or choose it from your computer
Everything runs in your browser — the file is never uploaded.
Natural next step
No valid file to start from?
If the source is still a PDF statement, it has to be converted before any accounting software will take it. The converters produce files that pass these checks — including derived FITIDs, so a second import of an overlapping range does not collide.
What it gives you
Fast enough for a first pass
Each tool is intentionally narrow. The job here is a clean estimate, not a fake replacement for a full statement analysis.
Checks what actually breaks imports
Catches the failure modes importers actually reject on: missing or duplicate FITIDs, malformed DTPOSTED, unparseable amounts.
Nothing is uploaded
The file is read locally and never leaves your device, so client statements stay confidential.
Says what will happen, not just what is wrong
Explains each problem in terms of what the importer will do — skip the row, reject the file, or import it blank.
Who it is for
Everything is checked from the file itself, in your browser. Nothing is uploaded.
Bookkeepers with a rejected import
QuickBooks reports a generic failure and names no line. This tells you which transactions are malformed and why.
Anyone whose import 'worked' but imported nothing
The classic duplicate-FITID case, where transactions are skipped silently rather than reported as an error.
Developers generating OFX
Checks the header, serialisation, required tags, date format, and id uniqueness against what importers actually enforce.
Anyone handed a file by a client
Confirms whether the file is sound before you spend time chasing a problem inside the accounting software.
FAQ