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.
Some context first, because the feed change sits inside a longer wind-down.
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.
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. |
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.
There are three, and most bookkeepers will end up using more than one across a client list.
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.
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.
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 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.
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.
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.
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