How to Fix QuickBooks Import Errors

QuickBooks gives you maddeningly vague messages. "This file isn't formatted correctly" can mean six different things. So rather than guessing, it's faster to match the symptom to the cause. The table below is the one I keep coming back to.

QuickBooks import errors and how to fix each one

Work top-down. The date and amount rows cause the most rejections, and they're the quickest to fix once you know which one you're looking at.

The QuickBooks 3-column rule

QuickBooks Online's manual import is fussier than people expect about width. It wants three fields per transaction and gets unhappy when you hand it the whole statement: Date, Description, Amount. That's it.

The Amount comes in one of two accepted shapes, and mixing them is a classic cause of the "not formatted correctly" message:

• One signed column. Money out is negative (`-42.50`), money in is positive (`128.00`). Cleanest for most files.
• Two columns. A separate Debit column and Credit column, each with positive numbers. Fine too — just don't also leave a signed column hanging around.

Everything else from the original statement has to go. The running balance column, the transaction-type column, reference numbers, a second description line — strip them out before you save. A file that imports cleanly is usually a file you've cut down hard.

Fix the date format error

This is the one that catches people who work across countries. A statement printed as `04/06/2026` is the 6th of April in the UK and the 4th of June in the US. QuickBooks doesn't guess for you; if the order is wrong, dates either land on the wrong day or the whole row gets bounced.

QuickBooks Online lets you choose the date format on the mapping screen during upload, so the safe move is to set it there and then eyeball one known transaction — find a payment you remember and confirm it landed on the right day. If you're editing the CSV by hand, write dates in an unambiguous order (`YYYY-MM-DD` is the least error-prone) and confirm the format selection matches. Don't rely on Excel's auto-formatting; it loves to silently reinterpret dates when you open and re-save a file.

Fix the amount column

Two problems live here, and they look similar from the error message. First, formatting inside the number: a value like `1,240.00` reads as text, not a number, because of the symbol and the comma. Clear both. The cell should hold `1240.00` and nothing else.

Second, the shape of the column. If your statement uses separate Paid in and Paid out columns and you try to import both *plus* a signed total, QuickBooks sees columns it can't place. Decide on one signed Amount column or a clean Debit/Credit pair, then delete the rest. A money-out value in a signed column has to carry its minus sign — without it, an expense imports as income, and you won't spot that until reconciliation goes sideways.

Stop duplicate transactions

Duplicates almost always come from an overlap. You import January, then later import a range that includes the last few days of January again; or you upload a month a connected bank feed has already pulled. QuickBooks doesn't dedupe across an upload and a feed automatically.

Two habits prevent it. Import in clean, non-overlapping date ranges — know the exact last date you imported and start the next file the day after. And before a file upload, check whether the bank feed already covers those dates; if it does, you don't need the file for that window. If duplicates do slip in, they sit in the For Review tab where you can exclude them before they reach your books.

Why a reconciled CSV avoids most of these

Here's the part most guides skip. Every error above is a *format* problem — but there's a quieter one that no format check catches: a transaction that's simply missing. A converter can hand back a tidy three-column CSV that imports without a single complaint and is still wrong, because one Direct Debit fell off the bottom of page four. A clean file that's incomplete is worse than an obvious mess, because you'll trust it.

This is where the running balance does real work. It's a built-in checksum: opening balance, plus money in, minus money out, has to equal the printed closing balance. Recompute it line by line and the first row where your total stops matching the bank's figure is the exact line where something was dropped or misread. Reconcile before you import and you're not chasing a hole through your QuickBooks accounts a fortnight later.

Export Bank Statement converts the PDF — including scanned and photographed statements, via OCR — into a clean CSV or Excel file, then runs that running-balance check for you. It recomputes the totals against the printed closing balance and flags any statement that doesn't reconcile, so a missing or misread line surfaces before it ever reaches QuickBooks. We once watched a neat-looking import fail the check over a single payroll line clipped from a batch; the flag turned an afternoon of hunting into a one-minute fix. It writes the file in QuickBooks' native bank-import CSV format, so the columns arrive shaped the way QuickBooks expects — which clears the format errors and the completeness gap in the same pass.

Be plain on what it is, though: convert, then upload. It doesn't push transactions into QuickBooks through a live bank-feed API, and it isn't a bookkeeping service — you decide what gets imported and reconciled. For the field-level detail, the QuickBooks CSV import format walkthrough and the import PDF statements into QuickBooks guide go column by column, and can QuickBooks import PDF bank statements? answers the question underneath all of this. You can also browse the wider US accounting guides.