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.

Yes, and the accuracy check is the point. Before the .qbo downloads, the converter adds up every transaction it parsed and compares that to the total in your Citibank CSV. If a row is missing or misread, you see it in the preview instead of finding it during reconciliation. Working from a different bank? Use the CSV to QuickBooks Online converter for any account, turn a spreadsheet into a .qbo with the Excel to QBO converter, handle a stack of statements with the bulk CSV to QBO converter, compare the best CSV to QBO converters on price, switch to the Chase CSV to QBO converter, Capital One CSV to QBO converter, Bank of America CSV to QBO converter, or Wells Fargo CSV to QBO converter for those accounts, read the step-by-step Citibank CSV to QuickBooks guide, or follow how to import the .qbo file into QuickBooks once it is built.

Intuit has moved this menu, and both versions are still live depending on the account, so check for whichever one you see. The current path is All apps, then Accounting, then Bank transactions, and from there Link account followed by Upload from file. Older accounts still show Transactions and then Bank transactions in the left menu, which reaches the same screen. Pick the account the transactions belong to, upload the .qbo, and the rows land in the For review tab rather than posting straight to your books.

Review is where the work actually happens. QuickBooks proposes a category for each row, and accepting those proposals without reading them is how a Citi card ends up with six months of transactions in Uncategorized Expense. Work through the review queue before you reconcile, and set up bank rules for the merchants that repeat, because a Citi card statement is mostly the same twenty vendors every month.

Use MM/DD/YYYY for a United States QuickBooks company file. This sounds obvious until you follow Intuit's own help article on CSV formatting, because the version that ranks highest in search is the global edition and it recommends DD/MM/YYYY. Apply that to a US company file and every transaction dated the first through the twelfth of a month posts to the wrong month, with no error message to tell you.

Opening the Citi export in Excel introduces its own traps. Two digit years from 00 to 29 resolve to 2000 through 2029 while 30 to 99 resolve to 1930 through 1999, so an older file can land decades out. Windows Excel defaults to the 1900 date system and Mac to 1904, so a workbook passed between the two shifts every date by four years and a day. The converter normalizes dates as it writes the .qbo file, which removes the whole category of problem, but it is worth recognizing if something looks wrong in a report later.

Because a credit card account reverses the meaning of a positive number. On a checking account a positive amount is money in and a negative amount is money out. On a credit card the account is a liability, so a purchase increases what you owe and a payment decreases it, and a file built for a checking account will post every charge as though it reduced your balance.

The signature of this problem is a reconciliation difference exactly equal to twice the value of the transactions involved, because each one is wrong by its own amount in both directions. If you see that pattern after importing a Citi card file, do not adjust transactions one at a time. Convert the file again against the correct account type and re import, which fixes every row at once. Use a minus sign for negatives rather than parentheses, since QuickBooks reads a minus sign and does not reliably read brackets.

Not once it is a .qbo. Every transaction in a .qbo file carries a FITID, a transaction identifier unique within the account that is never reused. QuickBooks records the identifiers it has accepted and skips them on any later import, and it keeps that memory even after you delete the transaction. That is what makes re importing a converted file safe when you are not sure a batch went in cleanly.

A raw CSV gives you none of that protection. There is no transaction identifier anywhere in a plain CSV, so QuickBooks cannot recognize a row it has seen before and importing the same Citi export twice posts everything twice. If you are catching up several months of Citi activity and expect to re run at least one batch, that single difference is the strongest reason to convert rather than upload the spreadsheet directly.

Read the size of the difference before you start hunting line by line, because the number itself usually names the cause. A difference that divides evenly by nine means transposed digits somewhere. A difference exactly equal to twice a single transaction means a sign flip, which on a Citi card almost always means the credit card reversal described above. A difference matching one transaction exactly means a row either failed to convert or was accepted twice.

If none of those fit, check the date range boundaries first. Citi exports are frequently pulled in overlapping windows, and an overlap is the most common way a transaction gets counted once in each of two files. Compare the first and last dated transaction in the imported batch against the statement, and confirm the opening balance matches the statement's opening figure rather than whatever QuickBooks carried forward.

Use whichever one you can rely on for the period you actually need. A live feed is less work when it runs, but a newly connected feed commonly reaches back only about 90 days, which is not enough if you are catching up a year. A converted .qbo file has no such limit, so file import is the route for backfilling history and for any period the feed missed.

Many bookkeepers run both, and that is a reasonable setup rather than a compromise. Let the feed handle the current month, and use converted files for anything older or for the gaps that appear when a connection drops. Since QuickBooks deduplicates on the FITID, transactions the feed already brought in will not double up when a file covering the same dates goes in behind it.