Chase CSV to QBO Converter: Convert Chase CSV to QuickBooks

Log in at chase.com, open the account, go to the activity or transactions view, and choose Download. Pick the CSV (spreadsheet) 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.

On chase.com, select the account and open its activity page. Click the download icon near the transaction list, choose Spreadsheet (CSV) as the file type, set the date range you need, and download. Chase activity downloads usually reach about 24 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 Chase CSV to a .qbo first is the reliable route for Desktop users, since it produces the one file format Desktop actually accepts.

Chase business accounts often hand back a .qbo whose headers or transaction types do not match what your QuickBooks company file expects, which triggers import errors or a file QuickBooks refuses to read. Converting the Chase CSV instead rebuilds a clean OFX 1.02 .qbo with correct Web Connect headers, so QuickBooks accepts it as a standard bank feed without the errors the raw download throws.

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. Chase exports rarely match that exactly. The converter reads the Chase 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 Chase 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 Chase history.

The .qbo carries each transaction's date, description, and amount, which is what QuickBooks uses to build your register. Chase CSV exports do not always include a running balance column, and QuickBooks recalculates the balance from the imported transactions anyway. As long as every transaction comes through, your QuickBooks balance reconciles to your Chase statement.

Yes. Chase business 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 card charges and payments land in the right register.