How to Import Citi Statements into QuickBooks

To import Citi statements into QuickBooks without a bank connection: download your Citi statement as a PDF, convert it to a .QBO file on your own computer, then import that file into QuickBooks the same way it handles a bank feed. Here's the full walkthrough - Citi-specific, duplicate-safe, and with no Citi login handed to anyone.

If the Citi bank feed in QuickBooks has stopped syncing, never connected in the first place, or you simply don't want a live link between your Citibank account and your accounting software, you can still get every transaction in cleanly. QuickBooks accepts a .QBO (Web Connect) file as a manual import - and Citi already gives you everything you need in the statement PDF you can download today.

Why import from a PDF instead of the bank feed?

The direct Citi-to-QuickBooks bank feed relies on a stored connection that breaks often: Citi rotates its security flow, the feed silently stalls for days, and historical transactions older than 90 days frequently never come through. Importing from the statement PDF sidesteps all of that:

• No login to share. You're working from a file you downloaded, not a live credential. Nothing to connect, nothing to revoke.
• Complete history. Statements go back as far as Citi keeps them, so you can backfill an entire tax year QuickBooks' feed would never reach.
• You control the data. The conversion happens on your machine, so your Citi transactions never pass through a third-party server.

Step-by-step: Citi statement → QuickBooks

1. Download your Citi statement as a PDF

Sign in to Citi (citi.com or the Citi Mobile app), open the account - Citi checking, a Citi savings account, or a Citi-branded card like the Double Cash, Custom Cash, or Costco Anywhere Visa - and go to Statements & Documents. Pick the billing period you need and choose Download PDF. Citi card and bank statements both come as standard PDFs; grab one file per statement period for the range you want to import.

2. Convert the Citi PDF to a .QBO file

QuickBooks can't read a raw statement PDF, so the file has to become a format QuickBooks understands. The cleanest target is .QBO (Web Connect), the same format the bank feed would deliver. Run your Citi PDF through a local converter that parses each transaction - date, description, and amount - and writes a valid .QBO file.

This is exactly what Quill does: drop in your Citi statement PDF and it parses every transaction on your own computer, then exports a QuickBooks-ready .QBO (or OFX) file. Because Quill assigns stable transaction IDs, QuickBooks can recognize re-imports and skip duplicates instead of doubling up your register.

If you prefer to map columns yourself, Quill can also export CSV, which QuickBooks Online imports through its three-column (Date, Description, Amount) mapping screen. But .QBO is the lower-friction path because QuickBooks ingests it without any manual mapping.

3. Import the .QBO file into QuickBooks

In QuickBooks Online: go to Transactions → Bank transactions, select the Citi account (or add it as a new account first), click the dropdown by Link account, and choose Upload from file. Select your .QBO file and confirm the account it belongs to.

In QuickBooks Desktop: go to File → Utilities → Import → Web Connect Files, choose the .QBO file, and link it to the matching Citi account when prompted. Either way, the transactions land in the For Review queue just like a normal bank feed.

4. Review, categorize, and confirm

Your Citi transactions now sit in the review queue. Accept QuickBooks' suggested categories or adjust them, match anything against existing entries, then add them to the register. If you already sorted everything in Quill into Personal and Business with categories and manual overrides before exporting, this final pass is fast - you're confirming clean data, not starting from scratch.

How to avoid duplicate transactions

Duplicates are the number-one headache when importing statements by hand, and they happen for two reasons: overlapping date ranges, and files without stable IDs that QuickBooks can't de-duplicate against. Avoid both:

• Import non-overlapping periods. If March is already in QuickBooks, start your next import on April 1 - don't re-import a range you've already brought in.
• Use .QBO with stable transaction IDs. Each transaction carries a consistent ID across exports, so when ranges do overlap, QuickBooks matches the re-import against what's already in the register and skips the duplicates. Quill's .QBO and OFX exports are built this way specifically so re-running a statement is safe.

If a few duplicates still slip through, you can exclude them from the For Review tab before adding them - but with stable IDs, that cleanup is rarely needed.

What about Citi credit cards specifically?

Citi card statements import the same way as bank statements, with one nuance: in QuickBooks, set the account type to Credit Card so charges and payments post with the correct sign. Quill reads Citi card PDFs and bank PDFs alike, and the .QBO it produces carries the right transaction direction for the account type you're importing into.

For a broader look at moving any bank's transactions into QuickBooks this way, see our guide on how to export bank transactions to QuickBooks.