Remote bank feeds in Sage 50 v27?

SOLVED

Hi,

We just set up bank feeds in our Sage 50 C. A remote user sent me a screen shot this morning - it says:

'This option is not available on a remote site. To complete this task, please contact the main site. This will be the site that originally set up Remote Data Access'.

I've had a look at some similar questions on here, and there seems to be some allusion to the idea that this was being worked toward for v26. Is this still not the case in v27 - or have I missed something?

  • 0

    PS Bit puzzled by this, as I checked this was working by installing Sage on a virgin machine at the office, then choosing to download the cloud data - not connect to the local data.

    Is this behaviour correct - that you can connect to the cloud data and use bank feeds provided your'e on the local LAN - but not if you're similarly connected to the cloud data, but off-site?

  • 0

    Hi Jon,

    Thanks for using Sage City.

    Sage 50 Bank Feeds will work on a remote site but with the limitations that it must be set up on the MAIN site first and the remote site cannot download transactions. This was introduced as part of v26.3 - What's new in Sage 50 Accounts v26

    If you're getting that message it would suggest

    1. The Bank being selected hasn't been set up on the MAIN SIte

    2. The bank being selected is different from the one set up on the MAIN Site

    3. The remote site isn't connected to the MAIN Site. You can check both sites are talking to each other by going to Help > About and under Remote Data Access Information compare Data Set ID on both machines, they should match. If they don't match we'll need to reconnect them.

    If this has answered your question please click More > Verify Answer.

    Ian

  • 0 in reply to Ian C

    Thanks for getting back to me, Iain.

    To confirm:

    - There is only one bank feed, and it WAS set up on the main site (more about this below)
    - The error was happening before any bank accounts could be selected - no question of whether it was the right account or not.
    - The remote site WAS connected to the main site.

    So I' then got myself into a pickle. The way we have Sage set up is that there is one main server that the local data lives on, and every user connects to the cloud data remotely, on their own machines - no one ever has console access to the server apart from me. I (perhaps incorrectly) assumed that more than one computer could be set to access the data at the main site, locally, so I set about setting up Sage on a Remote Desktop session host, so that users who needed full bank feed access (i.e. being able to download transactions per your comment above) could do so ('and the remote site cannot download transactions').

    During setup on the RD server, it prompted me to reactivate bank feeds, which I thought was strange, but went through with anyway. Shortly after, I got a message from a remote user saying that they were getting warnings that the computer at the main site was no longer online. It seemed that the RD server had now become the main computer. I had to go back to original server and reupload the data again, then reshare it for all users, meaning everyone will have to once again add/download the company data.

    This seems to indicate that only one computer can ever access the local data - or do I have this wrong?

    I then tried logging into Windows on the (now reactivated) source server as a different (non admin) Windows user, with the idea that they could open the local data - but Sage tells me they don't have access.

    What am I doing wrong? What's the correct way for multiple users to access the local data, thus being able to have full bank feed functionality?

    Thanks.

  • 0 in reply to Jon Rose

    PS remote users can now see the bank feed, and it works, after reuploading the company and resharing it. I didn't have to change anything with the bank feed itself, other than reactivate it with the email link. Just need to know how folks should best access the local data, if this is the only way transactions can be downloaded.

  • +1 in reply to Jon Rose
    verified answer

    Hi Jon,

    Thanks for the information.

    It sounds like the MAIN site didn't have a valid token and is why it needed to be re-activated. 

    With Bank Feeds it will only download transactions from the bank once a day at 7am. What you could do on the MAIN site is go to Settings > Bank Defaults and set the sync time on Bank Feeds to be more frequent. (The data will still be from the day before but at least if it tries to sync more frequently remote users know they have up-to-date transaction information.)

    Accessing local day would be by using Remote Desktop Connection and Sage 50 Accounts supports multiple Windows logins / terminal services so there shouldn't be a reason why the data moves / needs to be uploaded again.

    If you need further help it may be worth giving us a call or popping up on webchat to discuss this in real-time. (Chat options at the bottom - Sage Help Centre)

    Hope this helps

    If this has answered your question please click More > Verify Answer.

    Ian

  • 0 in reply to Ian C

    Thanks Iain. I just tried connecting to the local data from the RD server again, and this time it worked perfectly. No idea what went wrong before - it's a mystery! Anyway, thanks for the help - appreciated.

  • 0 in reply to Ian C

    One final question: after resharing the cloud data, users are saying that when they go to recall memorised journals under Nominal Codes, they can't see any that have been saved. They've sent me a screen grab, and this is correct - they can only see the default ones.

    When I log in as manager I can see them. Any advice?

    Thanks.