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

Sage 50 crashes when saving transactions

Sage Account Reauthorisation Issue: Causes and Solutions

A Sage account reauthorisation issue can occur when a connected bank account or credit card requires renewed permission to share transactions with Sage Accounting. You may see a reauthorisation message, find that bank feeds have stopped updating, or complete the bank’s approval process only to return to Sage without the account reconnecting.

These problems can affect different financial institutions in different ways. For example, a Lloyds current account may reconnect successfully while an American Express credit card remains stuck on an authorisation screen. In other cases, the bank’s approval page may open but fail to return the completed authorisation to Sage.

Sage Accounting requires many connected bank feeds to be reauthorised every 90 days for security reasons. After successful reauthorisation, transactions can take up to 72 hours to appear, depending on the connection. Browser pop-up restrictions, incorrect banking credentials, outstanding bank messages, and temporary bank-feed service issues can also prevent the process from completing.

Why Is Sage Account Reauthorisation Not Working?

Before disconnecting a bank account, identify where the authorisation process fails. The correct solution depends on whether Sage is requesting new permission, the bank is rejecting the login, or the authorisation completes without updating the connection in Sage.

ProblemWhat to check first
Sage asks you to reauthorise every 90 daysRenew the bank-feed authorisation
Reauthorisation screen does not openBrowser pop-ups and redirects
Bank login failsCredentials, security verification, and bank access
Bank approves access but Sage does not updateRedirect completion, browser session, and connection status
American Express will not reconnectAmex authorisation flow and browser settings
Lloyds account will not connectLloyds online banking access and connection approval
Bank feed remains disconnectedBank-feed status and supported connection method
Authorisation succeeds but transactions are missingSynchronisation delay and transaction availability
Reauthorisation repeatedly failsBank-side restrictions or a persistent integration problem

1. Expired Bank Authorisation

Many Sage bank feeds require renewed authorisation every 90 days. When the permission expires, Sage displays a message asking you to reconnect the bank account. Until the authorisation is renewed, the feed may stop retrieving new transactions.

2. Browser Pop-Up or Redirect Problems

Sage may open a separate window or redirect you to your bank’s website to complete the approval process. If the browser blocks the window, the process may stop before the connection is completed. This is particularly relevant when the bank’s website says to return to Sage, but the Sage account still displays the original reauthorisation message.

3. Incorrect Credentials or Incomplete Bank Verification

The connection may fail if you enter outdated credentials, use a different login from the one required by the bank, or leave a security prompt unanswered. Some banks also require you to accept updated terms and conditions or approve third-party access before allowing Sage to retrieve transactions.

4. Temporary Bank Feed or Synchronisation Problems

Even after successful authorisation, transactions may not appear immediately. The bank and Sage must complete the connection and retrieve the available transaction data. A delay does not automatically mean that the authorisation failed.

How to Fix Sage Account Reauthorisation Issue

Follow the steps below in order. Start with the bank’s own website and the normal reauthorisation process before attempting to disconnect and reconnect the account.

Step 1: Check Your Bank Account and Sage Bank Feed Status

First, confirm that the financial institution is accessible and that Sage is not reporting a wider bank-feed problem.

  1. Open a web browser.
  2. Visit your bank’s official website.
  3. Sign in using your normal online banking credentials.
  4. Complete any security verification requested by the bank.
  5. Review outstanding messages, updated terms, or requests to approve connected services.
  6. Check the Sage bank-feed status information for a reported incident.

If you cannot sign in to the bank directly, resolve the banking login issue before attempting to reauthorise Sage. If the bank works normally but Sage still requests authorisation, continue to the next step.

What the result means:

  • If the bank rejects your credentials, correct the banking login problem first.
  • If the bank requests approval for third-party access, complete the bank’s official process.
  • If Sage reports a bank-feed incident, wait for the service to recover before repeatedly reconnecting the account.
  • If both services appear operational, attempt the normal reauthorisation process.

Step 2: Reauthorise the Connected Bank Account

