Yardi Breeze Bank Feed Not Importing: Troubleshooting Checklist

If Yardi Breeze bank feed transactions are not importing, check the connection status, date range, account mapping, and whether the feed is paused or filtering out items. Then confirm the bank actually sent new transactions and that Breeze is pulling the correct ledger account. If all requirements are already met, the issue is usually a bank-side outage, a stale token that needs re-auth, or transactions being imported but hidden by filters or already matched/reconciled.

 

Quick checks that fix most cases

 

• Confirm the feed is connected: In Breeze, open the banking or bank feeds area and verify the status shows connected (not expired, attention, or needs login).
• Re-authenticate the bank login: Even if credentials are correct, banks often expire the connection token. Disconnect and reconnect the feed if Breeze allows, then sign in again.
• Check the date range: Many feeds only pull a limited history. Set the import view to include the last 30 to 90 days and refresh.
• Verify the correct bank account is linked: Make sure the feed is mapped to the right Breeze bank account (the ledger cash account). Wrong mapping can make imports appear “missing.”
• Refresh and look for filters: Remove filters like “unmatched only,” “cleared only,” or specific categories. Transactions may already be matched or marked cleared and therefore not visible.

 

Common reasons transactions do not show up

 

• No new bank activity: If the bank has pending items only, the feed may not import them until they post (pending is not final).
• Duplicate prevention: If transactions were previously imported, Breeze may block duplicates. Look for them in prior days or in the reconciliation screen.
• Multi-factor authentication loop: Some banks require periodic verification. If MFA is waiting, imports stop until re-verified.
• Bank maintenance or aggregator outage: The bank may be temporarily blocking third-party feeds. This can happen even when everything is set up correctly.
• Wrong entity or property context: If Breeze has multiple companies/properties, confirm the correct one is selected before checking the feed.

 

How to validate whether Breeze imported anything

 

• Compare counts: Check the bank’s posted transactions for the last few days, then compare to Breeze’s imported list for the same dates.
• Search by exact amount: Use the transaction amount from the bank and search in Breeze; it may be matched to a bill, deposit, or reconciliation item.
• Check reconciliation status: If a transaction is already reconciled, it may not appear in the “to import” or “to match” view.

 

If all requirements are met and it still will not import

 

• Force a clean reconnect: Disconnect the feed, wait a few minutes, reconnect, and complete MFA. This refreshes the authorization token.
• Try a different browser and disable VPN: VPNs, ad blockers, and strict privacy settings can break bank authentication screens.
• Wait for posting: If the bank shows pending only, wait until items post, then refresh the feed.
• Use manual import as a temporary workaround: Download a bank file (CSV or OFX/QFX if supported) and import to keep bookkeeping current.

 

When to contact support

 

• Connection shows error codes or “needs attention” after reconnecting: Provide screenshots, bank name, last successful import date, and the affected bank account.
• Imports stopped on a specific date for multiple users: This often indicates a bank-side change that support can confirm.
• Transactions import but land in the wrong account: Support may need to correct mapping or reset the feed link.