QuickBooks Bank Feed Not Working? A Manual Import Workflow

Confirm that the bank feed has a gap

A missing transaction does not always mean the QuickBooks bank connection failed. Current US Intuit guidance says QuickBooks downloads posted activity, not pending activity, and does not pull transactions older than 90 days through the feed. A posted item can also sit in For review, Categorized, Excluded, the account register, or an uncategorized account.

Write down the account, the last posted transaction you can see in QuickBooks, and the first later transaction that appears after the gap. Compare those boundaries with the bank website or issued statement. You need a defined missing range before you upload a file.

Run Update before changing the connection

Go to All apps, Accounting, then Bank transactions. Select Update. Intuit says bank update times vary and a posted transaction may take up to 48 hours to appear. Follow any verification prompt that QuickBooks shows during the update.

If Update brings in the missing rows, stop there and review them. Do not import a backup file for the same dates. If Update fails, Intuit suggests testing QuickBooks in a private browser window to rule out a stale sign-in or browser extension before you alter the bank connection.

Check the bank website and sign-in details

Sign in through the bank's own website. Look for an outage, maintenance notice, security message, new consent request, or changed login flow. Confirm that the missing transactions have posted and that you can open the account without an alert blocking access.

Update the sign-in details in QuickBooks if the bank username, password, or account number changed. Intuit's current path starts from the account card in Bank transactions, then Edit and Edit sign in info. Use the bank's known website address rather than a link from an email or message.

• Record the bank-feed error code before you dismiss it.
• Complete a bank security or consent prompt shown through the trusted bank flow.
• Confirm the account number did not change after a replacement card or bank migration.
• Follow Intuit's error-specific instructions before you disconnect or reconnect an account.

Search QuickBooks before you import anything

Select the affected account in Bank transactions and inspect For review, Categorized, and Excluded. A bank rule with auto-add can move a transaction into the books before you see it in For review. An excluded item can also look missing until you open the Excluded tab and undo the exclusion.

Check the account register through the Chart of accounts and search Uncategorized Income and Uncategorized Expense. Use dates, amounts, and description fragments from the bank statement. If you find the transaction in QuickBooks, correct its status or account rather than uploading another copy.

Build a duplicate-safe gap worksheet

Use the bank statement as the source for the missing period. List each posted bank row in the gap, then mark whether QuickBooks contains a matching record. Date, description, and amount help you search, but repeated purchases can share all three values. Use account context and statement order before you mark a row as a duplicate.

The synthetic worksheet below shows a five-day gap with nine printed rows. QuickBooks contains two of them through a prior entry, so the import file should contain seven rows. Uploading the full nine-row statement would create two duplicates.

Choose the cleanest manual source

Use a transaction file from the bank when it covers the missing dates and account. Current Intuit guidance accepts QBO, QFX, CSV, and direct PDF or image statement uploads. A bank-provided file can avoid PDF extraction, but you must still inspect its date range for overlap.

Use the issued PDF when the bank does not offer a transaction file for the gap. QuickBooks can process a whole PDF statement through its statement-upload flow. A reviewed CSV gives you tighter control over a partial gap because you can include the seven missing rows and leave the two existing rows out of the destination copy.

Create a reviewed gap file from a PDF

StatementMint converts entitled statement pages into CSV and formatted Excel with Date, Description, and signed Amount. It does not connect to QuickBooks, repair a bank feed, categorize transactions, or create QBO and QFX files. Use it when the issued PDF contains the missing activity and you want to inspect the rows before import.

Compare the export with the PDF. Preserve the reviewed source, then create a QuickBooks destination copy with the confirmed gap rows. Keep one header row, one transaction per row, consistent dates, and numeric signed amounts. The QuickBooks template guide linked below includes a downloadable synthetic three-column file.

Upload the gap once

Open Bank transactions, select Upload from file, choose the destination file, and select the affected QuickBooks account. Map Date, Description, and Amount, then inspect the preview. Compare its row count with the gap worksheet before you confirm the import.

Use one import route for the gap. Do not upload the PDF and its CSV copy into the same account for the same dates. Keep an import note with the account, gap dates, source file, imported row count, and import date so another bookkeeper can see what changed.

Match the rows and reconcile the statement

Imported bank rows still need accounting review. Match a row to an invoice, bill, payment, or other record when that record exists. Categorize a new row from the business records and chart of accounts. A merchant description cannot choose the accounting treatment for you.

Reconcile the account to the issued statement ending date and balance. A nonzero difference can point to a row that the feed missed, a duplicate from the manual import, a wrong sign, or an older book error. Resolve the difference and retain the reconciliation report with the gap worksheet.

Escalate the connection issue without blocking the books

Contact Intuit or follow its error-code article when Update, the bank website check, credential refresh, and transaction search do not restore the feed. Bring the full error message, bank name, affected account, last successful download date, and steps you tested.

The manual gap import keeps the books current while the connection issue remains open. Keep checking for restored feed activity after the import. If the feed later sends the same dates, compare those rows with the import note before you accept them.

Frequently asked questions