How to Convert a Citibank Statement to Excel

Citibank statements split roughly into two families: deposit accounts (Priority, Accelerate Savings) and credit cards (Costco Anywhere Visa, Double Cash, Premier, Rewards+). The two layouts are genuinely different — they use different field orders, different balance-summary placements, and different sign conventions — and most free "PDF to Excel" tools either mangle one or invert the other. Our parser routes each through the right extraction path and reconciles the result against the statement's own printed arithmetic.

This guide covers both — where to download each kind, how we parse them, how to pick the right export format, and how to import the result into QuickBooks without double-posting.

Pulling your Citi PDF

Sign in at online.citi.com (or citi.com, which will redirect you), open the account, and use the Statements section from the account-level menu. For deposit accounts the statements are monthly PDFs going back at least seven years; for credit cards they're billing-cycle PDFs on the same retention. Individual downloads are one click each, or use the year selector to pull a full year sequentially.

• Citi Priority Checking and Citi Accelerate Savings — deposit accounts, monthly statements with the usual beginning/ending summary, transactions table, fees, and daily balances.
• Citi credit cards: Costco Anywhere Visa, Double Cash, Premier, Rewards+, Simplicity, Strata Premier. Billing-cycle PDFs with their own layout (payments, purchases, fees, interest, rewards).
• Citigold relationship combined statements — one PDF covering multiple linked products.

Citi occasionally delivers password-protected combined statements for Citigold customers — the upload prompts inline for the password and decrypts the file in memory during parsing. Nothing is stored after the job finishes.

Handling Citi credit-card statements correctly

Credit-card PDFs are where most free converters fall over. They don't know whether to treat a purchase as positive or negative and often invert the whole statement, which then re-inverts when you import it into QuickBooks, which then makes your reconciliation fail in a way that's very hard to trace because every row looks plausible individually.

We follow the bank's accounting view consistently: purchases, fees, and interest charges are positive (they increase the balance owed), payments and merchandise credits are negative (they reduce it). If the LLM's first pass gets this wrong — which can happen on the Double Cash statement layout, where the subtotal line visually resembles a transaction row — the validator detects the sum mismatch and either auto-flips the signs or re-runs the pass with targeted feedback, then validates again. The file only gets stamped Verified if the arithmetic works.

Converting the Citi PDF to Excel

Drop the PDF on our Citi conversion page and pick the output format. Citi deposit statements take the fast-path extractor (text is clean, rows are laid out consistently); credit cards go through the LLM fallback with sign handling tuned to Citi's format.

On both paths the same running-balance validator runs before the file is offered for download. You'll see either a green Verified badge or a yellow Unverified one with the exact mismatch amount, so a problem is something you can see, not something that turns up weeks later.

XLSX, CSV, or QBO — which export to pick

The same parsed row set can come out in three formats. Pick based on what you're doing with the data next, not on which one sounds safest — they all carry identical transactions, only the wrapper differs.

XLSX — when you want Excel to do the work

Choose XLSX when a human is going to open the file. The workbook comes with amounts formatted as currency, dates as real Excel dates (not text strings), and a running-balance column ready to sort, filter, and sum. It's the right pick for month-end review, handing a statement to an auditor, or pasting a block of transactions into a forensic-accounting report. Under the hood it's a standard .xlsx that Excel, Numbers, LibreOffice, and Google Sheets all open without fuss.

CSV — when another tool will consume it

Choose CSV when the next step is a script, a database import, a pandas notebook, or a Google Sheets IMPORTDATA call. CSV strips away all formatting, which is what you want when you're going to reformat yourself anyway. Amounts are plain numbers with a dot decimal separator, dates are ISO-8601 (YYYY-MM-DD), and descriptions are double-quoted to survive commas in merchant names.

QBO — when it's going straight into QuickBooks

Choose QBO when you're importing into QuickBooks Online or QuickBooks Desktop. The .qbo file is an OFX document with a QuickBooks-specific wrapper; QuickBooks opens it via the "Upload transactions" flow and matches rows to your existing Citi account by routing number and account number (both preserved from the statement). If you've been pasting transactions by hand, QBO import will save you hours per month per account.

Importing the file into QuickBooks

If QuickBooks is the destination, skip XLSX and export straight to QBO — QuickBooks accepts OFX-format .qbo files natively and matches transactions against the correct Citi account without manual mapping. The end-to-end flow looks like this:

1. On bankpdftoxls.com, upload the Citi PDF and pick QBO as the export format.
2. In QuickBooks Online, open Banking → Transactions → Link account (or, on the account already linked, Upload from file). Drop the .qbo file in.
3. QuickBooks reads the routing number + account number from the file and asks which account to post to — pick your linked Citi account.
4. Review the matched transactions. QuickBooks will suggest splits based on prior categorizations; accept them or adjust.
5. If there are duplicates with transactions already imported via direct bank feed, QuickBooks flags them so you can exclude and avoid double-posting.

For QuickBooks Desktop the flow is slightly different — File → Utilities → Import → Web Connect Files — but the .qbo format is identical and the matching works the same way. Either way, the Verified badge on our side means the amounts you're about to import sum to the bank-printed ending balance, so your reconciliation inside QuickBooks starts from a known-good state.

Batch-converting a year of Citi statements

Most of our traffic is people who need not one statement but twelve — a full year for a tax return, three years for a mortgage pre-approval, or six months for a divorce discovery request. The batch upload takes up to 10 PDFs at once, processes them in parallel, and packages the results into a single ZIP.

1. Sign in (batch requires a free account — this is the quickest path to running-balance verification across a multi-month period).
2. Open /app/new and drop 2–10 PDFs onto the upload zone at once. File order doesn't matter.
3. Each file gets its own status row — queued, parsing, verified or flagged. You can keep working in another tab while they run.
4. When the batch finishes, click Download all (ZIP) to get every converted file in XLSX, CSV, or QBO — whichever format you picked.

If one statement in the batch fails verification, the rest still download. The failed one stays on the dashboard with the specific reason (missing ending balance, scan too low-res, etc.) so you can retry or hand that one file to a human without blocking the whole job.

Citi-specific tips

• Costco Anywhere Visa statements include a large rewards-summary block — parser correctly excludes it from the transaction total.
• Double Cash statements show cash-back earned and redeemed in a separate section; only actual transactions count toward the reconciled sum.
• Citigold combined statements come out as a single unified export with a Citi-account-number column.
• If you're importing a Citi credit-card QBO into QuickBooks and the sign direction looks flipped, use the "invert signs" toggle at export — QuickBooks models credit-card liabilities in different directions depending on how your chart of accounts is set up.

Why the "Verified" badge matters

Every export we produce is reconciled against the arithmetic printed on the statement itself: the sum of every transaction must equal the ending balance minus the beginning balance, to within a penny. If it doesn't, you see an honest "unverified" badge rather than a silently broken XLSX. Most OCR-only and direct-LLM tools skip this check, which is how subtle sign errors end up in bookkeeping months later — by the time the mismatch surfaces during reconciliation, the original PDF is often archived and the error takes hours to trace.

For forensic and audit work this is non-negotiable. If you're preparing a bank-statement analysis for a divorce discovery packet, a loan application, or an IRS audit, "close enough" transcription will be challenged the minute someone runs a sum. The Verified badge is our way of saying "this file sums to the same number the bank printed" — and if it can't, we tell you instead of hiding it.

Frequently asked questions

Do I need an account?

No — one-off conversions work without signing in. A free account unlocks conversion history and the 10-file batch upload, which is the thing most users end up wanting once they've done a single file.

Are my Citi PDFs stored on your servers?

No. The PDF is parsed in memory and discarded as soon as the extraction finishes. Only the structured JSON (dates, descriptions, amounts) is persisted, and only if you're signed in, with a 24-hour default retention on the free tier. If you want zero retention, do the conversion signed out — nothing is saved at all.

Password-protected PDFs?

Yes. If the PDF is encrypted, the upload prompts for the password inline and decrypts in memory during parsing. We never store the password.

Can I convert multiple Citi statements at once?

Drop up to 10 PDFs in a single batch. Each runs through the queue with its own status row, and when everything finishes a single ZIP packages all the converted files in your chosen format — XLSX, CSV, or QBO — for one download.

How accurate is the conversion?

For digital PDFs (ones you downloaded directly from the bank, not scans) accuracy is effectively 100% on transaction rows, validated by the running-balance check. For scanned or low-quality PDFs we route through a vision LLM pass, and the same running-balance check still runs — so you always know whether the output is safe to use.

Convert a Citi statement now →