Download QBO File From Bank: How to Get a QBO File for QuickBooks Online and Desktop

Sign in to your bank's website on a desktop browser, open the specific account, and switch to the transaction activity or statements view. Find the Download, Export or Save button, choose your date range, and select QuickBooks (.QBO) or Web Connect from the file type list. Save the file, then import it in QuickBooks.

1. Open the account whose transactions you need. QBO files are per account, so a checking account and a credit card are two separate downloads.
2. Set the date range before you pick the format. Some banks grey out .QBO for ranges that cross a statement boundary.
3. Choose QuickBooks, QuickBooks Web Connect or .QBO. Do not pick Quicken (.QFX), which is a different product's file even though the insides look almost identical.
4. Save the file somewhere you can find it. Do not open it in Excel or a text editor and re-save, which corrupts the OFX header.
5. Import it into QuickBooks and assign it to the matching account.

Sign in at bankofamerica.com, select the account, then choose Download transactions from the account activity page. Pick your date range and select QuickBooks as the file type, which produces a .qbo. Bank of America splits this by account, so repeat it for each checking, savings and credit card account you keep in QuickBooks.

If the QuickBooks option is missing on a particular account, it is usually a business account served by a different online banking platform. Download the CSV instead and import that, or pull the same period from your statements section. The one thing not to do is rename a .csv to .qbo, which produces an import error rather than a working file.

Sign in at chase.com, click the account to open its activity view, and use the download icon near the top right of the transaction list. Chase offers Spreadsheet (CSV), QFX for Quicken and QBO for QuickBooks. Choose QBO. Chase caps the activity export at roughly the last 24 months and about 1,000 rows per file.

That row cap matters for a busy business checking account. If a year of activity exceeds it, download in quarters and import four smaller files rather than fighting a truncated export. QuickBooks does not mind several files covering consecutive periods, and it will flag any transaction that arrives twice.

Most large US banks give you at least 90 days of downloadable activity, and many give 12 to 24 months. Anything older is normally available only as a PDF statement, if at all. This is the single biggest reason catch-up bookkeeping stalls, because the transactions you need for last year are usually just past the edge of the export window.

Two things help. First, download and archive the .qbo files as you go, even for accounts you are not reconciling yet, so the history exists when you need it. Second, if the period you need has already fallen off the bank's site and you still have the records in Quicken, export those accounts to QIF and convert them, which is often a longer history than the bank will hand back.

You do not open a .qbo the way you open a document. You import it. In QuickBooks Online, go to Transactions, then Bank transactions, then Upload from file, and pick the .qbo. In QuickBooks Desktop, go to Banking, Bank Feeds, Import Web Connect Files. In both cases QuickBooks asks which account the transactions belong to.

After the import, the transactions land in the review queue rather than straight into your register. That is intentional. You accept, categorize or match each one against what is already recorded, and only then do they post. If you double-click a .qbo from your downloads folder and QuickBooks Desktop opens with a prompt, that is the same import flow started a different way.

Yes. QuickBooks Online rejects an upload over 350 KB, which usually works out to a few thousand transactions. QuickBooks Desktop is more forgiving but still slows badly on very large Web Connect files. If you hit the limit, split the date range and import the pieces in order, oldest first, so the running balance stays sensible.

Because .QBO carries a Financial Institution ID that Intuit issues, and maintaining it is a paid, ongoing arrangement between the bank and Intuit. Smaller banks and credit unions increasingly decide it is not worth it and offer CSV or QFX only. The bank has not broken anything; it has stopped paying for that specific format.

The practical consequence is that you now have a file QuickBooks will not read directly, and you have to bridge it. Which file you were left with decides how. A CSV imports into QuickBooks Online through its own three-column mapping flow. A QFX is a Quicken file and QuickBooks will refuse it. A QIF is refused by every version of QuickBooks, Online and Desktop alike.

Convert it. QuickBooks has never imported QIF in any version, so a .qif has to become a .qbo before QuickBooks will touch it. Drop the file into the converter at the top of this page and it returns a balanced Web Connect file with a valid Financial Institution ID, correct account type and the splits and signs already resolved.

This is the common ending for two different situations. One is a bank or credit union whose only machine-readable export is QIF. The other, and the more frequent one, is a Quicken file holding years of history that predates whatever the bank still has online. Either way the route is the same: export to QIF, run it through the QIF to QBO converter, import the .qbo. If you need the same data in a spreadsheet for a client workpaper, the QIF to Excel converter writes the parsed rows out instead.

Use the live feed for the current period and downloaded QBO files for history. A feed keeps itself current with no effort but typically reaches back only about 90 days when you first connect it, so it cannot build the prior year. Web Connect files have no such limit and are the standard way to fill a gap.

Most bookkeeping engagements end up running both at once, which surprises people who expect to choose one. The difference between the connection types, and why Direct Connect is a QuickBooks Desktop feature that Online users never see, is covered in Direct Connect versus Web Connect.

The four usual causes are a file edited and re-saved in Excel, a .qfx or .csv renamed to .qbo, an account mismatch where you pointed the import at the wrong QuickBooks account, and an expired or unrecognized Financial Institution ID in the file's OFX header. The first three you fix by starting over with a clean download.