Quick Answer: QuickBooks rejects CSV imports for six reasons: zeros in amount cells, currency symbols or thousand separators, wrong date format, encoding or delimiter mismatch, unrecognized column headers, and — for QuickBooks Desktop users — no native transaction CSV import path at all. The file is usually structurally fine; the importer enforces strict format rules. Each cause has a specific fix, and none of them require uploading your file to a third-party service.
What QuickBooks's Import Errors Actually Mean
QuickBooks error messages are rarely specific enough to tell you what to change. Here are the exact strings you'll see, what each one means, and where to go to fix it.
"Zeros are not allowed in this field" — QuickBooks Online rejects any amount cell containing 0. Files formatted in QuickBooks Desktop or exported from many bank portals represent blank amount cells as 0 rather than empty. In Excel, a zero formatted as accounting style looks blank — the character 0 is still there. Fix: replace whole-cell 0 with empty using Find & Replace's Match Whole Cell mode. → Zeros Not Allowed: full fix and the hidden-formatting-error variant
"There was a problem importing your file. Please review your file and try again." — The generic catch-all. Usually caused by a BOM character at the start of the file, Windows-1252 encoding instead of UTF-8, or a semicolon delimiter where QuickBooks expects commas. Fix: run Format Checker to detect and correct encoding and delimiter. → QuickBooks CSV Import Errors: every common failure
The Continue button stays greyed out (no error shown) — Column mapping is incomplete. QuickBooks Online requires Date, Description, and Amount to be recognized before it enables Continue. Column headers that don't match its expected names leave those fields unmapped. → Continue Button Grayed Out: fix
"Invalid date" / date value rejected silently — QuickBooks Online expects MM/DD/YYYY in US-locale accounts. DD/MM/YYYY causes silent row rejection. Some bank exports append a weekday abbreviation (20/11/2018 TUE), which also fails. → Fix Accounting CSV Date Format Errors
Amount column rejected or amounts import as zero — Currency symbols ($, £) and thousand separators (,) make the amount cell a text string rather than a number. QuickBooks silently drops or misreads these cells. → Fix Currency Symbols in Accounting CSV Files
No "Import Transactions" option in QuickBooks Desktop — QuickBooks Desktop does not have a native transaction CSV import feature. If you're on Desktop and can't find an import option for a bank CSV, the path doesn't exist — the file isn't broken. QuickBooks Online does support CSV import. → Complete QuickBooks CSV Import Guide
Cause and Fix at a Glance
| Symptom | Root cause | Fix | Guide |
|---|---|---|---|
| "Zeros are not allowed" | Blank cells exported as 0; QB Online rejects zero amounts | Find & Replace → Match Whole Cell → find 0, replace with empty | Zeros fix |
| Amount field rejected or wrong | Currency symbol ($ £) or comma separator in amount column | Find & Replace → regex → find [$£,], replace with empty | Currency symbols fix |
| Date rejected or import fails silently | DD/MM vs MM/DD order; trailing weekday text (TUE) | Strip trailing text via regex capture group; full reorder is a regex step | Date format fix |
| "Problem importing" generic error | BOM, Windows-1252 encoding, or wrong delimiter | Format Checker → detect and output clean UTF-8 comma-delimited file | Encoding fix |
| Continue button greyed out | Required column header missing or unrecognized | Rename headers to match QuickBooks expected names using Column Tools | Continue button fix |
| Separate Debit/Credit columns, not a single Amount | Bank export structure vs importer expectation | Debit→negative is a manual upstream arithmetic step; SplitForge handles symbol stripping, encoding, and header renaming around it | All common failures |
Fast Fix (Under 90 Seconds)
Before re-importing, run this sequence on your file:
- Open your CSV in SplitForge Data Validator. Select the
financial-transactionspreset — it flags missing required fields (TransactionID, Amount, Date, Currency, AccountNumber) before you attempt re-import. - Open Find & Replace. In regex mode, find
[$£,]and replace with empty. This removes currency symbols and thousand separators from the Amount column in a single pass. - Still in Find & Replace, enable Match Whole Cell. Find
0, replace with empty. This handles the "zeros are not allowed" case without touching values like10or100. - Open Format Checker. It detects Windows-1252 encoding and semicolon delimiters automatically — both fail QuickBooks silently — and outputs a clean UTF-8 comma-delimited file.
- Check your column headers. QuickBooks Online expects
Date,Description, andAmount(or equivalent mapped names). Use Column Tools to rename any that don't match. - Re-import.
TL;DR
QuickBooks rejects CSVs for format reasons, not content reasons — the transactions are usually fine. The most common culprits are zeros in amount cells, currency symbols, and wrong date order. Run the Fast Fix sequence above, then re-import with Data Validator to catch any remaining field issues before they reach the importer.
The Spreadsheet That Looked Fine
It's month-end. You've exported 340 transactions from your bank portal, opened the file in Excel to confirm it looks clean, and clicked Import in QuickBooks Online. Error. No useful message. You fix the one visible problem — a stray dollar sign — re-export, try again. Error again. Twenty minutes later you're staring at the same generic rejection screen.
The problem is that QuickBooks's importer validates format, not just content. A file can look correct in Excel — numbers in the right columns, dates readable, no visible formatting issues — and still fail because of a byte-order mark in the first cell, a zero in an amount field that Excel renders as blank, or a date formatted as DD/MM instead of MM/DD. None of these are visible problems. All of them are fixable in under two minutes once you know what to look for.
The causes below are compiled from Intuit's QuickBooks import documentation and QuickBooks Community error reports, May 2026. Each has an exact fix. None require uploading your file.
Your Bank Statement Is a Finance CSV — Handle It Accordingly
Bank exports and transaction files contain customer account numbers, transaction detail, and in many cases full PII. Most free online CSV fixers upload your file to a remote server and retain it for 30–90 days under their terms of service. For a file with account-level data, that's a GDPR Article 5 exposure: data processed beyond its original purpose without an adequate legal basis.
SplitForge processes entirely in your browser. The file never leaves your device — no upload, no server, no retention period. For a deeper look at the privacy risks specific to finance CSVs, see Finance CSV Privacy: Why Bank Statement Uploads Create GDPR Risk.
Table of Contents
- Why "Zeros Are Not Allowed" Appears (When There Are No Zeros)
- Why Currency Symbols Cause Rejection
- Why Date Format Failures Are Silent
- Why Encoding and Delimiters Trigger the Generic Error
- Why the Continue Button Stays Greyed Out
- Why QuickBooks Desktop Has No CSV Import Option
- Additional Resources
- FAQ
Why "Zeros Are Not Allowed" Appears (When There Are No Zeros)
QuickBooks Online treats 0 in an amount cell as a literal zero-value transaction, which its importer rejects. The confusing part: files exported from QuickBooks Desktop, or from many bank portals, represent blank amount cells as 0 rather than empty. Excel's accounting number format renders a zero as a blank cell visually — but the character 0 is present in the underlying data, and it exports to CSV.
The fix is a whole-cell exact match replace: find cells containing exactly 0 and replace with empty string. Find & Replace's Match Whole Cell mode does this precisely — it uses exact equality, so 0 is replaced but 10, 0.5, and 100 are left untouched. One pass clears every blank-looking zero in the file.
→ Fix QuickBooks 'Zeros Not Allowed' CSV Import Error — full explanation including the Excel rendering issue and the quoted-empty-string variant that looks blank but isn't.
Why Currency Symbols Cause Rejection
QuickBooks Online expects the Amount column to contain a plain number: 1234.56, not $1,234.56. Currency symbols ($, £, €) and thousand separators (,) make the field a text string rather than a numeric value — the importer then either rejects the row or silently reads the amount as zero. This is one of the most common causes of amount-column failures, and it's invisible in Excel because Excel renders formatted currency cells as numbers.
Find & Replace in regex mode handles this in a single pass: the pattern [$£,] matches any dollar sign, pound sterling, or comma. Replacing with empty removes all three characters, leaving the Amount column as plain numeric values ready for import.
→ Fix Currency Symbols in Accounting CSV Files for QuickBooks and Xero
Why Date Format Failures Are Silent
QuickBooks Online defaults to MM/DD/YYYY in US-locale accounts. A file from a UK bank or an accounting system set to DD/MM/YYYY will fail — but not with a date error message. The row is skipped silently, or the date is imported scrambled: 05/11/2024 is ambiguous (November 5 or May 11, depending on expected format), and QuickBooks Online resolves ambiguity silently in ways that produce wrong data.
A second date failure mode: some bank portals append the weekday to the date field — 20/11/2018 TUE, 15/03/2024 FRI. QuickBooks doesn't parse the weekday suffix and rejects the field. Find & Replace handles this with a regex capture group: ^(\d{2}/\d{2}/\d{4}).*$ → $1 strips everything after the year and keeps the date portion clean.
Reordering between DD/MM and MM/DD is also possible via a multi-capture-group regex — but it's a careful regex step, not a one-click operation. The exact pattern and instructions are in the date-format fix guide.
→ Fix Accounting CSV Date Format Errors: MM/DD vs DD/MM by Platform
Why Encoding and Delimiters Trigger the Generic Error
"There was a problem importing your file. Please review your file and try again." This appears when QuickBooks Online can't parse the file structure — most commonly from three specific issues:
BOM (byte-order mark): Some Windows tools prepend a BOM character (\xEF\xBB\xBF) to UTF-8 files. QuickBooks Online reads it as a character in the first cell, which breaks the header row — none of the expected column names match because they all have an invisible prefix character.
Windows-1252 encoding: Files exported from older accounting software or European bank portals often use Windows-1252 encoding. Characters like the € symbol or accented letters in payee names cause parse failures at the row level.
Wrong delimiter: A semicolon-delimited file (common in European exports) is read as a single-column file by QuickBooks's comma-expecting importer — the entire row becomes one unparseable field.
Format Checker detects all three automatically: it identifies encoding using jschardet with a confidence score, detects the delimiter, and outputs a clean UTF-8 comma-delimited file. The output will load in QuickBooks.
→ Fix Accounting CSV Encoding Errors: UTF-8, Windows-1252, and BOM
Why the Continue Button Stays Greyed Out
QuickBooks Online's CSV import wizard maps your columns to its internal fields before enabling the Continue button. If the Date, Description, or Amount columns aren't recognized — because the header names don't match what QuickBooks expects — those fields stay unmapped and Continue stays inactive. There's no error message.
The most common cause: headers that are close but not exact. "Transaction Date" instead of Date, "Memo" instead of Description, "Debit" and "Credit" instead of Amount — any mismatch means that field isn't mapped. Column Tools can rename headers individually in seconds: "Transaction Date" → Date, "Memo" → Description. A second cause is extra metadata rows at the top of the file (account number, statement period, bank name) that push the real header row to line 2 or 3 — QuickBooks reads only line 1 as the header.
→ Fix QuickBooks CSV 'Continue Button Grayed Out' Import Error
Why QuickBooks Desktop Has No CSV Import Option
If you're using QuickBooks Desktop and can't find an import option for a bank CSV, that's not a feature you haven't located — it doesn't exist. QuickBooks Desktop's native import format for transactions is IIF (Intuit Interchange Format), a tab-delimited format with QuickBooks-specific field codes. It is not a standard CSV.
To bring transaction data into QuickBooks Desktop from a bank CSV, the documented paths are: bank feed download if your bank supports the direct connection, a third-party integration that converts CSV to IIF, or manual entry. There is no File → Import → CSV transaction import in QuickBooks Desktop. This is the most common invisible root cause behind "why does QuickBooks reject my CSV" — the user is on Desktop, has a valid CSV, and is looking for an import path that doesn't exist in their version.
QuickBooks Online does support CSV import for bank transactions. If you're on Desktop and need this workflow, QuickBooks Online's import path is the documented alternative.
Additional Resources
- Intuit: Manually upload transactions in QuickBooks Online — Official QBO manual upload guide. Covers supported file types (CSV, .txt, .qbo, .ofx), the 1,000-line-per-upload limit, and the column mapping step.
- Intuit: Import and export data in QuickBooks Desktop — Official Desktop import/export reference. Confirms CSV is supported for lists (customers, vendors, items) only; bank transactions require Web Connect (.qbo) or IIF.
- RFC 4180: Common Format and MIME Type for CSV Files — The authoritative CSV format specification. Defines delimiter, quoting, and encoding expectations that QuickBooks's importer enforces.
- Unicode BOM FAQ — Why BOM characters appear in UTF-8 files from Windows tools and how to remove them.
- Finance CSV Data Prep: Complete Guide for Accounting Imports — Full reference covering QuickBooks, Xero, NetSuite, Stripe, and SAP imports, PCI-DSS/SOC2 considerations, and the complete prep workflow.
FAQ
Check Your CSV Before QuickBooks Does
Strip currency symbols and thousand separators from the Amount column
Replace whole-cell zeros with blank cells (QuickBooks Online rejects 0 in amount fields)
Confirm date format matches your QuickBooks locale (MM/DD/YYYY for US accounts)
Fix encoding and delimiter — Format Checker outputs clean UTF-8 CSV automatically
Match column headers to QuickBooks's expected field names before import
Your file never leaves your browser — no upload, no server, no retention
Run Data Validator on your file →
For a side-by-side look at how QuickBooks, Xero, and Sage each want their CSV shaped, see QuickBooks vs Xero vs Sage: CSV Format Differences Compared. For the complete accounting CSV workflow, start at the Finance CSV Data Prep guide.