Guide · Export CSV
Export CSV from your bank.
Every US bank exports CSV. Every US bank does it differently. Pick your bank below for the desktop route that works in 2026 — the date-range caps, the column quirks, and how Arden's importer handles each one without you mapping a thing.
Bank-by-bank guides
Chase
Checking, savings, and credit cards each have their own download. Roughly 7-year archive by statement; ~90 days for the rolling credit-card window.
Open the guide
Bank of America
18 months of activity for checking and savings, 12 months for credit cards. Account-summary preamble before the real header — Arden skips it.
Open the guide
Wells Fargo
18 months for checking, 90 days or 300 transactions for credit cards. The raw CSV often ships without a header row — Arden detects columns by content.
Open the guide
Capital One
~90-day rolling window, desktop-only. Split Debit/Credit columns instead of one signed amount — Arden's parser auto-detects the indicator format.
Open the guide
Citi
The shortest export window of any major issuer — about 90 days. Split Debit/Credit format, plus a Member Name column for authorized users.
Open the guide
American Express
Up to 6 billing periods at a time. Check the "Include all additional transaction details" box or you lose merchant address and reference fields.
Open the guide
Fidelity
One-click holdings export, separate transaction-history download. 90 days per pull for history — plan 20 downloads for 5 years of activity.
Open the guide
Charles Schwab
Multi-year history in a single download. Account-info prefix rows before the real CSV header trip up some tools — Arden skips them automatically.
Open the guide
SoFi
Two-year window for SoFi Money / Checking / Savings — one of the most generous on the market. SoFi Invest and the credit card are PDF-only.
Open the guide
Navy Federal Credit Union
90–180 days for live exports. Split Debit/Credit columns and an occasional Windows-1252 encoding quirk that breaks Excel — Arden handles both.
Open the guide
Your bank not listed? Drop the file in anyway.
Arden's importer doesn't have a fixed list of supported banks. Column detection works from the file itself — drag whatever CSV, XLSX, OFX, or QFX your bank produced into /import and the parser figures it out.