Guide

How to import a credit card statement into QuickBooks Online

Credit cards are where the statement-first approach pays off first, and usually where people hit the wall.

A business card that is still open and still connected has a working feed and is not the problem. The problem is everything else: the card that was closed last year and still needs its final statements booked, the card the client cancelled and cannot reconnect, the account where the feed brought in half of March, the personal card the owner used for business for three months before anyone noticed, and the twelve months of statements sitting in an email folder for a catch-up engagement.

None of those have a feed to fix. All of them have statements.

Get the statements first

Download the PDFs from the card portal, not from the client's phone. One multi-month download beats twelve email chases, and issuer portals usually keep statements far longer than a feed will backfill.

Two practical notes:

Extract the statement and confirm it is complete

Get the transactions out of the PDF, then check the set against the statement's own arithmetic before anything reaches QuickBooks. Previous balance, plus purchases and fees and interest, less payments and credits, equals the new balance printed on the statement.

That check is the whole reason the reconciliation at the end will be clean. If a month does not tie, resolve it there. A gap this early compounds into every month after it.

Card statements have a specific trap here: the summary block near the front repeats totals that also appear in the transaction detail. Anything reading the document has to know not to count them twice. Confirming the arithmetic catches that class of error immediately.

This is the step MatchLedger exists for. It pulls every transaction off the statement and checks the set against the statement's own opening and closing figures, so you find out whether anything is missing before the file goes anywhere near your books. See how it works.

Two dates, one transaction

This is the card-specific thing that trips up matching everywhere.

Card transactions carry a transaction date (when you swiped) and a post date (when the issuer settled it). They frequently differ, across a weekend, across a month end, and occasionally across a statement boundary. Your accounting software may hold one date, the statement shows another, and a perfectly legitimate match then looks like a mismatch.

Whatever tool you use, know which date it compared. MatchLedger shows this in Match Review: when two dates differ but the transaction is the same, it names which date it compared and shows the amount comparison alongside it, so a match is something you can check rather than something you have to trust.

Signs go the other way on a card

A bank account is an asset. A credit card is a liability. Money moving the same direction in real life produces the opposite sign on the two statements, and a purchase that looks like a debit on the card is an increase in what you owe.

It is a small thing that causes large messes, because a sign error does not look like an error. It looks like a transaction. MatchLedger checks this explicitly: bank to cash entries should agree in sign, credit card to liability should invert, and a pair that breaks its expected convention is flagged for a person to look at rather than being confirmed automatically. Treat it as a control, not a feature.

If you are reconciling several cards at once, also check that the tool tells you whichaccount it matched against. “Capital One ending 7330” is useful. “Card” is not.

Import into QuickBooks

Export the verified transactions as a QuickBooks-ready bank CSV. QuickBooks accepts a three-column layout (date, description, amount) or a four-column layout that splits credits and debits. Three columns is the simpler path.

MatchLedger writes that file for you. You pick the destination before exporting and the CSV comes out in that software's own column shape, date format and sign convention, so there is nothing to rework in a spreadsheet first. See the export formats.

In QuickBooks Online, go to Transactions, then Bank transactions, then Upload from file. Intuit moves this around, so check your current layout if it is not where you expect. Map the columns, assign the file to the credit card account, not a bank account, and the lines land in For Review.

If the card account does not exist yet, create it as a Credit Card type first. Importing card activity into an account typed as a bank account is fixable, but it is an hour you did not need to spend.

Let QuickBooks match and code it

Once the lines are in For Review, QuickBooks does the next part and it is already in your subscription:

The card payment itself is worth handling deliberately: the payment appears on both the bank statement and the card statement, once as money leaving the checking account and once as a credit reducing the card balance. It is a transfer, not an expense, and it is the single most common duplicate in card cleanup.

There is a fuller walkthrough of both features in the bank rules and auto-match guide.

Reconcile the card

Run QuickBooks' reconcile for the card account, one statement period at a time, against the statement's closing date and new balance.

Because you imported a set that was already proven complete, the reconciliation ties out with nothing missing and nothing duplicated. Whatever difference remains is the balance of your clearing account, meaning items still waiting on a decision or a document, which is visible open work rather than a mystery.

Calibrated honestly: the completeness is automated and proven, the open items are judgment work. Nothing here makes the judgment calls for you.

You can also do that check before QuickBooks ever sees the card. Give MatchLedger the account ledger for the period alongside the statement and it reconciles the two against each other rather than against a balance you typed in: one-to-one matching, so a transaction can only settle once; near-miss handling, so a fee-shaved amount does not read as missing; and a matched, missing and duplicate report naming the actual card, not just “credit card”. On a multi-card cleanup that is the difference between finding the problem now and finding it at close. See how reconciliation works.

If you only want the spreadsheet

Plenty of people arrive at this needing the data, not the bookkeeping. Expense reports, a spending review, or handing twelve months of card activity to an accountant.

That path stops after the extraction step. You get a CSV that opens straight in Excel or any spreadsheet, with the transactions from the statement, and you are done. To be exact about what the file is: it is a CSV, not an .xlsx workbook. There is a page for that path if bookkeeping is not what you came for.

Other accounting platforms

Xero, FreshBooks, Wave and Sage all accept a bank CSV and the general shape of this workflow should carry over. We have not tested how each one's matching and rules behave against an imported card statement the way we have with QuickBooks Online, so take the QBO steps as tested and verify the rest on your own first month.

Try it on your worst card

Pick the closed one, or the one with the missing months.

MatchLedger reads the credit card statement PDF or CSV, proves the extracted set ties to the statement's own balances to the cent, matches one-to-one against your account ledger with the date and sign checks above, and exports the CSV QuickBooks expects. Large and multi-month jobs run in the background, so a stack of statements does not time out. Any bank or card issuer works, in any country, PDF or CSV, scans included. There are no per-bank templates for you to pick or set up, and if a layout ever reads wrong, we build support for it free.

Common questions

How do I import a credit card statement into QuickBooks Online?

Extract the transactions from the statement into a QuickBooks-ready CSV, then in QuickBooks Online go to Transactions, then Bank transactions, then Upload from file. Map the columns and assign the file to the credit card account rather than a bank account. The transactions land in the For Review tab, where QuickBooks' matching and bank rules can process them.

Can I import a card statement if the card is closed?

Yes, and this is the most common reason to do it. A closed card has no feed to connect, but the issuer's statements still exist in the portal or in your records, and they contain every transaction for the period. Statement import is the only route for closed, cancelled or credential-restricted accounts.

Why do the dates on my card transactions not match my books?

Card transactions carry both a transaction date, when the purchase happened, and a post date, when the issuer settled it. They often differ by a few days and sometimes across a month end. Matching tools compare one of the two, so a genuine match can look like a discrepancy. MatchLedger's Match Review names which date it compared and shows the amount comparison next to it.

Do I get an Excel file or a CSV?

A CSV. It opens straight in Excel, Numbers or any spreadsheet application, and each statement comes back as its own file. If you upload several statements at once, they come back as a set of CSV files.

How do I avoid double-counting the card payment?

The payment to the card issuer appears on both statements, as money leaving the checking account and as a credit reducing the card balance. Record it as a transfer between the two accounts rather than as an expense, and when both sides are imported, use QuickBooks' Match rather than Add on the second one.

Will this work for personal cards used for business?

The extraction and import work the same way regardless of who the card belongs to. How you treat mixed personal and business activity in the books is an accounting decision, and the usual approach is to import the full statement so the account reconciles, then classify the personal lines to owner drawings or a similar account rather than leaving them out.

Keep reading

Start with the card that has no feed. 30-day trial, no credit card required.

Start Free