How to Fix QuickBooks Error 103 Due to An ID or password Issue?

Fix QuickBooks Error 103 by:

• Cconfirming the bank credentials work on the bank’s own website first, 
• Then clearing any auto-filled credentials in QuickBooks and typing the user ID and
• Password manually through Bookkeeping > Transactions > Bank Transactions > Edit sign-in info, 
• Then enabling the bank’s third-party access permission on the bank website for any bank that requires it, and 
• Then disconnecting and reconnecting the bank account as a last resort – after reviewing existing downloaded transactions first to prevent duplicates.

QuickBooks Online Error 103 appears with the message ‘We can’t connect to your bank (103)’ when the sign-in credentials entered in QuickBooks do not match what the bank has on record. 

The Intuit QuickBooks Community confirms three primary causes: 

• the wrong user ID or password was entered in QuickBooks, 
• the wrong financial institution was selected from the search list (many banks share similar names), and 
• the user’s credentials were recently changed at the bank but not yet updated in QuickBooks.

Intuit-published Error 103 articles document updating credentials and enabling third-party access as their primary steps. The Intuit QuickBooks Community confirms two critical causes: browser auto-fill silently inserting old passwords, and the wrong financial institution being selected from the connection list. 

Browser auto-fill is the most common reason a user correctly believes they entered the right password but still sees Error 103 – the browser quietly replaced what they typed with a saved old password. Testing in a private browser window takes under two minutes and confirms or eliminates auto-fill as the cause immediately.

The Intuit QuickBooks Community also confirms a specific bank-side cause: some banks require the user to log into the bank’s website and manually enable a setting that permits third-party applications – like QuickBooks – to access account data. Without this setting turned on at the bank, every connection attempt from QuickBooks is blocked by the bank itself regardless of whether the credentials are perfectly correct. This is not a QuickBooks problem and cannot be fixed inside QuickBooks.

What QuickBooks Error 103 Is and Why It Only Affects Bank Connections Specifically?

QuickBooks Online connects to banks through a process called bank feeds – an automatic connection that downloads the bank’s transaction records directly into QuickBooks without manual data entry. For this connection to work, QuickBooks sends the user’s bank login credentials to a secure data aggregation service that Intuit uses to access the bank on the user’s behalf. 

The Intuit QuickBooks Community confirms Error 103 fires specifically when that aggregation service sends the credentials to the bank and the bank responds that the credentials are wrong or unrecognised.

Error 103 is different from Error 102 and Error 185. Error 102 means the bank’s server is temporarily unavailable – a wait-and-retry situation. Error 185 means the bank is requesting additional authentication such as a security question or a one-time code. 

Error 103 means the credential check itself failed – the bank looked at the user ID and password sent and said they do not match any account on record. The Intuit QuickBooks Community confirms Error 103 requires an action inside QuickBooks or on the bank’s website to resolve – it does not resolve on its own with time.

The financial institution selection problem is a distinct cause that creates an Error 103 that looks identical to a wrong password error. Many banks operate under multiple names or have regional divisions with slightly different names in the QuickBooks institution search list.

 Selecting Chase Personal instead of Chase Business, or selecting a local credit union’s parent organisation instead of the credit union itself, sends the credentials to the wrong bank server – which rejects them because it has no record of that account. 

The Intuit QuickBooks Community confirms: correcting a wrong institution selection requires disconnecting the current wrong connection and setting up the connection fresh with the correct institution name.

A bank account used for QBO’s online banking connection can be locked out by the bank if QuickBooks sends the wrong credentials too many times in a row. The Intuit QuickBooks Community confirms multiple users reported their bank account became locked after QuickBooks continued to retry the failed connection automatically on its scheduled sync cycle. Stopping QuickBooks from retrying – by disconnecting the account temporarily – prevents a lockout while the correct credentials are located.

Can QuickBooks Error 103 Trigger Other Issues in QuickBooks Online?

Error 103 on an active bank connection stops all new transactions from downloading into QuickBooks. The bank feed shows the last successful download date and stops advancing. Bank reconciliation cannot be completed for any period after the last successful download because there are no transactions to match. 

Payroll, vendor, or customer transactions that cleared the bank during the error period must either be downloaded manually after the connection is restored or entered by hand if the connection cannot be quickly restored.

