Convert Citi Bank Statements to Excel

Upload the statement PDF and StackExtract turns the transaction activity into rows — dates, descriptions, amounts, and balances where they are printed.

Amounts are read as they appear, including the thousands separators and decimal marks the statement uses, and currency symbols are preserved rather than stripped. Where a transaction line carries more text than fits one row, the description is kept whole rather than split across rows — a wrapped description read as two transactions is a misread that changes the row count without changing the total.

Descriptions are worth reading as carefully as amounts on any statement with a lot of merchant detail, because a description is the field with nothing to check it against: no arithmetic relates it to anything, so no check can confirm it.

Every extracted cell is editable before anything is exported, and rows a check flagged are marked so the review is directed rather than a re-read of the whole statement. Where the statement prints opening and closing balances, the reconciliation check runs against them: the transactions should move the opening figure to the closing one.

Where the statement does not supply those figures, the check is reported as one that could not run — never as a pass. And nothing is silently corrected: where figures disagree, both are shown as printed and the row is flagged, because a tool that adjusted a number to make its own arithmetic work would be removing the evidence you needed.

The recurring reason to convert rather than connect is coverage: the months needed are older than the feed, or the account is closed, or the only copy is a download a client kept.

For expense work in particular the statement is the document of record, and getting it into a spreadsheet is what makes the rest of the job possible.

StackExtract is independent and is not affiliated with, endorsed by or connected to any bank or card issuer.

A long statement with heavy merchant detail is where the free preview earns its place: you see the whole extracted result, descriptions included, before deciding whether it is worth exporting. On documents where the descriptions are the point, that is a better test than any summary of the extraction could be.

XLSX is the usual choice when a person is going to read the file: it opens in Excel with the columns intact and the accented characters preserved. CSV is the choice when something else will consume the rows.

For bank statements there is also a QuickBooks-ready CSV, shaped for that import workflow. It is a file you download and import yourself — not a QBO file, not Web Connect, and not a connection to your accounting software or to the bank. Every import decision stays in your environment.

Accented characters and currency symbols survive extraction and export, which matters as soon as anything downstream is matched on a payee name.