Let us help you tackle any Software issues and optimize your accounting workflow. 

Sage 50 crashes when saving transactions

Missing Transactions in Sage 50 Bank Feeds: Here’s How to Fix It

You open Sage 50 expecting to see the latest transactions from your bank, but some payments, deposits, or transfers are missing. Perhaps the bank feed has downloaded newer transactions but skipped several from earlier dates. In other cases, the feed appears to refresh successfully, yet no new entries show up in the transaction list. This can make it difficult to keep your accounts current and complete your bank reconciliation accurately.

Missing transactions in Sage 50 Bank Feeds do not always mean that your financial data has been deleted. The transactions may fall outside the selected download period, remain unavailable through the bank connection, be affected by an authentication or synchronization problem, or already have been downloaded and processed. Sometimes the issue is limited to one bank account, while other feeds continue working normally.

Before reconnecting the bank or importing transactions manually, identify which transactions are missing and whether they appear on your bank’s website. This distinction helps you determine whether the problem is with the bank, the feed connection, or Sage 50’s transaction-processing workflow. The following solutions explain how to investigate missing transactions and restore the feed without creating duplicate accounting entries.

Why Are Transactions Missing From Sage 50 Bank Feeds?

Several factors can prevent transactions from appearing in Sage 50. The most useful starting point is to compare the bank’s transaction history with the entries available in the Sage 50 feed.

Possible causeWhat you may notice
Incorrect download date rangeTransactions from earlier dates are missing, while recent entries appear.
Bank feed synchronization delayTransactions appear on the bank’s website but are not yet available in Sage 50.
Authentication failureThe feed cannot retrieve transactions because the bank requires updated login information.
Bank connection interruptionThe feed refresh fails or returns a connection error.
Transactions already downloadedEntries are present in the feed history or have already been processed.
Incorrect bank account mappingTransactions are associated with a different Sage 50 bank account.
Bank-side feed restrictionsThe bank does not provide certain pending, historical, or recently posted transactions through the connection.
Duplicate or matching entriesA transaction has been matched, excluded, or processed and is no longer in the expected list.
Bank feed service issueThe connection provider or bank is temporarily unable to return transaction data.

A key distinction is whether the transaction is missing from the bank feed itself or from the Sage 50 accounting records. These are different problems. A transaction may have downloaded successfully but still need to be reviewed, matched, or posted before it appears in the relevant accounting activity.

How to Fix Missing Transactions in Sage 50 Bank Feeds?

Work through these solutions in order. Start by checking whether the transactions are genuinely missing, then investigate the bank feed connection and download process. Avoid disconnecting a working feed or manually entering transactions until you have checked whether the entries have already been downloaded.

1. Check the Bank’s Transaction History and the Sage 50 Date Range

First, establish whether the missing transactions have actually been posted by your bank. A transaction shown as pending may not yet be available to the bank feed service.

Steps to check:

  1. Sign in to your bank’s official website.
  2. Open the relevant account’s transaction history.
  3. Identify the missing payments, receipts, and transfers.
  4. Check their transaction dates and whether they are pending or fully posted.
  5. Open Sage 50 and select the corresponding bank account.
  6. Review the date range or filters used to display downloaded transactions.
  7. Expand the date range if the missing entries fall outside the period currently displayed.
  8. Compare the transaction dates and amounts with the bank statement.

Do not assume that a transaction is missing simply because it does not appear in the latest download. Some banks make transactions available to connected services later than they appear in online banking. If the transactions are still pending, wait until the bank posts them. If they are posted but unavailable through the feed, continue with the connection checks.

2. Check the Sage Bank Feeds Service Status

A bank feed can stop updating because of a temporary issue with the bank, the feed provider, or the Sage service. In that situation, changing employee permissions or editing the company data will not resolve the underlying problem. Sage provides a Bank Feeds status page for checking known service disruptions and bank-specific issues.

Steps to check the status:

  1. Identify the bank connected to the affected Sage 50 account.
  2. Open Sage’s Bank Feeds service status information.
  3. Check whether your bank or the feed service has a reported incident.
  4. Review any available information about the affected service and expected resolution.
  5. If an incident is reported, wait for the service to recover before making changes to the bank connection.
  6. Retry the download after the service is available.

