Bank of America CSV to QBO Converter: Convert CSV to QuickBooks

Sign in to Bank of America Online Banking, open the account, and choose Download. Pick the Comma Separated Values (CSV) format and a date range, then save the file. Upload that CSV to the converter at the top of this page. It detects the date, description, and amount columns, checks the parsed total against your file, and gives you a .qbo to import into QuickBooks Online or Desktop.

In Bank of America Online Banking, select the account and open the Activity or Statements and Documents view. Use the Download link above the transaction list, choose Comma Separated Values (CSV) as the file type, set the date range you need, and download. Online activity typically reaches about 18 months of history, so for older transactions you may need to pull a few date ranges and convert each one.

No, QuickBooks Desktop cannot import bank transactions from a raw CSV file. Desktop only imports a Web Connect .qbo through Banking, then Bank Feeds, then Import Web Connect Files. That is why converting your Bank of America CSV to a .qbo first is the reliable route for Desktop users, since it produces the one file format Desktop actually accepts.

Bank of America discontinued OFX access on September 30, 2025, citing fraud, which ended both Direct Connect and the direct Web Connect .qbo download for QuickBooks and Quicken. That is why accounts stopped updating and the .qbo download vanished from the site. Converting the free BofA CSV instead rebuilds a clean OFX 1.02 .qbo with correct Web Connect headers, so QuickBooks reads every transaction as a standard bank feed without any live connection. The full background is in our guide on Bank of America discontinuing QuickBooks Direct Connect.

Bank of America charges a monthly fee for Web Connect direct .qbo and QuickBooks integration on business accounts, but the plain CSV export is free. Downloading the free CSV and converting it here gives you the same import-ready .qbo without the subscription, and it works the same way for QuickBooks Online and QuickBooks Desktop.

QuickBooks Online accepts a CSV with three columns (Date, Description, Amount) or four columns (Date, Description, Credit, Debit), in English, under 350 KB, with one consistent date format and plain numbers. Bank of America exports rarely match that exactly. The converter reads the BofA layout as-is and outputs a .qbo, so you never have to reshape the columns by hand.

QuickBooks caps a single upload at 350 KB, which is roughly 1,000 transactions, so large Bank of America exports can fail when uploaded as a CSV. Converting to a .qbo and, where needed, splitting by month keeps each file inside that limit. The converter checks every batch against your file total so nothing is dropped when you split a long BofA history.

Yes. Bank of America Business Advantage and consumer credit card activity downloads as a CSV the same way checking activity does, and the converter handles card exports, including split debit and credit columns. You get a .qbo that imports into the matching QuickBooks credit card account, so charges and payments land in the right register.

Yes, and the accuracy check is the point. Before the .qbo downloads, the converter adds up every transaction it parsed and compares that to the total in your Bank of America CSV. If a row is missing or misread, you see it in the preview instead of finding it during reconciliation. Working from a different bank? Use the CSV to QuickBooks Online converter for any account, turn a spreadsheet into a .qbo with the Excel to QBO converter, handle a stack of statements with the bulk CSV to QBO converter, compare the best CSV to QBO converters on price, read the step-by-step Bank of America CSV to QuickBooks guide, try the Chase CSV to QBO converter for a Chase account or the PNC CSV to QBO converter for a PNC account, or follow how to import the .qbo file into QuickBooks once it is built.

Once the converter returns your file, the import path depends on which QuickBooks you run. In QuickBooks Online the upload sits under All apps, then Accounting, then Bank transactions, where you choose Link account and then Upload from file. Older accounts still show the same screen as Transactions, then Bank transactions, so use whichever navigation your company file presents. In QuickBooks Desktop the file goes through Banking, then Bank Feeds, then Import Web Connect File.

QuickBooks reads the account and date range from inside the file, so you point it at the matching account in your chart of accounts and it lands the transactions in the review queue rather than posting them straight to the ledger. Nothing hits your books until you accept each row, which is exactly the safety net a raw CSV paste does not give you.

No. Every transaction inside a .qbo file carries a FITID, a transaction identifier that is unique within the account and never reused. QuickBooks keeps a record of the FITIDs it has already accepted for that account and silently skips any it recognizes, so re importing a file you already loaded adds nothing.

QuickBooks remembers those identifiers even after you delete the transaction, which occasionally confuses people who delete a batch and try to reload it. A plain CSV has no such identifier, so nothing stops a CSV from loading the same $86.40 charge twice. That difference is the practical reason to convert before importing rather than pasting a spreadsheet.

Use MM/DD/YYYY for a United States QuickBooks company file. The Intuit help article that surfaces most often for CSV formatting is the global edition, which recommends DD/MM/YYYY. Follow it in a US file and every transaction dated the 1st through the 12th of a month silently posts into the wrong month. Nothing errors, the totals still foot, and the mistake only shows up when a reconciliation refuses to clear.

Watch what the spreadsheet does to the file as well. Two digit years from 00 to 29 resolve to 2000 through 2029 and 30 to 99 resolve to 1930 through 1999. Windows Excel defaults to the 1900 date system while Mac defaults to 1904, so a workbook opened on both platforms shifts every date by four years and a day. Opening the CSV in Excel to look at it is enough to introduce that.

Split it by period and convert each piece separately. QuickBooks caps a single upload at 350 KB, and that ceiling applies to .qbo, .qfx and .ofx files as well as to CSV, so a long history has to arrive in several files whatever format you use. Month by month or quarter by quarter both work, and the FITID protection means overlapping ranges will not double post if you misjudge a boundary.

This is also the route around a limitation of live bank feeds. A newly connected feed commonly pulls only about ninety days of history, which is why a business setting up QuickBooks mid year finds it cannot reach back to January. Downloaded CSV activity is not held to that window, so converting older exports is usually the only way to get a full year in without hand keying it.

Reconcile the first full period after the import against the paper or PDF statement rather than against the screen you downloaded from. Statement periods and calendar months rarely line up at Bank of America, and reconciling to the wrong end date is the most common reason a first reconciliation refuses to clear.

When the difference will not resolve, three patterns explain most of them. A difference that divides evenly by nine is transposed digits somewhere. A difference exactly equal to twice a transaction is a sign flip, which shows up constantly on credit card accounts because money in and money out reverse meaning there. A difference matching one transaction exactly is a row that either failed to convert or got accepted twice.