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

Sage 50 crashes when saving transactions

Sage 50 Bank Feed Error 526: Quick Troubleshooting

Trying to download bank transactions in Sage 50 only to receive an invalid security code message can interrupt your reconciliation work. You may be able to access your online banking account without any difficulty, yet Sage 50 continues to reject the authentication information when you refresh your bank feed. This situation can be confusing, particularly when you have not intentionally changed your banking password or security settings.

Sage 50 Error 526 is associated with Bank Feeds authentication. It indicates that the login information supplied for the bank connection is incorrect, specifically the security code required for one-time authentication. The message may appear when Sage 50 attempts to retrieve banking transactions or when you update the login information associated with an existing bank feed.

The best approach is to verify your banking credentials first, then check the additional security information used by the bank. Avoid repeatedly submitting different codes or disconnecting the bank feed without understanding the consequences. The following troubleshooting steps explain what Error 526 means, why it occurs, and how to restore the connection safely.

What Does Sage 50 Error 526 Mean?

Sage 50 Error 526 is a bank feed authentication error. It indicates that the authentication information entered for the bank connection is incorrect.

The associated message states:

You have entered an invalid security code that is required for one-time authentication. Please try again (Error 526).

This message is important because it points to the security information used during the bank’s authentication process, rather than necessarily indicating a problem with your Sage 50 company file or regular Sage user account.

Some banks require additional authentication beyond a username and password. Depending on the bank, this may involve a one-time security code, PIN, or another verification detail. If the information supplied through the bank feed connection does not match what the bank expects, the authentication attempt can fail.

Sage’s published guidance for Bank Feeds error codes 520–526 recommends signing in to the online banking service directly, confirming that the password and security information are correct, and checking that the same information has been entered in the accounting software. It also recommends trying again the following day if the problem continues.

Important distinction: Error 526 should not automatically be treated as a general Sage 50 application sign-in failure. If you cannot sign in to Sage 50 itself, rather than encountering the error while connecting or refreshing Bank Feeds, investigate the separate Sage account or company login issue.

Why Does Sage 50 Error 526 Occur?

Several authentication problems can cause the bank feed connection to reject a security code. The following table summarizes the most relevant possibilities.

Possible causeWhat happens
Incorrect one-time security codeThe code entered does not match the bank’s current verification code.
Incorrect banking passwordThe saved password in Sage 50 does not match the password accepted by the bank.
Outdated authentication informationThe bank’s security requirements or login details have changed.
Incorrect additional security detailsA PIN or other verification response is entered incorrectly.
Expired or previously used codeThe code is no longer valid when the authentication attempt is submitted.
Bank-side authentication changeThe bank requires updated security information or a different verification process.
Temporary bank feed problemThe connection between the bank and the feed service is temporarily unavailable or unreliable.
Unresolved bank account verificationThe bank’s website requires an additional action before an external connection can proceed.

Not every cause produces Error 526 specifically. For example, temporary connection problems may generate a different bank feed error. The exact message should guide the troubleshooting process.

How to Fix Sage 50 Error 526

Follow these solutions in order. Begin by confirming that your banking credentials work directly with the bank. Then update the information saved in Sage 50 and retry the connection.

1. Verify Your Banking Credentials Directly With Your Bank

The first step is to confirm that the username, password, and security information are correct outside Sage 50. A bank feed connection depends on the authentication details accepted by the financial institution. If your bank has changed its login requirements or your password has expired, Sage 50 may continue using information that is no longer valid.

Steps to verify your credentials:

  1. Close the bank feed authentication window in Sage 50.
  2. Open your bank’s official website in a browser.
  3. Navigate to the normal online banking sign-in page.
  4. Enter your current username and password.
  5. Complete any additional verification requested by the bank.
  6. Check whether the bank requires you to accept updated terms, review a security notification, or change an expired password.
  7. Confirm that you can access your account and view its banking information.

If the bank rejects your login, resolve that issue directly with the bank before changing the details in Sage 50. If you can sign in successfully, confirm which additional security information the bank requires. Some banks use one-time codes or other verification methods that are separate from the normal banking password.

Once you have verified the current credentials, use the same information when updating the bank feed connection. Why this matters: A successful login through the bank’s website helps establish whether the problem is with the banking credentials or with the connection between Sage 50 and the bank.

2. Update the Banking Password and Security Information in Sage 50

If you can access online banking but Sage 50 still reports Error 526, the saved banking information may be outdated or incorrect. Updating the bank feed credentials allows you to replace the stored login information with the details currently accepted by your bank.

For Sage 50 Accounts installations that provide the relevant bank feed controls, the documented workflow is to update the banking password from the bank account record.

Steps to update the banking information:

  1. Open Sage 50.
  2. Navigate to Bank accounts.
  3. Locate the bank account experiencing the error.
  4. Double-click the relevant bank account record.
  5. Select Update banking password, where this option is available.
  6. Enter the current online banking credentials.
  7. Select Update.
  8. Close the bank account window.
  9. Close any remaining settings window.
  10. Return to Bank Feeds and try downloading transactions again.

