How to Import a CSV into QuickBooks Online (2026, with column rules)

Importing a CSV into QuickBooks Online is not difficult. Getting your bank's CSV into the shape QuickBooks accepts is where the afternoon goes. The rules are stricter than most people expect, and the error messages do not say which rule you broke.

The two layouts QuickBooks accepts

A CSV of bank transactions has to arrive in one of two shapes.

Three columns: date, description, amount — one signed amount column, where money out is negative and money in is positive.

Four columns: date, description, credit, debit — two amount columns, each holding positive numbers, with the direction implied by which column the number is in.

That is the whole vocabulary. A running balance column, a category, a transaction type, a check number, a card number, a status: all of those have to go before the file will import cleanly. The import wizard lets you tell QuickBooks which column is which, so the order is flexible, but the count and the meaning are not.

The header row matters

QuickBooks expects the first row to name the columns, and it expects exactly one header row. Bank exports that lead with a summary block — Bank of America is the usual example, with a beginning balance and totals above the real header — will import that block as a transaction, or fail outright. Delete everything above the header row before uploading.

The limits nobody mentions until they bite

• File size. QuickBooks Online documents a 350 KB ceiling for a CSV upload. A large statement with long payee names gets there faster than you would think.
• Transactions per upload. Intuit caps a manual upload at 1,000 lines, whether the file is CSV or .qbo. Split larger files rather than hoping.
• One account per file. Each import goes into one QuickBooks account. A CSV covering two cards has to be split first.
• Dates must be consistent. One stray Sep 3, 2026 in a file of 09/03/2026 is enough to stop the import.

Cleaning a bank CSV by hand

If you are doing this manually, the order of operations that wastes the least time is:

1. Open the file and delete every row above the header row, plus any total or balance rows at the bottom.
2. Delete every column except date, description and amount — or date, description, credit and debit.
3. Check the amount column for currency symbols, thousands separators and parenthesised negatives like (45.00). Convert those to plain -45.00.
4. Make sure the date column is one consistent format, and remember which one it is: the wizard asks.
5. Save as CSV, not as a workbook.

Then in QuickBooks Online: Transactions, Bank transactions, the dropdown next to Link account, then Upload from file. Pick the file, pick the account, map the columns, and review what the preview shows before confirming.

Why a .qbo file is usually less work

A Web Connect file sidesteps all of the above. It carries its own column definitions, so there is no mapping screen, no header row to fix and no 350 KB limit — and because it is the same format a bank feed delivers, QuickBooks treats it identically once imported.

That is what the converter on this site produces: drop the bank's CSV in, get a .qbo out, with the summary rows, split debit and credit columns and sign conventions already handled for the major banks. It runs in your browser, so the statement is never uploaded anywhere. There are per-bank walkthroughs for Chase, Bank of America and Wells Fargo, among others.

After the import

Imported transactions land in the For review tab. Nothing has hit your books yet — they are candidates. Categorise them, match them against invoices and bills you have already recorded, and only then accept. If you imported the wrong file, the whole batch can be undone from the uploaded-files history, which is much safer than deleting transactions one at a time.

The 90-day question

A newly connected bank feed typically brings in about 90 days of history, and no amount of clicking extends it. An uploaded file has no such limit: if you can export it, you can import it. Catching up on a year of bookkeeping is therefore a file job, not a bank feed job — which is the main reason CSV and .qbo imports still matter in 2026.