A credit card upload error in QuickBooks Online usually has one of four causes: the file is going into a bank account instead of a Credit Card account, the charges carry the wrong sign, the file type or size isn't accepted, or the dates overlap transactions already there. Check them in that order before you edit the file.
Is the credit card upload going into a Credit Card account?
A credit card upload belongs in an account with the Credit Card account type in QuickBooks Online. If the card was set up as a bank account, or you pick checking on the upload screen, QuickBooks warns you or brings the charges in as bank withdrawals, and the balance never shows as money owed.
Intuit's article on fixing bank upload errors in QuickBooks Online lists the warning "The uploaded file is of a different type than these accounts." Its advice is to select Cancel and pick the correct account, or OK to carry on. With a card file, Cancel is almost always the right choice.
To check the account:
- Open the chart of accounts and find the card.
- Look at the Type column. It should say Credit Card.
- If it says Bank, create a Credit Card account for the card and upload the file there instead.
A QBO or QFX file also carries its own idea of the account. Card files describe the account in a credit card block rather than a bank block, which the OFX 2.2 specification from the Financial Data Exchange calls CCACCTFROM. A card file uploaded to a bank account, or a bank file uploaded to a card account, triggers the warning above.
The card payment that lands in two accounts
Once the card has its own account, one line needs care: the monthly payment. It appears on the checking statement as money out and on the card statement as money in. Upload both files and the payment exists twice, unless you record it as a transfer between the two accounts and match the second copy to it. Leaving both as separate transactions inflates expenses and leaves the card balance too low. The post on recording card payments from your bank once, not twice shows the matching step by step, and it is worth checking before you blame the upload for a balance that won't agree with the statement.
Charge and payment signs in a credit card upload
The signs in a credit card upload decide whether each line raises or lowers what you owe. In the file, a charge should read as money out, so negative, and a payment or refund as money in, so positive. Many card issuers export the opposite, which makes every charge look like a payment.
The OFX specification states the rule for QBO and QFX files plainly: amounts are signed from the customer's point of view, so a credit card payment is positive and a credit card purchase is negative. A CSV doesn't follow any standard, so its signs depend on the issuer.
You will know the signs are backwards when:
- The card balance in QuickBooks goes down as you spend.
- Your monthly payment from checking shows as a new charge on the card.
- A refund from a store appears as an extra purchase.
The fix depends on whether the whole file is reversed or only part of it. The video walkthrough in Intuit's manual upload steps for QuickBooks Online says to check that amounts show as positive or negative correctly on the review screen, and to select the option to reverse all values if they are the wrong way round. If only some lines are wrong, fix those rows in the file and upload again. The full worked example of card signs is in whether credit card charges are positive or negative in the file.
Credit card upload file types and size limits
A credit card upload must be a file type QuickBooks Online reads and small enough for the upload. Intuit's upload article names CSV, QBO and QFX for transaction lists, sets a limit of 350 KB per file, and says a file can hold up to 1,000 lines. A file outside these limits fails before you reach the review screen.
What each limit means for a card file:
- File type. A PDF card statement isn't a transaction list, though the same article says QuickBooks can also take a PDF or image statement through its statement upload. A CSV or QBO file lets you check every sign and date before the upload.
- Size. 350 KB is reached quickly by a busy card with long descriptions. Split a year into quarters or months.
- Lines. Each line is one transaction. A company card used for every small purchase can pass 1,000 lines in a few months.
- CSV columns. The article asks for three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit), with the word "amount" removed from Credit and Debit headers and zero-only cells left blank.
- Language. The same article says the upload file must be in English.
Intuit's error article adds one more case: "The uploaded file contains invalid transaction amount information" means a transaction has 12 or more digits. On a card file this is usually a reference number pasted into the amount column, not a real charge. If the amount is genuine, Intuit suggests removing that line and entering it by hand.
Credit card upload dates that overlap what is already there
Credit card upload dates should begin right after the last transaction already in the card account. If the file overlaps a period QuickBooks already holds, from a bank feed or an earlier upload, the same charges come in twice. If it starts too late, charges go missing and the balance won't agree with the statement.
Intuit's upload article gives the rule for each case. For a new account, set the range as far back as you want QuickBooks to track. For an account that already has transactions, find the date of the last one and start the file the next day.
Card statements make this tricky in two ways:
- Statement periods cross months. A statement closing on the 17th covers half of two months. Go by transaction dates, not the statement month.
- Posted and transaction dates differ. A charge made on the 16th may post on the 18th. Your file and the bank feed must use the same one, or the overlap check misleads you.
After uploading, sort the account by date and look at the days around the join. A charge that appears twice with the same amount and payee is a duplicate; exclude one of them before you categorize either.
Why does a credit card upload fail on a sub-account card?
A credit card upload fails on a sub-account card because QuickBooks Online doesn't support uploading into a sub-account. Intuit's upload error article names this directly, under the message "We were unable to upload the file. Please start over and re-select the file you want to upload." Employee cards set up under a main card account are the usual case.
The same article lists related messages: "Errors with Sub/Parent account download", "(Parent Account Error)" and "(Sub-account Error)". For those, it suggests disconnecting the connected parent or sub-account from online banking, uploading the file and then reconnecting.
For a card that must stay a sub-account, the options are:
- Connect that card directly to its bank feed instead of uploading.
- Enter its transactions by hand, or as expenses with the card as the payment account.
- Restructure, making each employee card its own Credit Card account and grouping them in reports instead.
If cardholders share one statement, consider whether you need separate accounts at all. One account with a memo or class per cardholder is simpler to upload into.
Credit card upload messages that are really bank feed errors
Some messages you see while uploading a credit card file are not about the file. They come from the card's bank feed connection, which QuickBooks runs on its own schedule. If a feed is broken or busy, fixing the file changes nothing, and you need to deal with the connection first.
| Message or symptom | Where it comes from | What to do |
|---|---|---|
| "An Online Banking update is currently in progress" | The daily feed download is running | Wait for it to finish, then upload |
| "Bank Error" on the account | The card issuer's side | Hover for details; shorten the date range or try another file type |
| Error 9999 on the card account | A bank feed script error | See QuickBooks error 9999 and bank feed script errors |
| Error 324 on the card account | The issuer can't find the account | See QuickBooks error 324, bank account not found |
| "Couldn't upload your file. Please click Save again" | A temporary QuickBooks server problem | Wait a few minutes and try again |
The first, second and last rows come from Intuit's upload error article. A card with a working feed rarely needs an upload at all, except to fill gaps the feed can't reach.
If you are on the smallest plan, importing bank transactions into QuickBooks Online Simple Start walks through the upload screen there. If your card issuer only gives you PDF statements, SimpleBankConvert is being built to turn them into CSV or QBO files with charges shown as money out. It is not open for accounts yet; the homepage has the details.