All articles

Chase CSV to QuickBooks: Convert and Import Transactions

7 min read CSVQBO Team
csv / xls / xlsx → .qbo
No file handy?

No account needed for your first conversions. We never store your bank login.

Short answer: Download your transactions from chase.com as a CSV, then convert that CSV to a .qbo Web Connect file and import it into QuickBooks. QuickBooks Online can take a plain CSV with the right columns, but QuickBooks Desktop has no native CSV transaction import at all, so a .qbo file is the only format both versions read cleanly. Converting first also fixes the date and column problems that cause most failed Chase CSV imports.

Chase is one of the most common bank connections in QuickBooks, and most months the live feed handles everything. But there are real situations where you end up with a Chase CSV in hand instead: you needed transactions older than the feed reaches, the Chase connection in QuickBooks dropped, you exported business activity to edit it, or you simply prefer to control exactly what posts. This guide covers how to pull the file from Chase, the format QuickBooks expects, and the fastest way to get those transactions booked.

How do I export a CSV from Chase bank?

Sign in at chase.com, open the account, and go to the account Activity page. Use the download icon near the transaction list and choose the CSV (spreadsheet) format, then set the date range you want. Chase also offers QBO, QFX, and OFX downloads here. The CSV download is capped at roughly 24 months of history and a limited number of rows per file, so split large pulls into smaller date ranges.

Can QuickBooks import a Chase CSV directly?

QuickBooks Online can import a Chase CSV through Transactions, then Bank transactions, then the Link account dropdown and Upload from file. The catch is formatting: the file must have a clear Date, Description, and Amount layout (or a Credit and Debit split), stay under 1,000 rows and 350 KB, and use one consistent date format. QuickBooks Desktop cannot import a CSV of transactions at all, which is why many users convert to .qbo instead.

Why convert a Chase CSV to a .qbo file?

A .qbo file is the Web Connect format QuickBooks builds internally from a live bank feed, so it imports with no column mapping and no date guesswork. Converting your Chase CSV to .qbo removes the two things that break manual imports: mismatched columns and ambiguous dates. The same .qbo file works in QuickBooks Online and Desktop, which a raw CSV never does, so it is the safest single format for Chase data.

Here is how the three routes for Chase data compare so you can pick the right one.

MethodWorks in QuickBooks OnlineWorks in QuickBooks DesktopBest for
Live Chase bank feedYesYes (Web Connect)Routine, recent transactions inside the 90-day window
Upload Chase CSV as-isYes, if columns and dates are exactNo native CSV importOnline users with a clean, small file
Convert Chase CSV to .qbo, then importYesYesOlder data, edited files, Desktop, or avoiding mapping errors

How do I convert a Chase CSV to QBO?

Upload the CSV you downloaded from Chase to a CSV to QBO converter, confirm the date, description, and amount columns are read correctly, and download the .qbo file. The converter reads each row, formats the dates into the fixed structure QuickBooks expects, and writes a valid Web Connect file. You can do this in the converter at the top of this page in a few seconds, with no spreadsheet cleanup needed first.

How do I import the .qbo file into QuickBooks Online?

In QuickBooks Online go to Transactions, then Bank transactions, click the Link account dropdown, and choose Upload from file. Select the .qbo file you converted, pick the matching Chase account, and review the imported transactions before you accept them. Because the .qbo already carries clean dates and amounts, there is no column matching step, and the transactions land ready to categorize.

How do I import the .qbo file into QuickBooks Desktop?

In QuickBooks Desktop go to File, then Utilities, then Import, then Web Connect Files, and select your .qbo file. Desktop reads the Web Connect format natively and posts the transactions to the Chase account you choose. This is the only supported way to bring a Chase CSV into Desktop, since Desktop has no menu option to import a CSV of bank transactions.

Can I import Chase business banking transactions this way?

Yes. Chase Business accounts download in the same CSV, QBO, QFX, and OFX formats from the Activity page, and the convert-to-.qbo route works identically. Business users often have to import older ranges or reconcile across multiple accounts, exactly the cases where a converted .qbo beats a raw CSV. Pull each account's CSV, convert it, and import the .qbo into the matching account in QuickBooks.

Why is my Chase CSV not importing into QuickBooks?

The usual causes are a column layout QuickBooks does not recognize, a date format it reads wrong (Chase often exports month-first dates that get misread), too many rows in one file, or extra header lines. Converting the Chase CSV to a .qbo file sidesteps all of these because the converter normalizes the dates and writes the exact structure QuickBooks accepts, so the import stops failing.

How do I import Chase transactions older than 90 days?

The live feed only reaches back about 90 days, so older Chase transactions never arrive automatically. Download the older range from the Chase Activity page as a CSV (within Chase's roughly 24-month export limit), convert it to a .qbo file, and import that. The .qbo carries each historical date and amount in a fixed format, so even months-old transactions post cleanly in Online or Desktop.

Is it safe to convert my Chase CSV?

A CSV from Chase contains transaction dates, descriptions, and amounts, not your banking password or full account number, so it carries far less sensitive data than a live connection. Use a converter that processes the file over an encrypted connection and does not retain it. The output is a standard .qbo file you import yourself, so you stay in control of what posts to your books.

The reliable Chase to QuickBooks workflow

When the live feed is not an option, the dependable path is short: export the range you need from Chase as a CSV, convert it to a .qbo Web Connect file, and upload that into QuickBooks. The .qbo is the same structure a healthy feed produces, so the transactions post with dates, descriptions, and amounts intact, and the one file works in both QuickBooks Online and Desktop. It is the method that does not depend on the Chase connection being live or the data being recent.

Related guides: Convert your export with the CSV to QuickBooks Online converter or the CSV to QuickBooks Desktop converter. Importing card activity? See credit card CSV to QuickBooks. Compare tools on the best CSV to QBO converter roundup, and read the step-by-step walkthroughs for how to convert a CSV to QBO, importing a QBO file into QuickBooks, and the QuickBooks CSV import template rules.

If Chase only gives you a PDF statement for the months you need, fix the source first: turn the PDF bank statement into a clean CSV or Excel file, or convert the PDF statement straight to QBO and skip the spreadsheet step. And when you take those Chase financials to apply for a business line of credit, the bank runs them through loan underwriting software on their end, so clean, reconciled books help your case.

Convert your CSV to QBO now

Upload your CSV or Excel statement, map the columns, and download a QuickBooks ready QBO file in seconds.

Start converting