Wells Fargo View-Only Access Failures Block QuickBooks Downloads
Wells Fargo view-only logins are failing for some bookkeepers and blocking QuickBooks Desktop imports. Here is what to do while the bank investigates.
Bookkeepers who sign in to Wells Fargo online banking with view-only credentials are hitting a wall. The site stops them at login with a message directing them to call the bank. Nothing reaches the accounts page, so nothing reaches QuickBooks Desktop either. According to community reports, callers are being told the bank is investigating, with no timeline for a fix.
What exactly is failing?
The block sits at the bank, not inside QuickBooks. The restricted profile is stopped at sign-in, before any accounts, statements, or export options load. QuickBooks Desktop never throws an error because the download never starts. Repairing the company file, reinstalling the software, or re-linking the account will not change the outcome, and there is no reason to try them for this.
Does this touch QuickBooks bank feeds as well?
The reports so far describe manual sign-in at the bank’s own website. Anything behind that login, including a hand-exported transaction file, is blocked with it. We have seen no confirmed reports covering server-side feed connections, so treat broader claims with caution. If your feed still updates while the web login fails, that fits a permissions fault on the web profiles rather than a wider outage.
What can you do right now?
- If the client’s own full-access login still works, have them export the transactions and hand you the file. Import it into QuickBooks Desktop as you normally would.
- Never ask for the client’s primary username and password. Shared primary credentials typically violate the bank’s terms and destroy the separation that view-only access exists to provide.
- Space out retries on the blocked profiles. Repeated failed sign-ins can look like unusual activity to a bank’s security systems and risk a lockout.
- Keep a one-line log for each client: the date range blocked and the exact wording on screen. It makes any call with the bank shorter and tells you precisely what to pull later.
- Test one other client’s view-only profile before assuming the problem is systemic. If several fail the same way, the fault is on the bank’s side, not in your setup.
Has this happened before?
Yes, in shape at least. Practitioners recall an earlier outage with the same pattern, traced at the time to permissions settings on the bank’s side. No cause has been confirmed for the current failures, so treat that history as a hint rather than a diagnosis. If the pattern repeats, the fix will land at the bank and the profiles will start working again without any change on your end.
Close the gap cleanly once access returns
When the login works again, export one file covering the entire blocked period, if the site’s export screen lets you choose dates. A single continuous import avoids duplicate or missing transactions at the seams. Then reconcile the affected accounts against the statements, and the interruption leaves no trace in the books.