Your first row was data, not headers
How you'll know: The first customer or invoice in your file is missing after the import.
Fix: QuickBooks uses row one to map columns and never imports it. Add a header row with plain column names.
QuickBooks Online has its own import screen for lists and a handful of transaction types, and it takes CSV, Excel or Google Sheets. It's good at a clean customer or product list. It gets fussy with transactions, and it caps how much you can load in one go. Here's what to expect before you upload.
Open the import screen, pick what you're importing, upload the file, then match your columns to QuickBooks fields.
Settings ⚙ › Import dataImports natively: customers, vendors, chart of accounts, products and services, bank data, invoices, bills and journal entries.
Limits that catch people: each file must be under 1,000 rows, and invoices go in 100 at a time at most. Split anything bigger into several files.
On QuickBooks Desktop? Lists in CSV need Intuit's free Import Excel and CSV Toolkit, a Windows download with sample files and a field reference.
The import screen is the right tool for some of these and the wrong one for others. Find your row.
Most failed imports are a file problem, not a QuickBooks problem. Check these before you try again.
How you'll know: The first customer or invoice in your file is missing after the import.
Fix: QuickBooks uses row one to map columns and never imports it. Add a header row with plain column names.
How you'll know: Invoices land in the wrong month, or 03/04 became April 3 instead of March 4.
Fix: Pick the date format that matches your file on the mapping screen, and make every date in the column use it. Mixed formats in one column are the usual cause.
How you'll know: Journal entries or invoices reject rows, or invoice lines show a generic Sales item instead of your product.
Fix: Import in Intuit's order: chart of accounts, customers, vendors, products and services, then the transactions that use them. Names in the transaction file must match exactly.
How you'll know: The upload stalls or refuses the file.
Fix: Keep each file under 1,000 rows and each invoice batch to 100 invoices. Split by month or by customer so you can tell which batch is done.
How you'll know: That entry is rejected while the others go in.
Fix: Total the debits and credits for each journal number in Excel before uploading. They have to match for every entry, not just for the whole file.
How you'll know: QuickBooks says the file can't be read, even though it opens fine in Excel.
Fix: Copy the data into a brand new sheet, save it as CSV, and upload that instead.
Same steps for a list or a batch of invoices. The data type you pick changes which fields you have to map.
Each import screen offers a sample CSV. Copy your data into its columns rather than inventing your own layout. It's the fastest way to see which fields are required.
Choose your file, then match each column to a QuickBooks field. Required fields are marked. Set anything your file doesn't have to Not applicable.
Watch for: the option to add customers that don't exist yet on an invoice import. Ticking it creates them as bare names, which you'll have to fill in later.
QuickBooks shows what it's about to create. Fix anything flagged in your spreadsheet, not on screen, so the file stays your record of what went in.
If some rows don't import, QuickBooks lists the reasons. Copy them down before you click Done, so you know which rows to fix and re-import.
Company moving off an older accounting system
About two years of invoices and journal entries sat in exported spreadsheets, far more than the import screen was built for.
Every attempt stopped partway through, and the errors didn't say which rows were wrong. Someone was going through thousands of lines by hand to find out.
n-frames built an import pipeline that checks each row against QuickBooks' real field rules before sending anything.
Rows that don't fit are flagged one by one instead of failing the batch, and everything else loads in one pass.
What looked like weeks of retries became a short list of flagged rows someone fixed in an afternoon.
A free download from Intuit for QuickBooks Desktop on Windows. It holds sample CSV and Excel files, a PDF manual, and a reference of the fields each list (customers, vendors, items and so on) accepts. Desktop needs it installed before it will import lists in CSV. QuickBooks Online doesn't use it, because the import screen and its sample files are built in.
Some. QuickBooks Online imports invoices, bills and journal entries natively, with limits: under 1,000 rows per file, up to 100 invoices at a time, and no negative lines. For years of history or several transaction types at once, most people use a third-party importer or a custom import that checks the data first.
Usually a mismatch between the file and what QuickBooks expects: a missing header row, a date format that doesn't match, an account or customer name that doesn't exist yet, an unbalanced journal entry, or a file over 1,000 rows. Fix the file and re-upload rather than editing on screen.
In QuickBooks Online, yes. CSV, XLS and XLSX all go through the same upload and column mapping, and so do Google Sheets. If a particular import refuses an Excel file, saving it as CSV usually fixes it, and it also strips out formatting that can confuse the upload.
Not in bulk. Imported contacts have to be deleted or made inactive one at a time, and an overwrite of products and services can't be undone once you click Import. Test with a small file first.