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

The table above is the part worth checking before you download anything, because no two US issuers agree on what a card export should look like. Some write one Amount column with a sign on it, some write separate Debit and Credit columns, and they do not agree on which direction a purchase points. The converter detects both layouts and both conventions on upload, so you do not have to normalize the file by hand, but if you are mapping columns manually in QuickBooks Online it is the difference between a clean import and a register that reads backwards. Issuer portals also get redesigned, so treat the location column as a starting point rather than a permanent address.

Convert your card's CSV or Excel export to a .qbo file using the converter above, then open Bank transactions in QuickBooks Online. Newer accounts reach it through All apps and Accounting, older ones through 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 from the bank transactions screen, reached through All apps, Accounting, Bank transactions, then Link account and Upload from file, or through the older Transactions, Bank transactions menu if that is what your account shows, 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 Bank transactions, which sits under Transactions in the classic navigation and under All apps then Accounting in the newer one. 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.

Reconcile to the statement, not to the calendar. A credit card closes on a cycle date that is almost never the last day of the month, so the balance QuickBooks shows on the 31st will not match anything the issuer printed. In QuickBooks Online go to Settings, then Reconcile, pick the card account, and enter the ending balance and ending date exactly as they appear on the statement. In Desktop it is Banking, then Reconcile.

Importing the full cycle first is what makes this quick. When every charge and payment is already in the register, reconciling a card is a matter of ticking items until the difference is zero, usually a few minutes. When half the charges were keyed in from a receipt pile, you spend the time hunting instead. If the difference will not clear, the usual culprits are a payment recorded in the checking account but never linked to the card, a charge that posted in a different cycle than it was made, and a duplicate created by importing an overlapping date range twice.

You can, and it is worth thinking about for a minute before you upload. QuickBooks matches on date, amount and description, so a transaction that arrives from both the live feed and your file usually gets flagged as a match rather than added twice. Usually is not always: descriptions frequently differ between the feed and the CSV for the same charge, and when they do you get two entries.

The safe pattern is to check the date of the oldest transaction the feed already pulled, then convert and import only the period before it. That is the normal reason to import a card file at all, since a feed typically reaches back about 90 days on first connect while a file import has no date limit. If duplicates do appear, exclude them from the For review tab before you accept anything, because removing them after they have been categorized and reconciled is considerably more work.

Yes, and how you handle them is a bookkeeping decision rather than a conversion one. Most issuers export every cardholder on the account into a single file, often with a cardholder name column alongside the description. Converting that file brings all of it into the one card account in QuickBooks, which is correct, because the debt is one balance owed to one issuer.

If you need spending broken out by employee, use classes or a custom field rather than creating a separate QuickBooks credit card account per cardholder. Separate accounts will not reconcile, since the issuer only ever gives you one statement balance for the whole account. Keeping the cardholder detail in the description or memo also means you can search it later, which matters when somebody asks in November what a charge in March was for.

Record them, do not delete them. The charge happened, it is on the statement, and the statement is what you reconcile to, so removing the transaction guarantees the account will never tie. Import everything, then categorize the personal charges to Owner's Draw or a Due from Officer receivable depending on the entity type and how the money will be settled.

The reason this matters beyond tidiness is that a card account that has had inconvenient transactions deleted out of it is a card account nobody can reconcile, and it tends to be discovered a year later by whoever is preparing the return. Categorizing a personal charge takes one click. Explaining a card account that is $3,000 off takes an afternoon.

Cash back redeemed as a statement credit reduces the card balance, so it imports as a positive amount, the same direction as a payment. The question is what it offsets. The common treatment is other income or a reduction of the expense category the rewards were earned on, and either is defensible as long as you pick one and stay with it.

What you should not do is leave it uncategorized or lump it in with vendor refunds, because rewards and refunds behave differently at year end and a preparer will want to see them apart. Points redeemed for travel or merchandise rather than cash generally do not create a bookkeeping entry at all, since no money moved through the account.

Yes, and for Desktop it is the only route that does not involve typing. QuickBooks Desktop cannot import a bank or card CSV in any version, which surprises people who assume the more expensive product does more. It imports .qbo Web Connect files, so converting is not a shortcut, it is the mechanism. Set the card up as a Credit Card type account first, then import and point the file at that account.

One Desktop specific caution: a .qbo file downloaded straight from your issuer often fails to import because of the institution identifiers baked into it, the FID, INTU.BID and BANKID values, rather than anything wrong with the transactions themselves. A file converted from CSV sidesteps that entirely, which is why converting a CSV frequently works when the issuer's own QBO download does not. The CSV to QuickBooks Desktop page covers the Desktop side in more detail.

Save the Excel workbook as it is and upload the .xlsx to the converter at the top of this page; it reads the date, description and amount columns straight from the worksheet, applies the credit card sign convention so charges post as charges, and returns a .qbo you import through Bank transactions, Upload from file (QuickBooks Online) or Bank Feeds, Import Web Connect File (QuickBooks Desktop). Going through Excel is often the cleaner route when the card issuer's CSV has a summary block, a running balance column or merged header rows, because you can delete those rows in the workbook first and keep one header row above the transactions. QuickBooks Online's own upload screen also accepts a spreadsheet, but only in its strict 3-column or 4-column layout with a 1,000 transaction and 350 KB ceiling, and QuickBooks Desktop cannot import a spreadsheet of bank transactions at all, so the .qbo route is the one that works on both products. The Excel to QBO converter page covers workbook-specific traps such as two-digit years and the 1904 date system on Mac.

Try it free with three conversions and no account. Paid plans start at $49 per month, or $24.50 per month billed yearly, for 100 conversions. Plus is $149 per month, or $74.50 yearly, for 500 conversions, with every conversion saved to your account history. Pro is $499 per month, or $249.50 yearly, for unlimited conversions with API access. A business cleaning up one or two card accounts is normally fine on Starter; a bookkeeper running card imports for many clients each month usually wants Plus for the higher monthly allowance.