If Sage displays a reauthorisation message, use the account’s built-in reconnect option. In Sage Accounting, the usual process is:

  1. Open Sage Accounting.
  2. Go to Banking.
  3. Open Bank accounts or locate the affected bank account.
  4. Find the account displaying the reauthorisation message.
  5. Select Actions.
  6. Choose Reconnect to bank or Reauthorise connection, depending on the interface.
  7. Follow the prompts to access your bank.
  8. Enter the required credentials and complete any security verification.
  9. Approve the connection and return to Sage.

The exact wording can vary by Sage Accounting product and interface. After returning to Sage, check whether the reauthorisation warning has disappeared. Do not assume the process is complete just because the bank displayed an approval message.

If the account status updates successfully, allow time for transactions to arrive. Sage indicates that bank transactions can take up to 72 hours to appear after reconnection. If the bank approves the request but Sage continues to display the reauthorisation message, proceed to the browser checks.

Step 3: Allow Pop-Ups and Redirects in Your Browser

If selecting Reconnect to bank does nothing, or the bank’s authorisation page does not return you to Sage correctly, check your browser settings. A blocked pop-up or redirect can interrupt the third-party banking authorisation process. Try the following:

  1. Open your browser settings.
  2. Find the permissions for pop-ups and redirects.
  3. Allow the necessary pop-ups for the Sage site.
  4. If the bank’s authorisation page is blocked, allow the required redirect.
  5. Return to Sage Accounting.
  6. Start the reauthorisation process again.

Use the browser’s permission controls rather than disabling all security protections permanently. If the page opens but remains blank or fails to complete, temporarily test another supported browser, such as Chrome, Edge, or Firefox.

A. What the result means:

If reauthorisation works after allowing pop-ups, the problem was likely related to the browser blocking part of the connection process.

If the bank approves access but Sage still does not update, continue to the next step.

Step 4: Clear Browser Cache and Cookies

If the authorisation page repeatedly fails to return to Sage, stored browser data may be interfering with the sign-in session. Before clearing data, make sure you know your Sage and bank login credentials. Then:

  1. Open your browser’s privacy settings.
  2. Find the option to clear browsing data.
  3. Clear cached files and cookies for the relevant browser session or site, as appropriate.
  4. Close and reopen the browser.
  5. Sign in to Sage Accounting again.
  6. Start the bank reauthorisation process from the affected account.

You may need to sign in to websites again after clearing cookies. If the process works in another browser but not in your normal browser, the issue is more likely related to the original browser’s data or configuration. If the problem continues across browsers, investigate the bank-specific connection next.

Sage American Express Credit Card Linking Problems

American Express connections can behave differently from current-account connections because the credit card provider has its own authorisation and approval process.

A common symptom is that the American Express website confirms authorisation and instructs you to return to Sage, but the Sage account does not appear to reconnect. If your American Express credit card will not link to Sage, follow these checks.

Step 1: Start the Process From Sage on a Computer

If you are trying to reconnect the Amex feed through the Sage mobile app, try completing the connection from Sage Accounting in a desktop browser.

A desktop browser can make it easier to see the authorisation window and manage pop-ups or redirects. Once the bank connection is restored, the connected account can also be accessed through the mobile app where supported.

Step 2: Start a Fresh Authorisation Attempt

Open the affected American Express account in Sage and select the available reauthorisation option.

Follow the prompts to open the American Express authorisation page. Sign in through the official bank page and approve the requested access.

When American Express tells you to return to Sage, return to the original Sage session and wait for the account status to update. Avoid starting multiple authorisation attempts in separate tabs at the same time. Multiple sessions can make it harder to identify which attempt completed.

Step 3: Check the Return From American Express to Sage

If Amex displays an approval confirmation but Sage does not change:

  1. Check whether the original Sage browser tab is still open.
  2. Confirm that pop-ups and redirects are permitted.
  3. Close any incomplete authorisation windows.
  4. Return to Sage and check the bank account status.
  5. If the account still needs authorisation, start a new attempt after checking the browser settings.

If the same failure occurs, try a different supported desktop browser and repeat the process.

Step 4: Confirm Whether the Connection Was Completed

Do not repeatedly authorise the same account without checking the result. Look for the reauthorisation warning in Sage. If the warning disappears, the connection may be restored even if transactions have not yet arrived.

If the warning remains, the authorisation handoff may not have completed successfully. If the bank repeatedly approves access but Sage never updates, contact Sage support and American Express as appropriate to determine which side is failing.

