Citibank Statement to QuickBooks: Convert a Citibank PDF Statement to QBO

Yes, Citibank works with QuickBooks. Citi connects to QuickBooks Online through bank feeds, and CitiBusiness Online can export activity directly in QuickBooks Web Connect (.qbo) and Quicken (.qfx) formats. The limit is history. Citibank shows the last 24 months of statements for immediate online viewing and a fresh bank feed usually imports only about 90 days. For anything older, closed accounts, or any period the feed skipped, you download the Citibank PDF statement and convert it.

For recent activity, CitiBusiness Online lets you download transactions as a Web Connect .qbo file you import straight into QuickBooks. One quirk to know: CitiBusiness appends an account-type tag (CKG for checking, SAV for savings, MMA for money market) after the account number, so confirm you are importing into the right QuickBooks account. For statements older than the download window, you convert the Citibank PDF to a .qbo file with the converter above and import it the same way.

Citi feeds break for a handful of common reasons: Citibank security or login changes, an expired online banking password, a multi-factor prompt QuickBooks cannot pass, or a temporary outage on either side. While the feed is down, your bookkeeping does not have to wait. Download the Citibank PDF statement for the affected period, convert it to a .qbo file here, and import that into QuickBooks so the account stays current until the connection comes back. This also fills any gap the broken feed left behind.

Sign in at citi.com, choose the account, and open Statements (you may need to activate online statements first). Citibank keeps the past 24 months immediately available and statements stay online for up to seven years, so you can download whichever months you need as PDFs. There is also a transaction export for recent activity, but for older periods, or when you want the figures exactly as printed, the PDF statement is what you convert from.

Convert the Citibank PDF to a .qbo file with the converter above, then import that file. In QuickBooks Online, go to Transactions, Bank transactions, then Upload from file, and pick the .qbo. In QuickBooks Desktop, go to File, Utilities, Import, Web Connect Files. QuickBooks asks which account the transactions belong to, then drops them into the banking review queue for matching and categorizing, the same as a downloaded feed would.

Citibank statements follow a steady layout that converts cleanly. Checking and savings statements list transactions in date order with a description and amount, separating deposits and credits from debits, checks, and withdrawals, with balance figures alongside. Citi often bundles linked checking, savings, and money market accounts into one combined statement, so when you convert one that spans several accounts, confirm which account each transaction set belongs to before importing. Citi credit card statements convert the same way, with dated charges, payments, and credits parsed into clean rows. The converter strips out the summary boxes, fee tables, and inserts Citi adds, so only real transactions reach your .qbo file.

Citibank keeps the last 24 months of statements immediately available online and stores statements for up to seven years, far beyond the roughly 90-day window a fresh bank feed imports. That gap is why converting matters. You can pull a Citibank statement from two or three years ago, convert it to QBO, and bring those transactions into QuickBooks even though the live feed would never reach them. For records older than the online window, you can request archived statements from Citibank and convert those PDFs the same way.

Connect the Citibank feed for transactions going forward, because it keeps QuickBooks current with little effort. Convert the PDF statement when you need history the feed missed: opening balances for a new QuickBooks file, a catch-up period before the connection existed, a closed Citibank account, or any month where the feed dropped or duplicated transactions. Most real Citibank cleanups use both methods together, the feed for new activity and converted statements to backfill the rest.

Accuracy is the part that matters most, because a converter that quietly drops or misreads a Citibank transaction costs you far more time than it saves. The error usually surfaces during reconciliation, sometimes weeks later, when you are chasing a few dollars across a long register. This converter totals the transactions it parsed and checks that figure against the statement total before it lets you export, so the .qbo you import reflects every line Citibank printed. You review the parsed rows in the preview first, then export when the numbers tie out.