QuickBooks CSV Import Errors and How to Fix Them

Short answer: a bank statement CSV fails to import into QuickBooks Online when the file breaks one of QuickBooks' formatting rules. The most common causes are a date that is not in MM/DD/YYYY, an amount column with dollar signs or thousands-separator commas, a file larger than 350 KB, blank rows in the middle of the data, or a description cell that is entirely numeric. Fix the formatting and the same file imports cleanly. If you would rather skip the cleanup, a converter that outputs a QuickBooks-ready CSV or QBO does the formatting for you.

QuickBooks Online is strict about the shape of an uploaded CSV. It accepts a 3-column layout (Date, Description, Amount) or a 4-column layout (Date, Description, Credit, Debit), and it reads the file one row at a time. The moment it hits a row it cannot parse, it stops and shows an error. Below are the errors people actually see, what triggers each one, and how to clear it.

Why won't my CSV import into QuickBooks Online?

Your CSV will not import into QuickBooks Online when the data does not match the format QuickBooks expects. Nine times out of ten it is the date column (must be MM/DD/YYYY in the US), the amount column (digits and a decimal point only, no currency symbols or commas), the file size (350 KB maximum), or stray blank rows. QuickBooks validates row by row and rejects the whole file at the first cell it cannot read, so a single bad row is enough to block the import.

The most common QuickBooks CSV import errors

Here are the errors that block a bank statement import, what causes each one, and the fix.

How do I format a bank statement CSV for QuickBooks?

Format a bank statement CSV for QuickBooks by giving it exactly three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit) with a single header row. Put every date in MM/DD/YYYY, remove dollar signs and commas from amounts, use a leading minus for money leaving the account, and delete any blank or subtotal rows. Save the file as CSV UTF-8 so no hidden characters sneak in. Once the columns are clean, QuickBooks maps them in the import wizard without complaint.

A few details trip people up even after the obvious cleanup. Banks sometimes export with a UTF-16 byte-order mark or invisible control characters that QuickBooks silently rejects; opening the file in a plain text editor and re-saving as UTF-8 clears them. Excel also likes to re-format your dates when you open a CSV, so check the date column again right before you upload. And if your bank splits debits and credits into two columns, use the 4-column layout rather than trying to merge them into one signed amount.

Why does QuickBooks only import part of my file?

QuickBooks imports only part of your file when it hits a row it cannot parse and stops there, so every transaction below that row is dropped. A blank line, a subtotal row, or a single bad date in the middle of the file will cut the import short without a clear warning. Scroll to the last transaction that did import, look at the very next row in your CSV, and you will usually find the blank line or malformed cell that stopped it.

The faster path: convert the PDF straight to a QuickBooks-ready file

Most of these errors come from editing a raw bank export by hand in Excel, where it is easy to leave a comma in an amount or a stray blank row. If you are starting from PDF statements, you can skip the cleanup entirely. Our QuickBooks bank statement converter reads the PDF and outputs a file already shaped for QuickBooks: dates in MM/DD/YYYY, clean numeric amounts, no summary rows, and no encoding surprises. You can export a clean CSV for the standard import, or use the IIF file for QuickBooks Desktop. When the destination is QuickBooks Online, some teams prefer to go one step further and turn the data into a QBO file so it matches the bank register like a downloaded feed; you can convert a statement into a QuickBooks-ready file that imports the same way a bank connection would.

Whichever route you take, keep the file under the 350 KB ceiling. A year of transactions from a busy account can exceed that on its own, so split by month or quarter and import each piece. Our note on why QuickBooks only pulls 90 days of transactions explains why the bank feed leaves gaps that a statement import fills, and the QuickBooks import template shows the exact column layout to copy.

After the import: reconcile before you trust it

Once the file lands, do not assume every row is correct. Open the imported transactions, confirm the count matches the statement, and check that debits and credits landed on the right side. Then reconcile the account against the statement's closing balance so you catch any dropped or duplicated rows. Our walkthrough on reconciling a bank statement in QuickBooks Online covers the match step. Getting the import clean the first time saves the far bigger headache of unwinding a mis-imported month later.