Chase Credit Card Statement to QuickBooks

Download your Chase credit card activity as CSV

Chase's card downloads live in a different place than the checking export covered on our Chase CSV to QuickBooks page. Sign in at chase.com, open the credit card account, and go to the account Activity view. Use the download icon (often shown as a small download or export control near the activity list), choose a date range, and pick CSV / Spreadsheet as the format.

• Chase card CSVs typically have the columns Transaction Date, Post Date, Description, Category, Type, and Amount — note the two date columns, unlike a checking export.
• Chase caps each download at roughly 24 months of history (and about 1,000 rows per download), so older statements may need to be pulled in batches.
• If Chase offers a direct .QBO/QuickBooks (Web Connect) download for your card and it imports cleanly, you may not need a converter at all. Chase doesn't always offer Web Connect on credit cards, though, so when only CSV is available, or the direct file is incomplete, that's where QBO Maker comes in.

The credit-card sign convention that flips everything

This is the single biggest gotcha with card data. On a credit card, a charge increases what you owe, and a payment reduces it — the opposite of a checking account, where a debit reduces your balance. Chase's Amount column reflects this in its own way: purchases usually export as negative numbers and payments/credits as positive.

QuickBooks reads a credit card file so that charges should raise the liability. If the signs come through the wrong way for your card register, your charges land as if they were payments and your balance runs backwards. QBO Maker doesn't silently re-orient the numbers based on account type — it keeps your amounts as exported and, when you convert as a credit-card account, flags that card statements often need flipping. If your charges would import as payments, turn on the Flip plus and minus signs option and reconvert. Always sanity-check a couple of known rows (a recent purchase and your monthly payment) after conversion.

Convert the CSV to a .QBO as a CREDITCARD account

Open the converter pre-set for a card: convert as a CREDITCARD account. This tells QBO Maker to write a credit-card account type into the file instead of a bank (checking) type, so the transactions land in your card register.

1. Drop your Chase card CSV (or Excel) onto the converter.
2. Confirm the auto-detected mapping. For Chase cards, use Transaction Date as the date and Amount as the signed amount; Post Date, Category, and Type are ignored.
3. Make sure the account type shows CREDITCARD (not BANK). This is what keeps QuickBooks from treating the file as a checking feed. If the preview warns that charges may import as payments, tick Flip plus and minus signs.
4. Choose .QBO as the output and download. You can also export QFX or OFX if your software prefers those.

Want to confirm the file before importing? Drop it into the free OFX/QBO validator to check the structure and account type.

Import the .QBO into QuickBooks

In QuickBooks Online: go to Transactions → Bank transactions, choose the credit card account (or add it), and use Upload from file to select your .QBO. If the card account doesn't exist yet, create it as a Credit Card type first so the transactions attach to a liability account rather than a bank account.

In QuickBooks Desktop: use Banking → Bank Feeds → Import Web Connect File and select the .QBO, then link it to the credit card account when prompted. After import, review the matched and new transactions before accepting them. For the full upload walkthrough and screen-by-screen detail, see importing CSV into QuickBooks Online.

Common credit-card import problems

• Charges show up as payments. The signs are oriented the wrong way for your register — reconvert as a CREDITCARD account with Flip plus and minus signs turned on, then spot-check a known purchase.
• File imports into a bank account. The account type was BANK; rebuild it as a credit card so QuickBooks offers it for the card register.
• Duplicate transactions. Overlapping date ranges across downloads are the usual cause. Pull non-overlapping ranges and review matches at import. See avoiding duplicate transactions.
• Generic import errors. Malformed rows, stray columns, or odd date formats can break the file — the converter usually fixes these, but our CSV import error guide covers the rest.

This page covers Chase specifically; for the sign rules and card concepts across all issuers, read the broader import a credit card statement into QuickBooks guide.

Frequently asked questions

Related