Hey Josh,

Potentially two things to check for this common Bank Feeds error:

1. https://gb-kb.sage.com/portal/ss/?querytext=hresult&searchaliases=custom_gb_en_twohundredcloud_professional&tabid=2 If you receive your Sage200 support from a business partner, pass on the article so they can action the necessary change. They may have to liaise with your local IT team.

2. https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200427112457796&page=1&position=1&q=hresult Pass this article to your local IT team to whitelist the two URLS in your companies firewall.

Thanks Stu. We followed these steps and pleased to say it's working now. For #1 though, my IT team were against adding the Sage 200 Secured Services to the Domain Administrators and so we did not do this and it still worked. 

The additional steps we took in addition to the instructions listed was to add Sage 200 Secured Services as a user / enable it, and ensure the relevant companies were added to the user.  

Thanks