QuickBooks Import Excel and CSV Toolkit imports lists only, never bank transactions. See what is inside it, what it cannot do, and how to convert CSV to QBO.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF · Max 50MB
Uploading...
The QuickBooks Import Excel and CSV Toolkit is a free Windows download from Intuit that helps you import lists into QuickBooks Desktop: customers, vendors, items and the chart of accounts. It is a manual, four sample CSV files, a sample Excel workbook and a field reference, not an import engine. The part most people are actually looking for, importing bank transactions, is not in it. QuickBooks Desktop takes bank and credit card activity only as a .qbo Web Connect file, which is why converting your statement to QBO is the step that finishes the job.
Last updated August 2026. Toolkit contents and installation steps checked against Intuit's own import and export CSV help article for QuickBooks Desktop in August 2026. Several widely shared guides claim the toolkit imports bank transactions. It does not.
Here is exactly what lands on your desktop when you unzip QuickBooks_Import_Excel_and_CSV.exe. There is no installer service and nothing gets added to QuickBooks itself. You are downloading documentation and templates.
| What is in the toolkit | What it is for |
|---|---|
| Import from Excel and CSV Manual | A PDF walkthrough of the guided list import, with best practices and the gotchas Intuit knows about. |
| CSV Examples folder | Four sample CSV files, one per list type, showing the exact column headers QuickBooks expects. |
| XLS Example folder | One sample Excel workbook with four worksheets, the same four list types in spreadsheet form. |
| Allowed Fields reference | The full list of fields you can map for each list type, including the ones the guided wizard hides. |
Four sample files, four list types. That count is the fastest way to understand the toolkit's scope, and it is also where the confusion starts. People download it after searching for a way to get a bank download into QuickBooks, open the folder, and find nothing about transactions.
| Data you want to import | Toolkit covers it? | How it actually works |
|---|---|---|
| Customer list | Yes | QuickBooks Desktop: File > Utilities > Import > Excel Files, then map your columns. |
| Vendor list | Yes | Same guided wizard. The Allowed Fields sheet tells you which vendor fields accept data. |
| Item list | Yes | Supported, though advanced inventory fields and assembly builds are outside what the wizard maps. |
| Chart of accounts | Yes | Account names and types map cleanly. Account numbers only import if account numbering is switched on first. |
| Bank and credit card transactions | No | Not a toolkit function. QuickBooks Desktop imports these only from a .qbo Web Connect file, through Banking > Bank Feeds > Import Web Connect Files. |
| Invoices, bills, checks, journal entries | No | Needs IIF, a third party importer, or manual entry. The toolkit's guided wizard is list only. |
| Payroll and paychecks | No | Not importable through this route at all. |
That fifth row is the whole reason this page exists. QuickBooks Desktop has never accepted a CSV of bank transactions. QuickBooks Online will take a CSV in a three or four column layout, capped at 1,000 rows and 350 KB per file, but Desktop will not, and no toolkit changes that. If you are holding a spreadsheet or a PDF statement and your books live in Desktop, the file has to become a .qbo before QuickBooks will look at it.
Use this to work out your route in one step, based on what you are holding and which QuickBooks you run.
| What you have | QuickBooks Desktop (Windows) | QuickBooks Online |
|---|---|---|
| Customer, vendor, item or account list in Excel or CSV | Use the toolkit. File > Utilities > Import > Excel Files. | Use the built in importer under Settings > Import Data. |
| Bank download as CSV | Convert the CSV to .qbo, then import as a Web Connect file. The toolkit cannot do this. | Upload directly. Reformat to Date, Description, Amount first. |
| PDF bank or credit card statement | Convert the PDF to .qbo with the converter at the top of this page, then Import Web Connect Files. | Convert to .qbo and upload, or use QuickBooks Online's own PDF upload where your bank layout is recognized. |
| QFX or OFX file from your bank | Convert to .qbo. Desktop's Web Connect reader accepts the .qbo flavor only. | Upload the .qbo. Intuit's own guidance on QFX in QuickBooks Online is inconsistent, so QBO is the safe format. |
| IIF file from an older system | Import through File > Utilities > Import > IIF Files. | Not supported. Convert the data or use a connected importer. |
| Statements for 30 clients, monthly | Convert in bulk to .qbo, one file per account per period. | Same. Batch conversion is faster than 30 CSV cleanups. |
Two honest notes before you spend an afternoon on the toolkit. First, it is Windows only. The .exe is a WinZip self extractor and there is no Mac build, so QuickBooks for Mac users import lists through the application's own File menu instead. Second, the toolkit is genuinely useful for the job it does. Setting up a new company file with 400 customers and a real chart of accounts is exactly what those sample files are for, and the Allowed Fields reference saves a lot of guessing. It just is not a bank feed tool, and no amount of column mapping will make it one.
Where a converter fits: you upload the PDF statement, the extraction reads dates, descriptions and amounts, the totals get checked against the statement's own closing balance, and you download a .qbo that QuickBooks Desktop accepts through Bank Feeds. It skips the CSV cleanup entirely, which matters because most CSV import failures are formatting problems, not QuickBooks problems: two date columns, a running balance column QuickBooks reads as an amount, negative numbers wrapped in parentheses, or a header row your bank changed last quarter.
Built for the statements US banks actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to the statement total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
OCR runs before parsing, so a scanned or photographed paper statement comes out the same as a digital PDF.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Enter the password on upload. Multi-column and multi-page statement layouts are parsed too.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a PDF, a scan, or a phone photo. Password-protected and multi-page files are fine.
Every transaction is extracted and checked against the statement total. You see the parsed rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, email [email protected].
Intuit hosts it in the QuickBooks Desktop help article on importing and exporting CSV files, as a direct .exe download. Search Intuit's support site for import and export CSV files in QuickBooks Desktop and the download link sits at the top of the list import section. Take it from Intuit rather than a third party mirror, because the sample files change between QuickBooks versions.
Yes. It is a free download from Intuit and there is no license, subscription or activation attached to it. What you are getting for free is documentation and templates, not software that runs. The guided import wizard it documents is already built into QuickBooks Desktop, so the toolkit adds no capability you do not already have.
Save QuickBooks_Import_Excel_and_CSV.exe to your Windows desktop, double click it to open the WinZip Self Extractor, select Browse and pick a folder such as your desktop, then select Unzip and Close. Open the QuickBooks Import Excel and CSV folder that appears. Nothing installs into QuickBooks and nothing runs in the background.
No. The toolkit ships as a Windows .exe and macOS cannot run it. QuickBooks for Mac users import lists through the application's own File menu, and for bank transactions the route is the same as on Windows: get the activity into a supported file and import it, rather than pasting a spreadsheet.
Yes, for lists. QuickBooks Desktop imports customers, vendors, items and the chart of accounts from Excel through File > Utilities > Import > Excel Files, and the toolkit's sample workbook shows the expected columns. Transactions are a different mechanism: bank activity needs a .qbo file, and invoices or bills need IIF or a third party importer.
Yes, with a narrower set. QuickBooks Online imports customers, vendors, products and services, the chart of accounts, invoices, bills and journal entries from Excel or CSV under Settings > Import Data. Bank transactions are handled separately, through the Banking screen, and QuickBooks Online caps uploads at 1,000 rows and 350 KB per file.
It depends which QuickBooks and what the CSV holds. For lists in Desktop, use the guided Excel and CSV wizard the toolkit documents. For lists and some transaction types in QuickBooks Online, use Settings > Import Data. For bank transactions in QuickBooks Online, use Banking > Link account > Upload from file. QuickBooks Desktop has no CSV route for bank transactions at all.
No. QuickBooks Desktop accepts bank and credit card activity only as a .qbo Web Connect file, imported through Banking > Bank Feeds > Import Web Connect Files. A CSV has to be converted to .qbo first. This is the single most common reason people download the toolkit, and it is the one thing the toolkit does not solve.
QuickBooks Online caps a bank transaction upload at 1,000 rows and 350 KB per file, so a busy account often needs splitting by month. QuickBooks Desktop's Web Connect import has no published row ceiling, but very large .qbo files import slowly and are easier to reconcile if you split them by statement period anyway.
Almost always the file's shape, not QuickBooks. The usual causes are a date format QuickBooks does not recognize, a running balance column sitting where the amount column should be, debits and credits split across two columns when a single signed column is expected, currency symbols or parentheses inside the number, blank rows, or a header row your bank quietly changed. Fix the file, do not fight the importer.
The toolkit is documentation for importing static lists into QuickBooks Desktop. A converter reads a bank or credit card statement, extracts the transactions and writes a .qbo file that QuickBooks imports as a bank feed. They solve opposite halves of setting up a company file: one loads who you deal with, the other loads what happened in the account.
Not directly. QuickBooks Desktop has no PDF reader for statements, so the PDF has to be converted to .qbo first and then imported through Bank Feeds. QuickBooks Online has added PDF statement upload for some recognized bank layouts, but coverage is uneven, and converting to .qbo gives you the same result on both platforms.
Yes. The guided Excel and CSV list import is part of QuickBooks Desktop Pro, Premier and Enterprise on Windows, and the toolkit's samples apply to all three. Enterprise also has Advanced Import and the Add or Edit Multiple List Entries grid, which many Enterprise users find faster than mapping a spreadsheet for anything under a few hundred rows.
Convert each statement period to .qbo and import the files in date order through Bank Feeds, oldest first. Working in statement periods keeps each import reconcilable against a closing balance you can verify, which is far easier to unwind than a single twelve month file that lands a few dollars off.
Often yes, for a new company file. The two do different jobs: the toolkit loads your customer, vendor, item and account lists once at setup, and a converter loads bank activity every month afterwards. Firms setting up a client from scratch usually use both in the same week.
One practical sequencing tip for a new file. Load the chart of accounts before anything else, then customers and vendors, then items, and only then bring in bank transactions. Importing activity first means every transaction lands uncategorized and you end up recategorizing the same rows twice.
And if account numbers matter to you, switch account numbering on before you import the chart of accounts. QuickBooks silently ignores a Number column when numbering is off, and there is no warning, just a chart of accounts with no numbers in it.
Upload a PDF, see every transaction extracted in seconds. No card to try it.
Still comparing tools? See our bank statement to QuickBooks converter comparison.
Same converter, tuned for the layout each bank uses. Find yours:
For one bookkeeper running monthly close.
USD
per month
per month
$288 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
For an accounting firm or finance team with steady volume. Adds QuickBooks .qbo export and bulk conversion.
USD
per month
per month
$888 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
For lenders, audit firms and analysts running thousands of statements a month.
USD
per month
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
