Bank files · Runs in your browser

View and validate an OFX or QBO file.

Open an OFX, QBO or QFX file as a readable table and run structural checks before you try to import it. The checks run on your device and the file is never uploaded.

How to read the report

  1. Choose the file. Name it .qbo or .qfx, or set “Treat the file as”, to switch on the extra checks for Intuit files.
  2. Optionally enter the balance before the first transaction.
  3. Press Check file. Findings are sorted: errors first, then warnings, then notes.
  4. Below the findings you get a table of statements and a table of transactions, so you can see what an importer would see.

The checks, exactly

Structure. For OFX 1.x the page expects OFXHEADER:100, DATA:OFXSGML and a VERSION line. For 2.x it expects an <?OFX OFXHEADER="200" ...?> instruction. It then parses the elements. In the SGML form, a value element needs no closing tag, but every container such as a statement or a transaction does. A container that is never closed, or closed out of order, is reported with the tag name. Because a missing close is the most common hand-edit mistake, this is usually the first thing to look at.

Account. Each statement needs an account number of at most 22 characters and a currency. A bank statement also needs a bank ID of at most 9 characters and one of the account kinds CHECKING, SAVINGS, MONEYMRKT, CREDITLINE or CD. A credit card statement needs only the account number.

Transactions. Each needs a TRNTYPE from the OFX list, a DTPOSTED that is a real date (a value such as 20240231 is an error, because February has no 31st), a TRNAMT that reads as a number, and a FITID. FITIDs must be unique within the statement. Amounts with a comma as the decimal mark are read but warned about. A DEBIT with a positive amount, or a CREDIT with a negative one, is warned about as a sign mismatch.

Period and date. DTSTART must not be after DTEND, and a transaction dated outside them is warned about. A transaction after today is warned about too.

Balance. The OFX definition requires a ledger balance in every statement. If it is missing you get a warning. If you provide an opening balance, the page tests opening plus the sum of transactions against it.

Intuit extras. For a QBO or QFX, the page looks for an institution block with ORG and FID and, for a QBO, INTU.BID, and notes if they are missing. It cannot tell you whether the values are on any approved list.

What a pass does not tell you

Passing means no structural errors were found. It does not mean a bank issued the file, that the numbers are right, or that a given program will take it. A converter vendor lists, among the reasons QuickBooks Desktop rejects QBO files, an institution the program does not recognise, and payee names that are too long. The first is outside what any local check can see. The file might also contain real transactions that are simply not yours. Always compare the first and last transaction and the total with a statement you trust.

Worked example

A downloaded file shows ten transactions but the report says: FITID “20240105” is used by more than one transaction (first at 3, again at 7). The bank has built its IDs from the date only, so two rows on 5 January collide, and an importer may keep only one. The fix is to give the colliding rows distinct IDs. Our own CSV-to-QBO and CSV-to-OFX pages build FITIDs that avoid this, and the original file should be regenerated rather than patched by hand. Another common finding is opening balance 1500.25 plus the transactions (310.00) is 1810.25, but LEDGERBAL says 1960.25 (difference 150.00), which means 150.00 of activity is missing from the file or the opening balance entered was taken at the wrong date.

Common mistakes

  • Fixing warnings in a text editor and saving as UTF-8 with a byte order mark. For OFX 1.x, keep the declared Windows-1252 and plain line endings.
  • Deleting a transaction without adjusting the ledger balance.
  • Reading a note (such as identical transactions with different FITIDs) as an error. Two identical coffees on one day are legitimate.

What this tool does not do

  • It does not check digital signatures, because OFX files from a bank download carry none.
  • It does not look up a bank or validate an FID or routing number.
  • It does not modify or save the file.

What happens to your file

The conversion is done by JavaScript running inside this page’s tool frame. The frame is sandboxed and its content security policy forbids network requests, so even a bug in the code could not send your file anywhere. The page that holds the advertising is a separate document and cannot read the frame. The file is read with the browser’s own file reader, the result is built in memory, and the download link points at a temporary address that exists only in your tab. Close the tab and it is gone. You can confirm it yourself: open your browser’s network panel, convert a file, and watch for requests. There are none.

To turn the file into a spreadsheet, use the QBO to CSV converter or the OFX to CSV converter. To build a clean file from a spreadsheet, see the CSV to QBO converter.

Frequently asked questions

What does the validator check?

The header form (OFX 1.x or 2.x), the sign-on status and date, that each statement has an account number and currency, that bank statements have a bank ID and a valid account kind, that dates are real calendar dates and inside the statement period, that every transaction has a type, date, amount and FITID, that no FITID repeats, that field lengths are within the OFX limits, that the amount sign agrees with the type, and that a ledger balance exists.

Does a clean result mean QuickBooks or my bank will accept the file?

No. The checks come from the OFX field definitions and from common importer behaviour. A file can pass and still be refused, because Intuit products also check the institution block and each program applies its own rules. The report says so each time it finds no errors.

Why is a duplicate FITID an error?

A FITID is the transaction’s unique ID within its account. Importers use it to detect transactions they already hold, so when two rows share one, an importer may keep one and drop the other. The report names both positions.

How does the balance check work?

You enter the balance before the first transaction. The page adds every transaction amount in whole cents and compares the result with the ledger balance in the file. If they differ it shows the difference, which is often a missing transaction or an opening balance taken at a different date.

What are the 32-character and 255-character warnings?

OFX limits NAME to 32 characters, MEMO to 255, FITID to 255, ACCTID to 22 and BANKID to 9. Some importers truncate longer values and others reject the transaction. The page counts how many values exceed each limit.

Why does it warn about future dates?

A transaction dated after today is often a sign that the day and month were swapped when the file was made. The comparison uses today’s date from your device clock, so a wrong clock gives wrong warnings.

Can it fix the file?

No. It reports problems and leaves the file untouched. To rebuild a clean file, export the transactions to CSV with the converter pages and generate a new QBO or OFX.

Is my file uploaded for checking?

No. The file is read and checked in your browser, and the tool frame is not allowed to make network requests. The account numbers shown in the table are masked to the last four characters.

Sources

Checked

Runs entirely in your browser. Nothing you load or type is sent or stored. This page is not affiliated with Intuit, Quicken, any bank or the OFX standards body.

Common mix-ups

  1. Open Financial Exchange 2.2 specification (Internet Archive copy)

Checked against these sources on .

Advertisement
Advertisement