Is anyone else going through a horror year with connection issues with NAB and Quickbooks? Since Jan 1, I've had only 1 month when this has worked...

I can see the importance to be able to connect with National Australia Bank (NAB). I'm here to to guide you on how to fix the issue, peter23.

Generally, error 103 means that the user ID or password for the bank account you're trying to connect is incorrect. You'll have to make sure that you're using the correct login credentials for the bank account. I've outlined the steps below: 

1. Open a new window in your web browser and go directly to your bank’s website.
2. Make a note of the web address (such as https://www.bank.com). This may come in handy later.
3. Sign in with the user ID and password you have. If you have separate accounts with the bank (such as a business account and a personal account), sign in to the account you want to fix in QuickBooks.
4. If you sign in successfully, then you know the user ID and password are correct. If you get a sign-in error, follow your bank’s instructions to get your user ID, reset your password, or both.

Once done, you can now enter your bank sign-in to your bank account. Here's how: 

For an existing connection
 

1. Go to Banking, select Transactions, then select Bank transactions (Take me there).
2. Select the bank or credit card account you need to update.
3. Select Edit ✎.
4. Select Edit sign-in info.
5. If your web browser auto-fills the user ID and password fields, clear them. This ensures your browser doesn’t put in old info by mistake.
6. Manually type in the user ID and password for your bank account. If your bank offers a Show option, select it so you can confirm you entered the password correctly.
7. Select Update.

For a new connection
 

1. Go to Bookkeeping, select Transactions, then select Bank transactions (Take me there).
2. If you're connecting an account for the first time, select Connect account on the landing page. Or if you've already connected online banking accounts in the past, select Link account.
3. In the Search field, enter your bank's web address (such as http://www.bank.com) that you got from visiting the bank’s website. Or, enter your bank’s name.
4. Select your bank in the search results. Note: If you see multiple options, select the type of account you want to connect. For example, if you’re trying to connect your business account, select the option labelled “Business” if there is one.
5. If your web browser auto-fills the user ID and password fields, clear them. This ensures your browser doesn’t put in old info by mistake.
6. Manually type in the user ID and password for your bank account. If your bank offers a Show option, select it so you can confirm you entered the password correctly.
7. Select Continue.
8. Your bank should connect successfully now. If you see error 103 again, select Go back. Repeat steps 4 through 7 with a different option from the search results.

However, if you're still unable to connect your bank account, I recommend reaching out to our support team so they can double-check on this and investigate further. They have the tools to pull up your account in a secure environment. Here's how to reach them: 

1. Sign in to your QuickBooks Online company.
2. Select Help (?).
3. In QB Assistant, enter the topic you need help with. You can also enter questions.
4. Select Contact Us to connect with a live support agent.
5. Choose a way to connect with us:
   • Start a chat with a support expert. Live chat M-F, 8:00 AM to 10:00 PM and S-S, 8:00 AM to 8:00 PM, AEDT.
   • Call us. M-F, 8:30 AM to 6:30 PM, AEDT.

Additionally, once bank transactions are downloaded, QuickBooks looks for and tries to match them with those you've already entered. To give you a detailed quick guide on how this works, check out this article for more information: Categorise and Match Online Bank Transactions In QuickBooks Online.

You can always get back to us if you have any concerns with your connection or bank transactions. The Community is always here and is the right place for you if you need help.

HI Maria,

Thanks for getting back to me.

I have done all this...including contacting your support team.  They have no idea on what is going on and just tell me "its something being worked on" or tell me to call NAB, who say it has nothing to do with them.  I have gone through the process you have detailed (at last count) honestly 100 times...just to get it working.

I can easily log into my bank account with NAB normally and never had an issue.  It is via a NAB Connect account btw, so the password changes each time you log in.  Your system allows for this and had been doing so for quite some time up until Jan 2022.

In mid January 2022, suddenly I could not.  It took nearly 5 months before QB support found a fix which worked for about a month.  Now it has stopped working again right before EOFY.  Again, your support department is at a loss and noting - predicted fix is several months away.  Several months!  This is a software issue and already took 5 months prior to get a fix...now more months?

It is an absolute joke!  If I do a manual download of my bank account and apply it (which I have in the past), when the system works again it then downloads all the transactions as QB cannot recognise that I have already processed these manually.  So I have the tedious task of going through deleting all these now download transactions on my bank account!

Honestly, QB is handling this by handballing it around with no-one really trying to do anything.

Hello peter23,

First of all, I sincerely apologize for the experience and frustration you have gone through, this is not what we are expecting our customers to encounter.

I understand that you have fundamental issues with NAB's online banking connection. There was a reported product investigation for NAB direct feed transactions from 17 June 2022 and onwards are not downloading into QuickBooks Online but has been resolved last weekend of June 2022. I get your part that the NAB bank feeds issue occurred again at a crucial time in your account after the fix has been deployed. I'd recommend contacting back to our Live support team through Chat or Phone. That way, they can re-escalate the incident with our banking team or senior support specialist and have a look at the account connection.

I understand some aspects of our products could use some work, customer satisfaction is our top priority and it's feedback like yours that help us improve our product so it fulfills its duty of making your time easier when dealing with your connected bank account or QuickBooks file.

If I can be of help to you in any way please let me know, my sole purpose is to support you the best way we can.

This is an ongoing and issue. To be honest we are ready to walk away from both QBA and NAB due to the time and effort and no commitment to resolve. Disappointing. There are much better baking platforms and finance systems that integrate and offer support.

If you have an OTP it just does not connect.

We have been through support a number of times. QBO blame NAB. NAB blame QBO.

Quick books bank links not working.

"Something isn't working

I too am having an identical ongoing issue since early June 2022. My accounts are with a Sydney based credit union, but identical symptoms, Error 105. no bank links. Previously this worked pretty fault free for 2 years. Multiple contacts with support lead to no resolution. I even used a trial version of Xero to test the bank links and they worked perfectly.  The time and energy to change accounting systems is daunting however I don't think I have any choice now and do not want to continue paying for a service that is not working.

Anyone else?

So I finally had someone from Quickbooks tell me to register for a direct feed.  This is at least a 10 day process as you have to fill out a request form, send it to QBs who then process it with the NAB.

Apparently this overrides the need for an OTP everytime as you are authorising the system to have direct access.

I am holding my baited breath here...

The fact that QB and NAB are not able to work out this OTP sign-in issue is a disgrace tbh. This should be a software solution that should be done in a month or two at the most, not years.  It seems that the QB team just keep handballing this around like a hot potato.  I seriously wonder who really governs such support issues within QBs and does anyone actually raise it to a high level saying "this needs to be fixed now"?

Totally understand your frustration - I have been dealing with this since January this year and have had about 1 week of where it was fixed then it fell over again.

The issue is that it seems that very (and I mean very) few people within QBs either care about this, or have any knowledge on how to solve the issue.

It obviously isn't even in the top 100 of their "things to be fixed".  Terrible support for their own software.

I was finally guided last week to setting up a direct feed.  This is the first time after speaking to well over 30 different people in QB service team that anyone said to do this.  So now I wait with baited breath to see (it takes min 10 days to process this request) if this will overcome this issue.

Even if it does, I am still wary that either QB or NAB shuts the connection down for some unknown reason and then I have to reapply again and again and again...

Thanks Peter, 

I'll be watching to see if this solves it for you, but yes I am just losing faith in QBs system abilities to sort out issues at all. I think they are just focused on fixing problems for people who get mixed using the software, working from scripts etc. I've been told twice that my problem has been escalated but then nothing. No doubt like everything it is qualified staff shortages.

It is a worry that there is such a big issue with one of the big 4 banks not being resolved, not sure how much action I'll get for my little credit union accounts. I thought my issue might be related to NAB as my credit union did at one time have a relationship with NAB, possibly they share similar IT systems.

I only have a small business so not a lot of accounts employees etc so switching to Xero shouldn't be too bad but still likely hours of work away from my main occupation. Unfortunately stupid little glitches like this will be the end of 23 yrs of Quickbooks usage.

Regards

Mark