Summary
Description
Sage checks for new bank transactions each day and downloads any that are available.
Your bank can take longer to share new transactions, so Sage can show them later than your bank statement.
Wait 72 working hours before you treat missing transactions as an issue. After 72 working hours, investigate the delay only when the following apply:
- No new transactions have appeared
- The bank feed still shows as connected
- sage.com/en-gb/sage-business-cloud/sage-accounting/bank-feed-status shows no active incident
This helps you tell the difference between a normal delay and a problem that needs investigation.
Resolution
If your transactions haven’t appeared after 72 working hours, disconnect and reconnect your bank feed.
Before you disconnect and reconnect
Key points:
- Disconnecting the bank feed deletes all unmatched transactions
- The start date you choose when reconnecting affects your transactions. Choosing the wrong date can cause duplicates or gaps
What this means:
When you reconnect, you set a date for Sage to start downloading transactions again.
If you choose an earlier date than your last processed transaction, Sage will import duplicates. Choosing a later date could cause missing transactions.
- From Banking, find the bank account you want to disconnect.
- Select Actions, then select Disconnect bank.
- Read the warning message, then select Disconnect to confirm.
- Now select Connect to Bank.
- Enter the name of your bank or credit card provider in the search box.
- Follow the on-screen steps to authorise the connection.
- Confirm the date you want to start importing transactions from.
After you reconnect your bank feed, Sage Accounting starts downloading transactions from the date you chose.
When they’re ready, the new entries appear on the Transactions page so you can check and save them.
Alternatively, if your bank feed is unavailable, you can Import a bank statement.