QuickBooks Error 2000

Let’s Dive in to see…

How to Fix QuickBooks Payroll Error=2000

QuickBooks Online

QuickBooks Banking Error · OFX / Bank Feeds

How to Fix QuickBooks Error 2000

QuickBooks displays: "QuickBooks is unable to verify the financial institution information for the download" or "Sign-on was rejected" when connecting to online banking or bank feeds.

Error 2000 is an external banking error — the bank's OFX/Direct Connect server rejected QB's connection. At QuickFix Bookkeeping, the first fix is always verifying your bank credentials directly on the bank's website, then checking if online banking is still active. The QBWUSER.INI rename is the QB-side fix that resets the stored banking preferences when the bank's server returns a persistent 2000 code.

The QuickFix Bookkeeping Distinction — Error 2000 Is External, Not Internal

Error 2000 originates at the bank's server, not inside QB. The bank's OFX Direct Connect server responds with a 2000 status code meaning it refused the connection attempt.

Error 2000 — bank-side rejection

Bank's server returns OFX error code 2000 = authentication failed or account not authorized for Direct Connect. Start: verify credentials directly on bank website, check if online banking is still active, update password in QB if changed.

Error 102/103/105 — server issues

Bank's website is down or unavailable (not an authentication rejection). QB can't reach the bank at all. Fix: wait for bank server to come back online. Error 2000 is different — the bank is reachable but rejected the specific authentication attempt.

The QBWUSER.INI rename fix — 2000-specific QB-side reset: The QBWUSER.INI file stores QB preferences including banking connection settings and cached credentials. When the bank's server returns a 2000 code due to a credential mismatch that was stored in this file, renaming it (QB recreates it fresh on next launch) clears the corrupted banking preferences and forces QB to re-establish the connection cleanly. Navigate to the QB company file folder → find QBWUSER.ini → rename to QBWUSER.ini.OLD → reopen QB → re-enter bank credentials when prompted.

What Causes QuickBooks Error 2000?

Incorrect Bank Login Credentials in QB

Primary cause — the username or password stored in QB for your bank account no longer matches the bank's records. Common after a bank password change that wasn't updated in QB, or after a bank-side account security event that requires credential re-verification. The bank's server returns 2000 when authentication fails.

Online Banking Not Active on Account

The bank account has been deactivated for online/Direct Connect access (common after extended inactivity, account closure, or bank security policy changes). QB's Direct Connect request is rejected with code 2000 because the account isn't authorized. Verify the account is still active for Direct Connect on the bank's website or by calling the bank.

Corrupted QBWUSER.INI File

The QBWUSER.INI preferences file contains cached banking connection parameters that have become corrupted or stale. QB sends invalid connection data to the bank, which returns 2000. Renaming the file forces QB to recreate it with clean, default settings, eliminating stored invalid parameters.

Bank Changed Its Connection Method

Some banks migrate from Direct Connect to Web Connect (or vice versa) or update their OFX server endpoints. When QB still uses old connection parameters for a method the bank no longer supports, the bank's server returns 2000. QB's Financial Institutions Directory (FiDir) may be outdated; updating it pulls the latest connection parameters.

Bank Account Information Was Just Updated

If direct deposit or employee bank account information was recently changed in QB and transmitted to the bank, but the bank's server hasn't fully processed the change yet, subsequent data uploads receive a 2000 rejection. Retrying after 24–48 hours often resolves this as the bank processes the pending change.

Firewall or Network Blocking the Bank Connection

Firewall rules can intercept and modify the OFX authentication packets that QB sends to the bank, causing the bank to see an invalid authentication and return 2000. Configuring QB as an allowed program in Windows Firewall and disabling SSL inspection for QB's bank connections resolves this.

How to Fix QuickBooks Error 2000

Start by verifying credentials on the bank's website — this confirms whether it's a credential issue or a QB-side preferences issue.

METHOD 1 Verify Bank Credentials + Update in QB + Check Account Status Always start here — confirms if it's credential-based
1