If the status page shows no known issue, continue with the local connection and synchronization checks. A successful status check does not guarantee that every individual bank account is working. It simply helps rule out a reported service disruption.

3. Refresh the Bank Feed and Check for New Transactions

If the bank feed is connected but the latest transactions are not appearing, try downloading them again. In Sage 50 Accounts, the bank feed download process is available from the bank account’s Bank Feeds options.

Steps to refresh the feed:

  1. Open Sage 50 Accounts.
  2. Select Bank accounts.
  3. Open the bank account experiencing the problem.
  4. Select Bank Feeds.
  5. Choose Download transactions.
  6. Wait for the download attempt to finish.
  7. Review the returned transactions.
  8. Compare the available entries with your bank statement.

If you receive a timeout or similar connection error, avoid clicking the download option repeatedly. Sage’s guidance for certain Bank Feeds timeout errors recommends checking online banking access and waiting approximately 60–90 seconds after the previous refresh before trying again. If the refresh completes but the transactions remain missing, note the last successful download date and move to the next solution.

4. Restart the Computer Holding the Sage 50 Company Data

A bank feed problem can sometimes be associated with the Sage 50 data environment rather than the bank credentials themselves. For existing Bank Feeds problems, Sage’s troubleshooting guidance recommends restarting the computer that holds the company data. This is particularly relevant in a network installation where workstations access a shared company.

Steps to restart safely:

  1. Ask all users to save their work.
  2. Make sure everyone has closed Sage 50.
  3. Confirm that no one is processing transactions or working in the company.
  4. Restart the computer that holds the Sage 50 company data.
  5. Allow Windows and the required Sage services to finish starting.
  6. Open Sage 50 again.
  7. Select the affected bank account.
  8. Try downloading the transactions.

Do not restart the server while employees are using Sage 50. A forced shutdown can interrupt accounting operations and create additional problems.

If the missing transactions still do not appear, check the Sage 50 version and follow the relevant guidance for your release.

5. Check the Sage 50 Version and Reconnect the Bank Feed if Necessary

Sage’s troubleshooting instructions for existing Bank Feeds problems distinguish between installations running version 29.2 or above and older releases. The general guidance is to check the version, restart the computer holding the data, and, when there is no reported error but transactions remain missing, wait five working days before retrying. If the transactions are still missing after that period, Sage recommends disconnecting and reconnecting the feed.

First, check your version:

  1. Open Sage 50 Accounts.
  2. Select Help > About.
  3. Find the Version Number under Program Details.
  4. Record the version so you can follow the appropriate reconnection instructions.

If you need to reconnect the feed:

  1. Make sure all users have closed Sage 50.
  2. Confirm that the existing feed has been checked and that the missing transactions are not simply delayed.
  3. Open the relevant bank account’s Bank Feeds settings.
  4. Follow the disconnect procedure applicable to your Sage 50 version.
  5. Select the option to reconnect the bank account.
  6. Complete the bank’s authorization process.
  7. Wait for the connection to finish.
  8. Download transactions and compare them with the bank statement.

Reconnecting a feed is not the first step for every missing transaction. It should follow the appropriate waiting and troubleshooting process. Sage notes that a newly reconnected feed can take time to become available again.

Important: Before reconnecting, record the last transaction date already entered or processed in Sage 50. Check the date range and transaction history carefully afterward so you do not create duplicate entries.

6. Check Whether Transactions Have Already Been Downloaded or Are Hidden in the Transactions List

Sometimes transactions appear to be missing because they have already been downloaded, matched, processed, or displayed in a different order. This is particularly important when investigating bank reconciliation differences. A transaction may exist in Sage 50 but be difficult to locate because the Transactions window is sorted by another column.

