QuickBooks error 9999 is a general connection failure that stops a bank feed in QuickBooks Online from updating. Start with the browser: a private window, then a cleared cache. Check the bank's site for an outage. Disconnect and reconnect the account only if the error stays, and fill any missing days with an uploaded file.
What error 9999 tells you about the bank feed
Error 9999 tells you the bank feed tried to update and failed, without saying why. Unlike codes that point at a password or a closed account, it is a catch-all. The fault can sit in your browser, at the bank or in the connection between them, so the fixes run from the cheapest to the most disruptive.
That vagueness is the main thing to understand. A code such as QuickBooks error 324 means the bank can't find the linked account, so you know to reconnect. Error 9999 gives no such clue. If the bank's own website lets you sign in and see your transactions, the account itself is probably fine and the failure lies in the link.
Intuit's article on bank errors when downloading transactions gives three general steps for feed errors. Run a manual update, check the bank's website for outages or alerts, and update your sign-in details if they changed at the bank. Intuit notes that bank outages usually resolve within 24 to 48 hours.
Browser steps that clear error 9999
Browser steps come first because they change nothing in your books. Intuit's bank error article says that if a manual update doesn't bring in transactions, sign in to QuickBooks through a private or incognito window and update the connection again. That window starts without stored data from earlier sessions.
Work through these in order, stopping when the feed updates:
- In QuickBooks Online, go to Bank transactions and select Update.
- If error 9999 comes back, open a private or incognito window, sign in and select Update again.
- If that works, clear your normal browser's cache and cookies, then sign in there again. Old stored data is the likely cause when a private window succeeds.
- If the private window fails too, try a different, up-to-date browser.
- Sign in to the bank's website directly. Accept any notices, read any secure messages and look for maintenance warnings.
- If the bank shows an outage, wait a day or two before going further.
Clearing the cache is a general browser fix, not a QuickBooks setting. Clearing cookies signs you out of other sites, so have your passwords ready first.
Should you disconnect the account to fix error 9999?
Disconnect only after the browser steps and a day's wait have failed. Disconnecting removes the bank feed link and builds it again from scratch, which can clear a stuck connection. It also has costs, set out in Intuit's guide to disconnecting accounts connected to online banking.
The three costs Intuit names:
- Pending lines are removed. When you disconnect, QuickBooks removes any transactions still waiting for review in the Pending tab. Accept or match them first.
- History stops at 90 days. Transactions older than 90 days can't be downloaded again when you reconnect.
- Duplicates are possible. Disconnecting an account while it has an error may download duplicate transactions when you reconnect.
The third point matters most with error 9999, because the account has an error by definition. After reconnecting, compare the first download with what is already in the register. Exclude any repeats before you accept them.
To disconnect, Intuit's steps are: go to Bank transactions, select the account's tile, select the pencil icon, then Disconnect account, and confirm. The option is hidden while QuickBooks is downloading.
Can an uploaded file fill the error 9999 gap?
Yes. An uploaded file fills the days error 9999 kept out of the feed. Download a CSV or QBO file from the bank's website covering only those days and upload it to the same account. A file doesn't depend on the broken link, so it works while the feed is down.
Take an example. The feed last updated on October 3, error 9999 started on October 4, and the reconnected feed brought in transactions from October 12. The gap runs from October 4 to October 11. Download exactly that range and no more.
Intuit's guide to manually uploading transactions sets the limits: 350 KB or less and up to 1,000 lines per file. A week or two of activity sits well inside both. If the upload itself fails, the guide to a QuickBooks Online bank upload error sorts the cause.
Xero has its own size rules for the same job. The guide to the Xero bank statement import limit shows how to split a longer gap by date.
If the bank only gives you PDF statements for those days, SimpleBankConvert is being built to turn a PDF into a CSV or QBO file for this kind of gap. It isn't open yet; get started to be told when it is.