Xero Bank Feed Troubleshooting: Yodlee Outages And The 30-Day Import Window

Xero lost the bank feed. The transactions stopped syncing on the 14th. You have 16 days of unposted transactions and the close is in 5 days.

Xero bank feed failures usually trace to one of 3 places: Yodlee (Xero’s connection provider), the bank itself, or Xero’s reconciliation engine. This page covers the 3 Xero-specific failure modes, the manual import window, and the 12-minute recovery workflow.

Xero’s bank feed uses Yodlee for most US banks. Yodlee outages cause most Xero feed failures. The outage affects every Xero feed using that connection, often 5-10 accounts per bookkeeper. The recovery: download the affected statements, convert to .qbo or .csv with the recon cutoff tool, import via Accounting → Bank Accounts → Import statement.

Xero has 3 specific failure modes that don’t apply to QBO: the 30-day manual import window (the import is duplicate-safe for 30 days), the Yodlee 24-hour outage cycle (most Yodlee outages resolve within 24 hours), and the bank reconciliation report (Xero’s built-in tool for finding what didn’t import).

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

The Yodlee Outage Problem

Xero’s bank feed uses Yodlee for most US banks. Yodlee outages cause most Xero feed failures. The outage affects every Xero feed using that connection, often 5-10 accounts per bookkeeper. The outage is silent: the feed shows “Connected” and “Last synced today” but no new transactions are pulled.

What most guides miss about bank feed connection 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.

Yodlee outages happen 4-6 times per year, lasting 2-48 hours each. The outage usually resolves itself, but during the outage window, every Xero feed is stuck. The bookkeeper finds out when they open the client file and notice the transactions haven’t synced since the outage started.

How to Detect a Yodlee Outage

Yodlee outages are silent. The feed status shows “Connected” but transactions aren’t pulling. The detection is manual: open each client file, check the last sync date, and compare against today’s date. If the last sync is more than 24 hours old and the feed shows “Connected,” it’s likely a Yodlee outage.

The recon cutoff tool’s archive feature tracks the last sync date for each Xero feed. After each month-end close, the tool logs the last sync date. If the gap is more than 24 hours, the bookkeeper can investigate before the close.

The 30-Day Manual Import Window

Xero has a 30-day window for manual import without creating duplicates. The 30 days start from the last feed transaction. If the feed pulled a transaction on the 14th and you import the PDF on the 18th, Xero recognizes the imported transactions as duplicates and skips them.

After 30 days, the manual import creates duplicates. The fix is to either match each imported transaction manually against the existing feed entry, or to delete the existing feed entries and re-import.

The 30-day window is more forgiving than QBO’s behavior. QBO will create duplicates on the same day. Xero’s 30-day window gives you time to recover without manual de-duplication.

When the 30-Day Window Doesn’t Apply

The 30-day window only applies if the feed was working before the failure. If the feed was disconnected for 30+ days, the import will create duplicates. The fix is to disconnect the feed in Xero before importing, then reconnect after the import.

Xero Bank Feed Troubleshooting: Yodlee Outages and

Turn any PDF statement into a clean sheet

Skip the typos and the hours of copying. Our converter handles any bank statement format and outputs Excel, CSV, or QBO for QuickBooks. No file retention, free to try.

Convert your statement

The Bank Reconciliation Report

Xero’s bank reconciliation report is the built-in tool for finding what didn’t import. The report is at Accounting → Reports → Bank Reconciliation. The report shows: starting balance, ending balance, cleared transactions, uncleared transactions, and the gap between the bank statement and the books.

The report is updated in real time. If a feed outage causes 16 days of unposted transactions, the bank reconciliation report shows the gap. The gap is what you need to fill with the manual import.

The recon cutoff tool’s per-period split aligns with the bank reconciliation report. Pre-cutoff transactions for the current period, post-cutoff transactions marked OUTSTANDING. The reconciliation report shows OUTSTANDING transactions in the “Uncleared” section, which is exactly where they belong.

The 12-Minute Recovery Workflow

When a Xero feed fails, the recovery is the same regardless of cause. The 6 steps take 12 minutes per account.

Step 1: Confirm the Outage

Check Xero’s status page (status.xero.com). If there’s a Yodlee outage, Xero posts it on the status page. If the status page shows no outage, the issue is bank-specific.

Step 2: Check the Bank Reconciliation Report

Open Accounting → Reports → Bank Reconciliation. Note the gap between the bank statement and the books. The gap is the number of transactions you need to import.

Step 3: 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 4: Convert with the Recon Cutoff Tool

Upload the PDF to the recon cutoff tool. The tool emits a .qbo file or a .csv file. The per-period split is automatic: pre-cutoff for the current period, post-cutoff marked OUTSTANDING.

Step 5: Import to Xero

In Xero, go to Accounting → Bank Accounts → Import statement. Select the .csv or .qbo file. Xero’s 30-day manual import window means no duplicates if the feed was working within the last 30 days.

Step 6: Verify the Reconciliation Report

Re-run the bank reconciliation report. The gap should be closed. If transactions are still missing, the import didn’t catch all of them, or the per-period split is off. Re-convert with the recon cutoff tool and re-import.

Xero vs QBO: The Differences

Xero and QBO handle bank feeds differently. The 3 main differences matter for bookkeepers managing both platforms.

Connection provider. Xero uses Yodlee. QBO uses Yodlee, Finicity, and Plaid depending on the bank. QBO’s multi-provider approach is more resilient: if Yodlee is down, QBO can fall back to Finicity for some banks. Xero has no fallback.

Manual import window. Xero’s 30-day window is more forgiving than QBO’s same-day duplicate detection. Xero bookkeepers have more time to recover without manual de-duplication.

Reconciliation report. Xero’s bank reconciliation report is a built-in tool. QBO’s reconciliation worksheet is more powerful but requires manual setup. Bookkeepers managing both should learn both tools.

The Yodlee Outage Calendar

Yodlee outages happen 4-6 times per year. The outages are predictable: they tend to cluster around bank maintenance windows, end-of-month cycles, and major US holidays. The bookkeeper who knows the pattern can plan around it.

The 3 prevention tactics for Yodlee outages.

Batch PDF download before known outage windows. End of month, end of quarter, and the days around US holidays (Thanksgiving, Christmas, New Year) are the highest-risk windows. Download PDFs before these windows even if the feed is working.

Monitor Xero’s status page. status.xero.com shows current and recent Yodlee outages. Check it every Monday. The page also has an RSS feed for outage alerts.

Document every Yodlee outage. Log the date, the affected clients, the recovery time, and any client communication. After 6 months, you have data on which clients are most affected. This data lets you prioritize the manual import workflow for high-risk clients.

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 Xero Support

Contact Xero support when the recovery steps don’t work. The 3 scenarios that need support: a Yodlee outage that lasts more than 48 hours, an account that disconnects immediately after reconnection, or a feed that connects but pulls zero transactions for 2+ cycles.

Xero support responds within 24 hours for paid plans (Xero Growing 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 QBO-specific, see the QBO 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.

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.