QuickBooks Bank Feed Missing Transactions: How to Fix

Short answer: transactions usually go missing from a QuickBooks bank feed for one of four reasons. They are still pending at the bank and have not posted, they are older than the 90-day window the feed can reach, the bank connection dropped or was re-authorized and skipped a stretch of dates, or they are already in QuickBooks but sitting in a tab you did not check. Once you know which one it is, the fix is straightforward. For any transactions the feed simply will not pull, the cleanest way to fill the gap is to convert the PDF bank statement to a QBO file and import that, so every transaction matches the statement exactly.

A missing transaction is more than an annoyance. If even a handful of deposits or charges never reach the register, your balance will not reconcile, your profit and loss is wrong, and any report you hand a client or a lender is off. Bookkeepers who do catch-up work hit this constantly, because the further back you go, the less the feed can reach. Here is how to track down what is missing and get it in correctly.

Why are transactions missing from my QuickBooks bank feed?

Transactions are missing from a QuickBooks bank feed because the feed only downloads what the bank releases, and banks limit that in several ways. The four common causes are pending transactions that have not posted yet, transactions older than the roughly 90-day download window, a bank connection that expired or was reconnected and skipped a date range, common after switching banks or a merger, and transactions that did download but landed in the Categorized or Excluded tab instead of For Review.

QuickBooks does not invent transactions. It mirrors the feed your bank sends through its data aggregator, so anything the bank withholds, holds as pending, or drops during a connection error simply never arrives. That is why the same statement line can be visible on your bank's website but absent from QuickBooks. The bank's site shows everything; the feed shows only what it was allowed to push.

How do I find missing transactions already in QuickBooks?

Before adding anything, confirm the transaction is not already in QuickBooks in a place you did not look. QuickBooks sorts downloaded transactions into three tabs, and a transaction in the wrong one looks missing. Check the For Review tab for anything waiting to be added, the Categorized tab to see what was already accepted or matched, and the Excluded tab for items QuickBooks flagged as duplicates or personal.

If you find it in Excluded by mistake, select Undo in the action column to move it back to For Review. If a transaction was matched to the wrong existing entry, open it from the Categorized tab and unmatch it. Run a manual update first by going to Transactions, then Bank transactions, then Update, in case the feed simply had not refreshed. Banks typically sync once every 24 hours, so a charge from this morning may just not be in yet.

How do I get transactions older than 90 days into QuickBooks?

For transactions older than 90 days, the bank feed cannot help, because most banks only let QuickBooks download about the last 90 days automatically. You have to add older transactions yourself. The two practical routes are uploading a file of the missing transactions or converting the original bank statement into an import file QuickBooks accepts. This is the same workflow used to record prior year transactions in QuickBooks when a whole year sits outside the feed's reach.

If your bank lets you export a CSV for the older date range, you can use Upload from file under the bank account's Link account menu and map the date, description, and amount columns. The catch is that bank CSV exports are inconsistent: column layouts differ by bank, dates come in odd formats, and debits and credits are sometimes split across columns, so the upload fails or imports amounts with the wrong sign. That is where working straight from the PDF statement is more reliable, because the statement is the authoritative record and a converted QBO file carries the correct dates, amounts, and signs without column mapping.

How do I add missing transactions from a bank statement?

To add missing transactions from a bank statement, convert the PDF statement to a QBO file and import only the period you are missing. Download the PDF for the missing month or months from your bank, run it through a converter, and follow the steps to import the resulting QBO file into QuickBooks. Every transaction on the statement becomes a register entry, so nothing the feed skipped is left out.

This is the approach our PDF bank statement to QuickBooks converter is built for. You upload the statement, review the extracted transactions on screen, and download a QBO file that QuickBooks imports in one pass. Because you start from the statement rather than the feed, there is no 90-day limit and no pending-versus-posted guessing: if it is on the statement, it is in the file. If you need to fill several months at once during catch-up work, the batch convert PDF bank statements workflow handles a full year of statements in one session.

Will importing missing transactions create duplicates?

Importing missing transactions can create duplicates if you import a period that already has entries in the register, so import only the dates that are genuinely missing. A QBO file uses a unique transaction ID for each entry, which helps QuickBooks Online recognize and skip ones it already has, but it is not foolproof across manual entries and feed entries. The safe practice is to identify the exact gap first, then import a statement period that covers only that gap.

If duplicates do slip in, you can delete them from the register or exclude them in the For Review tab before accepting. After the import, run a reconciliation against the statement so the cleared balance matches the bank's ending balance. If your opening balance looks wrong after an import, our guide on fixing a wrong opening balance after a QBO import walks through the most common causes.

What if the bank feed stopped pulling transactions entirely?

If the feed stopped pulling transactions entirely, the connection most likely expired, the bank changed its login or security requirements, or the bank is doing maintenance on the data connection. A merger or a login change on the bank's side can also break the feed the same way switching banks does, which needs its own fix for QuickBooks after a bank change. Reconnect the account from the banking screen, complete any new multi-factor verification, and when prompted choose the earliest available start date so the reconnection backfills the gap. Any dates between the disconnection and the reconnection are the ones at risk of being skipped.

Reconnecting often recovers recent gaps, but it rarely reaches far enough back to cover a long outage, and it will not retrieve anything past the 90-day limit. For the stretch the reconnection misses, convert those statement months to QBO and import them. That combination, reconnect for the recent days plus a statement import for the older gap, is the fastest way back to a complete, reconcilable register.

QuickBooks Desktop bank feed missing transactions

QuickBooks Desktop has the same root causes plus its own quirks. Desktop bank feeds depend on the Web Connect or Direct Connect method your bank supports, and Direct Connect is being retired by a growing number of banks, which leaves Web Connect QBO file imports as the dependable path. If Desktop shows fewer transactions than the statement, download the QBO Web Connect file from your bank for the right date range, or convert the PDF statement to a QBO or IIF file and import that.

Desktop accepts both formats: QBO Web Connect files import through the bank feeds center, and IIF files import as a batch of transactions. For Desktop users who need full line-item detail or who import on a schedule, our PDF bank statement to QuickBooks Desktop page covers both routes and which to choose.

Getting to a complete register

Missing bank feed transactions almost always come down to a limit on what the feed can reach, not a problem with your books. Work through it in order: refresh the feed, check all three tabs, reconnect if the connection dropped, and for anything older than 90 days or skipped during an outage, go to the source. The bank statement has every transaction, so converting it removes the guesswork.

If the transactions you need are in a PDF, you have a few options for getting them into your accounting in a usable shape. You can convert the bank statement to Excel or CSV when you want to review or edit the data in a spreadsheet first, or if your bank only gives you a CSV export you can turn that CSV into a QBO file for a clean import. For a direct statement-to-QuickBooks path with no spreadsheet step, a dedicated bank statement to QuickBooks converter takes you straight from the document to an importable file. Whichever route fits your setup, the goal is the same: a register that matches the statement line for line, so reconciliation is clean and your reports are right. And if the feed is missing because the institution never appears in the connection list at all, see what to do when your bank is not listed in QuickBooks.