Home › Blog › QuickBooks › QuickBooks bank feed gaps: why they happen and how to fill them
Why QuickBooks bank feeds only reach back so far, how gaps form after disconnects and new accounts, and how statement conversion fills history safely.
By StatementVerified Editorial · November 5, 2026 · 7 min read · Filed under QuickBooks
Bank feeds feel like they should contain everything, so a gap in feed history surprises bookkeepers the first time they meet one. In reality a feed is a window, not an archive. When an account is connected, the feed typically retrieves a limited lookback period, and many banks provide only a few months of history to the connection, regardless of how long the account has existed. Activity older than that window was never delivered, and no amount of refreshing the connection will summon it, because the limitation sits in what the bank offers the feed, not in QuickBooks itself.
Gaps also form later: a connection breaks during a bank security update and weeks pass before anyone reconnects it, an account is closed and reopened, or a business changes banks mid year. This guide explains the common gap patterns, how to measure a gap precisely using statement balances rather than guesswork, and how to fill it with converted statements in the correct order, with continuity checks that prove the filled history joins the feed history seamlessly at the boundary.
When you connect an account, QuickBooks requests historical transactions and the bank responds with what its feed service is configured to share. For many institutions that is a window measured in weeks or a few months, and it varies by bank and sometimes by account type. The practical consequence is that a business connecting feeds for the first time in, say, the autumn should expect the books to begin partway through the year, with the earlier months simply absent. That absence is silent. The feed area shows the transactions it has, the register balances from them, and nothing announces that the opening months of the year never arrived, unless the bookkeeper checks the earliest feed date against the start of the period they are responsible for.
Plan around the window rather than fighting it. At connection time, record the date of the earliest transaction the feed delivered for each account. Everything before that date is statement territory. Request the statements for the gap immediately, while the client request is fresh and bank portal access is at hand, instead of discovering the gap at tax time. For a brand new account, there is no gap: the feed window reaching back before the account opened is harmless. The distinguishing test is the account opening date and the first statement, which together tell you whether missing months are missing history or simply months when the account did not yet exist.
A feed disconnect creates a different gap shape: solid history, then a silent hole, then solid history again after reconnection. Banks periodically require reauthentication, merge systems, or change security requirements, and if the prompt goes unnoticed in a busy practice, the feed stops updating while the business keeps transacting. On reconnection, the feed resumes and may backfill some of the hole, but whether it backfills all of it depends on the same lookback limits, now measured from the reconnection date. Never assume a reconnected feed healed itself completely. Measure the hole explicitly before categorizing anything new.
Bank changes create a structural gap risk at the seam. The old account feed ends, the new account feed begins, and transfers between them, opening deposits, and final charges on the old account can fall between the two records. Handle the seam as its own mini project: obtain the final statement for the old account and the first statement for the new account, reconcile the old account to zero activity after closure, and confirm the opening funding of the new account matches the closing movement of the old. Seams are where money appears to vanish or duplicate in sloppy transitions, and statements, with their fixed anchors, are the only records that prove the seam is clean.
Measure any suspected gap with the continuity method. Take the bank statements for the period in question and lay out their opening and closing balances in date order, confirming the chain connects. Then compare the register: find the book balance at each statement boundary implied by the transactions QuickBooks actually holds. Where book and statement boundaries agree, coverage exists. Where the book record jumps, skips, or starts late, you have located the gap edges precisely, in dates and in net amount. That measurement becomes the specification for the fill: exactly these statements, exactly these dates, expecting exactly this net movement and this transaction count where the statement prints one.
This precision matters because an imprecise fill creates the duplicate problem covered elsewhere in this series. Importing a full quarter to fix a gap that was actually five weeks double covers the healthy weeks at both ends. The balance based measurement tells you which statements are wholly missing and which are partially missing. Wholly missing statements import in full. Partially missing statements get trimmed to the missing dates in the import copy, with the boundary verified by a running balance or subtotal check on the trimmed section, so the fill joins the existing record without overlap and without a remaining sliver of missing days.
Fill gaps from oldest to newest, one statement at a time, reconciling or at least balance checking each month before importing the next. Sequential filling means each month opening balance can be checked against the prior month closing balance in the books as you go, so an error announces itself in the month that introduced it. Importing a year at once and checking only the final balance forfeits that localization, and a single bad month inside the batch can hide behind offsetting noise. The sequential method feels slower and is reliably faster, because problems are found while the relevant statement is still open on your desk and the fix is a single file rather than a forensic review of a merged batch.
At the final boundary, where filled history meets feed history, perform an explicit seam check. Confirm the last imported transaction date precedes or meets the first feed transaction date with no overlap and no missing day, confirm the book balance at the seam equals the statement closing balance at that date, and scan the seam window for duplicates by amount and date. Then reconcile through the seam month fully. A clean reconciliation that crosses the seam is the strongest evidence the gap is truly closed, and it deserves a note in the workpapers stating the gap dates, the source statements used, and the boundary balance that was proven.
Prevention is monitoring, not hope. Add feed freshness to the monthly close checklist: for each connected account, note the date of the most recent feed transaction and investigate any account whose latest activity is older than the business rhythm suggests it should be. A busy operating account with no feed activity for two weeks is a disconnected feed until proven otherwise. Also calendar the known reauthentication patterns for your clients main banks where you can, and act on connection prompts the week they appear rather than at month end, because every week of delay lengthens the hole that statements will later need to fill.
Keep the coverage log current as the final defense. One page per account recording feed start, disconnects and reconnections with dates, statement imports with ranges and counts, and seam balances proven. With that log, a gap question that would otherwise consume an afternoon is answered by reading a single page, and a new bookkeeper inheriting the client can see exactly which source covers which dates. Feeds will keep having windows and disconnects; that is their nature. A practice with a coverage log and a statement based filling method treats those events as routine maintenance instead of emergencies.
It varies by bank, and typically the initial connection retrieves only a limited window, often a few months, even for long established accounts. Record the earliest delivered date at connection time and plan to fill everything earlier than that from statements.
Not necessarily. Reconnection backfill is limited by the same lookback the bank offers, measured from reconnection. Measure the gap against statement balances and fill any remaining missing dates with trimmed statement imports, checking the seams for duplicates.
Oldest to newest, one statement at a time, checking each month opening against the prior closing as you go. Finish with an explicit seam check and a full reconciliation across the boundary where imported history meets feed history.
QuickBooks · November 3, 2026
Fix QuickBooks Online date import errors from weekday text, mixed formats, and day month ambiguity, with a safe format choice for every converted file.
QuickBooks · November 4, 2026
Why QuickBooks shows duplicate transactions after an import, how feed overlap creates them, and the safe exclude, delete, and prevention workflow.
QuickBooks · November 2, 2026
How QuickBooks Desktop imports bank data with QBO Web Connect files, why plain CSV does not work for banking, and how to prepare a clean import file.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.