💡 Quick Answer
QuickBooks bank feed CSV imports fail at column mapping when the exported file uses non-standard header names or includes extra columns that the mapping wizard cannot resolve.
The root cause is a format mismatch between bank export schemas and QuickBooks' required column structure: Chase exports Transaction Date and Payee; QuickBooks needs Date and Description. Wells Fargo exports separate Deposits and Withdrawals columns; QuickBooks needs them named Credit and Debit exactly.
The fix: Use SplitForge Format Checker to detect column header issues before import, then SplitForge Data Cleaner to rename headers and remove extra columns — entirely in your browser.
Why it matters: Bank feed CSV imports go through QuickBooks' column mapping wizard, which silently fails with a grayed-out Continue button when it cannot auto-map your column headers — no explicit error message, just an unusable import screen.
⏰ FAST FIX (90 Seconds)
If your QuickBooks bank feed import is stuck at column mapping, try this first:
- Open the bank CSV in a plain text editor — check the first row. Does it show
Posting Date,Transaction Date, orPost Dateinstead ofDate? Does it include aBalance,Running Bal., orCheck #column? - Remove extra columns — delete
Balance,Running Balance,RunningBal,Check or Slip #,Type, andCategorycolumns. QuickBooks accepts exactly 3 or 4 columns; any extra causes silent wizard failure. - Rename headers to match QuickBooks schema — rename
Posting DateorTransaction Date→Date, renameMemoorPayee→Description. For split-amount formats, renameDeposits→CreditandWithdrawals→Debit. - Validate column structure — use SplitForge Format Checker to confirm header names and column count before re-attempting the import.
- Re-import — the Continue button should unlock once headers match
Date,Description,Amount(3-column) orDate,Description,Credit,Debit(4-column). - Check file size if the wizard freezes — QuickBooks Online enforces a practical ~350 KB / ~1,000 row import limit for bank feed CSV files. Files exceeding this limit fail silently or time out. Split into monthly batches using SplitForge CSV Splitter before re-attempting.
If your bank uses a multi-currency account, international date format, or exports more than 5 columns, continue below for the full diagnosis.
TL;DR: Bank feed CSV imports fail at column mapping because bank exports use non-standard header names (Posting Date, Payee, Running Bal.) and include extra columns (Balance, Check #) that QuickBooks' mapping wizard cannot resolve. Rename headers to match QuickBooks' schema, remove extra columns, and process with SplitForge Format Checker — no upload required.
Your controller flagged a 90-day reconciliation gap at 4:45 PM on a Friday. You pull the Chase CSV directly from the bank portal — 847 transactions, three months of vendor payments and payroll. You drag it into QuickBooks Online's bank feed import screen and watch the column mapping wizard load.
Then: nothing. The Continue button is grayed out. No error message. No red text. The wizard shows your columns in the preview pane but refuses to advance.
You rename Post Date to Date. The button stays grayed out. You check the Description column — it's labeled Description already. You try importing again. Still grayed out. Meanwhile, the Balance column in column 5 is silently breaking the entire mapping.
This is the bank feed CSV column mapping failure pattern: the QuickBooks Online mapping wizard silently rejects files with extra columns or unrecognized header schemas — returning no actionable error, just an unusable Continue button. Unlike general CSV import errors that surface explicit messages, bank feed column mapping failures require diagnostic inspection of your file structure before the wizard will cooperate.
For the broader QuickBooks CSV error guide covering currency symbols, date formats, and encoding issues, see QuickBooks CSV Import Error: Fix Common Failure Modes.
Each error type in this guide was reproduced using QuickBooks Online (US edition), May 2026.
What QuickBooks' Bank Feed Errors Actually Mean
Continue button grayed out (no error message) — Column headers don't match QuickBooks' accepted schema, or the file contains more columns than the expected 3 or 4. The mapping wizard cannot assign your columns to its required fields and silently blocks progression. Inspect the header row and column count first.
"Some info may be missing from your file" — The CSV has an unrecognized column structure or a column count that doesn't match either the 3-column or 4-column format. This appears after the file is uploaded but before the mapping wizard completes. Usually triggered by extra columns.
"Date format not recognized on row N" — The mapping wizard accepted your column structure, but the date values in the Date column don't match your QuickBooks account's regional setting. This can appear even after successful column mapping — it means the headers were right but the date values are wrong.
"Invalid amount format on row N" — The Amount, Credit, or Debit column contains a currency symbol, thousand-separator comma, or parentheses for negative values from the bank export. The column mapped successfully but the values fail row-level validation.
Transactions imported with wrong values (no error raised) — Column mapping succeeded but assigned the wrong column to the wrong field. Common when a Balance column in position 4 gets mapped as the Amount field. QuickBooks imports but all transaction amounts reflect account balances instead of transaction values.
📋 Table of Contents
- Why Bank Feed CSV Import Works Differently from General CSV Import
- Error 1: Column Header Name Mismatches (Bank-by-Bank)
- Error 2: Extra Columns Breaking the Mapping Wizard
- Error 3: Credit/Debit Split Format Requires Exact Header Names
- Error 4: The Column Mapping Wizard's Silent Failure Behavior
- Error 5: Date Format Errors That Survive Column Mapping
- Why Your Bank Feed CSV Data Should Never Leave Your Browser
- Additional Resources
- FAQ
This guide is for: Bookkeepers, accountants, AP/AR specialists, and finance operations teams who regularly import bank exports from Chase, Bank of America, Wells Fargo, Citi, and other major US banks into QuickBooks Online. If you are importing general accounting CSV files (not bank exports), see QuickBooks CSV Import Error: Fix Common Failure Modes instead.
Already know your bank? Jump to Quick Answer or Fast Fix.
| Error / Symptom | Root Cause | Fix |
|---|---|---|
| Continue button grayed out (no error) | Column headers don't match QB schema; extra columns present | Rename headers to Date/Description/Amount; remove extra columns |
| "Some info may be missing from your file" | Column count doesn't match 3-column or 4-column format | Remove extra columns; verify exactly 3 or 4 columns present |
| Deposits/Withdrawals columns rejected | Split amount format requires exact Credit/Debit header names | Rename Deposits → Credit, Withdrawals → Debit |
| Transactions imported with wrong amounts | Balance column in position 4 mapped as Amount field | Remove Balance column before import; verify column order |
| "Date format not recognized on row N" | Date column values don't match QB account regional setting | Convert dates to MM/DD/YYYY (US) or DD/MM/YYYY (UK/AU) |
| "Invalid amount format on row N" | Currency symbol or thousand separator in Amount column | Strip non-numeric characters from Amount, Credit, Debit columns |
| Import freezes or times out | File exceeds QB's ~350 KB / ~1,000 row practical import limit | Split into monthly batches using CSV Splitter |
| Column mapping preview shows wrong field assignments | Non-standard header names partially matched by QB wizard | Rename headers explicitly before import; don't rely on auto-mapping |
Why Bank Feed CSV Import Works Differently
QuickBooks Online offers two distinct import paths for bank transactions: the bank feed connection (direct bank sync) and manual CSV upload through the bank feed section. When a direct bank connection is unavailable or a bookkeeper needs to backfill historical transactions, the CSV upload path activates a column mapping wizard that differs substantially from the general CSV import wizard.
The bank feed CSV import wizard attempts to auto-map your columns to QuickBooks' required schema using partial header name matching. If it successfully maps all required columns, it advances to the preview screen. If it cannot resolve all required columns — because of unrecognized header names or extra columns disrupting the schema — it silently stops at the mapping step with the Continue button grayed out.
This behavior differs from general CSV import errors, which produce explicit error messages on specific rows. Bank feed column mapping failures are structural: the wizard fails before it reads any data rows, so no row-level error messages are generated. The only signal is the grayed-out Continue button.
Error 1: Column Header Name Mismatches
QuickBooks Online's bank feed column mapping wizard recognizes a specific set of header names for each required field. Headers outside this set do not auto-map, leaving the Continue button grayed out. The core problem is that every major US bank exports transactions with different default column names — and none of them match QuickBooks' required schema exactly.
The table below shows the exact column headers each major bank exports and the renamed headers required for QuickBooks import. These schemas were verified against current bank CSV export formats, May 2026.
| Bank | Exported Headers | Required QuickBooks Headers | Columns to Remove |
|---|---|---|---|
| Chase | Transaction Date, Post Date, Description, Category, Type, Amount, Memo | Date (from Transaction Date), Description, Amount | Post Date, Category, Type, Memo |
| Bank of America | Date, Description, Amount, Running Bal. | Date, Description, Amount | Running Bal. |
| Wells Fargo | Date, Description, Deposits, Withdrawals, RunningBal | Date, Description, Credit (from Deposits), Debit (from Withdrawals) | RunningBal |
| Citi | Date, Description, Debit, Credit | Date, Description, Credit, Debit | none — column order matters (see Error 3) |
❌ BROKEN: Chase export — Transaction Date and extra columns cause wizard failure
Transaction Date,Post Date,Description,Category,Type,Amount,Memo
01/15/2026,01/16/2026,VENDOR PAYMENT ACH,Services,Sale,-850.00,REF-20260115
Note: 7 columns; QB bank feed wizard cannot map "Transaction Date" → "Date"
and rejects the 7-column schema entirely
# FIXED: Chase export normalized for QuickBooks 3-column import
Date,Description,Amount
01/15/2026,VENDOR PAYMENT ACH,-850.00
Fixing in bulk: Use SplitForge Data Cleaner to rename headers and remove extra columns across all rows in one operation. The column rename function maps Transaction Date → Date and removes Post Date, Category, Type, and Memo columns without modifying the transaction data.
Error 2: Extra Columns Breaking the Mapping Wizard
QuickBooks Online's bank feed import accepts exactly two CSV layouts: a 3-column format (Date, Description, Amount) and a 4-column format (Date, Description, Credit, Debit). Any file with a column count other than 3 or 4 causes the mapping wizard to fail silently at the structure-validation step — before any header name matching is attempted.
Bank exports routinely include additional columns that serve reporting purposes but break QuickBooks' column count requirement. The most common extra columns:
- Balance / Running Bal. / RunningBal — account balance after each transaction; present in BofA, Wells Fargo, and most community bank exports
- Check or Slip # / Check # / Num — check number reference; present in QuickBooks Desktop exports and some credit union downloads
- Category / Type / Transaction Type — transaction classification; present in Chase exports and Mint/budgeting app exports
- Memo / Note — free-text reference field; present in Chase and some credit card exports
❌ BROKEN: Bank of America export — Balance column creates 4-column format that
QB reads as Credit/Debit split but "Running Bal." doesn't match
Date,Description,Amount,Running Bal.
01/15/2026,VENDOR PAYMENT,-850.00,4250.00
01/14/2026,PAYROLL DEPOSIT,3200.00,5100.00
Note: QB interprets column 4 as a "Debit" field in 4-column mode;
Balance values get imported as transaction amounts
# FIXED: Running Bal. column removed — clean 3-column format
Date,Description,Amount
01/15/2026,VENDOR PAYMENT,-850.00
01/14/2026,PAYROLL DEPOSIT,3200.00
The column count failure is more insidious than a header name mismatch. A 5-column file doesn't produce an error — it produces a wrong-values import where the fifth column's data ends up mapped to an unexpected field. Review the column mapping preview screen carefully before clicking Continue: verify each field assignment matches your data.
Error 3: Credit/Debit Split Format Requires Exact Header Names
Some banks separate transaction amounts into two columns: a deposits column and a withdrawals column. Wells Fargo uses Deposits and Withdrawals; some credit unions use Credits and Debits; Bank of America's older export format uses Withdrawal Amt. and Deposit Amt.. QuickBooks Online's 4-column format accepts this split, but the header names must be exactly Credit and Debit — not Deposits, Withdrawals, Credits, Debits, or any other variation.
❌ BROKEN: Wells Fargo split format — Deposits/Withdrawals headers not recognized
Date,Description,Deposits,Withdrawals,RunningBal
01/15/2026,VENDOR PAYMENT ACH,,850.00,4250.00
01/14/2026,PAYROLL DIRECT DEPOSIT,3200.00,,5100.00
Note: QB does not auto-map Deposits → Credit or Withdrawals → Debit
# FIXED: Renamed to QB 4-column schema; RunningBal removed
Date,Description,Credit,Debit
01/15/2026,VENDOR PAYMENT ACH,,850.00
01/14/2026,PAYROLL DIRECT DEPOSIT,3200.00,
Citi's standard CSV export uses the order Date, Description, Debit, Credit — the reverse of QuickBooks' expected Date, Description, Credit, Debit order. This is a column REORDER issue, not a header rename: the column names are already correct, but their positions need to be swapped before import. If you import a Citi file without reordering, transactions will appear with inverted signs (deposits posted as withdrawals and vice versa). Swap the Credit and Debit column positions in your CSV before importing. For how Xero handles the same split-format scenario differently, see Xero CSV import errors and fixes.
Fixing in bulk: Use SplitForge Data Cleaner to rename the Deposits and Withdrawals headers to Credit and Debit, and remove the RunningBal column — one operation across all rows.
Error 4: The Column Mapping Wizard's Silent Failure Behavior
QuickBooks Online's 2026 bank feed import UI introduced a column mapping preview screen that shows field assignments before you finalize the import. The wizard attempts to auto-map column headers using partial string matching: Transaction Date maps to Date, Payee maps to Description, Transaction Amount maps to Amount. When the auto-mapping succeeds, the assigned fields appear in the preview pane and the Continue button is active.
When auto-mapping fails — because a header is too different from any recognized pattern, or because extra columns disrupted the schema detection — the preview pane shows unassigned fields and the Continue button stays grayed out. No error message identifies which column caused the failure.
The diagnostic sequence when the Continue button is grayed out:
- Count your columns — if not exactly 3 or 4, column count is the issue; remove extras before checking headers
- Check the preview pane column assignments — any field showing "Not mapped" or blank assignment is the blocker
- Compare your first-row headers against QuickBooks' recognized header list:
Date,Transaction Date,Posted Date,Description,Payee,Memo,Amount,Transaction Amount,Credit,Debit - If your header doesn't appear in that list, rename it before re-importing
For the full diagnostic sequence covering all causes of a grayed-out Continue button — including BOM character corruption and encoding failures — see QuickBooks Continue button grayed out: complete fix guide.
Error 5: Date Format Errors That Survive Column Mapping
Date format failures in bank feed imports occur in two phases. The first phase is structural: wrong date column header names prevent the wizard from identifying the date field. This is covered in Error 1. The second phase is row-level: the wizard successfully maps a Date or Transaction Date column, but the date values inside that column don't match QuickBooks' regional format requirement.
QuickBooks Online US requires MM/DD/YYYY. QuickBooks Online UK and Australia require DD/MM/YYYY. The mapping wizard checks header names but not date value format — a file with correct headers but wrong date format passes the mapping step and fails at row validation with "Date format not recognized."
❌ BROKEN: Chase export date in YYYY-MM-DD format — mapping succeeds but row fails
Date,Description,Amount
2026-01-15,VENDOR PAYMENT ACH,-850.00
Note: Column header "Date" maps correctly; ISO 8601 date value fails row validation
Verbatim error: "Date format not recognized on row 2"
# FIXED: Date converted to MM/DD/YYYY for QuickBooks Online US
Date,Description,Amount
01/15/2026,VENDOR PAYMENT ACH,-850.00
A more dangerous variant: European bank exports with DD/MM/YYYY dates that pass both the mapping step and row validation in a QuickBooks US account — because 01/04/2026 is a valid MM/DD/YYYY date (January 4) even though the bank meant April 1. The import succeeds with no error, but all Q1 April transactions appear in January. For a full treatment of regional date format defaults and silent date misinterpretation, see Finance CSV data prep: complete guide.
Fixing in bulk: Use SplitForge Data Cleaner to convert date formats across your entire bank export in one operation. The date converter handles ISO 8601, European DD/MM/YYYY, and other formats without row-by-row editing.
⚖️ NOT LEGAL ADVICE. This article discusses technical architecture and publicly available regulatory guidance. It does not determine your organization's compliance obligations. Consult qualified legal counsel for compliance determinations.
Why Your Bank Feed CSV Data Should Never Leave Your Browser
Bank feed CSV files are not generic data files. A 90-day Chase transaction history contains your business account number, routing number, counterparty names, payment references, and exact transaction amounts — the combination that constitutes financial transaction records subject to Bank Secrecy Act recordkeeping requirements and, for EU-connected businesses, personal financial data under GDPR Article 4(1).
Most column mapping guides recommend cloud-based tools that require uploading the file before processing. RocketStatements stores uploaded files in cloud document folders. DocuClipper and EasyBankConvert process files on remote servers with standard SaaS retention windows of 30-90 days. For any business with EU vendors or customers, uploading a bank statement to a third-party cloud processor creates a GDPR Article 28 processor relationship — even when the underlying transaction involves a German vendor paying a US entity, the processing of that vendor's banking reference constitutes personal data processing.
SplitForge processes your bank feed CSV entirely in your browser via Web Worker threads. The Format Checker reads file bytes into browser tab memory — the same mechanism a text editor uses to open a file — and identifies column header issues, encoding problems, and column count errors without transmitting any data. The Data Cleaner applies header renames and column removals in the same isolated worker thread. No bytes leave your device.
You can verify this: open DevTools (F12), go to the Network tab, and process a bank export through SplitForge. You will see zero outbound POST requests carrying file data. SplitForge does not claim GDPR or PCI-DSS certification. The claim is architectural: no server transmission means no third-party processor relationship is created for your bank statement data.
For the full regulatory framing across QuickBooks, Xero, NetSuite, and bank export workflows, see our Finance CSV data prep complete guide.
Additional Resources
Official QuickBooks Documentation:
- Format CSV files in Excel to get bank transactions into QuickBooks — Official column schema and format requirements for bank transaction CSV imports
- Common errors importing bank transactions using CSV — Intuit's official error reference for CSV bank import failures
Technical Standards:
- RFC 4180: Common Format and MIME Type for CSV Files — IETF standard for CSV file structure; context for column count and header requirements
- ISO 8601: Date and Time Format — International date format standard; context for why bank exports use formats that differ from QuickBooks requirements
- Unicode BOM FAQ — What a BOM is and why it appears in CSV exports from bank portals
Browser Processing Reference:
- MDN Web Workers API — How browser-native file processing works and why it does not transmit data to any server