QuickBooks Import Excel and CSV Toolkit: Download, Contents, and How to Import CSV Into QuickBooks Desktop

It is a free utility from Intuit that helps QuickBooks Desktop users import list data from Excel or CSV files. It is not a feature inside QuickBooks. It is a separate download containing a manual, sample files, and a reference guide that tells you which fields QuickBooks will accept for each list. You still perform the import from inside QuickBooks under File, Utilities, Import.

Four things. An Import from Excel and CSV Manual as a PDF, with instructions and best practices. A CSV Examples folder holding four sample CSV files, one for each type of list. An XLS Example folder with a single Excel workbook containing four worksheets, again one per list. And an Allowed Fields reference guide explaining which fields are available for Excel and CSV import.

Download QuickBooks_Import_Excel_and_CSV.exe from Intuit's help article, save it to your Windows desktop, then double click it. A WinZip Self-Extractor window opens. Choose Browse, pick the folder you want the toolkit unpacked into, select OK, then Unzip. Close the extractor and open the new QuickBooks Import Excel and CSV folder. Nothing installs into QuickBooks itself; you are simply unpacking documents and samples.

No. Intuit's CSV article scopes the toolkit to lists such as customers, vendors and items, and its import and export overview sends bank data down a different path: import bank transactions using Web Connect (.qbo) files. QuickBooks Desktop has no native CSV import for bank or credit card activity. A CSV of transactions has to become a .qbo first, or an .iif if you are pushing journal entries.

No. The toolkit ships as a Windows executable that unpacks through WinZip Self-Extractor, and Intuit's install steps tell you to save it to your Windows desktop. QuickBooks Desktop for Mac users have no toolkit to download. For bank and card history on a Mac the answer is the same as on Windows: convert the CSV to a .qbo file and import it through the bank feeds menu. The converter on this page runs in the browser, so the operating system stops mattering.

Nothing. Intuit publishes it as a free download alongside the help article for importing and exporting CSV files in QuickBooks Desktop. What it costs you is scope. It solves list setup, which most companies do once, and leaves the recurring monthly job, getting bank and credit card lines into the register, untouched.

It depends entirely on what the CSV contains. For a list of customers, vendors, items or accounts, use the toolkit templates and go to File, Utilities, Import, Excel Files, then Advanced Import and build a column mapping. For bank or credit card transactions, convert the CSV to a Web Connect file and go to Banking, Bank Feeds, Import Web Connect Files. Those are two different menus solving two different problems, and mixing them up is the single most common reason a CSV import stalls.

Yes, for lists. QuickBooks Desktop reads .xls and .xlsx workbooks through Advanced Import, where you map each spreadsheet column to a QuickBooks field and save the mapping for reuse. Transactions are the exception again. QuickBooks will not accept a spreadsheet of bank lines, which is why converting the workbook to a .qbo is the shortcut most bookkeepers land on after the third failed attempt.

QuickBooks Online can, and QuickBooks Desktop cannot. Online accepts a manual CSV upload under Transactions, Bank transactions, Upload from file, provided the file matches a strict three column or four column layout. Even there, a .qbo file skips the column mapping screen and the date format guessing entirely, because the format already carries the field labels inside it.

A CSV is only a grid of text. Nothing inside it says which column holds the date or whether a negative number is a payment or a refund, and every bank lays it out differently. A .qbo file is Web Connect, an Intuit format where each transaction carries labelled fields, an account identifier and a statement date range. QuickBooks reads it identically no matter which bank produced it, which is why the desktop bank feed accepts it and rejects everything else. Note that importing Web Connect files requires you to be signed in to your Intuit Account inside QuickBooks Desktop.

No. Web Connect reads .qbo files only. QFX is Quicken's Web Connect variant and QIF is an older Quicken interchange format, and neither is accepted by the QuickBooks Desktop bank feed import. If your bank only offers QFX or QIF, or only offers CSV, the file has to be converted to .qbo before QuickBooks will take it.

They are aimed at opposite ends of your company file. The toolkit builds the master lists that transactions later get coded against, and it is a one time setup job. A CSV to QBO converter handles the transactions themselves, every month, for every account. Firms that run monthly closes for several clients touch the toolkit once and a converter constantly.

Upload the CSV or Excel export in the converter at the top of this page. It detects the date, description and amount columns, normalizes dates to the format QuickBooks expects, keeps debits and credits on the correct sides, and writes a Web Connect file with the opening and closing balances set. Before the download appears it sums every parsed transaction and compares that total to your source file, so a silently dropped row shows up as a mismatch rather than as a reconciliation problem three weeks later.

That is the normal case for catch up work. A live bank feed typically reaches back about 90 days, and it cannot see closed accounts or the months before you connected. Your bank's export screen will usually hand you years of CSV history, and converting that CSV gives QuickBooks a file it accepts without complaint about the date range.