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.

Download Account Activity, not Statements. The Statements area gives you a PDF of a closed billing or statement period, which is a document rather than data, and QuickBooks has no use for it in a bank feed. The activity view is the one with the download icon that offers Spreadsheet (CSV) as a file type, and it is the only place Chase hands you machine readable rows.

The distinction matters most on business accounts, where people often go looking for the statement because that is the thing the bookkeeper asks for. If you have already saved a stack of PDFs, you have not wasted the effort, but for importing into QuickBooks go back to activity and pull the same period as CSV. The dates will match the statement as long as you set the range to the statement's start and end dates rather than to calendar months.

Because Direct Connect is being retired across the industry. New enrollments ended April 30, 2026 and the service reaches its industry wide end on October 30, 2026, and this is not one bank making a decision on its own. Individual banks have moved earlier than the industry date, so your own bank's notice always outranks the general timeline. If a message in QuickBooks or in online banking gives you a specific date, believe that one.

What replaces it is not a like for like swap. Intuit's own setup guidance for QuickBooks Desktop bank feeds lists exactly two connection types, Direct Connect and Web Connect, so on Desktop the practical successor to a Direct Connect feed is a Web Connect .qbo file. That is precisely what this converter produces from a Chase CSV, which is why a lot of Chase Desktop users end up here after a connection notice rather than after an import error.

They point at three different problems. Codes 102 and 105 mean the bank's own site is down or not responding, so nothing on your side will fix them and waiting is the correct response. Code 185 means the bank wants more than a user ID and password, usually a one time code you need to supply. Code 324 means QuickBooks cannot find the account it expected, which happens after an account number changes or an account is closed and reopened.

None of these are worth fighting when you are simply trying to get a month of Chase transactions into the books. A converted .qbo does not touch the bank connection at all, so it imports whether or not the feed is healthy. Bear in mind too that a freshly established bank feed commonly pulls only about 90 days of history, so even a working connection will not backfill the year you are trying to close.

Not with a .qbo. Every transaction inside an OFX or .qbo file carries a FITID, a transaction identifier unique within the account that is never reused. QuickBooks skips FITIDs it has already seen, and it remembers them even after you delete the transaction, so re importing a corrected file behaves predictably instead of doubling your register.

A raw Chase CSV has no equivalent. Nothing in a CSV row identifies the transaction, so QuickBooks cannot distinguish a genuine second $48.00 charge at the same merchant from an accidental second load of the same file. If you are catching up several months and expect to reload at least one file while you get the date ranges right, that difference is the whole argument for converting first.

Almost always a day and month swap. Use MM/DD/YYYY for a United States QuickBooks company file. The Intuit help article that ranks highest for CSV formatting is the global edition and it recommends DD/MM/YYYY, which is right for the market it was written for and wrong for a US file. Follow it and every date from the first to the twelfth of a month posts silently into a different month, with nothing failing to warn you.

Spreadsheet software adds its own traps if you open the Chase CSV in Excel before uploading. 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 historically used 1904, a four year and one day shift that quietly ruins a file moved between machines. The safest habit is to upload the Chase download untouched and let the converter read it.

In current QuickBooks Online, open All apps, then Accounting, then Bank transactions, and use Link account followed by Upload from file. Some company files still show the older Transactions then Bank transactions path in the left hand menu, and both are live depending on the account, so use whichever your file presents. The upload screen is the same once you reach it.

On QuickBooks Desktop the route is different: Banking, then Bank Feeds, then Import Web Connect Files. Either way the transactions land in a review queue rather than posting straight to the ledger, which is what gives you the chance to match against existing entries and categorize before anything hits the books.

Reconcile against the Chase statement, not against the CSV you exported. The CSV proves the converter read every row it was given. Only the statement proves you exported the right date range in the first place, and a missing week is a far more common failure than a misread row.

Three quick diagnostics resolve most differences. A difference that divides evenly by nine is transposed digits somewhere. A difference exactly twice the value of a single transaction is a sign flip, most often a Chase credit that arrived as a debit. A difference matching one transaction exactly is a row that did not import or one that was accepted twice. Chase card accounts flip the meaning of the sign compared with checking accounts, so check that first on a credit card import.