Quick answer
A QuickBooks transaction download error means the feed stopped pulling new activity, not that your books are wrong. Bank errors 390 and 1000 need a disconnect and reconnect, and error 377 needs a connection refresh. Before you reconnect, finish everything already in For review so old transactions cannot land twice, then import the missing date range by hand.
What a transaction download error means
A download error means the link between QuickBooks and your bank stopped returning new activity. Your recorded transactions are untouched — the feed is the failing part. In QuickBooks Online, the message appears in a banner above the account tiles on Bank transactions, and the number in the message tells you what QuickBooks needs next.
| Message or code | Where it appears | Start with |
|---|---|---|
| Error 390 — "Your Bank is making a change" | QuickBooks Online | Step 3 — disconnect and reconnect the account |
| Error 1000 — "Fix your bank connection" | QuickBooks Online | Step 3 — disconnect and reconnect the account |
| Error 377 — QuickBooks is unable to download transactions | QuickBooks Online | Step 3 — update the online bank connection |
| OL and OLSU codes (for example OL-301) | QuickBooks Desktop | Step 6 — refresh the feed, then use Web Connect |
| No error, no new transactions | Both products | Step 1, then review the date-range limits |
Errors 390 and 1000 are re-authorization problems: the bank changed how it shares data, and the old connection stays off until you rebuild it. Error 377 means the connection exists but cannot finish a download. QuickBooks Desktop uses OL and OLSU codes instead. A feed can also stop quietly: QuickBooks Online downloads only posted transactions, and a Desktop download can succeed while the batch waits in the Bank Feeds Center for review.
Symptoms that point to the feed, not the data
- The Update button finishes without adding anything, or the account tile shows a bank error instead of a balance.
- Transactions stop on a specific date — often exactly 90 days back — while activity before that date is missing.
- One account stops while other accounts at the same bank keep updating.
- The bank's website shows posted transactions that QuickBooks does not list.
- After a reconnect, some transactions appear twice, usually because they were re-downloaded while the originals were still unreviewed.
- In QuickBooks Desktop, the Bank Feeds Center shows items with statuses such as Unmatched, Matched or Renamed, but nothing reaches the register.
Common causes, ranked by how often they occur
- The bank changed its connection and the feed needs re-authorization. This is the normal cause of errors 390 and 1000. The account stays visible; the data pipeline does not.
- An expired or rejected sign-in. Changed passwords, new multi-factor prompts and stuck one-time codes surface as error 377 or a silent feed. The same pattern appears in credit card feeds that stop syncing.
- The 90-day download window. QuickBooks Online cannot download transactions older than 90 days; they must be uploaded. QuickBooks Desktop usually receives about 90 days on the first download, and some banks allow up to a year.
- Duplicate or mis-mapped accounts. Connecting the same account twice, or connecting a parent account and its subaccounts, produces errors like 323 and 324 and can stall the feed.
- Pending, not posted. A card authorization that has not settled does not exist to QuickBooks Online yet. Nothing is broken; the transaction has not posted.
- Desktop session failures. Multi-user changes, a stale company file or a damaged feed configuration break Direct Connect and produce OL or OLSU codes.
- Browser and cache problems. A saved stale sign-in or an extension that blocks bank scripts can stop the update from completing in QuickBooks Online.
Review before you reconnect, and back up before you touch a Desktop file. Disconnecting and reconnecting a feed makes QuickBooks download recent activity again, which is how duplicate transactions get created. Work through the For review tab first. In QuickBooks Desktop, create a company-file backup before you change feed settings or import anything.
Before you begin
- Write down the exact code and wording from the error message. It decides which step below fixes the problem.
- Confirm you can sign in to the bank's website directly; bank outages usually clear within 24–48 hours.
- For error 377, have the original person who set up the feed available. The re-authorization link goes to that account holder.
- Plan on 10–15 minutes for QuickBooks Online, plus a longer review session if the feed has been silent for weeks.
How to fix transactions that will not download
Run a manual update and check the bank's website
Open Bank transactions and select Update. If a verification message appears, complete it. When the update finishes without new activity, sign in to the bank or credit card website and confirm the transactions are actually posted there — not pending — and check for a service notice.
If the update stalls, sign in to QuickBooks Online in a private or incognito browser window and update again. This rules out cached sign-ins and browser extensions, which are the two most common false alarms.
Clear the For review list before you reconnect
Open each affected account tile and work the For review tab: match everything that already exists in QuickBooks, add what is genuinely new, and exclude anything you do not want. QuickBooks stops re-downloading a transaction once it has been added or excluded, so this step is what prevents duplicates after a reconnect.
If a transaction appears twice, keep the copy that is reconciled (it shows C or R in the checkmark column). The two-minute review here saves an hour of cleanup later.
Re-authorize the bank connection for errors 390, 1000 or 377
For errors 390 and 1000, disconnect the account: select the pencil icon on the account tile, choose Edit account info, select Disconnect this account on save, and save. Then select Link account, find the institution, and sign in with your current online banking credentials. Errors 390 and 1000 both mean the bank reworked its connection and the old one is retired.
For error 377, select the Fix now link in the error banner and follow the prompts to update the connection. If the feed belongs to someone else, select Send a request so the original user receives an email link to re-establish it. This is also the right moment to fix a bank or QuickBooks sign-in loop if the credentials keep bouncing.
Remove duplicate connections and fix account mapping
If the bank reports a similar-name or already-connected error, you have two feeds fighting for one account. Disconnect the duplicate, then merge or rename accounts so each bank account maps to exactly one QuickBooks account. The same rule applies to parent and subaccounts: connect either the parent or its subaccounts, never both.
If one account has been dead for a while, a clean rebuild of the feed is more reliable than repeated retries. The reconnect order is covered in the bank feed guides for QuickBooks Online and QuickBooks Desktop.
Import the missing date range manually
Anything older than 90 days will never download, no matter how many times you reconnect. On the Bank transactions page, open the Link account menu and choose Upload from file. QuickBooks Online accepts an account statement as a PDF or image, or a list of transactions as a QBO, QFX or CSV file. The file must be in English and 350 KB or less, and a list can contain up to 1,000 lines per upload.
Download the range from your bank's website starting at least one day before your oldest QuickBooks transaction, then upload it into the matching account. Exclude any row that already exists so the import cannot double-post.
Refresh a Desktop feed and fall back to Web Connect
In QuickBooks Desktop, open Banking → Bank Feeds → Bank Feeds Center, select the bank, and use Sync this bank or Refresh account(s). If the session still fails with an OL or OLSU code, the bank may have moved off Direct Connect. Sign in to the bank's website, download the activity as a Web Connect (.QBO) file, then use Banking → Bank Feeds → Import Web Connect Files.
Two Desktop rules cause most support calls. Web Connect accepts only .qbo files — QFX and QIF will not import. And QuickBooks cannot download the same transactions into one company file twice, so once a batch has been added or deleted it will not come back unless the bank reopens it.
Verify the fix
- Select Update and confirm new posted transactions arrive, with the date of the most recent one matching the bank's website.
- Match or add every item in the For review tab, and confirm the account's opening balance line is correct.
- Compare the transaction count and ending balance against the bank statement for the same period.
- In QuickBooks Desktop, select Banking → Bank Feeds → Bank Feeds Center and confirm no items remain in the pending categories, then record a fresh backup.
- Reconcile the account to lock in the imported range.
If transactions still will not download
Start with the bank. Ask the business banking team to confirm the account is enabled for QuickBooks connections and to escalate to the group that supports OFX or QuickBooks connectivity. Bank-side migrations are the largest source of long-running 390 cases.
If the bank confirms everything is healthy, test the account in a second, empty QuickBooks Online company or a test company file. When the feed works there, the problem is specific to your company file or user permissions, not the bank. For Desktop, Intuit support can review OFX logs, which record the exact handshake failure. Avoid repeated disconnect-and-reconnect cycles while you wait — each pass raises the duplicate risk without fixing a bank-side outage. A clean reconnect is covered in how to connect bank and credit card feeds.
Prevention: keep the feed running
- Update the connection whenever you change your online banking password, before the feed fails.
- Review the For review tab weekly; small batches are easier to match and narrow the duplicate window.
- Do not mix manual uploads with an active feed over the same dates unless you exclude the overlapping rows.
- Reconcile monthly so a stalled feed is caught within days, not months.
- In QuickBooks Desktop, keep the company file backed up before changing feed settings.
Frequently asked questions
Why can't QuickBooks download transactions older than 90 days?
QuickBooks Online limits feed downloads to the last 90 days, and Desktop typically receives about 90 days on the first connection, though some banks allow more. Older activity has to come in through the manual upload process, or be entered by hand. Reconnecting does not reset that window.
Will disconnecting and reconnecting create duplicate transactions?
It can. The reconnect re-downloads recent activity, and anything still sitting unreviewed can arrive a second time. Clear the For review tab first, keep the reconciled copy when duplicates appear, and exclude the extra row. QuickBooks stops downloading a transaction once it has been added or excluded.
Why does one account stop updating while the others work?
Feeds are authorized per account. One card or checking account can lose its connection — often after a security prompt the feed could not answer — while the rest stay healthy. Fix the affected account on its own tile rather than reconnecting the whole bank.
Do I need to disconnect to fix bank error 1000?
Yes. QuickBooks documents error 1000 as broken bank connection data and lists disconnect and reconnect as the fix. There is no in-place repair for it, which is why the review step comes first.