Late or missing bank transactions in Xero most commonly stem from temporary Xero/bank feed disruptions, expired or disconnected feeds, or recent security changes at the bank that require renewed consent or re‑authentication. The first diagnostic step is to check Xero’s Bank Feeds Disruptions page and confirm whether the account is flagged as “late” in Xero before taking reconnection or import actions.
Xero maintains a Bank Feeds Disruptions page that’s updated with known issues affecting feeds by region, which is the authoritative source to confirm widespread disruptions before troubleshooting locally. Xero also surfaces in‑app notices on the Bank Accounts widget when there are known disruptions, helping operators avoid unnecessary rework during an outage window. In addition, the general product status page links to the disruptions page and directs users to Xero Central for support when incidents arise.
Temporary Xero or bank-side incidents can delay or stop feeds, which is why checking the disruptions page and status is step one.
Expired Open Banking consent (typically every 90 days in affected regions) or lapsed connections stop new transactions until consent is renewed.
Security changes such as new passwords, MFA resets, or expired tokens require renewing the bank connection or resetting the integration.
Bank posting schedules vary; transactions often arrive on the next business day rather than in real time, and update cadence depends on the bank/provider.
Provider upgrades or transitions (e.g., open banking/Yodlee changes) can intermittently affect reliability and require re‑connecting or waiting for provider fixes.
Check Xero’s Bank Feeds Disruptions page to rule out known outages in the region.
Confirm general platform health and support routes via the Xero status page.
Look for “late” flags or alert banners on the Bank Accounts dashboard widget in Xero.
Use Manage Account to Renew/Update bank connection and follow prompts to re‑authenticate if required.
Re‑confirm 90‑day consent where open banking applies; lack of reconfirmation halts feeds from the expiry date.
If consent or credentials were renewed after a gap, expect to manually import missing days because some feeds won’t backfill prior to the refresh date.
Consider normal bank cadences and wait for the next business-day import if no disruption is listed and no connection errors persist.
If issues persist beyond normal cadence after reconnection, contact support through Xero Central as directed from the status page.
Run Xero’s reconciliation/statement reports to compare Xero’s statement balance to the actual bank statement and isolate the missing date range or lines. Use the Bank Statements tab and Reconciliation Report to identify duplicates or gaps and to ensure the “balance in Xero” ties to the bank statement for the target date. Pinpoint the last imported statement line and compare to online banking to determine if the gap is isolated or continuous.
Use Manage Account > Import Statement to upload a CSV (using Xero’s template) or an OFX file for larger ranges, then validate mappings before saving. Avoid duplicate entries by not importing periods already covered by a working feed, and if duplicates appear, remove only the manual or duplicated statements while preserving authentic feed lines. After import, reconcile with Find & Match and re‑run the reconciliation/statement checks to confirm everything now ties.
Establish a periodic control where the Xero statement balance is compared to actual bank statements (e.g., at month end or VAT return time) to catch drift early. Keep bank credentials current, complete MFA challenges promptly, and renew open banking consent as soon as Xero prompts to avoid feed stoppages. Monitor in‑app alerts and the disruptions page during known outages, and switch to temporary manual imports if a delay would otherwise block time‑sensitive reconciliation. Understand the provider’s cadence and avoid manual imports for dates already covered to prevent duplicate statement lines and reconciliation churn.
Provider transitions (direct feeds, open banking, or Yodlee changes) can cause intermittent interruptions or require re‑consent; follow Xero communications and re‑connect when prompted. New direct feeds sometimes have a lead time before transactions start appearing, and onboarding videos note it can take up to around 10 business days after applying with some banks. Not all banks support in‑Xero reconfirmation yet, so some organizations still need to authenticate on the bank’s site depending on the bank’s open banking implementation status.
Confirm disruptions or incidents, then check for “late” flags.
Renew or update the bank connection and complete any consent prompts.
If a gap remains, import the missing date range via CSV/OFX and reconcile.