Why QuickBooks Won't Accept Your Bank CSV (And the 9 Rules That Fix It)

The Error Message That Explains Nothing

You export transactions, open Banking → Upload transactions, drop in the file, and QuickBooks says:

Some info may be missing from your file.

That's it. Not which row. Not which column. Not which of the 340 lines has a date it couldn't parse. You're now doing binary search on a spreadsheet — delete half the rows, try again, repeat — to find one bad cell.

This is the single most common support question in bookkeeping forums about bank imports, and almost every case comes down to a handful of formatting rules that Intuit documents but nobody reads until something breaks.

Here they are, ranked by how often they're actually the problem.

The Rules, Ranked By How Often They Break Imports

1. Mixed date formats in the same column

The most common cause by a wide margin.

Banks are inconsistent within a single export. You'll get 2026-03-15 on one row, 3/15/2026 on the next, and 15-Mar-26 further down. Some banks append the weekday — 20/11/2026 TUE — which QuickBooks cannot parse at all.

QuickBooks reads row by row and fails on the first date it doesn't recognize. Every date must use one identical format.

Fix: Select the date column in Excel, set a single custom format, and retype any row that didn't convert. Watch for the weekday suffix — it survives a format change because Excel treats it as text.

2. Wrong number of columns

QuickBooks Online accepts exactly two layouts:

That's the whole list. A file with Date, Description, Debit, Credit, Balance is a 5-column file and will be rejected — even though the extra column is harmless data.

Fix: Delete every column that isn't in one of those two layouts, then reorder the survivors to match exactly. Balance and reference columns have to go, however useful they are to you.

3. File over 350 KB or 1,000 rows

Intuit caps uploads at 350 KB and 1,000 transactions per file. A full year of a busy business account clears both easily.

The failure here is quiet — you'll often get a generic error rather than "your file is too big."

Fix: Split by date range. Month-by-month for a busy account, quarter-by-quarter for a quiet one.

4. Zeroes where blanks belong

In the 4-column layout, every transaction is either a credit or a debit — never both. Banks commonly export 0.00 in the unused column.

Intuit's guidance is explicit: cells in Amount, Credit, or Debit that contain only zero should be blank, not 0.

Fix: Find and replace 0.00 with nothing in the Credit and Debit columns. Leave genuine zero-value transactions out entirely; they import as nothing anyway.

5. The word "amount" in your headers

If your header row reads Credit Amount and Debit Amount, strip the word Amount. The headers must be Credit and Debit.

Small, silly, and a real cause of rejected files.

6. Numbers inside the Description column

Intuit asks you to remove numbers from Description cells. In practice, a description like POS PURCHASE 4471 STARBUCKS #219 can cause QuickBooks to misread where the amount begins.

Fix: Strip leading transaction and card-fragment numbers. Keep the merchant name — that's what your bank rules match on.

7. Blank rows in the middle of the file

Bank exports often include a blank line between statement periods, or a trailing blank at the end. QuickBooks treats a blank row as a malformed transaction.

Fix: Sort by date, which pushes blanks to one end, then delete them.

8. Currency symbols, thousands separators, and parentheses

$1,240.00 is text, not a number. So is (45.20) — the accounting convention for negatives that Excel understands and QuickBooks doesn't.

Fix: Format the amount columns as plain numbers. Convert parenthesized negatives to a leading minus sign.

9. Non-English files

Intuit states the upload must be in English. Statements from non-US banks frequently carry localised column headers or month names, both of which fail.

Fix: Translate headers to English and normalise dates to numerals.

What This Costs In Practice

The cleanup itself isn't hard. What costs the hours is that the error message doesn't tell you what's wrong, so most of the time goes to diagnosis rather than fixing.

The Honest Ranking Of Ways To Avoid This

Download CSV directly from your bank. Free and fastest when available. The catch: most banks only expose the last 90 days, many credit unions offer no CSV at all, and the file still routinely breaks rules 1, 2, and 4 above. You're cleaning, just less.

Clean it manually in Excel. Total control, no cost. Fine for one account. It stops scaling somewhere around five clients, and it's the step where tired people introduce errors — a transposed digit in a tax filing is worse than a rejected import.

Use a QBO/QFX converter. Converting to QuickBooks' native format sidesteps CSV rules entirely, since QBO carries its own structure. Costs money, and quality varies sharply between tools.

Convert from the PDF and skip the bank's CSV. If you're pulling from statement PDFs anyway — which you are, for anything older than 90 days — a converter that outputs a clean, QuickBooks-shaped CSV means the nine rules above are handled before you ever open the file.

That last one is what we built, so treat this as disclosure rather than a neutral recommendation: Accurate Bank Statement Converter outputs date, description, debit, credit, balance, and reference as separate normalised columns, splits combined amount columns by sign, and uses a consistent date format throughout. You'll still delete the balance column for QuickBooks' 4-column layout — no converter can guess which of the two layouts you want.

Common Questions

Why doesn't QuickBooks just tell me which row failed? No good reason. The parser stops at the first unreadable row but the interface doesn't surface which one. This is the single most requested improvement in Intuit's community threads on the topic.

Can I import a PDF bank statement directly? No. QuickBooks Online accepts CSV, QBO, QFX, and OFX. QuickBooks Desktop accepts only QBO, QFX, and OFX — not CSV. A PDF has to be converted first either way.

Does the 350 KB limit apply to QBO files too? The 350 KB and 1,000-row limits are documented for CSV uploads. QBO imports have their own constraints, generally more forgiving for a single statement period.

My file looks identical to one that worked last month. Why did it fail? Almost always a date. Banks change export formats without notice, and a single row where the format shifted is enough. Check the dates before anything else.

Will fixing these rules make my transactions categorise correctly? No — these rules only get the file accepted. Categorization depends on your bank rules and chart of accounts, which is a separate problem.

The Bottom Line

QuickBooks' CSV importer is strict and quiet about it. Nine formatting rules cover essentially every rejection, and eight of the nine are things a bank export gets wrong on its own — not mistakes you made.

Check dates first. It's the culprit far more often than everything else combined.

If you're converting from PDF statements anyway, getting the CSV right at the conversion step means you never meet these rules at all.

Try Accurate Bank Statement Converter free — 1 daily conversion anonymously (no signup), 50 free credits on signup (no card required). Excel + CSV output, batch upload up to 10 files, files deleted immediately after processing.

Convert your first bank statement in 30 seconds →

Neha Poonia is the founder of Accurate Bank Statement Converter and a former software engineer at AWS.