How to Manually Import Bank Transactions Into QuickBooks Online

Short answer: In QuickBooks Online, open Transactions, then Bank transactions, select the account, and use the upload option to add a file. QuickBooks Online accepts a .qbo (Web Connect) file, which imports with no setup, or a CSV, which makes you map the date, description and amount columns by hand and enforces a file size limit that long exports exceed. If you have a CSV, converting it to .qbo first removes the mapping step, the size cap, and most of the errors people hit on this screen.

Last updated July 2026.

Manual imports have a reputation as the sad fallback for when the bank feed breaks. In practice a lot of people import on purpose. Bookkeepers doing catch-up work need eleven months of history that no feed will ever hand them. Anyone banking with a fintech has no Desktop feed to fall back on. And plenty of business owners simply do not want Intuit holding a live session with their bank login. Whatever put you here, the mechanics are the same.

Where the upload actually lives

Go to Transactions in the left menu, then Bank transactions. Pick the account tile at the top for the account you are importing into, then find the upload option (it sits behind the Link account dropdown, as Upload from file). If the account has never been connected, QuickBooks walks you through creating or choosing the register the transactions belong to before it will take the file.

That last part matters more than it looks. Every transaction in the file lands in one register. If you export a CSV that mixes two accounts, or you point the upload at the wrong account, you will spend more time undoing it than the import saved you.

The CSV route, and what it costs you

QuickBooks Online will take a CSV, but on its terms. It expects either a three column layout (date, description, amount, with negatives for money out) or a four column layout that splits debits and credits into separate columns. You then map your bank's headers onto those fields, and QuickBooks previews what it thinks it read.

The failure modes are boringly consistent. Dates in the wrong order, because your bank writes 03/04/2026 and QuickBooks reads it as the fourth of March. Amounts that carry a dollar sign or a thousands separator, which QuickBooks reads as text. A running balance column that gets mapped to amount by accident, so every row posts the wrong number. And a file size ceiling that a full year of a busy checking account walks straight through, forcing you to slice the export into chunks and import them one at a time.

You can fight all of that in a spreadsheet. Clean the dates, strip the symbols, delete the balance column, split the file. Many people do, once, and then look for a better way.

The .qbo route

A Web Connect (.qbo) file is what QuickBooks was designed to eat. It carries the dates in an unambiguous format, the amounts already signed, and a unique transaction ID for every line, which is what lets QuickBooks flag likely duplicates instead of posting them twice. There is no mapping screen because there is nothing to map, and the file size problem goes away.

To get one from a CSV, upload the bank's export to the CSV to QBO converter, confirm which columns hold the date, description and amount, and download the .qbo. Then upload that file on the same QuickBooks Online screen you would have used for the CSV. It is the same import path, minus the parts that break. If your bank only hands you a statement as a PDF rather than a data export, turn the PDF statement into a clean spreadsheet first, then convert that.

Getting the date range right

Before you export anything, open the register and find the date of the last transaction that actually posted. Export from the day after that through yesterday. That one habit prevents nearly every duplicate.

If the feed delivered patchy results, some days in, some days missing, do not import a file covering the whole mess. Import only the ranges that are genuinely empty, and review before you accept. QuickBooks does compare incoming transactions against what is already posted and holds the likely duplicates for you, but it is matching on the data in the file, and it is easier to give it a clean range than to sort out an overlap afterwards.

After the upload

Imported transactions do not go straight into your books. They land in the For review tab, exactly like feed transactions, where you categorize them, match them against invoices and bills already recorded, and accept them into the register. Bank rules apply to imported transactions too, so if you have rules set up for this account, they will do their usual work.

Then reconcile. Pick a statement, enter the ending balance and date, and tick off what cleared. If the difference is zero, the import was complete and correct, and you can stop worrying about it. If it is not, the discrepancy is almost always a duplicated line, a missing day at the edge of your date range, or an amount that came in with the wrong sign.

Can you do this in QuickBooks Desktop?

You can import, but not from a CSV. QuickBooks Desktop's Bank Feeds importer reads .qbo, .qfx and .ofx files only, and has no CSV bank import at all. Advice written for QuickBooks Online sends Desktop users chasing an upload button that does not exist. In Desktop the path is File, Utilities, Import, Web Connect Files, and the file has to be a .qbo. See CSV to QuickBooks Desktop for the full walkthrough, and QuickBooks file extensions explained if you want to know which format does what.

When manual import is the right answer, not the backup plan

Catch-up bookkeeping is the obvious case: a client shows up in March with nothing recorded since last spring, and no bank feed will ever reach back that far. Fintech accounts are another, since Mercury, Brex, Ramp, Relay, Novo and Bluevine publish no Direct Connect service at all. And with Intuit retiring Direct Connect on October 30, 2026, a lot of Desktop users who have relied on automatic downloads for years are about to become manual importers whether they planned on it or not.

If your feed is the reason you are here, the fuller diagnosis lives in QuickBooks bank feed not working. If you just want the transactions in, use the converter, upload the file, and get on with the close. The money page for this workflow is CSV to QuickBooks Online.