How to import a credit-card statement into QuickBooks

QuickBooks doesn't read PDFs. Banks don't send statements as anything else. That mismatch is the reason most bookkeepers I've talked to retype credit-card transactions by hand — sometimes hundreds of them per client. It doesn't have to be that way.

QuickBooks accepts two file formats for credit-card imports: .qbo (Intuit's flavour of OFX) and plain CSVwith a manual column mapping step. Convert the PDF to either one and you're done in minutes.

The short version

1. Download your credit-card statement from online banking as a PDF.
2. Run it through a converter (our free one is one option) and download the result as a .qbo file.
3. In QuickBooks: Banking → Upload from file, pick the .qbo, and assign it to the credit-card account.
4. Match the imported transactions, then mark the statement reconciled.

Step 1: Get the statement PDF

Every major bank lets you download statements as PDF, even when their in-browser transaction view only goes back ~90 days. Look in “Statements & documents” (Chase), “eStatements” (Bank of America), or “Statements” on the card management page (Amex).

If the bank gives you a choice between PDF and CSV: take the PDF anyway. The CSVs banks generate are usually limited to the last 30–90 days and often lack the trailing months you actually need for a year-end import.

Step 2: Convert PDF → QBO

QuickBooks .qbo files are a finicky text format (an Intuit-flavoured dialect of OFX). Hand-rolling one is unpleasant, which is why most people use a converter. The choice of converter mostly comes down to (a) does it produce a file QuickBooks actually accepts, and (b) does it get the sign convention right for credit cards.

Either upload to our converter or use a paid alternative like DocuClipper or MoneyThumb. With ours: drop the PDF, click the QuickBookstab on the results, hit Download. The file is produced server-side with signs already flipped to QuickBooks' convention (more on that below).

Step 3: Import in QuickBooks Online

From the QuickBooks Online sidebar: Transactions → Banking (or Bank transactions, depending on your version) → Upload transactions → pick your .qbo file → choose the matching credit-card account → Continue.

QuickBooks parses it instantly and drops the new transactions into your For Review queue. From there it's the same workflow as a bank feed — match the ones it auto-finds, categorise the rest.

Step 3 (alt): Import in QuickBooks Desktop

Desktop uses essentially the same flow: Banking → Bank Feeds → Import Web Connect File, pick the .qbo, choose the account it belongs to. The imported items land in the Bank Feeds Centre.

The sign-convention gotcha

Here's where everyone trips up the first time. In a credit-card .qbo file, purchases are negative and payments to the card are positive. Yes, that's the opposite of what your statement shows you visually.

It feels backwards but it's correct accounting: from the credit card liability account's perspective, a purchase is money going out (debit) and a payment is money coming in (credit). If you've only ever looked at credit cards through the consumer lens, this is genuinely counterintuitive. We wrote a whole short post on why credit-card payments come out negative if you want the full explanation.

Any converter that produces purchases as positive numbers in a .qbo file is broken — QuickBooks will import the data and quietly add to your liability every time you make a payment, the opposite of what should happen. It's the single most common reason “imported credit-card statements” produce wrong balances in QuickBooks.

Reconciling the import

Once the transactions are in QuickBooks, reconcile against the statement balance to confirm nothing went wrong. Pull up the credit-card register, click Reconcile, enter the statement's ending balance, tick off everything. If the ending balance ties to zero, you're done.

If it doesn't tie, the most likely culprits are: (a) a transaction that didn't come through in the import (rare with a good converter), (b) a date-range mismatch (you imported January but the statement period was 12/15 to 1/14), or (c) sign-flip wrong (which our converter checks for you before download — look for the ✓ balanced indicator).

One more thing: CSV as a fallback

If for any reason the .qbo path won't work, QuickBooks Online accepts a CSV import as well. The flow is the same (Banking → Upload transactions) but you'll manually map the columns: Date, Description, Amount. Our convertercan give you a Xero-style CSV with the sign-flipped Amount, which QuickBooks happily accepts. It's slightly more clicks than .qbo but works when you need it.

That's it

For a yearly catch-up: download 12 PDFs, run them through a converter, upload 12 .qbo files. The whole job is 20–30 minutes instead of the better part of a working day.