# How to Import a Credit Card Statement into QuickBooks

_Canonical: https://qbomaker.com/blog/import-credit-card-statement-quickbooks.html_

Importing a credit card statement into QuickBooks needs two things to be exactly right: the file must be wrapped in a credit-card OFX envelope (not a bank-account one), and the amount signs must match how QuickBooks treats charges versus payments. Convert your statement CSV or Excel export to QBO with the correct envelope, and your charges, payments, and balance import cleanly the first time.

## Why credit card statements are different from bank statements
QuickBooks stores a credit card as a liability account, while a checking account is an asset. That difference shows up inside the import file. A bank statement is wrapped in a bank-account envelope (<BANKMSGSRSV1> → <STMTRS> → <BANKACCTFROM>), but a credit card statement must use the credit-card envelope (<CREDITCARDMSGSRSV1> → <CCSTMTRS> → <CCACCTFROM>).If you wrap credit card data in a bank envelope, QuickBooks will either refuse the file, try to match it to the wrong account type, or post your purchases as deposits. Getting the envelope right is the single most important step.

## The amount-sign rule that trips everyone up
Inside the file, each transaction carries a <TRNAMT> value with a sign. For a credit card account the convention is:Charges and purchases → negative (they increase what you owe).Payments and statement credits → positive (they reduce your balance).Most bank CSV exports already follow this, but plenty list every charge as a plain positive number, or split debits and credits into two separate columns. If you import without fixing the signs, QuickBooks shows payments as charges and your ending balance is the mirror image of reality. When you set up the conversion at the converter, double-check that purchases come through negative before you generate the QBO.

## Step by step: CSV to QBO for a credit card
Download your statement as CSV or Excel from your card issuer's site. (QBO Maker also reads text-based PDFs; for a scanned or image-only PDF, export the transactions to a spreadsheet first.)Open the converter and drop in your file. Nothing uploads, conversion runs entirely in your browser.Choose “Credit card” as the account type so the file is built with the credit-card envelope.Map your columns: date, description, and amount (or separate debit/credit columns). Confirm the sign of charges is negative.Enter a credit card account number or any identifier for ACCTID, this only labels the file for matching.Generate the .QBO file and download it.In QuickBooks, go to File → Utilities → Import → Web Connect Files (Desktop) or Banking → Upload from file (Online), and select the credit card account.For the QuickBooks Online side in detail, see importing CSV into QuickBooks Online.

## Handling two-column debit/credit statements
Many card issuers export with one column for purchases and another for payments instead of a single signed amount. That is fine, you don't have to merge them by hand. During mapping, point the converter at both columns and tell it which one is money out and which is money in. It combines them into one correctly signed <TRNAMT> per transaction, so charges land negative and payments land positive automatically.

## Common errors and how to fix them
Everything imports as a charge (or as a payment). The signs are flipped, re-run with the charge column set to negative.QuickBooks won't match the account. You likely used a bank envelope, or selected a checking/savings account during import. Regenerate as a credit card file and pick the credit card account.Duplicate transactions. The date range overlaps a prior import. Trim the CSV to only new rows before converting.“The file you selected can't be read.” Usually a malformed date or a stray currency symbol. Run the output through the OFX/QBO validator to catch structural issues before importing.

## QBO, QFX, or OFX for a credit card?
All three formats use the same credit-card envelope and sign rules; the difference is which software accepts them. Use .QBO for QuickBooks, .QFX for Quicken (see CSV to QFX), and plain .OFX for most other accounting tools (see CSV to OFX). The converter sets the right envelope and signs for whichever format you pick, so you can convert the same statement once for QuickBooks and again for another tool without re-doing the column mapping. Start your conversion here.

**Do credit card charges import as negative or positive?**
On a credit card account, charges and purchases should be negative because they increase your balance owed, while payments and statement credits should be positive. If your imported balance looks inverted, the signs were reversed during mapping, regenerate the file with charges set to negative.

**Can I import a PDF credit card statement into QuickBooks?**
QBO Maker reads CSV, Excel and text-based PDFs. If your issuer only offers a scanned or image-only PDF, copy or export the transactions into a spreadsheet first, then convert that to a credit-card QBO file at the converter.

**Why does QuickBooks say the account types don't match?**
This happens when a credit card statement is wrapped in a bank-account OFX envelope, or when you point the import at a checking account. Generate the file as a credit card type so it uses the <CREDITCARDMSGSRSV1> structure, and during import select your credit card account.

**My statement has separate columns for charges and payments. Will that work?**
Yes. Map both columns during conversion and indicate which is money out (charges) and which is money in (payments). The converter merges them into one signed amount per transaction automatically, no manual math required.

**Is my credit card data uploaded anywhere?**
No. The entire conversion runs in your browser. Your statement file never leaves your computer and nothing is sent to a server, which matters when the file lists every purchase on your card.

---
Convert free at https://qbomaker.com/#tool, runs entirely in your browser.
