Why won't QuickBooks import my CSV at all?

The usual causes, in order: the file isn't really CSV (it's an Excel .xlsx renamed, or uses semicolons), the columns don't match a layout QuickBooks recognizes (3-column or 4-column), there are extra header/footer rows above the data, or the file exceeds the import limits. Strip the file to a clean header row plus data rows in one of the two layouts.

What are the 3-column and 4-column formats?

3-column: Date, Description, Amount — with one signed amount column (negative = money out). 4-column: Date, Description, Credit, Debit — two unsigned columns, only one filled per row. Mixing the two (a signed amount in a 4-column file, or both credit and debit filled) is a classic silent-failure source.

How large can the CSV be?

QuickBooks Online enforces a file-size cap (350 KB) and struggles beyond about 1,000 rows per import. For a multi-year cleanup, split the data into one file per statement period — which also keeps duplicates traceable when something goes wrong.

Why did my amounts import wrong?

Currency symbols, thousands separators, or parentheses-for-negative notation. QuickBooks wants bare numbers: 1234.56 and -1234.56, not $1,234.56 or (1,234.56). Also check the invisible one: some bank exports use a Unicode minus sign (−) that looks identical to a hyphen but doesn't parse as negative.

Why are my dates wrong after import?

Date-format mismatch — QuickBooks expects US-style MM/DD/YYYY by default, and a DD/MM/YYYY file either swaps day and month silently or collapses to 1/1/1970. That failure has its own guide: see our 1/1/1970 date-error post.

QuickBooks CSV import errors, and the rules behind them

Published August 27, 2026

The short answer: QuickBooks' CSV importer accepts exactly two column layouts, US-style dates, bare unsigned-or-signed numbers depending on the layout, and modest file sizes — and its error messages rarely say which rule you broke. The table below is the whole rulebook; check your file against it top to bottom and the failure will be one of these rows.

The rulebook

Rule	Requirement	Symptom when violated
Column layout	3-col (Date, Description, Amount) or 4-col (Date, Description, Credit, Debit)	"We can't detect the format" / mapping screen misassigns columns
Signs	3-col: signed amount (negative = out). 4-col: two unsigned columns, one filled per row	Everything imports as a deposit, or amounts flip direction
Dates	MM/DD/YYYY	Day/month silently swapped, or every date becomes 1/1/1970
Numbers	No currency symbols, no thousands separators, real hyphen-minus for negatives	Rows rejected, or amounts import as zero
Blank cells	Truly empty — not "0", not a space — in the unused Credit/Debit cell	Zero-amount transactions appear
Size	Under 350 KB and ~1,000 rows per file	Upload fails or hangs; split the file by statement period
File reality	Actual comma-separated UTF-8 text — not renamed .xlsx, not semicolon-delimited	Import dies at file selection
Extra rows	One header row, then data — no bank letterhead, totals rows, or blank lines	First transactions missing, or garbage rows imported

The fix that skips the rulebook

All of these rules exist between your bank's export and QuickBooks' importer — so the reliable fix is generating a file that's compliant by construction. Our CSV to QBO converter reads whatever the bank exported (either sign convention, any common date order, symbols and all) and emits a clean QuickBooks CSV in either layout — or skips CSV entirely and produces a .qbo Web Connect file, which carries structured dates and amounts and doesn't go through the CSV parser at all. Statements stuck as PDFs go through the PDF converter the same way, reconciled against printed balances before you download.

Importing months or years of history? Read the full guide to importing statements older than 90 days — batching, ordering, and duplicate handling live there.

Questions people ask

Why won't QuickBooks import my CSV at all?: The usual causes, in order: the file isn't really CSV (it's an Excel .xlsx renamed, or uses semicolons), the columns don't match a layout QuickBooks recognizes (3-column or 4-column), there are extra header/footer rows above the data, or the file exceeds the import limits. Strip the file to a clean header row plus data rows in one of the two layouts.
What are the 3-column and 4-column formats?: 3-column: Date, Description, Amount — with one signed amount column (negative = money out). 4-column: Date, Description, Credit, Debit — two unsigned columns, only one filled per row. Mixing the two (a signed amount in a 4-column file, or both credit and debit filled) is a classic silent-failure source.
How large can the CSV be?: QuickBooks Online enforces a file-size cap (350 KB) and struggles beyond about 1,000 rows per import. For a multi-year cleanup, split the data into one file per statement period — which also keeps duplicates traceable when something goes wrong.
Why did my amounts import wrong?: Currency symbols, thousands separators, or parentheses-for-negative notation. QuickBooks wants bare numbers: 1234.56 and -1234.56, not $1,234.56 or (1,234.56). Also check the invisible one: some bank exports use a Unicode minus sign (−) that looks identical to a hyphen but doesn't parse as negative.
Why are my dates wrong after import?: Date-format mismatch — QuickBooks expects US-style MM/DD/YYYY by default, and a DD/MM/YYYY file either swaps day and month silently or collapses to 1/1/1970. That failure has its own guide: see our 1/1/1970 date-error post.

This guide is about file conversion and bookkeeping tooling — it isn't tax, accounting, or legal advice. Verify converted data against the source statement before filing or posting it.