How to import a credit card statement into QuickBooks Online and Desktop (and get the signs right)

The short answer: how to import a credit card statement into QuickBooks

In QuickBooks Online, create the account with the Credit card account type, then go to Bank transactions, choose Link account → Upload from file, and upload a 3-column or 4-column CSV, a .qbo file, or the statement PDF. In QuickBooks Desktop, use Banking → Bank Feeds → Import Web Connect Files for a .qbo, or File → Utilities → Import → IIF Files for an IIF. Whatever the route, charges must reduce what you have (negative) and payments and refunds must increase it (positive), seen from your side, not the card issuer’s.

Set up the credit card account in QuickBooks Online first

The single most useful thing you can do before uploading anything is make sure the destination is a credit card account and not a bank account. Intuit’s CSV formatting page says it plainly: select the credit card account, not a bank account, when you upload. A card file uploaded into a checking account will import, and every number will mean the opposite of what it should.

1. 1Go to All apps → Accounting → Chart of accounts and select New account.
2. 2Enter an account name you will recognise, such as “Visa ending 4417”.
3. 3Set Account type to Credit card and pick the detail type.
4. 4Enter the Opening Balance and the As of date. For a card, the opening balance is what you owed on that date, taken from a statement.
5. 5Select Save.

If you connect the card to a bank feed, QuickBooks can create the account for you. That is fine, but check the account type on the Chart of accounts afterwards, and check the opening balance date, because both affect every upload you do later.

Why credit card imports flip charges and payments

A card statement is written from the issuer’s side. To the issuer, your purchase is money you owe them, so it is printed as a positive amount, and your payment reduces the debt, so it is printed as a negative amount or in a “credits” column. Many issuers’ CSV downloads keep that convention. Intuit’s own note on CSV files says the same thing: credit card files may show transactions in reverse, and payments may appear as negative amounts because paying the card reduces the balance.

QuickBooks Online’s upload reads a single Amount column the other way: negative for money out, positive for money in. Feed it the issuer’s signs and a $84.20 office supply charge becomes an $84.20 payment received, a $1,240.18 payment becomes a $1,240.18 charge, and the account balance moves in the wrong direction from the first row. Intuit Community threads on this go back years, and the fix that works in them is always the same: get the signs to the cardholder’s side before the import is accepted.

A quick test before you upload: purchases, fees and interest should be negative, and the payment and any refund should be positive. If the file shows the reverse, either flip the signs (in Excel, multiply the Amount column by -1 in a helper column and paste the results back as values) or use the reverse option QuickBooks offers during the upload, described next.

Upload credit card transactions to QuickBooks Online from a CSV file

Intuit’s “Manually upload transactions into QuickBooks Online” page (updated August 2026) sets the rules for a QuickBooks credit card CSV import: the file must be in English, 350 KB or smaller, with up to 1,000 transactions per upload, and it needs either 3 columns (Date, Description, Amount) or 4 columns (Date, Description, Credit, Debit). Larger statements go in smaller date ranges.

The 4-column layout looks safer because there are no minus signs to get wrong, but on a card it hides the same trap. On a card statement, “credit” means a payment or refund to your card account and “debit” means a charge. When you map the columns, the issuer’s credits are money coming into the card account and its charges are money going out. Check the preview rather than trusting the header names.

1. 1Go to All apps → Accounting → Bank transactions and select the card’s tile if you see one.
2. 2Select the Link account ▼ dropdown, then Upload from file. If the card is not connected to a feed, you may see “Or upload transactions manually” instead.
3. 3Drag in or select the CSV and select Continue.
4. 4Choose the credit card account as the QuickBooks account and select Continue.
5. 5Answer the questions about the header row and the date format, then map the file’s columns to Date, Description and Amount (or Credit and Debit), and select Continue.
6. 6On the next screen, check whether the amounts show correctly as positive or negative. If they are reversed, select reverse all values.
7. 7Select the transactions to import, select Continue, then Yes and Done.

Before the upload, delete any title rows, account summaries or totals above or below the transactions. The first row should be the column headers and nothing else, and a “Total” row at the bottom will import as a transaction.

Web Connect (.qbo) files for credit cards

A .qbo file avoids the mapping step entirely. It is an OFX file with an Intuit bank ID, and a credit card file uses the card statement blocks (CREDITCARDMSGSRSV1, CCSTMTRS and CCACCTFROM) rather than the bank ones. Amounts are already signed from the cardholder’s side, so charges are negative and payments positive, and every transaction carries a FITID, the identifier QuickBooks uses to recognise a transaction it has already seen.

Intuit’s upload page lists .qbo first among recommended transaction files for QuickBooks Online, alongside QFX, OFX and CSV, and the steps are the same as for a CSV, minus the column questions. If your issuer offers a QuickBooks download for the card, it is usually the better choice than its CSV. Our explainer on Web Connect files covers what is inside one and why the bank ID matters.

Import a credit card statement into QuickBooks Desktop

QuickBooks Desktop has no CSV upload for bank or card transactions. Intuit’s Desktop import page points bank data to Web Connect (.qbo) files, and its batch entry feature, which accepts rows pasted from Excel or CSV into a credit card register, is limited to QuickBooks Enterprise and QuickBooks Accountant Desktop. For Pro and Premier, the practical ways to import credit card statements into QuickBooks Desktop are Web Connect and IIF.

