Intuit CSV to QBO Converter: Is There an Official One?
No account needed for your first conversions. We never store your bank login.
Short answer: no. Intuit does not publish a CSV to QBO converter, and there is no CSV plugin inside QuickBooks. The official Import Excel and CSV toolkit imports four kinds of lists, not bank transactions. QuickBooks Online can upload a bank CSV directly, QuickBooks Desktop cannot import one at all, and the only file Desktop reads for banking is a .qbo Web Connect file. To get a CSV into Desktop you convert it first, with a third party converter. Last updated July 2026.
This question shows up constantly in the Intuit community forums, usually phrased as where is the CSV plugin in QuickBooks. The answer from Intuit staff has been consistent for years: there is no such plugin, QuickBooks Desktop does not import CSV or Excel files containing transactions, and customers are pointed at third party apps for the conversion. It is worth understanding why, because it explains what to look for in a converter.
What does the QuickBooks Import Excel and CSV toolkit actually import?
Four list types and nothing else: customers, vendors, items, and the chart of accounts. The toolkit is a download containing a PDF manual, sample CSV and Excel files, and an allowed fields reference. It exists to help you populate lists in a new company file. It has no path for bank or credit card activity, which is the data most people are actually holding when they go looking for it.
Where is the CSV plugin in QuickBooks?
There is not one. QuickBooks Desktop has no menu item, add-in or plugin that turns a CSV into bank transactions. The Banking menu offers Bank Feeds, and inside Bank Feeds the only file option is Import Web Connect File, which accepts .qbo. Anything that promises a CSV import into Desktop is either a third party tool or an import of lists rather than transactions.
Can QuickBooks Online import a CSV of bank transactions?
Yes, natively, within limits. QuickBooks Online accepts a three column layout of date, description and amount, or a four column layout with separate credit and debit columns. The file has to be in English, use one consistent date format, and stay under 350 KB and 1,000 rows per upload. Those caps are why a multi month or multi year backfill usually fails on the first try.
Why doesn't Intuit make a CSV to QBO converter?
Because a .qbo file is not a generic export format, it is a bank delivery format. Web Connect is Intuit's flavor of OFX, and every file identifies the institution that produced it through bank identifier fields. Historically that file was produced at the bank's end under Intuit's Web Connect program, not at the customer's end. Intuit built the reader, banks built the writer, and no one built the bridge from a spreadsheet.
Can I create a .qbo file myself in Excel or Notepad?
Technically yes, practically no. A .qbo is structured text, so you can hand author one, but QuickBooks rejects files that miss required elements, use the wrong date encoding, or repeat transaction IDs. Most people who try this spend an evening on OFX tags and end up with an error rather than an import. A converter writes the structure and the unique IDs for you.
Are third party CSV to QBO converters allowed?
Yes. Intuit's own support answers direct customers to third party apps for this conversion, and a converted .qbo enters QuickBooks through the same Import Web Connect File door as a bank downloaded one. QuickBooks does not treat a converted file as second class. What matters is that the file is well formed and that each transaction carries a unique ID so repeat imports are recognized.
What is the difference between a .qbo file and a CSV file?
| Aspect | CSV | .qbo (Web Connect) |
|---|---|---|
| What it is | Plain rows of text, any columns | Intuit's OFX based banking file |
| QuickBooks Online | Uploads directly, 350 KB and 1,000 row cap | Uploads directly, same size cap |
| QuickBooks Desktop | Not supported for transactions | The only supported banking import |
| Account details | None, you pick the account manually | Carries account and institution identifiers |
| Duplicate protection | None, QuickBooks compares dates and amounts | Unique transaction ID on every line |
| Column mapping | You map columns on every upload | Nothing to map, the structure is fixed |
Will a converted .qbo file import like a bank downloaded one?
It should behave identically. QuickBooks reads the account and institution identifiers, matches the file to the register you point it at, and drops the transactions into the review queue. On QuickBooks Desktop the flow is Banking, Bank Feeds, Import Web Connect File. Recent Desktop releases ask you to sign in to your Intuit Account inside the program before the import runs, which catches people off guard but is normal.
Which route should I use, CSV upload or converted .qbo?
On QuickBooks Desktop there is no choice, it is .qbo or manual entry. On QuickBooks Online, use the native CSV upload for a small single month file and convert to .qbo when you are importing several months, several accounts, or anything where accidental duplicates would be expensive. The unique transaction ID in a .qbo is the practical difference between the two.
Does the Intuit App Store list CSV to QBO converters?
The QuickBooks App Store lists apps that connect to QuickBooks Online through Intuit's API, which is a different mechanism from file conversion. A file converter never touches your QuickBooks account or your bank login, it just reads a file you already downloaded and writes another file. That is why many converters, including this one, are used through a browser rather than installed as an app.
What if my starting point is a PDF statement, not a CSV?
Then you have an extra step. QuickBooks reads neither PDFs nor scanned statements for banking, so the usual sequence is to turn the statement PDF into a spreadsheet first, check the rows and running balance against the paper copy, and then convert that spreadsheet to .qbo. Verifying the middle step matters, because an OCR mistake in an amount becomes a reconciliation problem later.
What should I check in the CSV before converting?
Three things catch most files. First, one account per file: a CSV that mixes a checking account and a card produces a .qbo that reconciles against neither. Second, one date format throughout, because a single row switching from 03/04/2026 to 4 Mar 2026 is enough to shift a month of transactions. Third, decide what the amounts mean. Some banks export one signed column where money out is negative, others export separate debit and credit columns, and a few export a running balance column that must not be treated as an amount. Open the file in a spreadsheet, sort by date, and check the first and last rows against your statement before you convert anything.
How do I convert a CSV to QBO right now?
Upload the CSV or Excel file from your bank to the converter at the top of this page, confirm the parsed dates, descriptions and amounts, then download the .qbo. In QuickBooks Online, go to Transactions, then Bank transactions, then Upload from file. In QuickBooks Desktop, go to Banking, then Bank Feeds, then Import Web Connect File, and pick the account when prompted.
If you want the mechanics in more detail, the step by step walkthrough is on how to convert CSV to QBO, the column layout QuickBooks expects is covered in the QuickBooks CSV import template guide, and the format itself is explained in what is a .qbo file. For tool choices see the best CSV to QBO converter comparison, and for the edition specific routes see CSV to QuickBooks Desktop and importing CSV into QuickBooks Enterprise.