If the bank requests additional security details during authentication, enter the current information supplied by the bank. Be careful not to confuse your Sage 50 user password with your online banking password. They serve different purposes, and changing the wrong password will not correct the bank feed authentication failure.

The precise menu names can vary between Sage 50 editions and regional versions. Use the equivalent bank feed credential-update control in your installation rather than assuming every version has an identical interface.

3. Enter the Correct One-Time Authentication Security Code

The specific wording of Error 526 points to an invalid security code required for one-time authentication. This makes the verification code an important part of the troubleshooting process.

A one-time code is different from a permanent banking password. It is generally generated or delivered by the bank for a particular authentication attempt. Depending on the bank, it may arrive through an approved verification method or appear in a banking authentication process. If the code is incorrect, expired, or entered in the wrong field, the bank feed connection may fail.

Steps to check the security code:

  1. Start the bank feed authentication process again.
  2. Wait for the bank to request the additional verification information.
  3. Obtain the current security code through the bank’s approved method.
  4. Check the code carefully before entering it.
  5. Avoid using a code from an earlier authentication attempt.
  6. Enter the current code in the requested security field.
  7. Submit the authentication request.
  8. Wait for Sage 50 to complete the bank connection.

Do not substitute your normal banking password for a one-time code. Similarly, do not enter an older code simply because it was previously accepted. If you receive multiple codes, use the one associated with the latest authentication attempt. Follow any instructions provided by your bank about code expiration and reuse.

If the bank does not send a code, check whether your registered phone number, email address, or authentication method is still correct. The bank may need to resolve the verification issue before Sage 50 can reconnect.

4. Check for Additional Security Requests on Your Bank’s Website

Sometimes the normal banking username and password are correct, but the bank requires an additional action before allowing an external service to access account information.

For example, you may need to accept updated terms and conditions, acknowledge a security notification, or complete an additional verification step. If that request remains incomplete, the bank feed authentication process may not work as expected.

Steps to check for pending bank requirements:

  1. Open the bank’s official website.
  2. Sign in using your normal banking credentials.
  3. Review the account dashboard and any security notifications.
  4. Check for pending terms and conditions or account verification requests.
  5. Complete any legitimate action requested by the bank.
  6. Confirm that you can access your banking information normally.
  7. Return to Sage 50.
  8. Retry the bank feed connection using your verified credentials.

Do not ignore messages displayed after signing in. A notification that appears unrelated to your Sage 50 connection may still affect whether an external service can authenticate with the bank.

If the bank requires you to register for a new authentication system, complete that enrollment directly with the bank. Then update the corresponding information in Sage 50 if the bank feed setup requires it.

5. Wait and Retry the Bank Feed Connection

If the credentials and security code are correct but Error 526 continues, the issue may not be resolved immediately.

Sage’s published guidance for Error 526 recommends confirming that online banking works, checking that the same password and security information are entered in the accounting software, and trying again the following day if the problem continues. This is particularly relevant when the bank or its authentication process has recently changed.

Steps to retry safely:

  1. Stop submitting repeated authentication attempts.
  2. Confirm that the bank accepts your current login details.
  3. Make sure you are using the latest security information.
  4. Close the failed bank feed attempt.
  5. Wait before trying again.
  6. If the error continues, retry the following day.
  7. Check whether the bank has announced an authentication or online banking service issue.

Repeated attempts with incorrect information may trigger additional security checks or temporary restrictions, depending on the bank. Waiting does not correct an incorrect password or code. It is useful when the credentials have already been verified and the remaining issue may be temporary. If the error continues after the recommended waiting period, contact the bank or Sage support to determine whether the authentication connection requires further attention.

6. Check Whether the Problem Is Specific to One Bank Account

If your Sage 50 installation has multiple bank feed connections, check whether Error 526 affects only one account or several. This helps determine whether the issue is associated with a particular bank’s authentication requirements or a broader Bank Feeds problem.

Steps to isolate the issue:

  1. Open Sage 50 and review the bank accounts configured for Bank Feeds.
  2. Identify which account displays Error 526.
  3. Check whether other connected bank accounts can download transactions.
  4. If another bank feed works, confirm that the affected bank’s login details and security information are correct.
  5. If multiple bank connections fail, investigate whether there is a broader Sage service, authentication, or connectivity issue.
  6. Contact the affected bank if its online banking service rejects the credentials or verification process.

Do not disconnect a working bank feed just to test the connection. Disconnecting and setting up feeds again can affect the existing connection and may complicate transaction retrieval. The goal is to identify the scope of the problem without changing unrelated bank account settings.

7. Contact the Bank or Sage Support if Error 526 Persists

If you have verified your banking credentials, updated the saved information, entered the correct one-time code, and retried the connection but still receive Error 526, further investigation may be necessary. The bank controls its own login requirements and authentication process. Sage manages the accounting software and the bank feed connection. Depending on where the authentication attempt fails, either provider may need to investigate.

Contact your bank when:

  • You cannot sign in to online banking.
  • The bank does not deliver the required one-time code.
  • Your account requires a new authentication method.
  • The bank rejects the security information even when it is correct.
  • You receive a security restriction or verification warning.