1. 1Back up the company file.
2. 2Download or create the card’s .qbo file.
3. 3Go to Banking → Bank Feeds → Import Web Connect Files, select the file and select Open.
4. 4Choose Use an existing account and pick the card account (or Create a new QuickBooks account if it is not set up yet), then Continue.
5. 5Select OK when QuickBooks confirms the data was read, then review and add the transactions in the Bank Feeds Center.

IIF is the other route, and it is the only one that needs no bank ID at all. It writes transactions straight into the register without the Bank Feeds review step, which is why it suits history a feed or Web Connect cannot reach. Intuit warns that IIF import does only limited error checking and that Intuit does not provide assisted support for creating IIF files. Its import path is File → Utilities → Import → IIF Files, signed in as admin in single-user mode, after a backup.

Intuit’s sample refund file shows the pattern: the TRNS line puts +15 on the card account and the SPL line puts -15 on the expense account, so the two sides balance to zero. A charge is the mirror image. Declare the card account with ACCNTTYPE CCARD, or create it in QuickBooks first, because an IIF file that names an account QuickBooks does not have can create it with the wrong type; Intuit’s sample files declare their accounts first for exactly this reason. Payments to the card are usually not card transactions at all: they are recorded once, as a check or transfer from the checking account. Our comparison of IIF and QBO for Desktop goes deeper on when each is the right file.

Duplicates when a bank feed overlaps an upload

When you upload credit card statements to QuickBooks for a card that also has a feed, duplicates almost always come from two sources covering the same days. A feed downloads its own copy of each transaction, and an uploaded file brings another. QuickBooks Desktop refuses to import a Web Connect transaction with an ID it has already seen, according to Intuit’s “Nothing imported” article, but a feed’s IDs and a converted file’s IDs will not agree, and a CSV or IIF has no IDs at all. Your date range is the only real protection.

• Before uploading, look at the account register and find the last transaction already in QuickBooks. Intuit’s rule for an account with existing transactions is to start the upload the day after it.
• When you connect a feed after uploading history, Intuit recommends choosing a start date immediately after the most recent transaction already in the account.
• Upload whole statements, from the day after one closing date to the next closing date. Statements line up end to end, which makes gaps and overlaps obvious.
• If duplicates are still in For review, select them and choose Exclude rather than adding them.
• Card payments are the classic hidden duplicate. The payment appears in the checking account feed and again in the card feed. Record it once as a transfer between the two accounts and match the other side to it, instead of categorising both as expenses.

Statements older than the bank feed provides

Intuit’s connection page says download history varies by bank, from 90 days up to 24 months. To import a credit card statement into QuickBooks from before that window, you upload it, and Intuit’s own upload page names this as one of the two reasons to upload at all. Older months are where people end up with a PDF and nothing else, because issuers’ download tools often reach back less far than their statement archives.

• QuickBooks Online now accepts a PDF or image statement directly under Upload from file, for English-language statements. It shows the statement and the extracted data side by side for you to correct, and Intuit notes some items may go to its experts for review before they are ready. For a handful of statements, try this first.
• If you need a file you can check before it touches your books, or you work in Desktop, convert the PDF to CSV, QBO or IIF and import that.
• Import the oldest statement first and work forward, so each month’s opening balance agrees with the previous month’s closing.
• Intuit’s rule for a brand-new account: go back as far as you want QuickBooks to track. For an account with an opening balance but no transactions: start on the opening balance date.

Watch the opening balance here. If the card account was set up with an opening balance as of January 1 and you now upload November and December of the previous year, those two months are already inside that opening balance. Move the opening balance back to the earlier statement, or the account will be overstated by exactly those transactions.

Reconcile against the statement’s new balance

Whichever route you used to import the credit card statement into QuickBooks, the job is only finished when the card account reconciles. In QuickBooks Online, go to All apps → Accounting → Reconcile (or Settings → Reconcile), choose the card account, and enter the Ending balance and Ending date from the statement. On a card statement those are the “New Balance” and the closing date. Tick each transaction that appears on the statement until the Difference is $0.00, then select Finish now. Intuit also offers an optional AI-powered reconciliation that reads an uploaded statement.

That summary box is your best check on the import itself. A card statement usually has no running balance, so the summary is the only total you can test against: payments and credits imported should match the printed figures, and so should purchases plus fees plus interest. If the Difference in the reconcile window is exactly twice a transaction, that transaction came in with the wrong sign. If it equals one transaction, it is missing or duplicated. If it is twice the period’s net activity, every sign is reversed, and the cleanest fix is to undo the import and upload again with reversed values.

Fixing an import that already went in the wrong way

1. 1If the transactions are still in For review, select them all and choose Exclude. Nothing has touched your books yet.
2. 2If they were added, select them in the Categorized tab and undo them, or delete them from the register, before importing again. Undo first, so the corrected file is not added on top.
3. 3Fix the source: flip the signs, swap the Credit and Debit mapping, or use reverse all values in the upload.
4. 4Upload again for exactly the same date range, then reconcile against the statement’s new balance.
5. 5In Desktop, restore the backup you made before the import. IIF imports in particular are hard to unwind row by row.

For a single month with a dozen charges, typing them in may be quicker than any of this, and it is a perfectly good answer. Imports pay off at volume: several cards, a year of history, or clients who send statements as PDFs.