Test credentials on the bank's website: open a browser → go to your bank's website → log in with your username and password. If login fails → your credentials are wrong or your account is locked. Reset your password on the bank's website before updating anything in QB.

2

Update credentials in QB: Banking → Bank Feeds → Set Up Bank Feed for an Account → find the account → re-enter your updated username and password → connect. Or: Lists → Chart of Accounts → right-click the account → Edit Account → Bank Feed Settings → edit sign-in information.

3

Check online banking status: while logged into your bank's website → check the Notifications section for any messages requiring action (security verification, terms acceptance, account review). Complete any required actions → return to QB and retry the bank feed connection.

METHOD 2 Rename QBWUSER.INI File Corrupted banking preferences — 2000-specific QB reset
1

Close QB. Press Windows + E → navigate to the QB company file folder (usually C:\Users\[username]\AppData\Local\Intuit\QuickBooks). Find QBWUSER.ini → right-click → Rename → add .OLD.

2

Reopen QB. QB recreates a fresh QBWUSER.ini with default settings. Re-enter your bank account credentials when QB asks you to set up bank feeds again. Test the connection — if it succeeds, the old .ini file had corrupted banking parameters.

METHOD 3 Deactivate and Reactivate Bank Feeds Reset the bank feed connection entirely
1

Lists → Chart of Accounts → right-click the bank account → Edit Account → Bank Feed Settings tab → click Deactivate All Online Services → OK → Save & Close. Close and reopen QB. Then: Banking → Bank Feeds → Set Up Bank Feed for an Account → search for your bank → enter credentials → reconnect. A full deactivation/reactivation clears all stored connection state and forces a fresh handshake with the bank's server.

METHOD 4 Update QB + Configure Firewall + Contact Bank Outdated QB or bank changed connection method
1

Update QB: Help → Update QB Desktop → Reset Update → Get Updates → restart (updates the Financial Institutions Directory with the latest bank connection parameters). Firewall: Windows Firewall → Allow an app → ensure QB is allowed on both Private and Public. Contact bank: if all above fails, call your bank and ask them to verify your account is authorized for Direct Connect, and whether they recently changed their OFX server or connection method.

Quick Reference

SituationCauseStart with
Error 2000 any occurrenceCredentials or account statusMethod 1 — verify on bank website first
Bank website login works but QB shows 2000Corrupted QBWUSER.iniMethod 2 — rename QBWUSER.ini
2000 recurring after credential updateBank feed connection state staleMethod 3 — deactivate + reactivate bank feeds
2000 after QB or bank updateBank changed connection methodMethod 4 — update QB + contact bank

Frequently Asked Questions

Is Error 2000 caused by QuickBooks or by my bank?
Error 2000 is an external banking error — it originates from your financial institution's OFX Direct Connect server, not from inside QuickBooks. The bank's server returns a 2000 status code in response to QB's connection request, meaning it rejected the authentication attempt. This is why the error message says "contact the Financial Institution" rather than "restart QB" or "repair QB." This doesn't mean QB has no role — sometimes QB's stored credentials or preferences file (QBWUSER.ini) is corrupted and QB is sending wrong authentication data. But the root cause is always resolved at the bank connection layer, not by repairing QB itself.
Will renaming QBWUSER.ini delete any of my data?
No. QBWUSER.ini contains QB preferences and application settings (including cached banking connection parameters) — not your accounting data, transactions, or company file information. Renaming it to .OLD causes QB to create a fresh file with default settings on its next launch. You'll need to re-enter bank credentials and some preferences (like window layout settings), but all your financial data remains untouched in your .QBW company file. The old .ini file is preserved as .OLD so you can compare settings if needed.

Related QuickBooks Errors

Error 2000 Persisting After Credential Update and QBWUSER.ini Rename?

Let QuickFix Bookkeeping Restore Your Bank Feed.

Persistent Error 2000 after credential reset and .ini rename typically means the bank changed its connection protocol or your account needs specific re-authorization on the bank's end — our ProAdvisors can coordinate with your financial institution.

Book a Free 30-Minute Consultation

No obligation. Same-day response. Bank feed restored fast.