Contact Sage support when:

  • You can sign in to the bank successfully, but Sage 50 continues to report Error 526.
  • The bank confirms that your credentials and security information are correct.
  • The error continues after updating the banking details.
  • Multiple bank feed attempts fail despite successful bank authentication.
  • You suspect that the Sage Bank Feeds connection needs further investigation.

Before contacting support, collect the exact error message, the affected bank account, the time of the failed attempt, and the troubleshooting steps already completed. Never provide your full banking password, one-time security code, or other confidential authentication information in an ordinary support message.

How to Troubleshoot Related Sage 50 Bank Feed Authentication Problems?

Error 526 is one of several bank feed errors that can occur when Sage 50 communicates with a financial institution. Understanding the differences can help prevent unnecessary troubleshooting.

Error codeGeneral meaning
520Additional banking authentication information is incorrect.
521The bank requires enrollment in a new authentication system.
522The login attempt or request has timed out.
523Additional login information is incorrect.
524Additional login information has expired.
525A temporary bank feed issue is preventing the request from completing.
526The login information includes an invalid security code required for one-time authentication.

These descriptions refer to the documented Sage Bank Feeds error-code guidance. They should not be confused with unrelated error numbers that may appear in other Sage 50 features or regional editions. If you receive a different code after correcting Error 526, troubleshoot the new message rather than continuing to apply the same solution.

How to Prevent Sage 50 Error 526 in the Future?

Although you cannot control changes made by your bank or the bank feed service, you can reduce avoidable authentication problems by maintaining accurate banking information.

  • Keep banking credentials current: Update the saved information in Sage 50 whenever your bank password or required security details change.
  • Use current one-time codes: Always obtain a new code for the active authentication attempt rather than reusing an older one.
  • Complete bank security requests: Review pending notifications, terms, and verification requests on your bank’s website.
  • Check access directly: Confirm that online banking works before troubleshooting the Sage 50 connection.
  • Avoid repeated incorrect attempts: Stop and verify the credentials when Sage 50 rejects the security information.
  • Monitor bank feed messages: Record the exact error code and message so you can distinguish authentication failures from temporary connection problems.
  • Preserve transaction records: If a bank feed stops working, retain your bank statements and other transaction records so reconciliation can continue through an appropriate alternative process.

These practices will not prevent every bank feed interruption, but they make it easier to identify authentication problems and restore access without unnecessary changes.

Conclusion

Sage 50 Error 526 indicates that the bank feed authentication process has received an invalid security code required for one-time authentication. The problem is generally related to banking credentials or additional security information, rather than a damaged Sage 50 company file or an ordinary Sage user login.

Start by signing in to your bank’s website and confirming that your password and security information are correct. Then update the banking details saved in Sage 50, enter the current one-time security code when requested, and check for pending bank verification requirements. If the error continues despite verified credentials, wait and retry as Sage recommends.

If you still cannot connect, contact your bank to investigate its authentication requirements or Sage support to review the Bank Feeds connection. Avoid repeatedly entering codes or disconnecting the bank feed without a clear reason.

FAQs of Sage 50 Error 526:

What is Sage 50 Error 526?

Sage 50 Error 526 is a Bank Feeds authentication error. It indicates that the login information entered includes an invalid security code required for one-time authentication. Verify your banking credentials and security information, update the saved details in Sage 50, and retry the connection.

How do I fix Sage 50 login error 526?

Sign in to your bank’s official website to confirm your password and security information. Then update the banking credentials in Sage 50, enter the correct one-time authentication code if requested, and try downloading transactions again. If the error continues, follow Sage’s recommendation to retry the next day.

Why does Sage 50 say I entered an invalid security code?

This message means the security code supplied during the bank feed authentication process was not accepted. The code may be incorrect, outdated, expired, or associated with a different authentication attempt. Obtain the current code through your bank’s approved verification method.

Can an incorrect banking password cause Sage 50 Error 526?

Yes. Sage’s guidance for Error 526 recommends confirming that your online banking password and security information are correct. Even if the specific message mentions an invalid security code, verify the complete set of banking credentials rather than checking only the code.

Why does Sage 50 Bank Feeds keep rejecting my login details?

Sage 50 may be using outdated banking credentials, or your bank may require additional verification. Sign in to online banking directly, complete any pending security requests, and update the information saved in Sage 50. If the details are correct but the feed still fails, contact the bank or Sage support.

Should I disconnect and reconnect my bank feed to fix Error 526?

Not as an initial troubleshooting step. First verify your banking credentials and update the saved authentication information. Disconnecting a bank feed can affect the existing connection and may complicate transaction retrieval. Only consider reconnecting when the applicable Sage instructions or support team recommend it.

What should I do if Sage 50 Error 526 continues after updating my banking details?

Confirm that your bank accepts your current credentials and that the required security code is correct. Sage’s guidance recommends trying again the following day if the issue persists. If the error remains, contact your bank to investigate authentication and Sage support to review the Bank Feeds connection.

Related Articles