QuickBooks missing bank transactions: find them or bring them in

First, check they aren’t already in QuickBooks

Transactions can download and still be out of sight. Intuit’s help page on missing transactions lists where to look:

• All three tabs in Bank transactions. Select the account, then check For review, Categorized and Excluded. If a transaction is in Excluded, select Undo and it goes back to For review.
• The account’s history. For older transactions, open Chart of accounts and select Account history for the bank account.
• Uncategorized Income and Uncategorized Expense. Run the report for each one from Chart of accounts. A transaction you find there can be unmatched and moved to the right account.
• Your bank rules. A rule set to auto-add puts transactions straight into your books, so they never appear in For review.

If the transaction is only a day or two old, it may just not be due yet. QuickBooks downloads posted transactions, not pending ones, and they can take up to 48 hours to arrive. Select Update on the Bank transactions page to check now.

Why the feed won’t fill a gap

Intuit says QuickBooks doesn’t download transactions older than 90 days. So if a connection stopped working in January and you fix it in October, the feed brings in the last 90 days and the months before that stay empty.

Some banks reach further when you connect an account: you pick a start date, and Intuit says how far back it can go depends on the bank, from 90 days up to 24 months. Past that, the transactions have to come from a file. Intuit advises a file import over typing them in.

How to bring in the missing months

1. Pin down the gap. Open the account’s register and note the last transaction before the gap and the first one after it. Those two dates are the range you need.
2. Get those dates from your bank. Download a QuickBooks Web Connect (.qbo) file if it offers one, otherwise a CSV. If the download doesn’t reach back far enough, look for the monthly PDF statements.
3. Keep each file small. Intuit’s limits are 350 KB and 1,000 lines per upload. One file per month or quarter also tells you where to look if something doesn’t add up.
4. Upload each file. On Bank transactions, select the account, open the menu next to Link account and choose Upload from file. The full steps are in how to import bank statements into QuickBooks Online.
5. Clear any overlap. Go through For review and Exclude anything QuickBooks already has, before you add the rest.
6. Reconcile against the statements. Once the transactions are categorized, reconcile one month at a time, oldest first. A month that won’t reconcile points to the file with a missing or doubled line.

Don’t count on .qbo transaction IDs to catch overlap with the feed. In our QuickBooks Online sandbox tests, uploading the same .qbo file twice added nothing, but we didn’t test a file against a live bank feed. Keep the dates from overlapping, and check For review either way.

If the months are older than your opening balance

Look at this before you upload. Intuit describes the opening balance as a summary of every older transaction in the account, so anything dated before it is already counted. You have two choices:

• Leave them out. Intuit says you don’t have to enter older transactions at all. If you only need the books right from the opening balance on, nothing is actually missing.
• Add them and move the opening balance. If you need the detail, upload the older transactions. Then open the account’s register from Chart of accounts and edit the entry labeled Opening Balance Equity, so its date and amount match your bank’s balance on the new start date. Without that step, QuickBooks counts those transactions twice.

Intuit says this is much easier before you reconcile the account for the first time. If you’ve already reconciled it a few times you can still do it, but you may need your accountant’s help.

When a CSV won’t upload

To see what really stops a file, we uploaded 22 deliberately awkward CSV files to a QuickBooks Online sandbox company (US, October 2026). They’re made-up files in one test, so your QuickBooks may differ.

What stopped the upload

• Rows above the column names. A bank’s title or account line above the header got “Your file does not contain the three required columns: transaction date, memo and amount.” Delete those rows so the column names are on the first line.
• Semicolons instead of commas. The same message. Save the file as comma-separated.
• More than 1,000 rows. “File length exceeded the allowed limit (1,000 rows).” Split the file.
• Something else in the date. With the day of the week in the date (09/23/2026 WED) there was no error message, but the date format box stayed empty and Continue stayed greyed out. Delete the weekday or move it to its own column. A file saved as UTF-16, which Excel calls Unicode Text, stopped on the same screen, so save as plain CSV.

What got through but lost rows

Rows with a date in a different format from the rest, and total or closing balance lines at the bottom, were marked Error under “We can’t upload everything from your file”. You can carry on, but those rows are left out. So compare the count in the last message (“QuickBooks will import 2 transaction(s)”) with your file. Losing a total line is fine; losing a real transaction leaves a new gap.

What didn’t matter

Intuit’s help page asks you to clean up several of these, but none of them stopped a file in our test, and each was read correctly:

• Numbers in the description, such as check, card and reference numbers. We finished that import and they came through intact.
• Extra columns such as Balance, Category and Status.
• Dollar signs, thousands commas, and brackets for negatives.
• Zeros in the Credit or Debit column, and headers like Credit Amount.
• Blank rows, trailing empty columns and accented letters.
• A 402 KB file, over Intuit’s 350 KB limit, as long as it stayed under 1,000 rows.

So if a file fails, look at the rows above the header and the dates first.

“Darn. File upload failed”

None of our files produced this message, and Intuit’s list of upload errors doesn’t include it. People report it when a CSV won’t go in, and QuickBooks Team replies in its community point to the file’s format or a temporary browser problem. Fix the file using the list above, then refresh the page, sign out and back in, and try again. If it still fails, try a shorter date range or a different file type from your bank. A .qbo file has no columns to get wrong.

Other upload messages

• “Invalid file format.” We got this for a file that wasn’t really text. Save the spreadsheet as CSV rather than renaming it.
• “The uploaded file contains invalid transaction amount information.” Intuit says this can mean a transaction has 12 or more digits. Take it out of the file, enter it by hand, and upload the rest.
• “The uploaded file is of a different type than these accounts.” The file is for another kind of account than the one you picked, such as savings instead of checking. Cancel and choose the right account.
• “We were unable to upload the file.” The upload timed out. Wait a few minutes and try again.
• “The uploaded file isn’t a valid Web Connect file.” In our sandbox tests, a .qbo file with no ending balance got this message, and so did one that declared UTF-8. More in what a QBO file is.

PDF statements, and CSVs QuickBooks won’t take

QuickBooks Online can read a PDF statement itself: see uploading a PDF statement to QuickBooks. For a run of months, converting first lets you check each one before it reaches your books.

BankToRows does that in your browser, one statement at a time. It adds the rows up against the opening, closing and running balances printed on the statement and shows any difference, so you can fix it before you download the .qbo file or the CSV for QuickBooks. It reads text-based PDFs, the kind you download from online banking, not scans.

A bank CSV that QuickBooks refuses can go through the CSV to QBO converter. It finds the column names below any title rows, reads semicolons and mixed date formats, and tells you which rows it skipped.