How to import a bank statement into QuickBooks Online

When you need a manual import

Bank feeds cover the easy case: transactions from the last 90 days or so, flowing into a connected account. Manual imports exist for everything else. A new client hands you a year of PDF statements. An account was closed and the feed is gone. A feed broke in March and nobody noticed until September. In each case the statement PDF is the only record you have, and QuickBooks Online will not read a PDF. You need the transactions as a CSV file shaped exactly the way QuickBooks expects.

That last part is where imports fail. QuickBooks is strict about column names, date formats, and file size, and its error messages rarely say which row broke. The sections below cover the exact rules, because most import problems are one of five known traps.

Convert a statement now

The two CSV shapes QuickBooks Online accepts

QuickBooks Online accepts exactly two column layouts. The 3-column format uses the header row Date,Description,Amount where Amount is one signed number: positive for money in, negative for money out. The 4-column format uses Date,Description,Credit,Debit where money in goes in the Credit column and money out goes in the Debit column, both as positive numbers.

The headers must match those names. Extra columns, a running balance column, a reference number, or reordered headers make QuickBooks treat the data as missing. Between the two, the 3-column shape is the safer choice: with separate Credit and Debit columns, imports have been observed reading one column and ignoring the other, so every debit arrives as zero. This converter exports 3-column by default and offers 4-column for the cases that want it.

The five traps that break QuickBooks CSV imports

First, dates. US companies need MM/DD/YYYY, and every row must use the same format. QuickBooks reads row by row and fails on the first date it cannot parse, so one ISO-formatted date or a stray day-of-week string stops the file. Second, amounts. Currency symbols and thousands separators must be stripped: 1,234.56 with a comma can be read as two fields, and a dollar sign fails the number parse.

Third, size. Uploads are capped at 350 KB, which is roughly 1,000 to 1,500 transactions. Bigger files must be split by date range. Fourth, categories. QuickBooks ignores any category or class column in a CSV import; every transaction lands in the For Review tab regardless, waiting for your bank rules. Fifth, payees. A Payee column imports as part of the description, not as a Payee record, so plan to assign payees inside QuickBooks after import.

Step by step: from PDF to posted transactions

Convert the statement first. Drop the PDF into the converter on this page: it reads the transactions in your browser, checks them against the balances printed on the statement, and builds a QuickBooks-ready 3-column CSV. If the file is large, the export splits automatically into date-ranged files that each fit under the 350 KB cap.

Then import. In QuickBooks Online, go to Transactions, then Bank transactions. Choose the account, open the dropdown next to Link account, and pick Upload from file. Select the CSV, map the three columns when prompted, confirm the date format, and import. The transactions appear in For Review, where your existing bank rules and categorization workflow take over. Import files in date order, oldest first, so running balances in QuickBooks stay meaningful as you reconcile each month.

Overlapping statements create duplicates

CSV imports carry no transaction IDs, so QuickBooks cannot recognize that a transaction in this file is the same one it imported from last month’s file. If two statement periods overlap, the overlap imports twice. The fix is prevention: trim the export to the statement period, or check the last posted date in QuickBooks before importing the next file.

This is a structural limit of the CSV format, not of any one converter. QuickBooks deduplicates natively only through Web Connect files with bank transaction IDs, which is a different import path with its own constraints.

Why the converter checks balances before you import

A misread digit in an import is worse than no import: it posts, it looks plausible, and it surfaces weeks later as a reconciliation that will not balance. So this converter refuses to be trusted blindly. It re-adds every transaction against the balances printed on the statement itself. When each row chains to the printed running balance, the export is stamped Verified row-by-row. When only the opening and closing balances are printed, it verifies the statement total. When the math does not hold, it shows you exactly which rows disagree, with both numbers, before you export.

The stamp is a verification aid, not a guarantee, and the arithmetic all happens in your browser: the statement is never uploaded anywhere.

Frequently asked questions

What CSV format does QuickBooks Online accept for bank transactions?

Two layouts: 3-column (Date, Description, Amount with one signed amount) or 4-column (Date, Description, Credit, Debit). Headers must match exactly, dates must be consistent, and files must stay under 350 KB.

Why did my QuickBooks import fail on the date?

QuickBooks fails on the first row whose date it cannot parse. Check that every row uses the same MM/DD/YYYY format for US companies and that no row carries day names or ISO dates.

Can I import categories or classes with the CSV?

No. QuickBooks Online ignores category and class columns in CSV imports. Every transaction lands in For Review, where bank rules can categorize it.

How many transactions can one import hold?

The limit is 350 KB per file, which is roughly 1,000 to 1,500 transactions. This converter splits bigger exports into date-ranged files automatically.

Will importing the same period twice create duplicates?

Yes. CSV rows carry no IDs, so QuickBooks cannot detect repeats. Keep statement periods from overlapping, or check the last imported date before adding the next file.