QuickBooks Bank Feed Troubleshooting: The 360-Day Rule And Web Connect Fix

QuickBooks can’t connect to your client’s bank. The 360-day rule is biting you. The PDF is in your inbox, and the close is in 3 days.

QBO bank feed failures are the most common QBO-specific issue bookkeepers face. This page covers the 360-day rule, the Web Connect import, the 5 most common QBO error codes, and the 10-minute recovery workflow.

QBO has 3 specific failure modes that don’t apply to Xero or Wave: the 360-day rule (QBO disconnects feeds after 360 days of no manual match), the 90-day initial connection window (if the connection fails within 90 days, you must re-enter credentials), and the 5 most common QBO error codes (which map to the 5 reasons in the generic troubleshooting guide).

The recovery is the same regardless of which failure mode: download the PDF from the bank, convert it to .qbo or .csv with the recon cutoff tool, and import via Banking → Upload transactions. The 10-minute recovery works for both personal and business accounts.

For the generic 5-reason framework, see the bank feed failure guide. For Xero-specific, see the Xero troubleshooting guide. For the broader bookkeeper workflow, see the book statement workflow for bookkeepers pillar.

The 360-Day Rule

QBO disconnects a bank feed after 360 days of no manual match. This is the most common QBO-specific failure. The feed shows “Connected” but QBO stops pulling new transactions.

What most guides miss about QuickBooks integration is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).

Choosing between tools based on UI alone misses the actual quality lever.

The 360 days start from the last manual match. If you match a transaction on January 1, 2025, the feed will disconnect on December 27, 2025 (360 days later). The fix is to match a transaction at least every 360 days, or accept that the feed will need to be reconnected annually.

Why the 360-Day Rule Exists

QBO’s data retention policy treats feeds as ephemeral. After 360 days of inactivity, QBO assumes the feed is no longer needed and disconnects it. The 360-day window is shorter than most banks’ statement retention (12-24 months), so the disconnect often happens before you need it.

The fix is to set a calendar reminder for the day before the 360-day mark for each feed. Log into QBO, review the feed, match a transaction, and the 360-day clock resets.

The 90-Day Initial Connection Window

QBO has a 90-day window for the initial connection. If the connection fails within 90 days of the first attempt, you must re-enter credentials. The 90-day window is shorter than most banks’ password rotation cycle, so the credentials often expire before the connection is fully stable.

The fix is to log into the bank portal the same day you set up the QBO feed, confirm the credentials work, and verify the feed pulls at least one transaction. This locks in the connection and avoids the 90-day re-auth issue.

From Bank Statement to QuickBooks-Ready File

That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.

Start Converting

The 5 Most Common QBO Error Codes

QBO has 5 error codes that cover 90% of bank feed failures. Each error code maps to one of the 5 reasons in the generic troubleshooting guide.

Error 103: Bank Connection Lost

Error 103 means QBO can’t reach the bank. The fix is to log into the bank portal, verify the credentials, then reconnect in QBO. The reconnect takes 2-3 minutes.

Error 108: Invalid Credentials

Error 108 means the bank rejected the login. The fix is to log into the bank portal, update the password, then re-enter the credentials in QBO. The bank might also require an MFA code on first login from a new device; QBO is treated as a new device.

Error 158: Bank Account Closed or Restricted

Error 158 means the bank account is no longer active. The fix is to disconnect the account in QBO, then either reconnect with a new account number (if the account was reopened) or leave it disconnected (if the account was closed).

Error 324: Connection Provider Maintenance

Error 324 means the connection provider (Yodlee, Finicity) is doing maintenance. The fix is to wait 2-4 hours and try again. The maintenance windows are usually overnight Eastern time, so the connection is restored by the next business day.

Error 999: Generic System Error

Error 999 is QBO’s catch-all error. It usually means a transient issue. The fix is to log out of QBO, log back in, and try the connection again. If the error persists, contact QBO support with the timestamp and account number.

The 10-Minute Recovery Workflow

When a QBO feed fails, the recovery is the same regardless of error code. The 5 steps take 10 minutes per account.

