Citibank checking statements have some of the longest transaction descriptions of any major US bank. A simple ACH transfer can carry 80+ characters of payment metadata, originator details, and reference codes. Citi credit card statements add a different challenge: the tier summary at the top of each statement (rewards points balance, fee summary, etc.) sometimes gets parsed as transactions by less careful tools.
This guide covers both: Citi personal and business checking, plus Citi-branded credit cards (Citi Premier, Custom Cash, Diamond Preferred, AAdvantage, etc.).
Short version: Citi's two main pitfalls: long ACH descriptors that wrap to multiple lines (causing phantom rows), and the credit card statement's tier-summary section that converters sometimes treat as transactions. Both are easy to handle once you know what to look for.
Citi statement quirks (checking and credit card)
1. Very long ACH transaction descriptions
Citi includes more transaction metadata than most banks. A typical ACH from a vendor looks like:
04/02 ACH ELECTRONIC CREDIT STRIPE PAYMENT
ID:1800948598 INDN:ACME LLC CO ID:1800948598
PPD CCD ENTRY CLASS $4,218.50
That's a three-line transaction. Tools that don't merge continuation lines produce phantom $0 rows. The fix is the same as with other banks: any row where the date column is empty should be merged into the previous row's description, then the empty row removed.
2. Foreign transaction fees on credit cards
Citi credit cards itemize foreign transaction fees on a separate line from the underlying purchase. So a $100 Euro purchase becomes two lines in your CSV: $100.00 (the purchase) and $3.00 (the FX fee). Both are valid transactions and both should import to QBO — but if you're trying to categorize the purchase to a specific account, the FX fee won't auto-match unless you create a rule.
3. The tier summary section on credit card statements
Citi credit card statements begin with a one-page summary: rewards points balance, payment due date, minimum payment, account summary (purchases this period, payments, credits, interest charged). Some PDF converters read this summary as transactions, which means you'd see "Purchases: $4,231.42" appear as a phantom transaction at the top of your CSV.
Skip this section. The actual transactions begin on the page labeled "Transactions" or "Statement of Activity" — usually page 2 or 3.
Three ways to do the actual conversion
Option 1: Copy-paste, one-time use
If this is a one-off and you have an hour, you can open the PDF, select the transaction table, paste into Excel, use Text-to-Columns to split, manually merge continuation rows, drop any extra columns, reformat the date, and save as CSV. Works for one statement. Doesn't scale.
Option 2: A generic PDF-to-Excel tool
Adobe Acrobat, Smallpdf, Tabula, and similar tools will extract the table mostly correctly. The catch: they don't know what a bank transaction is, so they won't merge continuation lines, they'll include columns you don't want, and they won't verify that the converted file reconciles. You'll spend cleanup time after.
Option 3: A bank-statement-specific converter that reconciles
A purpose-built converter recognizes the Citibank statement format, handles the quirks above automatically, and — the part that matters most — reconciles the converted file against the statement's beginning and ending balances before handing you the file. If the totals don't tie, you find out immediately, not after the QBO import is already done.
Worth trying: If you're processing Citibank statements regularly, an automated converter that reconciles to the statement totals before you download saves the manual cleanup. YourStatementConverter does this on every conversion — 25 pages free with no credit card to test on a real client statement.
Common errors and how to fix them
"My QBO balance is double what the statement shows"
Almost always: the tier summary section was imported alongside the transactions. Open the converted file, look for an early row labeled "Account Summary" or "Purchases This Period" with the full month's total. Delete that row, redo the QBO import.
"QBO is rejecting my date format"
QBO requires MM/DD/YYYY. If your conversion output uses a different format, fix it in Excel before importing. The simplest formula is =TEXT(A1,"MM/DD/YYYY") applied to the date column.
"Descriptions are showing up twice or in pieces"
Almost always a continuation-line problem. Sort the converted file by date; any row with a blank date is a continuation that should be merged into the row above. Filter for blank dates, copy descriptions up, then delete the empty rows.
Importing the converted file into QuickBooks Online
Once you have a clean Excel or CSV file from a Citibank statement, the QBO import is the same as for any other bank. QBO expects three columns:
| Column | Format | Notes |
|---|---|---|
| Date | MM/DD/YYYY | QBO is strict on date formatting |
| Description | Plain text | Keep under 4,000 characters |
| Amount | Decimal, negative for debits | Or use separate Credit/Debit columns |
To import:
- In QBO, go to Bookkeeping → Transactions → Bank transactions
- Choose the bank account, click the dropdown next to "Link account," and pick Upload from file
- Drag in the CSV, map the columns, click Next
- Spot-check a few transactions on the preview
- Confirm and import
QBO will check against existing transactions to prevent duplicate imports, so re-running a statement won't double-count.
Final checklist before importing your Citibank file to QBO
- Three columns only: Date, Description, Amount
- Date in MM/DD/YYYY format
- Debits are negative (or split into Credit/Debit columns)
- Any running balance column removed
- No empty rows or unmerged continuation rows
- Total of Amount column equals Statement ending balance minus Beginning balance
If all six are checked, the QBO import will be uneventful — which is the goal.
For more on the reconciliation discipline that makes catch-up work tractable, see our walkthrough on catching up 24 months of bookkeeping.