Steps to investigate:

  1. Open the relevant bank account.
  2. Review the bank feed transaction history.
  3. Check whether the missing entries have already been processed or matched.
  4. Open the relevant Transactions or Financials window.
  5. Search using the transaction date, amount, reference, or description.
  6. Check the column used to sort the transaction list.
  7. Select the No column to restore the account reference order.
  8. If you use Sage 50 version 29 or above, use the Refresh button where available to update the displayed list.

Sage documents transaction sorting and refreshing as checks when entries appear to be missing from the Transactions or Financials window. Do not enter an additional receipt or payment simply because you cannot immediately find it. Confirm that the original entry does not already exist in the accounting records.

7. Enter Confirmed Missing Transactions Manually

If the bank statement confirms that transactions are posted but they remain unavailable through the bank feed after the relevant checks, you may need to enter them manually. Sage’s guidance for missing transactions in Sage 50 Accounts recommends manually entering the missing entries and monitoring future downloads. Before doing so, compare the bank statement against both the bank feed and the Sage 50 accounting records.

Steps to enter a missing transaction:

  1. Identify each transaction that is genuinely absent.
  2. Record its date, amount, reference, and description from the bank statement.
  3. Determine whether it is a customer receipt, supplier payment, payment on account, bank payment, or bank receipt.
  4. Open the appropriate customer, supplier, or bank transaction area in Sage 50.
  5. Select the correct transaction type.
  6. Enter the details accurately.
  7. Check the nominal account, customer or supplier allocation, and VAT treatment where applicable.
  8. Save the transaction.
  9. Compare the updated bank account balance with the statement.

Use the appropriate transaction type for the underlying business activity. For example, a customer receipt should be allocated correctly rather than entered as an unrelated bank receipt.

Avoid duplicates: If the bank feed later downloads the same transactions, check whether they match the manually entered records. Do not post them again as new payments or receipts. Use the appropriate matching or reconciliation process available in your Sage 50 version. If you are unsure about the accounting treatment, ask your bookkeeper or accountant before posting manual entries.

How to Fix Sage 50 Bank Reconciliation Differences Caused by Missing Transactions?

Missing bank feed transactions can affect reconciliation even when the rest of the accounting records are correct. If a payment or receipt appears on the bank statement but not in Sage 50, the statement balance and Sage bank balance may not agree.

Before changing the reconciliation, identify the exact entries responsible for the difference.

A. Compare the Bank Statement With Sage 50

Start by comparing the statement period with the transactions recorded in Sage 50.

  1. Open the bank statement for the period you are reconciling.
  2. Open the corresponding bank account in Sage 50.
  3. Compare transaction dates, references, and amounts.
  4. Identify entries that appear on the statement but not in Sage 50.
  5. Check whether those entries are already recorded under a different reference or date.
  6. Make a list of confirmed missing transactions.

Also check whether the difference comes from an outstanding payment or receipt. A transaction that has been entered in Sage 50 but has not yet cleared the bank may be legitimate and should not automatically be treated as missing.

B. Check Whether Transactions Were Matched or Processed

If a transaction was downloaded previously, it may no longer appear in the unprocessed bank feed list.

Review the relevant bank account records and transaction history before entering anything manually. Confirm that the original entry is not already included in the accounting records.

This is especially important after reconnecting a bank feed. A new connection may retrieve transactions that overlap with entries already recorded in Sage 50.

C. Avoid Changing the Opening Balance to Force a Reconciliation

Do not adjust the opening balance simply to make the reconciliation agree. The difference may represent missing receipts, payments, duplicate entries, or transactions recorded with incorrect dates.

Identify and correct the underlying transactions first. If you change an opening balance without understanding the reason, future reconciliations may become more difficult.

What to Do if Sage 50 Bank Feeds Still Do Not Download Transactions?

If the feed remains connected but does not retrieve transactions after following the troubleshooting steps, gather the relevant information before contacting support.

Record:

  • The Sage 50 version and release number.
  • The name of the affected bank.
  • The last successful bank feed download date.
  • The dates and amounts of the missing transactions.
  • Whether the transactions appear on the bank’s website.
  • Whether other bank accounts can download transactions.
  • Any error message or code displayed by Sage 50.
  • Whether the problem began after a software update or bank authentication change.

