Direct Connect for QuickBooks Desktop ends October 30, 2026 — how to keep importing your bank statements
September 3, 2026
If you keep clients on QuickBooks Desktop, a bank notice has probably landed in your inbox this year: Direct Connect for QuickBooks Desktop is being discontinued on October 30, 2026. This is what it means, what it does not mean, and what to do about it.
Where QuickBooks Desktop stands
Some context first, because the feed change sits inside a longer wind-down.
Intuit stopped selling new subscriptions to QuickBooks Desktop Pro Plus, Premier Plus and Mac Plus after September 30, 2024. Enterprise was not affected.
QuickBooks Desktop 2023 lost support on May 31, 2026.
QuickBooks Desktop 2024 is supported until September 30, 2027, and is the last non-Enterprise version.
QuickBooks Desktop Enterprise has no announced end date. Intuit's own site cites 268,493 active Enterprise subscriptions as of January 1, 2026.
So Desktop is not going away in October. Existing Pro, Premier and Mac subscribers on a supported version keep working, and Enterprise continues. What changes on October 30 is one specific way of getting bank transactions into the file.
The three feed types, plainly
QuickBooks Desktop has always had three routes for bank data. They are easy to mix up because the names are similar.
Route
How it works
After October 30
Direct Connect
QuickBooks talks to the bank's own server. Two-way: it can download transactions and, at some banks, send transfers or bill payments. Often a bank-side enrollment and sometimes a bank fee.
Discontinued for QuickBooks Desktop by the banks announcing it. Check your bank's notice for its date.
Express Web Connect
Intuit's connection retrieves transactions from the bank and QuickBooks pulls them in. One-way, set up from inside QuickBooks. Not every bank offers it.
Not part of this notice. Availability depends on your bank and your QuickBooks version.
Web Connect
You download a .qbo file from the bank's website and import it into QuickBooks yourself. One-way, manual, no live link.
Unchanged. This is the route banks are pointing people to.
What changes on October 30
Banks are telling Desktop customers that Direct Connect is being discontinued on October 30, 2026. Amegy Bank's notice is a clear example: new enrollments ended on April 30, 2026, the service ends on October 30, and the bank recommends Express Web Connect or Web Connect instead. Many banks are announcing the same date; check your own bank's notice, because the date and the recommended replacement are the bank's to set.
After the cut-off, a Desktop file that relied on Direct Connect will stop receiving transactions through that link. Nothing already in the file is affected. The work is to move each affected bank account to another route before the month-end close that follows.
Your options
There are three, and most bookkeepers will end up using more than one across a client list.
Express Web Connect, if your bank supports it. The closest replacement for a live feed. Set it up from the bank feeds center inside QuickBooks Desktop. If your bank is on the list, this is the least work. If it is not, or if the connection is flaky for that bank, move on to the next option.
Web Connect, with a .qbo downloaded from the bank. Most banks still offer a "QuickBooks" or ".qbo" download from online banking, usually next to the CSV and PDF options. Save the file, then in QuickBooks Desktop go to File → Utilities → Import → Web Connect Files and pick it. The transactions land in the bank feeds review screen just as they always did. The habit to build is a monthly download per account, filed with the statement.
A .qbo made from the PDF statement. For banks that offer no download, for closed accounts, and for months already gone (catch-up books, a client who "has the statements somewhere"), the PDF is often all you have. Converting the statement into a Web Connect file gives you the same import path as option 2, with one difference: nobody but you checked the data on the way in. That is why the next two sections matter.
What a statement-built .qbo has to get right
A .qbo is a plain text file in OFX format with a few fields QuickBooks is strict about. When the file comes from the bank, the bank fills them. When it comes from a statement, whoever built it has to.
A valid institution ID. QuickBooks Desktop checks the bank identifier in the file against Intuit's institution directory. A made-up or mismatched ID gives an import error, or associates the transactions with the wrong bank. The converter has to carry the real directory and let you pick your bank.
Stable transaction IDs (FITIDs). Every transaction in the file has an ID, and QuickBooks uses it to skip transactions it has already seen. If the IDs are random or change between runs, importing the same statement twice, or two statements with an overlapping day, duplicates the transactions in the file. If they are stable and unique, re-importing is harmless. This is the difference between a converter you can trust with a re-run and one you cannot.
The statement's closing balance as the ledger balance. The file carries a ledger balance and an as-of date. It should be the closing balance printed on the statement, on the statement's end date, so that the reconciliation screen in QuickBooks has the right number to work toward.
Bank versus credit card blocks. A checking account and a credit card use different OFX sections. A card statement written as a bank block imports into the wrong kind of account with the signs reversed.
See it tie before you import it
A .qbo from the bank is an export of the bank's own ledger. A .qbo from a PDF is a reading of a document, and readings have errors: a digit misread on a scan, a row lost at a page break, a sign flipped in a withdrawals column. None of these show up as an import error. They show up weeks later as a reconciliation that will not balance.
The check that catches them is old and simple. Opening balance plus credits minus debits must equal the printed closing balance, and every running balance along the way must agree. If the converted grid passes that check against the numbers printed on the statement, every row was read correctly, or two errors cancelled exactly, which is rare enough to ignore. If it fails, you know before anything reaches the client file, and you know which row to look at.
So the rule for option 3 is: do not import a converted statement that has not been shown to tie to its own printed balances. Anything that gives you a file without showing you that arithmetic is asking you to find its mistakes at reconciliation time, one transaction at a time.
A short checklist for October
List every Desktop client account that currently uses Direct Connect. The bank feeds center in QuickBooks shows the connection type per account.
For each, check the bank's notice for its date and its recommended replacement.
Where Express Web Connect is offered, switch before the cut-off and confirm one download works.
Where it is not, find the .qbo download in online banking and do one manual import through File → Utilities → Import → Web Connect Files.
For accounts with no download, or for back months, convert the PDF statement, confirm it ties to the printed balances, then import the .qbo.
Reconcile each account once through the new route before relying on it at month end.
QuickBooks is a trademark of Intuit Inc. PennyClose is not affiliated with Intuit. Dates above were checked on September 2, 2026; your bank's notice governs for your bank.
Try it. Upload a statement and see whether it ties to its printed balances before you download anything. The preview is free and needs no account. Convert a statement