• A bank account that locks out due to repeated failed credential attempts requires the user to unlock it through the bank’s website or by calling the bank directly. 
• The Intuit QuickBooks Community confirms the bank account lockout is a consequence of QuickBooks retrying the failed connection on its automatic schedule – typically every night. 
• Disconnecting the bank account in QuickBooks immediately after Error 103 appears stops the retries and prevents the lockout from happening while the correct credentials are found.
• Missing transactions from the Error 103 period must be downloaded manually even after the connection is restored. 
• The Intuit QuickBooks Community confirms: reconnecting the bank account after an error period downloads transactions from the most recent period, not from the date the error started. Any gap between the last successful download and the reconnection date requires a manual bank statement import using a CSV or OFX file from the bank’s website to fill in the missing period.

Identifying the Root Cause of QuickBooks Error 103

Confirm the credentials work at the bank’s own website before making any change in QuickBooks. Open the bank’s website in a separate browser tab, sign in with the user ID and password, and confirm access to the correct account. 

This one step determines whether the problem is the credentials themselves or how QuickBooks is submitting them. A successful bank login with the same credentials means the problem is in QuickBooks, auto-fill, or the bank’s third-party access setting – not in the credentials.

Data Safety Advisory: Key Concepts Before Troubleshooting

What Is Browser Auto-Fill and Why Does It Cause Error 103?

Browser auto-fill is a feature in every modern web browser – Chrome, Firefox, Edge, Safari – that remembers login credentials and automatically fills them in when a matching website or form is detected. QuickBooks Online opens a bank credentials form when setting up or updating a bank connection, and the browser treats this form as a login screen for the bank. 

The Intuit QuickBooks Community confirms: the browser fills in the password field with whatever it saved last – which may be an old password that has since been changed at the bank. The password field shows dots rather than characters, so the user cannot see that the browser inserted a different password than the one they intended to type.

What Is Third-Party Access and Which Banks Require It?

Third-party access is a security feature that some banks use to control which external applications can access account data on behalf of the account holder. The bank’s website has a setting – often found under Security, Privacy, or Account Settings – where the account holder must explicitly turn on permission for external applications to connect. 

The Intuit QuickBooks Community confirms that banks with stricter security policies require this step before any connection from QuickBooks is accepted – even when the credentials are correct. Examples documented in the Intuit QuickBooks Community include certain regional US banks, Canadian banks, and credit unions. The setting is usually labeled Data Sharing, Connected Apps, or Third-Party Access.

What Happens to Transactions When an Account Is Disconnected and Reconnected?

Disconnecting a bank account in QuickBooks removes the active connection and stops all automatic transaction downloads. Reconnecting the same account re-establishes the connection and begins downloading recent transactions again – typically the last 90 days. 

The Intuit QuickBooks Community confirms: transactions that were already downloaded and categorised before the disconnection may reappear in the review queue after reconnection, appearing as new unreviewed entries. These are duplicates – reviewing them as new entries creates double-counted income and expenses. Before reconnecting, note the date of the last successfully downloaded and accepted transaction so duplicates can be identified and excluded after the reconnect.

Steps to Fix QuickBooks Error 103

Solutions are organised by confirmed causes. Start with Level 1 – verifying the credentials on the bank’s website and clearing auto-fill resolves the majority of Error 103 cases without any account disconnection or data risk. Advance to Level 2 and Level 3 only if Level 1 confirms the credentials are correct but Error 103 continues.

These solutions carry zero risk to QuickBooks data and address the three most common confirmed causes of Error 103. Try them in order before considering a disconnect and reconnect.

Solution 1.1: Confirm Credentials on Bank Website Then Update Them Manually in QuickBooks

Steps – Confirm Credentials at the Bank Website:

1.  Open a new browser tab. Navigate to the bank’s website directly – type the address manually rather than using a saved bookmark that might redirect. Sign in using the user ID and password. 

      Confirm the sign-in succeeds and the correct account is accessible. If the sign-in fails, use the bank’s Forgot Password or Forgot User ID option to reset the credentials before proceeding to QuickBooks.

Steps – Update Sign-In Info in QuickBooks Online:

2.  In QuickBooks Online, click Bookkeeping in the left menu. Select Transactions. Select Bank Transactions. Find the bank or credit card account showing Error 103 in the account list. Click the Edit pencil icon next to it. Select Edit sign-in info from the dropdown.

3.  The sign-in information window opens showing the user ID and password fields. Look carefully at both fields – if either field is already filled in, the browser has auto-filled it. Click inside the user ID field. Press Ctrl+A to select all text. Delete it. Type the user ID manually. Repeat this for the password field. Click the Show button or eye icon next to the password field to confirm the characters displayed match what was intended. Click Update.

Solution 1.2: Test in a Private Browser Window and Enable Third-Party Access at the Bank

Steps – Test in Private Browser Window:

