Your bank feed broke again. The client just sent you a PDF. You need it in QuickBooks by Friday, and the PDF is the only path left.
Bank feed failure is the #1 pain point for bookkeepers, and it happens more often than most people think. This page covers the 5 main reasons feeds break, the 10-15 minute recovery, and the spoke-by-spoke troubleshooting for QuickBooks and Xero.
Bank feeds fail in 5 main ways: the bank changes its API, the credentials expire, the account type changes, the transaction format changes, or the connection provider (Yodlee, Finicity, Plaid) has an outage. Bank feed failures are common across both QBO and Xero, often tied to bank API changes, credential expirations, or connection provider outages.
When the feed fails, the fix is the same: download the PDF, convert it, import manually.
The recovery takes 10-15 minutes per account. The recon cutoff tool’s period-end split is the key. Pre-cutoff transactions go to the current period. Post-cutoff transactions are marked OUTSTANDING. This is the same workflow you use for normal month-end, just triggered by an alert instead of a calendar date.
For QBO-specific troubleshooting, see the QBO bank feed troubleshooting guide. For Xero-specific, see the Xero bank feed troubleshooting guide. For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar.
The 5 Reasons Bank Feeds Break
Bank feeds break for 5 reasons. Each reason has a different fix. Knowing which one you have cuts the recovery time in half.
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.
Reason 1: Bank API Changes
Banks change their API (the technical connection) without warning. When this happens, QBO or Xero’s connection provider (Yodlee, Finicity, Plaid) loses the ability to pull transactions. The feed shows “Connection lost” or “We can’t reach your bank.” The fix is to wait for the connection provider to update, or switch to manual PDF import for that account until the connection is restored.
This is the most common reason. It happens to Chase, Wells Fargo, BofA, and other major banks about every 18-24 months. The recovery: download the PDF, convert with the recon cutoff tool, import.
Reason 2: Credentials Expire
Bank login credentials expire. Some banks rotate passwords every 90 days. Some require MFA on every login. Some lock the account after 3 failed attempts. The fix is to log into the bank portal, update the password, then re-enter the credentials in QBO or Xero.
The credential expiration hits hardest on business accounts with multiple users. The bank treats the QBO connection as a single user, and that user has a 90-day password rotation. Set calendar reminders for password rotation on bank accounts that connect to QBO or Xero.
Reason 3: Account Type Changes
Account type changes (e.g., a personal account becomes a business account, or a savings account gets closed and reopened) break the bank feed. The QBO or Xero connection is tied to the account number and routing number, both of which can change with a type change.
The fix: disconnect the old account in QBO or Xero, reconnect with the new credentials, and backfill the gap with PDF import.
This is the hardest reason to detect because the feed just stops pulling without an error message. The discovery usually happens during the month-end close when you notice transactions are missing.
Reason 4: Transaction Format Changes
Banks sometimes change how transactions are formatted. The bank statement might add a new column, change the date format, or restructure the merchant name. The QBO or Xero parser doesn’t recognize the new format and silently drops transactions. The fix is to contact QBO or Xero support, who will work with the connection provider to update the parser. In the meantime, use PDF import.
This is the silent failure mode. The feed shows “Connected” and “Last synced today” but transactions are missing. The only way to detect it is to compare the converted PDF against the feed transactions. The recon cutoff tool’s reconciliation worksheet makes this comparison fast.
Reason 5: Connection Provider Outage
QBO uses Yodlee and Finicity. Xero uses Yodlee. Plaid is the third major provider. These providers have outages. When they do, every bank feed using that provider goes down simultaneously. The fix is to wait. The outage is usually 2-48 hours. Use PDF import in the meantime.
Yodlee outages happen about 4-6 times per year. The outage affects every Xero feed and most QBO feeds. The recovery: download the affected statements, convert with the recon cutoff tool, import. The tool handles the per-account period-end split automatically.
The 10-15 Minute Recovery
When a feed fails, the recovery is the same regardless of which reason caused it. The 5 steps take 10-15 minutes per account. Multi-account clients take longer.
Step 1: Confirm the Feed is Down
Check QBO or Xero for the feed status. If the feed shows “Connected” and “Last synced today,” the issue might be a silent format change (Reason 4) or a credentials issue (Reason 2). If the feed shows “Disconnected” or “Error,” it’s Reason 1, 3, or 5.
Step 2: Download the PDF Statement
Log into the client’s bank portal. Download the statement as PDF. The bank-specific download paths are in the bank export guide. For credit unions, see the credit union export guide.
Step 3: Convert with the Recon Cutoff Tool
Upload the PDF to the recon cutoff tool. The tool emits a .qbo file (for QBO) or a .csv file (for Xero or Wave). The per-period split is automatic: pre-cutoff for the current period, post-cutoff marked OUTSTANDING.
Step 4: Import to QBO or Xero
For QBO: Banking → Upload transactions → select the .qbo file → match payees. For Xero: Accounting → Bank Accounts → Import statement → select the .csv or .qbo file → match payees.
Step 5: Document the Recovery
Note the date of the recovery, the reason for the failure, and the steps taken. The recon cutoff tool’s archive feature stores the original PDF, the converted file, and the import log. This documentation is what you need for the client if they ask why their books took longer this month.
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 ConvertingWhy This Happens So Often
Bank feeds fail more often than most bookkeepers expect. The connection provider ecosystem (Yodlee, Finicity, Plaid) is fragile. Banks change their APIs to add security features or migrate to new infrastructure. The connection providers have to update their parsers, which takes 2-8 weeks. During that window, the feed is broken.
The QBO and Xero platforms don’t make this easy. They show generic error messages that don’t help you diagnose the cause. The “We can’t reach your bank” message could mean any of the 5 reasons. The fix is the same regardless: download the PDF, convert, import.
For bookkeepers managing 10+ clients, the bank feed failure is a monthly event. The recon cutoff tool’s batch upload handles the recovery efficiently. The per-period split means you don’t have to manually figure out which transactions belong to which period. The archive feature means you have the original PDF for the audit trail.
What to Tell the Client
Bank feed failures are technical issues, not accounting errors. The client doesn’t need to worry about the books being wrong; they need to know the recovery is in progress and the deadline.
Sample client email: “The bank feed for your Chase account is down. We’ve downloaded the statement directly from Chase and are processing the transactions. Your books will be current by Friday. No action needed from you.”
The email is short, clear, and actionable. It tells the client what happened, what’s being done, and when to expect the result. The recon cutoff tool’s archive feature gives you the documentation to back this up if the client asks for details.
How to Prevent Bank Feed Failures
You can’t prevent bank feeds from breaking, but you can reduce the impact. The 4 prevention tactics below take 30 minutes per month to implement. The ROI is 2-3 hours saved per quarter in feed failure recovery.
Calendar reminders for password rotation. Bank credentials expire on a 90-day cycle for most banks. Set a calendar reminder for the day before the rotation. Update the password in the bank portal first, then update QBO or Xero. This avoids the 24-48 hour disconnect when the password expires.
Weekly feed status check. Every Monday, check the bank feed status for each client. The check takes 5 minutes per client. If a feed is down, you catch it early and can download the PDF before the next statement cycle. The recon cutoff tool’s archive feature tracks when each feed was last connected.
Batch PDF download monthly. Once a month, download all client bank statements as PDFs even if the feed is working. This creates a backup. If a feed breaks, you already have the PDF. The recon cutoff tool’s batch upload handles 50 statements in one go.
Document every failure. Every feed failure goes in a log. The log records: client, bank, date of failure, reason, recovery time, and resolution. After 6 months, you have data on which banks fail most often. This data lets you prioritize which banks to monitor more closely.
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.
The QBO and Xero Spokes
This page covers the generic 5-reason framework. The QBO-specific spoke covers the 360-day rule, the Web Connect import, and the QBO error codes. The Xero-specific spoke covers Yodlee outages, the manual import window, and the Xero bank reconciliation report.
For QBO troubleshooting, see the QBO bank feed troubleshooting guide . For Xero troubleshooting, see the Xero bank feed troubleshooting 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.
Related:
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.
Related reading and broader clusters
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.
From PDF to Excel in one click
Forget retyping line by line. Upload any bank statement, get a spreadsheet you can actually use. Your files are never stored, and you can test the converter with 3 free conversions.
Try it free
