How to Import Credit Card Transactions Into QuickBooks Desktop

Short answer: QuickBooks Desktop imports credit card transactions only from a .qbo Web Connect file, through Banking, Bank Feeds, Import Web Connect File. No version of Desktop, in any year, imports a CSV or Excel file of card transactions. If your card issuer offers a QuickBooks download, use it. If it only exports CSV, convert the CSV to a .qbo file first (the tool at the top of this page does exactly that, with a credit card account type), then import.

Last updated July 2026. This is one of the most common dead ends in Desktop bookkeeping: the card statement arrives as a CSV, QuickBooks refuses to touch it, and the fallback is hand-keying a month of charges. The fix takes about five minutes once you know the route.

Why can't QuickBooks Desktop import a credit card CSV?

Because Desktop's bank feed was built around the Web Connect standard, and Intuit never added a CSV path. QuickBooks Online has a built-in CSV uploader; Desktop does not, and it is not coming, since Intuit's development effort moved to Online years ago. The only file Desktop's Bank Feeds Center accepts is a .qbo file, which is an OFX-format document carrying the account type, the card number's last digits, and each transaction with a unique ID that powers duplicate detection. Everything in this guide is about getting your card activity into that format.

Step by step: import credit card transactions with a .qbo file

First, get the .qbo. Sign in to the card issuer's website and look for a download option labeled QuickBooks, Web Connect or .qbo. If the issuer only offers CSV or Excel, upload that export to the converter at the top of this page, set the account type to credit card, and download the .qbo it produces.

Then, in QuickBooks Desktop: go to Banking, Bank Feeds, Import Web Connect File and choose the .qbo. QuickBooks asks which account to link it to; pick your existing credit card account (or create one if this card is new to the file). Open the Bank Feeds Center, review the downloaded transactions, add or match each one, and you are done. Reconcile against the paper statement as usual at month end.

Which way do the signs go on a credit card import?

This is the mistake that quietly wrecks reconciliations. In a credit card account, charges increase what you owe and payments decrease it. A correct credit card .qbo file records purchases as negative amounts and payments or refunds as positive ones. Card issuers' CSV exports are wildly inconsistent about this: some list charges as positives, some as negatives, and some split them into separate debit and credit columns. Before importing, spot-check one known transaction, say a $50 charge, and confirm it lands in QuickBooks as money owed, not as a payment. A converter that understands credit card mode flips the signs for you; if you build the file any other way, this is the first thing to verify.

QuickBooks says the file is for a bank account, not a credit card

That is an account type mismatch inside the .qbo file. A Web Connect file declares its account type internally, and if the file says checking while your QuickBooks account is a credit card, Desktop will either refuse the match or push you to create a new account of the wrong type. Do not accept the new account; you will end up with card charges sitting in a fake bank account. Regenerate the file with the credit card type set correctly, then import again and link it to the right account. If you have already imported into a wrong account, the cleanup steps are in our guide to deleting imported bank transactions in QuickBooks.

Can I import several months of card activity at once?

Yes, and this is where the .qbo route genuinely shines. A Web Connect file can carry a long date range in one import, which makes it the practical tool for catch-up bookkeeping: a new client hands you a year of card statements, you convert them, and the whole year lands in the feed with duplicate protection intact. Two cautions. Import in chronological order if you split the work into multiple files, and check where your opening balances land so the earliest transactions do not double up against a beginning balance entry. Our walkthrough on importing older transactions into QuickBooks covers the date-range traps in detail.

What about statements that only come as PDFs?

Some issuers, especially for closed accounts or older periods, only provide statements as PDFs. A CSV converter cannot read those directly. For current accounts, check whether the transaction search screen has an export button even when the statements page does not; the CSV is often hiding there. For a stack of PDF-only statements, a dedicated tool can convert the PDF statement into a QuickBooks file, and from there the Desktop import works exactly as described above.

Should I use a bank feed or just enter charges by hand?

For a card with more than a handful of monthly transactions, the feed wins on both speed and accuracy. Hand-keyed entries carry typo risk, skip duplicate detection entirely, and take real time: a hundred charges is an hour of data entry versus a two-minute import. The feed also builds payee renaming rules as you go, so next month's import categorizes itself. Manual entry makes sense only for cards with two or three transactions a month, where setting anything up costs more than it saves.

Reconciling after the import

Once the transactions are added from the Bank Feeds Center, reconcile the card the normal way: Banking, Reconcile, pick the credit card account, enter the statement date and ending balance from the paper statement, and tick off the imported lines. If the difference is not zero, the usual suspects are a sign flip (a charge imported as a credit), a duplicate that slipped past because it was hand-entered before the import, or a missing transaction from a gap between file date ranges. Fix those and the reconciliation closes cleanly.

The bottom line: Desktop takes credit card activity one way only, as a .qbo Web Connect file. Download one from the issuer if you can, convert the CSV if you cannot. The full landing guide with issuer-specific notes is at credit card CSV to QuickBooks, and the general Desktop route is covered in CSV to QuickBooks Desktop. The converter at the top of this page handles the credit card sign conventions automatically, and three conversions are free, so you can verify the import against your own file before paying anything.