Step 1: Note the Error Code

Open the QBO feed status. Note the error code (103, 108, 158, 324, 999, or another). The error code tells you which fix to apply. If the error code is 324, just wait. If it’s 103, 108, 158, or 999, proceed to step 2.

Step 2: Download the PDF

Log into the bank portal. Download the statement as PDF. The bank-specific download paths are in the bank export guide.

Step 3: Convert with the Recon Cutoff Tool

Upload the PDF to the recon cutoff tool. The tool emits a .qbo file (the Web Connect format QBO imports natively) or a .csv file (for manual column mapping). The per-period split is automatic.

Step 4: Upload to QBO

In QBO, go to Banking → Upload transactions. Select the .qbo file. QBO imports the transactions and matches them against existing entries. Unmatched transactions appear in the “For review” tab.

Step 5: Reconcile

Review the “For review” tab. Match each transaction to the right account, category, or payee. The recon cutoff tool’s per-period split means pre-cutoff transactions go to the current period and post-cutoff transactions are marked OUTSTANDING.

The Web Connect Import

Web Connect (.qbo) is the official QBO import format. It’s based on the OFX (Open Financial Exchange) standard. The recon cutoff tool emits .qbo files that QBO imports natively, with payee matching and de-duplication working out of the box.

Web Connect is faster than CSV import. Web Connect handles date format, sign convention, and column order automatically. CSV import requires manual column mapping. Use Web Connect when the bank is supported (most major US banks), and CSV as a fallback.

Multi-Account Recovery

Multi-account clients (3+ accounts at the same bank) take longer to recover. Each account needs a separate connection in QBO. The recovery time is roughly 10 minutes per account, so a 5-account client takes 50 minutes.

The recon cutoff tool’s batch upload handles multiple statements from the same bank in one go. The tool emits one .qbo file per account, ready to import. The per-period split is per-account, not per-bank, which is important for multi-entity clients.

How to Prevent QBO-Specific Failures

The 360-day rule and 90-day initial connection window are unique to QBO. The 3 prevention tactics.

Set a 360-day calendar reminder. For each QBO feed, set a calendar reminder 350 days after the last manual match. Log into QBO, match a transaction, and the 360-day clock resets. The reminder takes 1 minute per feed per year.

Verify the initial connection within 90 days. When you set up a new QBO feed, log into the bank portal the same day and confirm the credentials work. Pull at least one transaction in QBO. This locks in the connection.

Document each QBO feed’s last manual match date. The recon cutoff tool’s archive feature can track this. After each month-end close, the tool logs the last manual match date for each feed. Set calendar reminders based on this log.

A common failure mode bookkeepers report is treating this as a single operation rather than a chain of dependent steps. The temptation is to find a tool that ‘just works’ and stop investigating the mechanism.

The result is a wrong-fix cycle: the tool gives partial output, the bookkeeper spends 30+ minutes troubleshooting, the fix is for the wrong step, and the same error recurs on the next statement. The fix: identify which step failed and apply the right intervention to that step.

When to Contact QBO Support

Contact QBO support when the recovery steps don’t work. The 3 scenarios that need support: error code 999 that persists after retry, an account that disconnects immediately after reconnection, or a feed that connects but pulls zero transactions for 2+ cycles.

QBO support responds within 24-48 hours for paid plans (QBO Plus and higher). The support team can see the connection logs and identify the issue. The recon cutoff tool’s archive feature gives you the documentation to send to support: error timestamp, account number, last successful transaction, and the steps you already took.

For the generic 5-reason framework, see the bank feed failure guide . For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

This topic is part of the bookkeeper-resource cluster on this site. The consolidated hub, covering onboarding, monthly close, year-end, client deliverables, and multi-entity workflows, lives in the complete bookkeeper workflow guide.

For related reading on the broader clusters, the covers credit-card-side mechanics, and the covers bank-account-side mechanics. The expanded bank statement anatomy is a useful primer.

Decision framework for this topic

For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.

Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.

When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.

For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.

Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.

For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.

Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.

The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.