Skip to content

Guide · Export CSV · Citi

Export a Citi CSV — short window, clean format.

Citi's transaction download is one of the shortest-window exports in the industry — about 90 days, full stop. That's annoying if you're migrating years of history from a Citi card to a new budgeting app, but the format itself is clean (single signed amount column, consistent header row) and the desktop path is reliable. Here's the route plus what to do for older periods.

Step-by-step: export from Citi

  1. Sign in at citi.com on a desktop browser. The Citi mobile app does not expose the CSV download.
  2. Click into the Citi credit card you want to export. Citi-branded debit accounts (Citibank checking, savings) live under a separate banking section but use the same download pattern.
  3. On the account's Activity or Recent Activity view, scroll past the filters. Look for the Download Transactions link, sometimes hidden under a "More" or "Options" menu near the date filter.
  4. In the download dialog, pick your date range: Current Statement, Last Statement, Last 30/60/90 Days, or Custom Range. Custom range still caps around 90 days.
  5. Choose CSV — Spreadsheets from the file-format dropdown. Other options include Quicken (QFX), Money (OFX), and QuickBooks (QBO); Arden ingests CSV.
  6. Click Download. File lands in your downloads folder.

For older transactions, Citi keeps up to 7 years of PDF statements under Statements & Documents. Those don't import directly into Arden — convert them first or accept the truncation.

What you'll get

  • Format: CSV with columns Status, Date, Description, Debit, Credit, Member Name. Citi uses split Debit / Credit columns rather than a single signed Amount.
  • Date range: ~90 days. This is the shortest export window of any major US card issuer.
  • Pending vs. posted: the Status column distinguishes Cleared from Pending. In practice, pending charges rarely make it into the export — Citi typically only writes posted rows.
  • Sign convention: split columns. Debit is populated for purchases; Credit for payments and refunds. The other column is blank per row.

Importing into Arden

Drag the file onto /import. Arden detects Citi's split debit/credit format automatically (indicator mode) and produces a single signed amount per transaction. The Status column gets ignored; the Member Name column (which authorized user made the charge) gets ignored. Tag a few payees the first time and Citi-formatted imports going forward are categorized automatically.

Quirks specific to Citi

  • Tightest export window of any major issuer. ~90 days. Plan to run the export monthly if you want a clean ongoing record without gaps.
  • Split Debit/Credit columns. Just like Capital One. Arden's parser handles this without a toggle; other tools may need format coercion.
  • Pending charges almost never appear. The Status column technically allows for Pending, but the export only reliably writes Cleared rows.
  • Citibank debit and Citi-branded credit cards share the same download UI. The format quirks (split columns, 90-day cap) apply to both.

FAQ

  • Can I download a year of Citi transactions as one CSV?

    No. The export caps at 90 days. For longer windows, you'll need to run the export multiple times or work from PDF statements.

  • Does Citi offer QFX or OFX directly?

    Yes — both are options in the same download dialog. Arden ingests CSV. If your other tools want QFX, download two copies.

  • Why is the Member Name column in my Citi export?

    For cards with authorized users, Citi tags each transaction with which cardholder made the charge. Useful for household budgets where two people share a card. Arden ignores it on import.

Exporting from other banks?

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