Skip to content

Guide · Export CSV · Chase

Export a Chase CSV — every account type, step by step.

You're moving off Mint, or you just signed up for a new budgeting app, and you need three years of Chase history out of chase.com and into a file you actually own. Chase has been one of the more reliable big banks for self-serve CSV export — but the path through the site is buried, and the file you get for a credit card doesn't look like the file you get for a checking account. Here's the route that works.

Step-by-step: export from Chase

  1. Sign in at chase.com on a desktop browser. Mobile and the app don't surface the CSV download — you need the full site.
  2. Click into the account you want to export — checking, savings, or a Chase credit card. Each account has its own download; Chase doesn't bundle them.
  3. Scroll past the recent activity and click See all transactions (or the small download icon near the activity header — Chase shuffles its position every few releases).
  4. Pick a statement period (a specific posted statement, going back ~7 years) or choose a date range (rolling window, typically the last 90 days for credit cards and longer for checking).
  5. Under File type, select Spreadsheet (Excel, CSV). Other options — QFX (Quicken), QBO (QuickBooks), QIF — won't import into Arden.
  6. Click Download. The file lands in your browser's downloads folder. Repeat once per account.

What you'll get

  • Format: CSV with columns like Transaction Date, Post Date, Description, Category, Type, Amount. Credit-card exports include Memo. Checking exports include Balance.
  • Date range: Credit cards are capped at roughly the last 90 days for the rolling-window download, but Chase keeps individual PDF and CSV-by-statement exports going back about 7 years. Checking and savings give you more headroom by date — generally up to 7 years of statement-by-statement exports.
  • Sign convention: Debits are negative, credits are positive on checking exports. Credit-card exports flip — purchases are negative, payments to the card are positive.

Importing into Arden

Drag the file onto /import. Arden auto-detects every column — Transaction Date for date, Description for payee, Amountfor the signed dollar value. If the sign direction looks backwards on a credit-card import, flip the sign-flip toggle once and the live preview confirms the direction before you commit. Whichever Chase account you're importing, no bank login or Plaid connection is required.

Quirks specific to Chase

  • Checking and credit-card exports use different layouts. Same bank, different schemas. Don't try to combine them into one file before import — give each account its own pass.
  • Credit-card downloads cap at ~90 days for the activity export. For older history, download statement-by-statement — Chase has the PDF/CSV-by-statement archive going back about 7 years.
  • Type column is descriptive, not categorical. Values like "ACH_CREDIT" or "DEBIT_CARD" describe how the transaction moved, not what it bought. Don't try to map this to your budget categories.
  • The download button moves. Chase has shipped at least three different positions for the spreadsheet download in the past two years. Always look near the top-right of the activity table.

FAQ

  • Can I export multiple Chase accounts at once?

    No. Each account exports separately. Run the flow once per account.

  • Does Chase offer OFX or QFX directly?

    Yes — QFX and QBO are both options in the same download dialog. Arden only ingests CSV, so pick Spreadsheet (Excel, CSV).

  • Why is my Chase credit-card CSV missing pending transactions?

    Chase's export only includes posted transactions. Pending charges live in the UI but never make it into the file — wait a day or two if you need them included.

Exporting from other banks?

Or just drop any CSV, XLSX, OFX, or QFX onto /import and Arden handles the rest.