Sage Lloyds Bank Account Connection Problems

If your Lloyds current account will not reconnect to Sage, start with the same basic checks: sign in to Lloyds directly, complete any outstanding security steps, and verify that Sage can open the authorisation page. If Lloyds authorisation completes successfully but the Sage connection remains inactive, use the following sequence.

Step 1: Verify Lloyds Online Banking

Sign in to the official Lloyds online banking service and confirm that the account is accessible. Check for any messages requiring you to accept updated terms, approve third-party access, or complete additional security verification.

Step 2: Reauthorise the Lloyds Account in Sage

Open the affected account in Sage Accounting and select the available reconnect or reauthorisation option. Follow the prompts and complete the Lloyds authentication process. Return to Sage and confirm whether the connection status has changed.

Step 3: Allow for the Bank Feed Schedule

A successful connection does not mean that every transaction will appear instantly. Sage’s published bank-feed guidance lists Lloyds among the banks whose direct-feed transactions may arrive on a scheduled basis rather than immediately after each transaction. The exact timing can depend on the feed and service conditions. If the connection is active but recent transactions are missing, compare the latest available transactions in Lloyds with the transactions displayed in Sage before repeating the authorisation.

Step 4: Escalate a Persistent Lloyds Connection Failure

If Lloyds repeatedly approves the connection but Sage continues to request authorisation, note the time of the last attempt and the exact message displayed. Contact Sage support if the failure appears to occur when returning to Sage. Contact Lloyds if the bank rejects the login, approval, or third-party access request. This helps identify whether the problem lies with the bank’s authentication service or Sage’s connection process.

Sage Account Authorisation Error: Additional Checks

If the standard reauthorisation process fails, check the following before disconnecting the account.

A. Verify the Login Details

Enter your online banking credentials manually instead of relying on saved or autofilled details. Make sure you are using the login required by the bank for the selected account. Never share your bank password or security codes with anyone offering to troubleshoot the connection.

B. Check Third-Party Access

Some financial institutions require you to approve access for external accounting services. Review the bank’s online banking settings and any pending approval requests. If third-party access has been disabled, follow the bank’s official instructions to restore it.

C. Use a Supported Browser

Try a different supported browser if the connection process fails repeatedly. Also check that cookies, pop-ups, and redirects required for the authorisation process are not being blocked. If necessary, temporarily disable a browser extension that may be interfering with the page, then re-enable it after testing.

D. Confirm the Correct Bank Feed

Make sure you selected the correct bank or credit card provider and account type when connecting the feed. If the bank offers multiple connection options, select the one that matches the account and connection method supported by Sage.

Sage Account Reauthorisation Succeeds but Transactions Are Missing

A successful reauthorisation and a successful transaction synchronisation are two different things. If Sage confirms the connection but the bank feed does not immediately update, use this sequence:

  1. Confirm that the bank account remains connected in Sage.
  2. Check the bank website for the latest posted transactions.
  3. Review the latest transaction date visible in Sage.
  4. Allow up to 72 hours for transactions to appear after reauthorisation.
  5. Check the bank-feed status information for a known service issue.
  6. If transactions are still missing after the expected delay, contact Sage support.

Do not disconnect the account simply because transactions have not appeared immediately after reauthorisation. If you need to maintain your accounting records while the feed is unavailable, use a supported bank-statement import or enter transactions manually. Review the date range carefully so you do not create duplicate transactions when the bank feed resumes.

Disconnect and Reconnect the Sage Bank Feed

Disconnecting and reconnecting a bank feed can help when normal reauthorisation and browser troubleshooting do not work. However, this should be a later step because it can affect unmatched transactions and the next import date.

Before proceeding:

  • Record the last date transactions were successfully imported.
  • Review any transactions awaiting processing.
  • Export or record bank rules if needed.
  • Confirm which Sage account is linked to the bank feed.
  • Choose a suitable date for restarting the transaction download.

Then:

  1. Open Banking in Sage Accounting.
  2. Find the affected bank account.
  3. Select Actions.
  4. Choose Disconnect bank.
  5. Read the warning and confirm only when you understand the consequences.
  6. Select the option to connect the bank again.
  7. Search for the correct bank or credit card provider.
  8. Follow the authorisation prompts.
  9. Select the appropriate transaction start date.
  10. Review the imported transactions and check for gaps or duplicates.

