Import Credit Card Transactions into QuickBooks Online: Convert Credit Card CSV to QBO

Convert your card's CSV or Excel export to a .qbo file using the converter above, then in QuickBooks Online go to Transactions, Bank transactions, pick the credit card account, and choose Upload from file. Select the .qbo and QuickBooks imports every charge and payment into the review queue for that card.

Because a credit card is a liability account, so a payment lowers the balance and a charge raises it, the opposite of a checking account. When a CSV lists charges as positive and payments as negative, QuickBooks reads them in reverse. Converting to a .qbo sets the sign QuickBooks expects, so charges and payments land on the correct side.

For a credit card account, charges (money you spent) import as negative and payments or credits as positive. Many issuer CSVs use the opposite convention, which is the usual cause of a reversed import. When the converter builds the .qbo, it writes each amount with the sign QuickBooks expects for a card register, so you do not flip them by hand.

You have two routes. Upload the CSV directly under Transactions, Bank transactions, Upload from file, then map the date, description, and amount columns and confirm the signs, or convert the CSV to a .qbo first and upload that. The .qbo route skips column mapping and sets the charge and payment signs for you.

Yes, as long as you have the activity as a CSV or Excel file. Download your card's statement period as a CSV from the issuer's website, then convert it to a .qbo with the tool above. The converter cannot read a PDF statement, so export the transactions as CSV or Excel first, which every major US issuer offers.

In QuickBooks Online open Transactions, then Bank transactions, select the credit card account, click the arrow by Link account, and choose Upload from file. Add your CSV, map the columns, and confirm charges are negative. If the mapping or signs fight you, convert the CSV to a .qbo first and upload that instead.

The common blockers are a wrong column count, mixed or non-US date formats, dollar signs or commas inside amounts, files over 350 KB, and reversed charge and payment signs. QuickBooks stops at the first row it cannot read. Converting the CSV to a .qbo applies the format and signing rules before import, so the file QuickBooks receives is already correct.

Yes. QuickBooks Desktop does not take a raw CSV for a credit card without an add-on, but it imports .qbo Web Connect files directly. Convert your card CSV to a .qbo, then go to File, Utilities, Import, Web Connect Files, and select the card account. The same .qbo works for both QuickBooks Online and Desktop.

A direct CSV upload is capped at 350 KB, roughly a thousand rows, so a long card history often has to be split. A .qbo import is not held to that CSV size limit, so converting lets you bring a full year of card charges and payments into QuickBooks in one file instead of several.

Yes. A refund or return is a credit to the card, so it imports as a positive amount, and interest or an annual fee is a charge, so it imports as a negative. The converter signs each line by whether it raises or lowers the card balance, so refunds, fees, and interest all land on the correct side without manual fixes.

After the .qbo imports, every charge and payment sits in the For review tab of that credit card account. QuickBooks suggests a category and matching rule for each, and you accept, edit, or create a bank rule to auto-categorize repeat vendors. Importing only brings the transactions in; you still review and post them like any bank feed.

This is the most common credit card import problem, and it comes from how QuickBooks treats the account. A credit card is a liability: spending raises what you owe, paying lowers it. So in the card register a charge must reduce your available balance (a negative line) and a payment must increase it (a positive line). Card issuers, though, often export the opposite, listing purchases as positive amounts. Upload that CSV as is and QuickBooks faithfully reverses everything, turning charges into payments. The fix is to set the sign before import, which is exactly what the converter does when it writes the .qbo, so you never paste a times-negative-one formula down a column again.

The converter reads CSV and Excel files, not PDF statements, so start from the transaction download rather than the printable statement. Every major US issuer offers it: in Amex, Chase, Capital One, Citi, or your bank's card portal, open the card, set a date range, and download activity as CSV or Excel. That file has clean date, description, and amount columns the converter can read. A PDF statement is an image of the same data and has to be left out of this workflow.