QFX to QBO Converter

QFX is what comes out of Web Connect, the download-a-file half of Intuit's online banking integration. When a bank builds a QFX export it starts from a plain OFX statement — the same sign-on block, the same BANKACCTFROM account block, the same list of STMTTRN transaction records — and then stamps it with Intuit-specific tags. The important one is INTU.BID, a numeric ID Intuit assigns to each participating institution. Some banks also write an INTU.USERID. Those tags exist to bind the download to a specific Intuit product and entitlement, and they are the whole of the difference between a QFX file and any other OFX statement.

That branding is why the obvious shortcut fails. Renaming a .qfx to .qbo leaves INTU.BID sitting in the file announcing that this download belongs to Quicken, and QuickBooks Online is entitled to reject it on that basis. The confusing part for anyone hitting this the first time is that the file is not corrupt and the transactions are not malformed — every date and amount in it is exactly what QuickBooks wants. It is a licensing marker, not a data problem, and no amount of re-downloading from the bank changes it.

This converter takes the direct route: it reads the transactions out and throws the wrapper away. Every STMTTRN record is parsed for its posted date, amount, description, and FITID, the routing number, account number, and currency are lifted from the original account block, and a clean OFX 1.02 SGML document is written from scratch with no Intuit branding tags in it at all. The result is the file the bank would have produced if it had enabled the QuickBooks channel. Practically, this is the path for a small business banking on a retail product, an accountant receiving Quicken-flavoured downloads from clients, or anyone whose Quicken subscription lapsed while a folder of QFX downloads sat unread.

The renamed file was rejected but the converted one imports fine. This is the expected result, not a fluke. Renaming leaves the Intuit branding tags in place; converting removes them and rebuilds the envelope. If a rename ever did work for you on a different bank, that bank simply omitted those tags from its export.

The account number in the file is masked with asterisks or X characters. Some banks redact ACCTID in Web Connect downloads. The converter carries whatever it finds through verbatim, so a masked value stays masked. QuickBooks then cannot auto-match the file to an account and will ask you to choose one during upload — pick it manually and the import proceeds normally.

Pending transactions appeared, then changed, then imported twice. Quicken Web Connect downloads sometimes include pending items, and banks routinely reassign the FITID once a pending transaction posts for real. The same purchase then arrives under two different IDs and QuickBooks cannot tell they are the same. Download and convert only settled activity, or expect to merge a handful of rows by hand.

Only part of the date range came through. Web Connect exports are commonly capped at 90 days per download regardless of how much history the online banking interface displays. If a quarter came in short, that ceiling is the usual explanation — pull consecutive windows, convert each, and import them in order.