1.  Open a private browser window. In Google Chrome press Ctrl+Shift+N. In Firefox or Microsoft Edge press Ctrl+Shift+P. In Safari press Command+Shift+N. The private window opens with no stored data, no auto-fill, and no cached sessions.

2.  In the private window, go to quickbooks.intuit.com. Sign into QuickBooks Online. Navigate to Bookkeeping > Transactions > Bank Transactions > select the bank > Edit > Edit sign-in info. Enter the user ID and password manually. Click Update. If Error 103 no longer appears in the private window, the regular browser’s cached data or auto-fill was the cause – clear the browser cache in the regular browser as described in Solution 1.3.

Steps – Enable Third-Party Access at the Bank:

3.  Log into the bank’s website in a separate browser tab. Navigate to the account settings, security settings, or privacy settings section of the bank’s website. Look for a setting labeled Data Sharing, Third-Party Access, Connected Apps, or API Access. 

      If this setting exists and is currently disabled or set to off, enable it. Follow any confirmation steps the bank requires – some banks send a one-time verification code. Return to QuickBooks and retry the bank connection.

Solution 1.3: Clear Browser Cache and Correct a Wrong Financial Institution Selection

Steps – Clear Browser Cache:

1.  In Google Chrome: click the three dots in the top-right corner. Select Settings. Click Privacy and security on the left. Click Clear browsing data. Set the Time range to All time. Check Cookies and other site data and Cached images and files. 

      Click Clear data. Restart Chrome. In Firefox: click the hamburger menu (three lines) > Settings > Privacy & Security > Cookies and Site Data > Clear Data > check both boxes > Clear. Restart Firefox.

Steps – Correct a Wrong Institution Selection:

2.  Identify the correct institution name first. Open the bank’s website and note the exact legal name shown at the top of the page or in the website address. In QuickBooks Online: Bookkeeping > Transactions > Bank Transactions > select the incorrectly connected account > Edit > Disconnect this account on save > Save and close. 

      After disconnecting, click Link account to set up a fresh connection. In the search box, type the exact institution name from the bank’s website. Select the result that matches exactly – pay attention to the account type shown (personal vs business, national vs regional). Enter the credentials manually.

Use this solution after Level 1 steps are complete and Error 103 still appears with confirmed correct credentials. The disconnect and reconnect clears the connection record in QuickBooks and Intuit’s aggregation service and rebuilds it fresh. Read the duplicate transaction warning before starting.

Solution 2.1: Disconnect and Reconnect the Bank Account – With Duplicate Transaction Review

Steps to Implement Solution 2.1:

1.  Before disconnecting, open the bank account’s transaction review screen in QuickBooks: Bookkeeping > Transactions > Bank Transactions > select the bank account. Note the date of the most recently accepted transaction – write this date down. Any transaction with this date or earlier that appears in the review queue after reconnection is a duplicate.

2.  Disconnect the account: select the bank account > click Edit (pencil icon) > select Edit account info from the dropdown > scroll to the bottom of the account info screen > check the box labeled Disconnect this account on save > click Save and close. The account is now disconnected.

3.  Reconnect the account: click Link account in the Bank Transactions screen. Search for the bank’s correct name in the institution search box. Select the correct result. Enter the user ID and password manually – do not use auto-fill. Select the bank account from the list QuickBooks provides after authentication. Match it to the correct QuickBooks account. Click Connect.

4.  After reconnection, open the review queue for the reconnected account. Look at the dates of the transactions shown. Any transaction dated on or before the date noted in Step 1 is a duplicate of an entry already accepted in QuickBooks. Click Exclude on each duplicate rather than Add – this removes them from the queue without creating a new transaction in the accounts.

Scenarios Requiring Immediate Intuit Escalation

Contact Intuit QuickBooks Support in the following situations. These scenarios require Intuit to investigate the connection on their side.

• Error 103 After All Fixes Are Confirmed – Specific Bank Only, Lasting More Than 48 Hours: The Intuit QuickBooks Community documents cases where Error 103 on a specific bank persisted despite correct credentials, third-party access enabled, and a fresh reconnection – because Intuit’s aggregation service had an ongoing unresolved issue with that specific bank’s feed. 

Contact Intuit support and provide the bank name, account type, and the date the error started. Intuit can check whether an active investigation exists for that bank’s feed.

