CAUTION: Customers that use Bank Feeds or Invoice Payments, in Sage 200 2021 R1 or below, must either install a patch or upgrade to the latest version of Sage 200, for these services to continue working. Patches for each applicable version can be found here.
TIP: The Bank Feed Help Files includes a troubleshooting section, this includes details on refreshing your signature key if you have restored a backup and your feed(s) stop working.
- The full version number of Sage 200 including whether a remastered version has been installed for versions prior to 2020 R1 (this article gives more information on this).
- Details of what you see in Sage 200, including the Status of the feed and the full error message if an error is received.
- The background of the problem, for example is it a new feed, does the problem coincide with a server move etc.
- The bank account details, including - bank name, sort code, account number, and account name.
- The email address used when setting up (or attempting to set up) the Bank Feeds connection.
- A copy of the Sage 200 Secured Services log (after Debug level logging switched on through Sage System Administration and the problem replicated - this article gives more information on this).
- The BankCloudOrganisationID, and BankCloudAdminEmail (if different from the email address from step 3) from the tblBankCloudConfiguration table in the Sage 200 Configuration database.
- The BankCloudBankAccountID, LastTransactionDownloadDateTime, and LastTransactionDownloadID from the CBCloudBankAccount table from the Company database for the affected Cashbook account.
- The BankCloudCompanyID from the SysCompany table in the Company database.
- If the problem relates to missing transactions, then please provide details of the transactions concerned (a snippet of the bank statement would also be useful).
|