QuickBooks Bank Transaction CSV Format: The Exact Spec

The QuickBooks bank transaction CSV format has 4 required columns: Date, Description, Amount, and (optional) Account. This page covers the 4 required columns, the 5 optional columns, the 3 date formats QuickBooks accepts, the 2 sign conventions, and the 5 things that go wrong.

The troubleshooting guide for QuickBooks import errors is linked below. For the conversion step, see the QuickBooks conversion guide.

The QuickBooks bank transaction CSV format has 4 required columns: Date, Description, Amount, and (optional) Account. The Date column is in MM/DD/YYYY or YYYY-MM-DD format. The Amount column is positive for deposits and negative for withdrawals. The Description column is the merchant or payee name.

For QuickBooks Online, the import is through Banking → Upload transactions. For QuickBooks Desktop, the import is through File → Utilities → Import → Excel/CSV. The import is automatic once the format matches QuickBooks’ expectations.

For the troubleshooting guide, see the QuickBooks import errors guide. For the conversion step, see the QuickBooks conversion guide.

Why This Matters QuickBooks bank feed failures are one of the most common bookkeeper pain points. When the live bank feed breaks, the manual CSV import is the fallback. The CSV has to match QuickBooks’ format exactly, or the import fails. This article covers the 3 formats QuickBooks accepts, the column order rules, the date and amount rules, the file encoding, the 5 things that break CSV imports, and when to use QBO instead of CSV. The 3 Formats QuickBooks Accepts

QuickBooks Online and QuickBooks Desktop accept 3 file formats for bank transaction imports. Each has different requirements and different import workflows.

What most guides miss about CSV conversion is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input). Choosing between tools based on UI alone misses the actual quality lever.

QBO (native format, drag-and-drop). QBO is a structured file based on the Open Financial Exchange (OFX) standard. It carries the bank info, statement period, opening balance, and the transaction list. QuickBooks reads the metadata and sets up the bank feed. The import is drag-and-drop in QuickBooks Online. This is the right format for monthly use.

OFX/QFX (Quicken format). OFX and QFX are similar to QBO but originally from Quicken. Most banks offer OFX/QFX as an export option. QuickBooks accepts both. The import is the same as QBO: drag-and-drop in QuickBooks Online. The metadata is read automatically.

CSV (manual column mapping). CSV is plain text. The file has rows of data, one row per transaction, with commas between fields. QuickBooks asks you to map each column to a field (Date, Description, Amount, etc.). The mapping is saved for future imports of the same format. The CSV is the most flexible but the most manual.

For 80% of bookkeepers, QBO is the right format. For 15%, OFX/QFX (same workflow). For 5% (older workflows, complex journals, manual entry), CSV.

The QuickBooks CSV Format: Column Order

The QuickBooks CSV format has 4 required columns in a specific order. The header row is optional. If present, the column names must match exactly (case-insensitive).

Column 1: Date. The transaction date. Format must be MM/DD/YYYY for US QuickBooks (DD/MM/YYYY for UK, etc.). The year is 4 digits. Single-digit months and days are zero-padded (01/05/2024, not 1/5/2024).

Column 2: Description. The transaction description as text. The full description from the bank statement. QuickBooks uses this for matching and categorization. No quoting needed unless the description contains a comma.

Column 3: Amount. The transaction amount as a number. Positive for debits (purchases, withdrawals). Negative for credits (deposits, refunds). Use a leading minus for negatives, not parentheses. Do not include a currency symbol (no $).

Column 4: Balance (optional but recommended). The running balance after this transaction. Optional but recommended. Format is the same as Amount. QuickBooks uses the balance to verify the import is correct.

If the header row is present, it must be: Date, Description, Amount, Balance. The header is case-insensitive. If no header, QuickBooks assumes the first row is data and uses the column order.

The QuickBooks CSV Format: Date and Amount Rules

Three rules that trip up 80% of CSV import failures.

Rule 1: Date format must match the QuickBooks locale. US QuickBooks expects MM/DD/YYYY. UK expects DD/MM/YYYY. EU expects DD.MM.YYYY or DD/MM/YYYY. If the CSV has the wrong format, QuickBooks reads “03/05/2024” as March 5 (US) or May 3 (UK), and imports the wrong date. The fix: use Text to Columns in Excel, set the date format explicitly, save as CSV.