This information helps distinguish a bank-side issue from a Sage service problem or a company-specific connection issue. Contact your bank if transactions are not available through its online banking service or if it confirms that its external banking connection is experiencing problems. Contact Sage support if the bank confirms that the transactions are available but the Sage 50 feed continues to omit them.

Do not share your online banking password, one-time security code, or other confidential authentication information in an ordinary support message.

How to Prevent Missing Transactions in Sage 50 Bank Feeds?

A few routine checks can reduce the risk of missing entries affecting your accounting records.

  • Review feeds regularly: Check downloaded transactions frequently rather than waiting until the end of a reconciliation period.
  • Monitor the last download date: Keep track of when each bank feed last updated successfully.
  • Check bank feed status: Investigate reported service disruptions before changing your account settings.
  • Maintain current authentication details: Complete bank reauthorization requests when required.
  • Keep transaction records: Retain bank statements and payment references so missing entries can be verified.
  • Check before entering transactions manually: Search Sage 50 for existing entries to avoid duplicates.
  • Reconcile regularly: Compare Sage 50 records with bank statements throughout the accounting period.
  • Document connection problems: Record error messages and missing transaction dates so recurring issues can be identified.

These checks help identify download problems early and reduce the chance of missing entries affecting month-end or year-end reconciliation.

Conclusion

Missing transactions in Sage 50 Bank Feeds can result from delayed bank updates, service disruptions, connection problems, authentication requirements, or transactions that have already been downloaded and processed. The first step is to compare the bank statement with the Sage 50 transaction history to confirm what is genuinely missing.

Check the bank feed status, refresh the connection, and follow Sage’s troubleshooting guidance for your installed version. If the transactions remain unavailable, consider reconnecting the feed after the recommended checks. For confirmed missing entries, Sage’s guidance is to enter them manually and monitor subsequent downloads carefully.

Always check for duplicates before posting or matching transactions. Keeping the bank feed, accounting records, and reconciliation history consistent will help maintain accurate financial information.

FAQs of Missing Transactions in Sage 50 Bank Feeds:

Why are transactions missing from Sage 50 Bank Feeds?

Transactions may be missing because the bank has not yet made them available, the feed has stopped synchronizing, authentication needs updating, or the transactions have already been downloaded and processed. Compare the bank statement with Sage 50 before deciding which correction is required.

How do I refresh bank feeds in Sage 50?

Open Bank accounts, select the relevant account, go to Bank Feeds, and choose Download transactions. Wait for the download to finish and review the returned entries. If the feed reports an error, follow the instructions for that specific error rather than repeatedly refreshing it.

Why does Sage 50 Bank Feeds show no new transactions?

The bank may not have released new transactions to the feed service, or a connection or authentication problem may be preventing downloads. Check the bank’s online transaction history, review the Bank Feeds service status, and confirm that the connection is still active.

How can I recover missing bank feed transactions in Sage 50?

First, check whether the entries are available through the bank feed or already exist in Sage 50. If confirmed transactions remain unavailable, Sage’s guidance recommends entering them manually and monitoring future downloads. Check for duplicate entries before processing any transactions retrieved later.

Can reconnecting a Sage 50 bank feed retrieve missing transactions?

It may help when an existing feed has stopped working, but reconnecting is not guaranteed to retrieve every historical transaction. Follow the troubleshooting guidance for your Sage 50 version, record the last successfully processed date, and check the download results carefully after reconnecting.

Why are bank transactions missing during Sage 50 reconciliation?

A transaction may be absent from the accounting records, recorded under a different date or reference, or already processed in Sage 50. Compare the bank statement with the Transactions window and review outstanding payments and receipts before making adjustments to the reconciliation.

Should I manually enter transactions if Sage 50 Bank Feeds does not download them?

Yes, confirmed missing transactions may need to be entered manually when they remain unavailable through the bank feed. Sage recommends this approach for missing transactions in Sage 50 Accounts. Use the correct customer receipt, supplier payment, or bank transaction type, and check for duplicates if the feed downloads the entries later.

Related Articles