Important: Sage warns that disconnecting a bank feed deletes unmatched transactions. Choosing an incorrect start date when reconnecting can also result in duplicate transactions or missing entries. Where possible, choose a start date after the latest transaction already processed in Sage. If the feed stopped partway through a day, review that day’s transactions carefully before deciding where to restart.

How to Prevent Future Sage Bank Reauthorisation Problems?

You cannot prevent every bank authentication failure, but these practices can reduce avoidable interruptions.

1. Complete Reauthorisation Prompts Promptly

When Sage asks you to renew bank-feed access, complete the process rather than waiting for transactions to stop downloading.

2. Keep Banking Access Current

Check that your online banking credentials work and review messages or security requests that could prevent third-party access.

3. Maintain Browser Compatibility

Keep your browser updated and allow the pop-ups, cookies, and redirects needed to complete the bank’s approval process.

4. Record the Last Successful Transaction Date

Knowing when the feed last updated makes it easier to identify missing transactions and choose a safe reconnection date.

5. Avoid Unnecessary Disconnections

Use the normal reauthorisation option first. Disconnect and reconnect only when simpler checks fail and you have reviewed unmatched transactions and bank rules.

Conclusion

A Sage account reauthorisation issue usually involves expired bank-feed permission, incomplete bank authentication, a browser redirect problem, or a connection that has not synchronised after approval.

Start by confirming that your bank account works, check the Sage bank-feed status, and use the normal reconnect option. If the authorisation page fails to open or return to Sage, check browser pop-ups, redirects, and cookies. For American Express, consider completing the process through a desktop browser. For Lloyds, verify online banking access and allow for the bank feed’s transaction schedule.

If these checks fail, investigate the connection further before disconnecting the feed. Back up relevant information, record the last successful transaction date, and review unmatched transactions before reconnecting. This helps restore the bank feed while reducing the risk of missing or duplicated accounting entries.

FAQs of Sage Account Reauthorisation Issue:

Why does Sage keep asking me to reauthorise my bank account?

Many Sage Accounting bank feeds require reauthorisation every 90 days for security. If you see a reauthorisation message, open the affected bank account and select the available reconnect or reauthorisation option. If the message remains after approval, check browser redirects and confirm whether Sage updated the connection status.

How do I reauthorise a connected bank account in Sage?

Open Sage Accounting, go to Banking, and locate the account displaying the reauthorisation message. Select Actions and choose Reconnect to bank or Reauthorise connection, depending on your interface. Follow the bank’s sign-in and approval steps, then return to Sage to verify the connection.

Why does my American Express account say authorised but still not link to Sage?

The bank may have approved the request without the authorisation process completing its return to Sage. Try using Sage on a desktop browser, allow required pop-ups and redirects, and repeat the process in a fresh session. If Sage still displays the reauthorisation message, contact support to investigate the connection handoff.

Why is my Lloyds bank account not reconnecting to Sage?

Check that you can sign in to Lloyds online banking, complete outstanding security requests, and approve third-party access where required. Then restart the reauthorisation process from Sage. If Lloyds approves access but Sage does not update, record the error and contact the support team best placed to investigate the failing stage.

How long does Sage take to download transactions after reauthorisation?

Sage states that transactions can take up to 72 hours to appear after a bank feed is reconnected. Some banks also provide transactions on a scheduled basis. If the connection is active but transactions remain missing after the expected delay, check the bank-feed status and contact Sage support.

What should I do if the bank authorisation page does not return to Sage?

First, allow the required pop-ups and redirects in your browser. Clear relevant cached data and cookies if necessary, then retry the process in a supported browser. If the bank approves the connection but Sage still does not update, avoid repeatedly starting new sessions and ask support to investigate the authorisation handoff.

Is it safe to disconnect and reconnect a Sage bank feed?

It can be an appropriate troubleshooting step when normal reauthorisation fails, but review the consequences first. Sage warns that disconnecting a feed deletes unmatched transactions, and an incorrect reconnection start date can cause duplicates or gaps. Record the last successful import date and review pending transactions before proceeding.

Related Articles