# Chase CSV to Beancount

Convert a Chase checking, savings or credit-card CSV export into balanced double-entry Beancount transactions — in your browser, with the column mapping already set.

Column mapping verified against a real Chase export

Processed locally in your browser.

[Open converter](https://beancount.io/tools/csv-to-beancount/chase#converter) [Export instructions](https://beancount.io/tools/csv-to-beancount/chase#export-guide)

## Saved mappings

Profiles live only in this browser. Your transactions never leave it.

No saved mappings yet. Paste a CSV, set the columns, then save the setup here to reuse it later.

### Import profiles from a file

Choose a .json file exported from this converter. Nothing is saved or applied until you choose.

## Beancount output

Your transactions will appear here as soon as you paste a CSV.

## How to export your Chase transactions

1. Sign in at chase.com and open the account you want to export.

2. Above the transaction list, choose the download icon, then “Choose a date range” if you need more than the visible activity.

3. Pick “Spreadsheet (CSV)” as the file type — not Quicken or QuickBooks, which produce QFX/QBO files this converter does not read.

4. Open the downloaded file in a text editor, copy everything, and paste it below.

### Chase writes dates month-first, and that is already handled

Chase exports US-style MM/DD/YYYY dates, so 08/01/2026 is August 1st, not January 8th. The preset below sets that for you. Checking exports also carry both a “Posting Date” and, on some account types, a separate transaction date — the mapping uses the posting date, which is what your statement balance reconciles against.

## Chase export questions

**Which Chase accounts does this work for?**

Checking, savings and Chase credit cards all export the same seven-column CSV, so the mapping applies to each. Credit-card exports write purchases as negative amounts, matching the checking convention, so no sign flip is needed.

**Why does my export stop short of the date range I asked for?**

Chase limits downloads to activity still available online — commonly the last 24 months for checking, and less on some card accounts. For anything older, download the PDF statements and enter those periods separately; the converter only sees what the CSV contains.

**Is my statement uploaded anywhere?**

No. The conversion runs entirely in your browser — the file never leaves your machine, and there is no server call to make. You can confirm this by disconnecting from the network and converting anyway.

[Converting an export from another bank or app?](https://beancount.io/tools/csv-to-beancount)

## Keep the ledger you just converted

Beancount.io hosts your plain-text ledger, imports future statements for you, and keeps every number auditable.

[Start Free→](https://beancount.io/sign-up/?next=%2Fledger%2F)

## Where to look next

- [Sitemap](https://beancount.io/sitemap.xml) - all pages with hreflang alternates
- [LLMs index](https://beancount.io/llms.txt) - curated links for AI agents (also /llms-full.txt for full docs)
- [Documentation](https://beancount.io/docs) - every doc is also available as text/markdown via .md suffix or Accept negotiation
- [REST API reference](https://beancount.io/docs/api-reference) - interactive endpoints, schemas, authentication, and code samples
- [OpenAPI spec](https://beancount.io/openapi.json) - OpenAPI 3.1 spec for this website's public content endpoints; the product contract for ledger operations is at https://beancount.io/api-gateway/v1/openapi.json
- [GraphQL](https://beancount.io/graphql) - public, read-only content API over the blog and research logs (no credentials, no ledger data): 12 query fields over 23 types
- [MCP server](https://beancount.io/mcp) - Model Context Protocol at https://beancount.io/api-gateway/mcp