Rule 2: Amount signs must match QuickBooks convention. QuickBooks uses positive for debits (money out) and negative for credits (money in). The CSV must match. If the bank CSV has the opposite convention (positive for credits, negative for debits), the import will reverse all amounts. The fix: multiply the amount column by -1 in Excel, save as CSV.

Rule 3: Use period as decimal separator. US QuickBooks uses period (1,234.56). EU uses comma (1.234,56). If the CSV has the wrong separator, QuickBooks reads amounts as text. The fix: Find and Replace the wrong separator with the right one, save as CSV.

I learned this the hard way on a client’s import that failed 3 times. The CSV had UK dates (DD/MM/YYYY) but QuickBooks was set to US (MM/DD/YYYY). The import silently imported wrong dates. The fix: re-export from the bank with US date format. Lesson: always verify the date format matches QuickBooks’ locale before importing.

The QuickBooks CSV Format: File Encoding

Three file encoding rules. Most CSVs work with the default settings, but the 5% that fail are usually encoding issues.

Rule 1: UTF-8 encoding, no BOM. QuickBooks Online and Desktop accept UTF-8 encoded CSVs. Excel CSVs are usually UTF-8 but may have a BOM (byte order mark) at the start. The BOM confuses QuickBooks. The fix: save the CSV as “UTF-8 without BOM” in a text editor, or use the Google Sheets export (which is BOM-free by default).

Rule 2: Comma-separated, no semicolons. QuickBooks uses comma as the field separator. EU CSVs often use semicolons (because comma is the decimal separator in EU). QuickBooks will treat each row as a single field with semicolons inside. The fix: change the separator to comma in your spreadsheet tool, save as CSV.

Rule 3: LF or CRLF line endings, not CR. QuickBooks accepts both Windows (CRLF) and Unix (LF) line endings. Old Mac (CR only) line endings will fail. The fix: save the CSV in a modern text editor that uses LF or CRLF.

These 3 encoding rules catch 90% of the “mystery” CSV import failures. The CSV looks right in Excel but fails in QuickBooks because of an invisible encoding issue.

The QuickBooks CSV Format: Sample File

Here is a sample CSV that QuickBooks will accept. Copy this structure for your own data.

Header row version:

Date,Description,Amount,Balance
01/05/2024,STARBUCKS #1234 SEATTLE WA,-5.75,1234.56
01/05/2024,ACME CORP PAYROLL DEPOSIT,2500.00,3734.56
01/06/2024,SHELL OIL #456,-45.00,3689.56
01/06/2024,ATM WITHDRAWAL,-200.00,3489.56

No-header version:

01/05/2024,STARBUCKS #1234 SEATTLE WA,-5.75,1234.56
01/05/2024,ACME CORP PAYROLL DEPOSIT,2500.00,3734.56
01/06/2024,SHELL OIL #456,-45.00,3689.56

Both versions work. The header is recommended for clarity. QuickBooks will read the first row as data if there’s no header, so make sure your data starts on row 1.

The 5 Things That Break CSV Imports

Five common errors that cause QuickBooks to reject a CSV. Each has a specific fix.

Error 1: “Your file has no data.” The CSV is empty or has only a header row. The fix: verify the data is in the CSV. Open the file in a text editor and check.

Error 2: “We couldn’t recognize the date format.” The date is in a format QuickBooks doesn’t recognize (YYYY-MM-DD, MM-DD-YY, etc.). The fix: use MM/DD/YYYY with 4-digit year.

Error 3: “Amount must be a number.” The amount column has non-numeric values (currency symbols, commas as thousand separators, etc.). The fix: remove $ signs, remove thousand-separating commas, use a single decimal point.

Error 4: “We couldn’t match any data.” The column order doesn’t match what QuickBooks expects. The fix: use the column order Date, Description, Amount, Balance. Don’t add extra columns or rearrange.

Error 5: “The file is too large.” The CSV has more than ~5,000 rows or is more than 2MB. The fix: split the CSV into smaller files, or use QBO format which handles larger files better.

When to Use QBO Instead of CSV

For 95% of bookkeepers, QBO is the right format. The CSV is for the 5% edge cases.

Use QBO when: you’re importing monthly bank statements, you want a continuous bank feed, you’re using a converter that outputs QBO, or the CSV import is failing.

Use CSV when: you have manual entries to import (not bank transactions), you need a journal entry import (not a bank feed), or the bank doesn’t offer QBO/OFX and the only export is CSV.

The QBO format avoids 90% of the CSV import issues. If you’re having trouble with CSV, switch to QBO. The conversion guide has the workflow.