Citibank CSV to QBO Converter: Convert Citibank CSV to QuickBooks

Sign in at citi.com or CitiBusiness Online on a desktop browser, open the account, and download your activity as a CSV for the date range you need. Upload that CSV to the converter at the top of this page. It detects the date, description, and amount columns, checks the parsed total against your file, and hands back a .qbo you import into QuickBooks. QuickBooks Online reads the .qbo directly, and QuickBooks Desktop imports it through Bank Feeds, so the same file works in either version.

On citi.com, open the account and use the download or export option on the transactions page, then choose Comma-Separated Values (CSV) and your date range. On CitiBusiness Online, use Download Transactions and select the CSV format. Use the desktop website rather than the mobile app, since the app does not offer the full export. Citi credit cards typically offer CSV as the download format, which is exactly what this converter turns into a .qbo.

CitiBusiness Online offers a QuickBooks Web Connect (.qbo) and Quicken (.qfx) download for business accounts, but Citi's consumer and credit card side usually limits you to a CSV file, with no direct .qbo option. Quicken and QuickBooks users regularly report that Citi allows no transaction download except CSV on card accounts. Converting that CSV to a .qbo gives you the Web Connect file those accounts never provide directly.

Citi has changed how several of its accounts connect to QuickBooks Online, so existing bank feeds can stop pulling transactions and new connections sometimes cannot find the account. CitiBusiness Online feeds are a frequent subject of unresolved connection threads in the QuickBooks community. When the feed is broken, downloading a Citibank CSV and converting it to a .qbo gets your transactions into QuickBooks without waiting for the connection to be fixed.

A Citibank CSV often has extra columns, no running balance, and debits and credits that QuickBooks Online's three or four column mapping reads the wrong way, so descriptions go missing or amounts flip sign. Converting the CSV to a .qbo builds a clean description and applies the correct sign for each transaction, so the import lands right the first time instead of needing row-by-row cleanup after the fact.

No, QuickBooks Desktop cannot import bank transactions from a raw CSV file. Desktop only imports a Web Connect .qbo through File, then Utilities, then Import, then Web Connect Files. Since Citi credit cards and many consumer accounts never offer a .qbo of their own, converting your Citibank CSV to a .qbo first is the only way to get those transactions into QuickBooks Desktop.

Citi checking and card accounts usually let you download a limited window at a time, often the current and past several statement cycles, and CitiBusiness Online caps how much you can pull in one file. To catch up a longer stretch, pull each available range as a CSV, convert each one to a .qbo here, and import them in order. The accuracy check on every file means nothing is dropped when you piece a long history together.

Yes. Citi credit card and CitiBusiness activity downloads as a CSV the same way checking activity does, and the converter handles card exports, including split debit and credit columns. You get a .qbo that imports into the matching QuickBooks credit card account, so card charges and payments land in the right register instead of your checking account.

QuickBooks caps a single CSV upload at 350 KB, which is roughly 1,000 transactions, so a long Citibank export can fail when uploaded as a CSV. Converting to a .qbo and, where needed, splitting by month or quarter keeps each file inside that limit. The converter checks every batch against your file total, so nothing is dropped when you split a long Citibank history across several files.