CSV to QuickBooks Online: Import CSV and Upload Bank Transactions to QBO

In QuickBooks Online, open Bank transactions. Depending on which navigation your account shows, that is either Transactions then Bank transactions, or All apps then Accounting then Bank transactions. Choose the account and select Upload from file. Pick your CSV, map the date, description, and amount columns, then review and import. If QuickBooks rejects the layout, convert the CSV to a .qbo file first and upload that instead, which removes the column-mapping step entirely.

QuickBooks Online accepts a CSV with either three columns (Date, Description, Amount) or four columns (Date, Description, Credit, Debit), in English, under 350 KB. Dates must be one consistent format and amounts plain numbers with no dollar signs or commas. Anything outside that fails, which is why a converted .qbo file imports far more reliably.

Yes. QuickBooks Online imports CSV bank and credit card transactions through Upload from file, and it also imports .qbo Web Connect files. The CSV route works when your file already matches the strict format. The .qbo route works with any source file, because the converter reformats the data into the exact structure QuickBooks expects.

The usual causes are a wrong column count, mixed or non-US date formats, dollar signs or commas inside amount cells, blank rows, and files over 350 KB. QuickBooks reads the file row by row and stops at the first line it cannot parse, so one bad cell blocks the whole upload. Converting to .qbo removes these failure points before you import.

Download the transactions from your bank as a CSV, then either upload that CSV under All apps, Accounting, Bank transactions, then Link account and Upload from file (older accounts still reach the same screen via Transactions, Bank transactions), or convert it to a .qbo first and upload the .qbo. The .qbo imports as a Web Connect bank feed, so QuickBooks routes every transaction straight into the review queue for categorizing and matching.

A CSV is a plain spreadsheet of rows and columns with no fixed structure, so two banks export wildly different CSVs. A .qbo file is a QuickBooks Web Connect file in OFX format with a defined layout QuickBooks reads natively. Converting CSV to QBO turns an unpredictable spreadsheet into the precise file QuickBooks was built to accept.

Yes. Credit card CSVs convert the same way as bank CSVs. Export the activity from your card account, convert it to a .qbo, and import it into the matching credit card account in QuickBooks Online; the credit card CSV to QuickBooks guide covers the sign convention in full. Charges need to import as negative and payments as positive, which the converter sets correctly when it builds the .qbo file.

A CSV upload is capped at 350 KB, roughly a thousand rows depending on description length, so long histories often have to be split into several files. A .qbo import is not held to that 350 KB CSV limit, so converting lets you bring a full year of transactions into QuickBooks in a single file.

QuickBooks Desktop will not take a raw CSV for bank transactions, but it imports .qbo Web Connect files directly. Convert your CSV to a .qbo, then in Desktop go to File, Utilities, Import, Web Connect Files; the CSV to QuickBooks Desktop guide walks through it. The same converted file works for both QuickBooks Online and Desktop, so you only convert once. If you are weighing the two editions, see QuickBooks Online vs Desktop CSV import for how each one handles the file.

Upload your CSV or Excel export in the converter above. The tool detects the date, description, and amount columns, normalizes the dates to MM/DD/YYYY, strips currency symbols and commas from the amounts, and shows the parsed row count and every row on screen. Download the .qbo and import it from the Bank transactions screen, which sits under All apps then Accounting on newer QuickBooks Online layouts and under Transactions on older ones, using Upload from file. The whole pass takes under a minute, with no mapping wizard to fight.

A manual import means hand-fixing your file to every QuickBooks rule: exactly three or four columns, one consistent date format, amounts with no dollar signs or thousands commas, expenses as negatives, no blank rows, and no commas inside descriptions. Miss one and the upload fails. Converting to .qbo applies all of that for you, so the file QuickBooks receives is already correct.

Bookkeepers and accountants doing catch-up work rely on it most, because clients hand over a year of bank and card CSVs that never match QuickBooks formatting. Small business owners use it to import accounts QuickBooks cannot connect by bank feed, and anyone cleaning up a bad import uses it to replace transactions that came in wrong the first time.

A live bank feed in QuickBooks Online usually pulls only the last 90 days, and it skips closed accounts and the gap before you connected. Your bank still lets you download those older months as a CSV. Convert each CSV to a .qbo and you can backfill any period into QuickBooks, well beyond what the feed alone would ever import.

You have three ways to import bank transactions into QuickBooks Online: connect the bank feed, upload a raw CSV and map the columns by hand, or upload a Web Connect (.qbo) file. The .qbo route is the most reliable of the three, because the file already carries the structure QuickBooks expects, so there is no mapping screen, no date format guessing, and no file size ceiling. Convert your CSV above and upload the result under Bank transactions.

Yes. QuickBooks Online never requires a live bank connection to receive transactions. You can import bank transactions from a file alone, which is what accountants do for clients who will not share banking credentials, and what everyone ends up doing when a feed breaks. If your feed has stopped delivering, see QuickBooks bank feed not working for the causes and the file based fix.