Chase Statement to CSV: When the Download Runs Out

Chase is better than most banks at handing you a spreadsheet. Sign in on a desktop browser and you can pull transactions straight out in CSV — no converter, no cleanup, no argument. So the interesting question is not how to download Chase activity. It is what you do the moment that download stops covering what you need.

That moment arrives more often than you would think: a mortgage underwriter asking for two full years, an accountant reconstructing a closed business account, a CPA who wants the actual statements rather than an export you generated yourself. Past the activity window, Chase's record is a PDF. This post covers both paths and, more importantly, how to prove the CSV you end up with matches the statement it came from.

Quick answer

Two ways to get Chase transactions into CSV:

1. Chase's own download. On a desktop browser, Chase's Spending Planner lets you download two years of transactions as a spreadsheet (CSV), Quicken Web Connect (QFX), Quicken or Microsoft Money (QIF), or QuickBooks Web Connect (QBO). There is also a Download transactions button on the account activity view, though Chase does not publish which formats that one offers. On mobile the download is PDF only, for the last calendar year.
2. Convert the statement PDF. Archived monthly statements are PDFs. For older periods, for closed accounts, or when you need the statement itself rather than a self-generated export, upload the PDF to a converter like BankStatementKit, which extracts the transactions and balance-checks the output against the statement's own printed totals.

Rule of thumb: if the account is open and the period is inside the download window, take Chase's export. Everything else goes through the PDF.

Convert a Chase statement PDF to CSV

Option 1: Chase's built-in activity download

Do this first when it applies — the data comes straight from the bank in a machine-readable format.

1. Sign in to chase.com on a desktop browser. The full set of download formats is a desktop feature; the mobile app's download is PDF-oriented.
2. Open the account whose activity you want.
3. Find the download control on the account activity view and choose a date range.
4. Pick a format: spreadsheet (CSV), QFX for Quicken, QIF for Quicken or Microsoft Money, or QBO for QuickBooks.
5. Open the CSV in Excel or Google Sheets.

Where the built-in download stops

• It is scoped to recent activity on accounts you can still open. Once an account is closed, the activity view it lived in is not somewhere you can go and export from.
• The archive is PDFs, not spreadsheets. Chase documents that, depending on account type, you can access up to 7 years of statements online. Those are PDFs. The exportable window is dramatically shorter than the viewable one.
• An export is not a statement. Lenders, auditors and accountants frequently want the bank-issued statement, not a CSV you generated from a date-range picker. If you must supply the statement anyway, you may as well derive the CSV from it.
• Format choice does not solve structure. QBO and QFX are convenient for Quicken and QuickBooks specifically; if your tool wants plain CSV with predictable columns, you are back to reshaping data by hand.

Every one of those ends at the same artifact: a PDF.

Option 2: Convert the Chase PDF statement to CSV

1. Download the statement PDF from the Statements area — pick the account, then the year and month.
2. Upload it. Chase statement PDFs are generally not password-protected, since the login is the access control, so there is usually nothing to enter.
3. The transactions are read into seven standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance.
4. Check the verification label, then download the CSV.

Convert a Chase statement

Uploads are limited to 20MB or 50 pages, and a scanned or photographed statement falls back to OCR automatically.

Why Chase PDFs trip up generic converters

Chase's checking layout is one of the harder mainstream US formats to extract correctly, for reasons that have nothing to do with how it looks to a human.

It is not one table — it is several. A Chase statement groups the month into separately headed all-caps sections: DEPOSITS AND ADDITIONS, CHECKS PAID, ATM & DEBIT CARD WITHDRAWALS and their siblings. Each section has its own column set. CHECKS PAID carries CHECK NO. and DATE PAID columns that DEPOSITS AND ADDITIONS does not. A converter that assumes a single consistent table across the whole document will either mangle the columns or turn section headings into transaction rows.

Direction lives in the heading, not the row. Amounts sit in one AMOUNT column. Nothing on a withdrawal row marks it as negative — the only thing that makes it a withdrawal is the section heading several lines above it. Lose track of which section you are inside and a block of withdrawals lands in your spreadsheet as deposits. This is the single most damaging Chase-specific failure mode, and it is completely invisible until a total refuses to reconcile.

The balance table is not transaction data. DAILY ENDING BALANCE is a separate DATE / AMOUNT table with one row per day, not per transaction. Converters that grab every date-and-amount pair on the page happily append it to the transaction list, inflating your file with rows that are balances, not payments.

More on how these map to output columns is on the Chase statement converter page.

Prove the CSV matches the statement

Because a Chase checking statement has no per-row running balance, the usual row-by-row chain is unavailable — which makes the other two checks essential rather than optional.

1. The CHECKING SUMMARY block. Chase prints beginning balance, ending balance, and per-category totals, each with an instance count: how many deposits, how many checks paid, how many card withdrawals. Those counts are unusually useful. Beginning balance plus additions minus withdrawals must equal ending balance, and your extracted row counts must match the printed instance counts category by category. A converter that invented rows or swallowed them will fail the count check even if the money happens to add up.
2. The DAILY ENDING BALANCE table. Sum your extracted transactions day by day and the cumulative total must land on each printed daily figure. This gives you a per-day checkpoint in place of a per-row one, so a discrepancy is localised to a single day rather than the whole month.

Doing both by hand takes real time per statement. BankStatementKit runs the checks on every conversion and labels the result VERIFIED, DISCREPANCY or FAILED, with a discrepancy pointing at where the numbers stop agreeing.

FAQ

The bottom line

Chase gives you a genuinely good native export, so use it whenever it reaches your period and the account is still open. The PDF path is for everything past that line: closed accounts, older months, and the times someone wants the bank's own statement rather than an export you made. Just verify the result, because a layout with no running balance and direction encoded in section headings is exactly the kind that fails quietly.