Import credit card transactions into QuickBooks Online by converting your card QIF to a .qbo file, so charges and payments get the right sign and import clean.
No account needed for your first conversions. We never store your bank login.
To import credit card transactions into QuickBooks Online, convert your card's QIF export into a .qbo Web Connect file and upload that to the credit card account. The converter above does it in one pass and, critically, signs charges and payments correctly so they do not import backwards. You get the .qbo, plus Excel and CSV copies, in under a minute.
Credit card accounts in QuickBooks are liability accounts, which is why a raw QIF so often imports in the wrong direction: charges land as deposits and payments as spending. Converting to a .qbo fixes the sign before the file ever reaches QuickBooks. Upload a QIF export from any US card (Amex, Chase, Capital One, Citi, or your bank's card), and every charge, payment, refund, and fee imports into the right register.
Built for the QIF files Quicken and finance tools actually export, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
Date, payee, and amount are read straight from the QIF tags, so there is nothing to map and no layout to match.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, apostrophe years, currency symbols, and split lines in a QIF are cleaned up and summed before the .qbo is built.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a .qif export from Quicken, your bank, or another finance tool. Any QIF type works.
Every transaction is parsed and checked against your file total. You see the rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, message us in chat.
Convert your card's QIF export to a .qbo file using the converter above, then in QuickBooks Online go to Transactions, Bank transactions, pick the credit card account, and choose Upload from file. Select the .qbo and QuickBooks imports every charge and payment into the review queue for that card.
Because a credit card is a liability account, so a payment lowers the balance and a charge raises it, the opposite of a checking account. When a QIF lists charges as positive and payments as negative, QuickBooks reads them in reverse. Converting to a .qbo sets the sign QuickBooks expects, so charges and payments land on the correct side.
For a credit card account, charges (money you spent) import as negative and payments or credits as positive. Many QIF exports use the opposite convention in the amount (T) tag, which is the usual cause of a reversed import. When the converter builds the .qbo, it writes each amount with the sign QuickBooks expects for a card register, so you do not flip them by hand.
QuickBooks Online no longer imports QIF directly, so the dependable route is to convert it. Convert the QIF to a .qbo with the tool above, then upload the .qbo under Transactions, Bank transactions, Upload from file. The .qbo route needs no field mapping and sets the charge and payment signs for you, which a raw QIF would not.
Yes, as long as you have the activity as a QIF file. Download your card's transactions as a QIF from the issuer's site or export them from Quicken, then convert it to a .qbo with the tool above. The converter cannot read a PDF statement, so export the transactions as QIF first wherever your issuer or finance software offers it.
In QuickBooks Online open Transactions, then Bank transactions, select the credit card account, click the arrow by Link account, and choose Upload from file. Because QuickBooks Online does not read QIF, convert your QIF to a .qbo first with the converter above, then upload that .qbo. Charges arrive already signed as negative, so there is nothing to flip.
The simple reason is that QuickBooks Online does not accept QIF for bank or card feeds, and Desktop dropped QIF transaction import years ago. Even where a QIF would load, reversed charge and payment signs in the amount (T) tag throw the balance off. Converting the QIF to a .qbo gives QuickBooks the file format it actually reads and applies the signing rules before import.
Yes. QuickBooks Desktop does not take a raw QIF for a credit card, but it imports .qbo Web Connect files directly. Convert your card QIF to a .qbo, then go to File, Utilities, Import, Web Connect Files, and select the card account. The same .qbo works for both QuickBooks Online and Desktop.
A native CSV upload is capped at 350 KB, roughly a thousand rows, so a long card history often has to be split. A .qbo import is not held to that size limit, so converting your QIF lets you bring a full year of card charges and payments into QuickBooks in one file instead of several.
Yes. A refund or return is a credit to the card, so it imports as a positive amount, and interest or an annual fee is a charge, so it imports as a negative. The converter signs each line by whether it raises or lowers the card balance, so refunds, fees, and interest all land on the correct side without manual fixes.
After the .qbo imports, every charge and payment sits in the For review tab of that credit card account. QuickBooks suggests a category and matching rule for each, and you accept, edit, or create a bank rule to auto-categorize repeat vendors. Importing only brings the transactions in; you still review and post them like any bank feed.
This is the most common credit card import problem, and it comes from how QuickBooks treats the account. A credit card is a liability: spending raises what you owe, paying lowers it. So in the card register a charge must reduce your available balance (a negative line) and a payment must increase it (a positive line). QIF exports, though, often record the opposite, listing purchases as positive amounts in the T tag. Load that file as is and QuickBooks faithfully reverses everything, turning charges into payments. The fix is to set the sign before import, which is exactly what the converter does when it writes the .qbo, so you never edit an amount tag by hand again.
The converter reads QIF files, not PDF statements, so start from the transaction download rather than the printable statement. Many issuers and every personal-finance tool can produce one: in Quicken or Microsoft Money, or in a card portal that offers a Quicken download, set a date range and export the activity as QIF. That file holds clean date (D), payee (P), and amount (T) tags the converter reads directly. A PDF statement is an image of the same data and has to be left out of this workflow.
Upload a QIF export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
For non-card accounts, the QIF to QuickBooks Online converter handles checking and savings exports the same way, and the QIF to QBO converter covers any Quicken or Money export. You can also convert any QIF to QBO on the home page, compare the best QIF to QBO converters on price and features, or read what a .qbo file is and why QuickBooks needs it.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly
