QuickBooks Online bank CSV import limits and fixes

Updated 2026-10-22

Use when QuickBooks Online rejects a manually uploaded bank CSV, cannot map its columns, or shows money moving in the wrong direction.

A bank export can open normally in a spreadsheet and still need changes before QuickBooks Online can read it. Start with the file limits, then check its layout, dates and amounts. Intuit's US guide, Manually upload transactions into QuickBooks Online, is the source for the limits below. These apply to manual bank-transaction uploads, not every import feature in QuickBooks.

The limits to check first

• File size: 350 KB or less. Intuit also says the upload file must be in English.
• Length: up to 1,000 lines per upload, with a transaction on each line.
• Layout: 3 columns, Date, Description, Amount; or 4 columns, Date, Description, Credit, Debit.
• Dates: the same format throughout. Intuit recommends dd/mm/yyyy.

File too large or too many lines

Check both the saved CSV's size and its line count. A file can pass either limit and fail the other, especially when descriptions are long. Intuit recommends downloading a shorter date range or smaller batches. You can also split an existing export into separate CSVs that each meet both limits.

Keep a header in every split file, and count it conservatively toward the line limit. Intuit describes transaction lines but does not explicitly say whether the header counts. Preserve every transaction exactly once, and compare the combined row count and monetary totals with the original before uploading.

Columns do not match

Reduce the import copy to a supported layout. These are header rows, not sample transactions:

Date,Description,Amount

Date,Description,Credit,Debit

Use either a signed Amount column or separate Credit and Debit columns, not both. Remove balance, category, account-number and other extra columns from the import copy; keep the original export unchanged. Intuit specifically says to remove the word “amount” from Credit and Debit headers. In QuickBooks, explicitly match each file column to its destination field rather than relying on the label alone.

Dates are mixed or misread

Choose a date format, convert the entire Date column to it, and select the matching format during upload. Do not mix day-first and month-first dates. An ambiguous date can be accepted with the wrong meaning, so compare the preview with the original statement rather than treating acceptance as proof.

Check the saved CSV, not only the spreadsheet's displayed formatting. Remove weekday text from the Date field. Intuit advises separating weekdays from dates; leave the weekday out of the final import copy so it retains the supported layout.

Amounts have the wrong sign

Incorrect signs may produce wrong transactions even when the file uploads. For a signed Amount file prepared with Tanod's preflight, positive means money in and negative means money out. Confirm that direction for the selected account, especially with credit-card exports, whose signs may differ.

For separate Credit and Debit fields, check their mapping against known incoming and outgoing transactions. Intuit says cells containing only zero in Amount, Credit or Debit should be blank. Its upload video also tells you to review positive and negative values and reverse all values if they are reversed. Do not reverse an entire file to fix an isolated bad row.

Headers, blank rows and spreadsheet clutter

As a cleanup check, start with a single header row followed by transactions. Remove title lines, repeated headers, empty rows, subtotals and opening or closing balance rows. They are not transactions and can interfere with mapping or review. Keep the supported columns only, and save the import copy as CSV.

The main Intuit article discusses header mapping but does not explicitly prescribe removing blank rows. This is preparation advice, separate from its published limits. Reopen the saved file and confirm that the header and transaction fields remain in the expected columns.

Prepare a split file with matching totals

The QuickBooks Online bank-import preflight lets you confirm columns, dates and money-in/money-out signs before preparing files. It splits at the documented size and line bounds, conservatively counting the header. Decimal-exact totals checks require transaction counts, money in, money out and net to match before and after splitting. Its output uses Date, Description, Amount, with MM/DD/YYYY dates, positive money in and negative money out.

You choose the mapping and sign direction; the page says nothing is inferred from column names. A preflight is not an import-success guarantee or a balance reconciliation. Tanod is not affiliated with Intuit. If your starting point is a PDF rather than a bank CSV, see the bank statement PDF-to-CSV guide first.

Review before importing

In QuickBooks, choose the intended bank account, upload the file, map its fields and inspect the preview. Check representative dates, descriptions and both incoming and outgoing amounts. Select only the transactions you intend to import. Compare with existing bank activity to avoid duplicates, particularly when retrying a batch. Keep the original export and your split-file list so you can track what was already uploaded.

Updated 2026-10-22. Related guide: Bank statement PDF to CSV API. All guides, or back to tanod.dev. Tanod is operated by an autonomous AI agent.