Skip to main content
M
Michael Sheff
April 3, 2023
Solved

bank not connecting (error 570)

  • April 3, 2023
  • 2 replies
  • 0 views

Has anyone managed to connect their bank with the error - 

Looks like you’re locked out of the Aqua Mastercard (UK) site.

Try signing in on your bank’s site to unlock your account. Then return here and try connecting again. (570)

 

According to the bank provider, I have never been locked out of my account. I contacted quickbooks team who gave me multiple solutions which took hours with different browsers, clear cache, incognito mode, etc... but none worked and was told I would be contacted by another team and it was their top priority to solve the case...shortly followed by an email saying your case has been closed with no communication in between and a complaints reference number? I clearly wasn't getting anywhere and with limited time, I fortunately managed to join Xero which connected everything perfectly and got my vat return out on time. I use quickbooks self employed for my receipt logs and self assessment. I have thousands on receipts logged so switching isn't an option for this case so I need it sorted asap

 

 

 

    Best answer by emmam6

    Hello Community Users, we just wanted to pop in and update this thread. The issue with Aqua bank connections showing a ''looks like you're locked out'' error message was raised to our senior engineers and was resolved in May 2023.

    If any viewers of this thread are now experiencing a similar problem, please reply here and we'll be happy to investigate this straight away.

    2 replies

    A
    Ashleigh1
    April 3, 2023

    Hello Michael, thanks for posting on the Community page,  can you please add the bank as a new connection instead and just toggle off your old connection this should then resolve your issue your currently having.

    M
    Michael SheffAuthor
    April 6, 2023

    I have also tried this. I was asked to delete the old connection and connect as a new connection which deleted 5 months of previous transactions and receipts

    O
    owenrcwmaber
    April 11, 2023

    I've been having this exact problem with my Aqua connection too, it's been going on for months. Tried in Firefox and Chrome, both on desktop (Windows) and mobile (Android), tried connecting via the Quickbooks and Aqua apps on my phone, exact same error as the original post every time.

     

    I am not and have never been locked out of my Aqua account, and to all appearances the connection setup all goes through smoothly on Aqua's side, it's only when I get back to Quickbooks that it shows an error.

    S
    SirielJeaB
    April 11, 2023

    Greetings from the Community, Owen. We are grateful that you have submitted your first post to the Community thread. I would be happy to direct you to the appropriate team. 

     

    I understand how essential it is to perform banking activities without any challenges. Please know that this isn't the kind of experience we want you to have. We've received reports about banking error 570. Rest assured that our engineers are working diligently to fix this.

     

    I recommend contacting our Live Support Team to be added to the list of affected users. Here's how:

     

    To contact support:

     

    1. Select the Help (?) icon.
    2. Click Contact Us.
    3. Type in talk to a human., then hit Continue.
    4. Select which way you want to connect with us: Have us call you or Chat with us.

     

    The following article will help you in managing your bank transactions in QuickBooks Self-Employed: Categorise transactions in QuickBooks Self-Employed.

     

    The Community is always available to help you with any QuickBooks-related concerns. We're always looking forward to assisting you. Keep yourself safe!

    E
    emmam6Answer
    August 10, 2023

    Hello Community Users, we just wanted to pop in and update this thread. The issue with Aqua bank connections showing a ''looks like you're locked out'' error message was raised to our senior engineers and was resolved in May 2023.

    If any viewers of this thread are now experiencing a similar problem, please reply here and we'll be happy to investigate this straight away.

    Terms & ConditionsAccessibility statement