Chase Bank Statement to QuickBooks: Import Chase Transactions to QBO

Yes, Chase connects to QuickBooks Online through bank feeds, and many Chase business products also support direct connection. The catch is history: a new bank-feed connection usually brings in only the last 90 days or so of transactions. Anything older, plus accounts you have closed or never connected, will not arrive through the feed.

Sign in at chase.com, open the account, and go to Statements and documents (on the Chase mobile app it is under the account's menu). Chase lists monthly statements as PDFs going back several years, and you download whichever months you need. Chase also offers a Download account activity option in CSV, QFX and QBO, capped at roughly the last 24 months and about 1,000 rows per file.

To import a file into QuickBooks Online, go to Transactions, then Bank transactions, then Upload from file, and choose the file. In QuickBooks Desktop the path is File, Utilities, Import, Web Connect Files. The file can come from three places: a .qbo or .qfx download from Chase online banking if it offers one, a QIF export from Quicken converted with the tool above, or a CSV you map by hand. QuickBooks Online does not accept QIF in any version, which is the step most people miss; the QIF to QuickBooks Online page walks through that conversion, and QIF to QuickBooks Desktop covers the Web Connect route.

In order of least work: a .qbo Web Connect file if it is offered, because QuickBooks reads it with no column mapping and it carries a unique ID on every transaction, so repeat imports are caught. Then .qfx or .ofx, which behave the same way. Then a QIF export from Quicken, converted to .qbo first. CSV last, because it has no transaction IDs and you map the columns yourself on every upload.

Chase exports transactions to QuickBooks two ways: a live bank-feed connection for ongoing activity, and an activity download for recent transactions. Chase offers CSV, QFX and QBO downloads for the recent window, and our guide to how to download a QBO file from your bank covers exactly where Chase puts that export and what its row cap is. Neither covers the full statement history you usually need for a clean set of books.

Chase typically keeps several years of monthly statements available as PDFs in online banking, well beyond the roughly 90-day window a fresh bank feed imports. For anything older than the feed window, a file import is the only way in, whether that file comes from the bank or from an old Quicken export.

Connect the Chase bank feed for transactions going forward, since it keeps QuickBooks current automatically. If you are weighing the two connection types Chase offers, the comparison of Direct Connect versus Web Connect explains why one costs a monthly fee and the other does not.

If a client has several linked Chase accounts on one combined statement, convert it once and confirm which account each transaction set belongs to before you import, so the right register in QuickBooks receives the right activity. Card accounts import exactly like checking: a .qbo or .qfx download if the bank offers one, otherwise a QIF from Quicken converted to .qbo first.

Importing card activity from statements is the reliable way to capture months the card feed never connected or dropped. Card accounts import exactly like checking: a .qbo or .qfx download if the bank offers one, otherwise a QIF from Quicken converted to .qbo first.

Accuracy matters more than speed here, because a converter that drops or misreads a transaction from Chase costs far more time than it saves. The error usually surfaces during reconciliation, sometimes weeks later, when you are chasing a few dollars across a long register. The converter parses every transaction in the QIF, resolves the date format once so the whole file is consistent, and shows you the parsed rows in a preview before you export.

Match the file to the gap and stop it the day before the feed's earliest transaction. .qbo, .qfx and .ofx files carry a unique ID on every line, so QuickBooks can recognize a transaction it has already seen and flag the repeat. A CSV carries no such ID and will happily import a second copy of a month you already have. If duplicates do land, review them in the For review tab before accepting rather than deleting them from the register afterward.

Check whatever software was tracking the account at the time. A Quicken file holds every transaction it ever downloaded, including accounts you closed and banks you left, and it keeps them long after the bank stops serving them. Export the account from Quicken with File, File Export, QIF File, then convert that QIF to a .qbo here and import it. Microsoft Money, Moneydance, Banktivity and SEE Finance all export QIF as well, so the same route works for those.

Import one period at a time and reconcile it before loading the next. Open the account register, compare the closing balance against the last line of the matching statement, and only then move on. Working period by period keeps a mismatch contained to a few weeks of activity instead of leaving you to hunt for one wrong figure across a year. If a period will not tie out, check for a transaction that arrived twice from an overlapping file before assuming the import dropped something.