Checking a download before it reaches the books
Convert first and read the CSV. Duplicated rows, a wrong date range or a missing week are far easier to spot in a sheet than after they have been posted and have to be unpicked.
Read a QuickBooks .qbo bank file as CSV in your browser, so you can see what is in it before anything is imported.
Maintained by Roshan · Page and browser-local behavior last reviewed August 31, 2026.
Reads a QuickBooks QBO bank file in this tab and writes the transactions out as CSV, so you can inspect or archive them outside QuickBooks. Nothing leaves your device.
Checked with a Canadian savings-account download containing an Intuit routing block and a transfer entry. The declared currency reaches every row rather than being left blank for a spreadsheet to guess at, and the transfer stays one signed row instead of being expanded into a pair that would have doubled the reported movement.
More in this category
Find related browser-local tools for nearby tasks without starting another search.
Browse all developer and data tools toolsA .qbo file is the bank download QuickBooks accepts through Web Connect. It is Open Financial Exchange underneath, carrying an Intuit routing identifier that QuickBooks checks before it will take the file at all — which is why a .qbo downloaded for one company file can be rejected by another, and why the format has a reputation for being awkward. The awkwardness is in the acceptance rules, not the data. The transactions inside are plainly structured and this page reads them in your browser, producing a CSV you can open anywhere. The most common reason to want that is not conversion at all but inspection: seeing exactly what a bank download contains before it goes into the books, or getting a period of transactions out of a file when the QuickBooks side has become the obstacle. Nothing is uploaded, no company file is touched, and no QuickBooks licence is involved.
Convert first and read the CSV. Duplicated rows, a wrong date range or a missing week are far easier to spot in a sheet than after they have been posted and have to be unpicked.
Acceptance depends on the routing identifier matching what the company file expects. That check is not repeated here, so the transactions can still be read out and entered another way.
A bank statement in Open Financial Exchange format with an Intuit routing block attached. The transaction records inside follow the ordinary OFX grammar, which is what makes them readable without any Intuit software.
QuickBooks checks the routing identifier and the account it is being imported into before accepting the file. That is an acceptance rule, not a property of the data, and this converter has no reason to apply it.
Not with this tool. Only reading is offered for now. Writing a Web Connect file that QuickBooks will accept means reproducing identifiers that belong to a financial institution, which is a different problem from parsing.
No. There is no sign-in, no API connection and no company file access. The tool reads a file from your device inside this browser tab and produces a CSV on the same device.
Convert an OFX bank statement to CSV in your browser. No upload, no bank connection, no account. Transaction dates, payees, amounts and FITIDs come out as columns.
Convert a Quicken QFX file to CSV in your browser. Works without a Quicken subscription. No upload, no bank login, no account needed.
Convert a QIF file to CSV in your browser, with the day/month order made explicit instead of guessed. No upload, no account, no bank connection.
Reconcile bank, ledger, processor and marketplace exports in your browser. Write your own matching rules, review the exceptions, and export a full audit package. The files are not uploaded.
Turn CSV into a real .xlsx workbook in your browser. Leading zeros and long numbers survive, unlike opening the CSV in Excel directly.