How to Fix Common QuickBooks CSV Import Errors
If QuickBooks Online keeps rejecting your bank CSV, the cause is almost always one of five things: a date it can't parse, debit and credit split across two columns, a blank amount, a stray summary row, or a file over 1,000 lines. Here's how to fix each one by hand, and why converting the same file to a .QBO avoids the whole guessing game.
Why QuickBooks rejects bank CSVs in the first place
QuickBooks Online reads a CSV row by row and stops on the first line it cannot understand. It expects one of exactly two layouts: a 3-column file (Date, Description, Amount) or a 4-column file (Date, Description, Credit, Debit), with a file size under roughly 350 KB and no more than 1,000 rows. Your bank's export rarely matches that. It ships extra columns, running balances, account headers, footnotes, and amounts with currency symbols.
The error messages QuickBooks shows ("Some info may be missing from your file" or a vague "can't read this file") almost never tell you which row broke. That's why people spend an hour editing in Excel. The five fixes below cover the vast majority of failures.
Error 1: Wrong or mixed date format
This is the most common failure. QuickBooks Online (US) wants dates as MM/DD/YYYY. Banks export all kinds of things: 2026-03-14 (ISO), 14/03/2026 (day-first), Mar 14, 2026, or even Excel's serial numbers like 45730 after the file is opened and re-saved.
The fix by hand:
- Select the date column in Excel and set the cell format to
Date→MM/DD/YYYY. - Watch for day-first dates:
03/04/2026could be April 3 or March 4. If your bank is non-US, this silently imports transactions on the wrong day. - Delete any row where the date cell is blank or contains text like "Pending".
The catch: if even one row keeps a different format, QuickBooks fails there. Mixed formats inside a single column are the number-one reason "I fixed it but it still won't import."
Error 2: Debit and credit in separate columns
Many banks export money out in one column and money in in another, leaving the unused cell blank. QuickBooks' 4-column layout can read this, but only if the columns are in the exact order Date, Description, Credit, Debit with the right headers. If your file has them reversed, mislabeled ("Withdrawal"/"Deposit"), or with a third "Balance" column wedged in, the import fails or flips the signs so every expense looks like income.
The fix by hand: collapse the two columns into a single signed Amount column. Debits become negative, credits stay positive. A formula like =IF(C2<>"", -C2, D2) works, but you must paste-as-values afterward and double-check no row has amounts in both columns.
Error 3: Blank amounts and currency symbols
Two related problems live in the amount column. First, blank amounts: pending or memo-only rows that have a date and description but no number. QuickBooks treats a missing amount as a broken row. Second, symbols it can't parse: $1,250.00, (45.00) for negatives, USD 30, or thin spaces copied from a web download.
The fix by hand:
- Strip currency symbols and thousands separators so
$1,250.00becomes1250.00. - Convert accounting-style negatives in parentheses to a leading minus:
(45.00)→-45.00. - Delete every row with an empty amount cell.
Error 4: Summary rows, headers, and blank lines
Bank exports love to add non-transaction lines: an account-holder header at the top, an "Opening balance" and "Closing balance" row, subtotals, a "Total debits / Total credits" footer, and blank separator rows between months. Every one of these is a line QuickBooks tries to read as a transaction and chokes on.
The fix by hand: delete all of them. Keep exactly one header row (the column names) and nothing but real transaction rows below it. Then check for hidden blank rows at the bottom of the file: scroll to the end, select the empty rows below your data, and delete them too. Excel often keeps phantom rows that pass the import count but break the parser.
Error 5: More than 1,000 rows (or over 350 KB)
QuickBooks Online caps a single CSV import at about 1,000 rows and ~350 KB. A full year of an active checking account blows past that easily. The import either errors out or silently truncates, and you don't notice the missing transactions until reconciliation doesn't balance.
The fix by hand: split the file by month or quarter into chunks under 1,000 rows each, then import them one at a time, repeating every other fix above for each chunk. It works, but it multiplies the tedium and the chances of a date or amount slip-up.
Why converting to .QBO avoids all five
A .QBO file is QuickBooks' native bank-feed format (OFX under the hood). Instead of QuickBooks guessing how to read loose CSV columns, a QBO tells it explicitly: here is the date, here is the signed amount, here is the description, and here is a unique ID per transaction. That structure removes the failure points entirely:
- Dates are written in a single unambiguous machine format, no MM/DD vs DD/MM confusion.
- Debit/credit is already merged into one signed amount, with correct signs.
- Blank amounts and summary rows never make it in, only real transactions are encoded.
- The row cap doesn't apply the same way, and matched transaction IDs help QuickBooks flag duplicates instead of importing them twice.
QBO Maker does this conversion in your browser: drop in the same messy CSV or Excel export, map the columns once, and download a clean .QBO (or .QFX for Quicken, .OFX for others). Nothing is uploaded, the conversion runs entirely client-side. See the step-by-step in importing CSV into QuickBooks Online, and if a download fails to import you can check the file at the OFX validator.
Frequently asked questions
Why does QuickBooks say "Some info may be missing from your file"?
That message means QuickBooks found a row it can't parse, usually a date in the wrong format, a blank amount, a currency symbol, or a summary/blank row mixed in with real transactions. Fix those rows, or convert the file to a .QBO so the data is encoded in a format QuickBooks reads directly.
Do I really have to use MM/DD/YYYY dates?
For US QuickBooks Online, yes, and the whole column must use the same format. A single day-first or ISO date will stop the import on that row, or import on the wrong day. Converting to QFX or QBO removes the ambiguity because dates are written in one fixed machine format.
My amounts are split into Debit and Credit columns. What do I do?
Either reformat the file into QuickBooks' 4-column layout (Date, Description, Credit, Debit) with the exact headers and order, or merge the two columns into one signed Amount where debits are negative. A converter handles the merge and the signs automatically.
How do I import more than 1,000 transactions?
With raw CSV you must split the file into chunks under 1,000 rows and import each separately. A .QBO bank-feed file avoids that bottleneck, which is why large exports are easier to bring in as QBO than as CSV.
Can QBO Maker convert a PDF bank statement?
QBO Maker reads CSV, Excel (.xls/.xlsx) and text-based PDFs, and outputs .QBO, .QFX, .OFX or CSV. For a scanned or image-only PDF, export the transactions to CSV from your bank first, then convert that.