Sage Bank Feeds Connection Error Fix
Quick Answer:
Bank feeds connection errors occur when Sage can't connect to your bank due to authentication issues, bank service outages, or incorrectly mapped categories. Fix by refreshing credentials, checking bank status, and remapping transaction categories.
What is a Sage Bank Feeds Connection Error?
Sage bank feeds connection errors prevent automatic import of bank transactions into your accounting software. These errors can result from authentication failures, bank service disruptions, expired credentials, or category mapping issues causing duplicate or missing entries.
Error Bank Feeds: Connection failed or transactions not importing
Your bank feed is unable to connect or transactions are not importing correctly into Sage.
Symptoms:
- •Error message when trying to refresh bank feeds
- •Duplicate transactions appearing in bank feed
- •Missing transactions that appear on bank statement
- •Authentication or login failures
- •Incorrect category mapping causing import errors
- •Bank feed shows "service unavailable" or timeout errors
Resolution Steps:
- 1.Refresh bank credentials and re-authenticate
- 2.Check bank service status for known outages
- 3.Review and correct category mappings
- 4.Delete duplicate transactions before accepting feed
- 5.Reconnect bank feed if authentication expired
Quick Fix for Bank Feeds Error (8 Minutes)
Fastest Solution
- Go to Banking module → Bank Feeds
- Click "Refresh" or "Update Feeds" button
- If error appears, click "Reconnect" or "Re-authenticate"
- Enter your online banking credentials
- Verify category mappings are correct
- Review imported transactions for duplicates before accepting
Detailed Solution Steps
Start by refreshing your bank authentication credentials:
- Open Sage and navigate to Banking → Bank Feeds
- Select the bank account showing connection error
- Click "Reconnect" or "Re-authenticate Bank"
- Enter your current online banking username and password
- Complete any multi-factor authentication (MFA) if required
- Wait for connection confirmation message
If your bank recently changed their online banking system or you changed your password, you must re-authenticate the connection.
Verify if the issue is with your bank's service:
- Check your bank's website for service announcements
- Verify you can log in to online banking directly
- Look for maintenance windows or known outages
- Check Sage's bank feed status page for known issues
- If bank is down, wait and retry in 30-60 minutes
101: Invalid credentials - Re-authenticate required102: Bank temporarily unavailable - Retry later103: Account locked - Contact bank185: Terms & conditions update - Accept in online bankingOL-301: Connection timeout - Check internet connectionIncorrect category mappings can cause import failures or duplicate entries:
- Go to Bank Feeds → Settings or Mapping Rules
- Review auto-categorization rules for each transaction type
- Ensure categories map to valid nominal codes in your chart of accounts
- Check for rules that might cause duplicate categorization
- Update or delete incorrect mapping rules
- Test by importing a small batch of transactions
Prevent and remove duplicate entries from bank feeds:
- Before accepting imported transactions, check for duplicates
- Compare feed transactions with existing bank entries in Sage
- Use "Match" feature to link feed items to existing entries instead of creating new ones
- Uncheck duplicates before clicking "Accept" or "Import"
- If duplicates already imported, void or delete the duplicate entries
- Adjust matching rules to prevent future duplicates
Address transactions that don't appear in bank feed:
- Verify date range for bank feed import
- Check if transaction date falls outside import window
- Manually enter missing transactions if they won't import
- Verify bank feed is set to import all transaction types (deposits, withdrawals, transfers)
- Check bank account filter settings aren't excluding certain transactions
If problems persist, completely reset the bank feed connection:
- Go to Bank Feeds → Manage Feeds
- Select problematic bank account
- Click "Disconnect" or "Remove Feed"
- Confirm disconnection
- Click "Add Bank Feed" or "Connect New Feed"
- Search for your bank and complete authentication
- Set import start date to avoid duplicating historical transactions
Be careful with the import start date when reconnecting to avoid creating duplicate historical transactions.
Why Do Bank Feeds Connection Errors Occur?
Common Causes
- Expired Authentication: Bank credentials changed or security tokens expired requiring re-authentication
- Bank Service Outages: Temporary disruptions in bank's online banking API or planned maintenance
- Terms & Conditions Updates: Bank updated terms requiring acceptance before feed will work
- Incorrect Category Mapping: Transaction categories mapped to invalid or deleted nominal codes
- Network or Firewall Issues: Corporate firewall blocking connection to bank's servers
- Account Changes: Bank account closed, frozen, or restructured requiring feed reconfiguration
How to Prevent Bank Feeds Errors
Best Practices:
- Test bank feeds regularly (daily or weekly) to catch errors early
- Update bank credentials in Sage immediately after changing online banking password
- Review and accept bank feed transactions promptly to avoid backlogs
- Set up clear, consistent categorization rules to reduce import errors
- Always check for duplicates before accepting imported transactions
- Keep a separate record of expected bank credentials for quick troubleshooting
Frequently Asked Questions
Why do I keep getting duplicate transactions in my bank feed?
Duplicates occur when transactions are both manually entered and imported via feed, or when the feed is reconnected with overlapping date ranges. Always check for existing entries before accepting feed transactions, or use the "Match" feature to link feed items to existing entries.
How often should I refresh my bank feeds?
For best results, refresh bank feeds daily or at minimum weekly. This keeps your records current and makes it easier to spot errors or discrepancies before they accumulate.
What if my bank isn't listed in Sage bank feeds?
Not all banks support direct feeds to Sage. If your bank isn't listed, you can manually import transactions using CSV/OFX file downloads from your online banking, or contact Sage support to request adding your bank.
Can I delete bank feed transactions I've already accepted?
Yes, but be careful. Once accepted, bank feed transactions become regular bank entries in Sage. You can void or delete them like any other transaction, but this may affect your reconciliation. It's better to review carefully before accepting.
Related Resources
Need Professional Help?
If you're still experiencing bank feed connection errors after following these steps, or if you need help setting up category mappings, our Sage experts are here to help.
Get Expert Support