OFX to QBO Converter

OFX (Open Financial Exchange) was published in 1997 by Microsoft, Intuit, and CheckFree as a shared standard so that any bank could hand transaction data to any personal finance program. Structurally an OFX file is not a spreadsheet — it is a nested document. A sign-on block (SIGNONMSGSRSV1) declares the server response, a bank message block (BANKMSGSRSV1) wraps a statement response, that statement declares the account it belongs to in BANKACCTFROM, and only inside a BANKTRANLIST do you finally reach the individual STMTTRN records that represent transactions.

QBO is what Intuit ships on top of that standard for QuickBooks. The transaction records are the same STMTTRN blocks with the same tags, so nothing about your data has to change — but QuickBooks Online is strict about the surrounding envelope. It wants the OFX 1.02 SGML header, a bank account block it can match, and a file named with the .qbo extension. A bank that only offers "OFX" or "Money" downloads therefore gives you data QuickBooks could read, in a wrapper QuickBooks refuses.

This converter closes that gap. It scans your file for STMTTRN records regardless of whether the source is SGML or XML flavoured, pulls the posted date, amount, description, and FITID out of each one, carries over the routing and account identifiers where the bank provided them, and writes a fresh OFX 1.02 SGML document with the .qbo extension. Typical reasons people need it: a business bank that only publishes OFX for its commercial accounts, a credit union whose download menu never mentions QuickBooks, a bank feed that disconnected mid-quarter and left a gap to backfill, or an accountant who receives OFX exports from clients on a dozen different banks.

QuickBooks says the file is not in the right format even though it converted fine. QuickBooks Online checks the file extension before it looks at the contents. If your browser or operating system appended something on download — statement.qbo.txt is the usual culprit — rename it so the name ends in exactly .qbo and upload again.

Nothing was found in the file. The converter looks for STMTTRN records. Three source files commonly lack them: an investment statement (which uses INVSTMTTRN instead), an OFX file covering a date range with no activity, and an HTML error page that your bank served instead of a download while your session had expired. Opening the file in a text editor tells you which of the three you have within a few seconds.

The account in QuickBooks doesn't match, or QuickBooks asks which account this is. That happens when the source OFX omitted BANKID or ACCTID, which some credit unions do. It is not an error — pick the correct QuickBooks account manually during the upload step and the transactions land in the right place.

Descriptions are truncated or oddly abbreviated after import. That truncation comes from the bank, not the conversion. Many institutions populate NAME with a 32-character abbreviation and leave the fuller text in MEMO. The converter prefers MEMO and falls back to NAME, so if you are seeing the short form, the long form was never in the file.