• Bank Account Locked Out Due to Repeated QuickBooks Retry Attempts: Contact the bank directly to unlock the account – QuickBooks cannot unlock a bank-side account lockout. After the bank unlocks the account, disconnect the bank account in QuickBooks to stop further retry attempts before re-entering the correct credentials. Contact Intuit support to report the connection failure that caused the lockout.
• Error 103 After Migrating to a New QuickBooks Online Account or Company File: Bank connections do not transfer between QuickBooks Online accounts or company files. Each new company file requires a fresh bank connection setup. If the fresh setup produces Error 103 with correct credentials and the institution is confirmed correct, contact Intuit support and describe the migration – there may be an account-level registration issue that the support team can clear.
• Bank Confirms Third-Party Access Is Enabled but QuickBooks Still Returns Error 103: Some banks use a different protocol for their third-party access approval than what Intuit’s aggregation service expects. Contact Intuit support and provide the bank name. Intuit maintains a list of banks with non-standard connection requirements and can provide bank-specific instructions that are not covered in the standard Error 103 resolution steps.

Prevention Strategy

Preventing QuickBooks Error 103 requires four consistent habits: 

1. updating sign-in information in QuickBooks immediately after any bank credential change, 
2. never using auto-fill when entering bank credentials in QuickBooks, 
3. checking the bank feed status weekly rather than monthly so a failed connection is caught before the transaction gap becomes large, and 
4. reviewing downloaded transactions before accepting them after any reconnection event.

• Update QuickBooks Sign-In Info Immediately After Every Bank Credential Change

The Intuit QuickBooks Community confirms that credentials changed at the bank but not updated in QuickBooks cause Error 103 on the very next automatic sync attempt – usually overnight. 

Updating QuickBooks credentials through Bookkeeping > Transactions > Bank Transactions > Edit > Edit sign-in info on the same day as any bank password or user ID change ensures the connection never fails for this reason. The update takes under two minutes.

• Never Use Auto-Fill When Entering Bank Credentials in QuickBooks

The Intuit QuickBooks Community confirms browser auto-fill inserting old passwords is one of the most reported causes of persistent Error 103 – the user is certain the password is correct because they typed it, but the browser replaced it with a saved old version after the user started typing. 

Clicking into the credential fields and pressing Ctrl+A to select and delete any pre-filled content before typing manually ensures the correct current credentials are submitted every time.

• Check the Bank Feed Status Weekly

A bank feed that stopped updating on a Tuesday may not be noticed until the Friday reconciliation – by which point four days of transactions are missing from QuickBooks. 

Checking Bookkeeping > Transactions > Bank Transactions once each week and confirming the Last updated date recently catches an Error 103 connection failure while the transaction gap is small. A small gap requires downloading one week of bank statements manually. A four-week gap requires downloading and importing a full month.

• Review Downloaded Transactions Carefully After Any Reconnection Event

The Intuit QuickBooks Community confirms reconnecting a bank account after any error – including Error 103 – causes previously downloaded transactions to reappear in the review queue. 

Accepting these transactions again creates duplicate entries that overstate income and expenses on every financial report. Noting the date of the last accepted transaction before any reconnection and excluding all transactions with that date or earlier from the post-reconnection download queue prevents this from affecting the books.

Conclusion

Fix QuickBooks Error 103 by confirming credentials work on the bank’s own website first – this one step identifies whether the issue is the credentials themselves or how QuickBooks is submitting them. Clear any browser auto-filled credentials in the Edit sign-in info screen and type the user ID and password manually. 

Test in a private browser window to confirm whether browser cache or auto-fill is the cause. Enable third-party access on the bank’s website for any bank that requires permission before allowing external connections.

Error 103 often continues despite correct credentials due to hidden technical or configuration issues:

• Error 103 is often assumed to be a simple password issue, but the root cause is frequently something else.
• The error can continue even after entering and updating the correct credentials in QuickBooks.
• Browser or system auto-fill may insert outdated login details without the user noticing.
• Repeated login attempts can trigger an account lockout from the bank’s side.
• Selecting the wrong financial institution during setup can lead to authentication failure.
• Disconnecting and reconnecting the account may create duplicate transaction conflicts.
• These overlooked factors explain why Error 103 persists despite correct login information.
• Proper diagnosis requires looking beyond just password updates.

Preventing Error 103 requires updating QuickBooks sign-in info on the same day as any bank credential change, never using auto-fill in the credentials form, checking the bank feed status weekly, and reviewing the download queue for duplicates after any reconnection. These four habits address every confirmed cause of QuickBooks Error 103 before a transaction gap or account lockout makes the error more disruptive.

Disclaimer: The information outlined above for “How to Fix QuickBooks Error 103 Due to An ID or password Issue?” is applicable to all supported versions, including QuickBooks Desktop Pro, Premier, Accountant, and Enterprise. It is designed to work with operating systems such as Windows 7, 10, and 11, as well as macOS.