How to Fix TD Bank Error 106 in QuickBooks (and a Workaround)

QuickBooks error 106 means the bank connection to your TD Bank account is broken: QuickBooks cannot reach the feed, usually because TD Bank ended or changed the connection on its side. The standard fix is to update or rebuild the bank connection in QuickBooks, and if that fails, wait for TD Bank to restore the link. While the feed is down, you can keep working by converting the PDF statement to a QBO file and importing that. Error 106 is a connection problem, not a data problem, so nothing in your books is broken. The transactions just are not flowing until the link is repaired.

This error shows up more on TD Bank than most banks, and TD Bank Business Direct accounts get hit the hardest. Here is what causes it, the fixes in the order worth trying, and how to stop it from stalling a close or a tax deadline.

What error 106 means

In QuickBooks, error codes 105, 106, 108, and 109 all point at the same general problem: the connection between QuickBooks and the bank is not working. Specifically, 106 means the account link no longer exists or has been deactivated on the bank's end, so QuickBooks has nothing to pull from. It is almost always caused by the bank side, TD Bank maintenance, a changed login flow, or an expired connection, not by anything you did in QuickBooks.

The fixes, in order

Start with a manual update, since a single failed refresh often clears on the next try. If it persists, sign in at td.com directly, because TD Bank sometimes holds the connection until you clear a security prompt or accept an updated agreement. If the account still will not pull, disconnect and reconnect it so QuickBooks rebuilds the link from scratch. When none of that works, the problem is on TD Bank's side and the only real fix is time.

Error 106 vs 105, 108, and 109

QuickBooks groups several bank-connection errors in the same family, and knowing which one you have tells you whether to act or wait. Error 105 and 106 both mean QuickBooks cannot reach the bank, usually a bank-side issue you resolve by refreshing or reconnecting. Error 108 means the bank has posted a notice or message on your account, so signing in at td.com and clearing it often restores the feed. Error 109 means your bank password or login changed and QuickBooks needs the new credentials. If you are seeing 106, the odds are high the fault is on TD Bank's end, which is why reconnecting and waiting are the two moves that actually work, rather than anything inside QuickBooks itself.

Why TD Bank Business Direct is the worst offender

TD Bank Business Direct, the platform for business accounts, generates error 106 far more than the personal side. Business Direct uses a different connection path, and QuickBooks community threads are full of business customers who lose the TD Bank feed for days or weeks at a stretch. When the feed is your only route in, an outage on a business account can freeze your bookkeeping right when month-end or a tax filing is due.

The workaround that keeps your books moving

You do not have to wait for the feed to come back. Every transaction error 106 is blocking is already sitting in your TD Bank PDF statements, and those you can always download. Sign in at td.com, download the statement, and convert it to a QBO file with the TD Bank statement to QBO converter. It writes the same Web Connect file the feed would have delivered, with dates and signed amounts mapped, and you upload it into QuickBooks by hand. This works whether or not the connection is up, because it never touches the feed.

When TD Bank restores the connection, it resumes pulling new transactions going forward. The converted statement covers the gap the outage left, so there is no missing stretch in the register and nothing to reconcile twice. If you convert a statement that overlaps dates already imported, QuickBooks flags the duplicates during review so you can leave them out.

How to reduce error 106 going forward

You cannot stop TD Bank from doing maintenance, but a few habits cut how often error 106 stalls your books. Run a manual update from the Bank transactions screen every few days rather than relying on the automatic overnight sync, so you catch a broken connection early instead of at deadline. Sign in to td.com directly once in a while to clear any pending security prompt or updated-agreement notice before it blocks the feed. And keep your TD Bank statements downloaded month by month as they close, so that if the feed does drop, the source data is already in hand and converting it takes a minute. The businesses that get blindsided by 106 are almost always the ones with no recent statement saved when the outage hits.

Loading the older history the feed never reaches

Even when the TD Bank feed is healthy, it only backfills about 90 days from the day you connect it. If you are setting up QuickBooks, catching up a prior year, or reconstructing a closed account, the feed cannot reach that far back no matter what you do about error 106. Converting the PDF statements is the same fix for both problems: a down feed and a shallow one. You download the statements TD Bank keeps online for years and convert each to a QBO file, one upload per period.

The bills and payments behind those transactions are the other half of a clean catch-up. If you are rebuilding an accounts payable trail at the same time, running the supplier invoices through software that reads and codes them automatically keeps that side moving as fast as the bank side. For the full import walkthrough, see how to convert bank statements to QuickBooks (QBO), and if a period runs long, check how many transactions QuickBooks Online will import before uploading.