Keeping Bank Downloads Alive in QuickBooks Desktop After Sunset
When Intuit sunsets your QuickBooks Desktop release, bank feeds are usually the first thing to go. Here is how to keep transactions flowing on Desktop.
When Intuit ends connected services for a Desktop release, the bank feeds are the first thing to fail. The register goes quiet and the Bank Feeds center reports OL or OLSU errors. That failure does not force you off Desktop. The automatic pipe can be replaced with a manual one, and the matching workflow you already use stays exactly where it is.
The services that stop at sunset
Direct Connect and Express Web Connect both rely on Intuit's connection service to broker every session. Sunset switches that broker off, so both methods fail on the same day, whatever the bank does on its end. Web Connect is the third method, and it works differently. You export a statement file from the bank's website in your browser, then import it into QuickBooks yourself. No broker, no session handshake, nothing that checks which release you run.
The import itself is local. QuickBooks reads the file, matches the bank's identity against the bank list it already carries, and queues the transactions for review. Our engineers put files on this path whenever a feed has to survive a sunset.
Prepare while the feeds still work
Start with a note per account: the date of the last transaction the feed delivered. Open each bank and credit card register and write that date down, because the first manual download starts the day after it. Then take a full backup from the File menu before you import anything. Imports are safe, but the first one on a sunset version is a poor time to test that claim.
Keep the latest reconciliation report for each account close by as well. It becomes your baseline if a matching session ever goes sideways.
Deactivate the old connection cleanly
Old feeds leave half-open session state behind, and that state causes trouble after sunset. Clear it before the first import. Open the Chart of Accounts, edit the first fed account, and open Bank Feed Settings; older releases call the same panel Online Banking Settings. Click "Deactivate All Online Services" and confirm. Repeat for every account that received a feed.
The Bank Feeds center will empty out, which is expected. This step also silences the startup warning about an unfinished online connection.
Download the file from the bank's website
Sign in to the bank's site and find the statements or transactions page. Look for a download in QuickBooks format, usually named Web Connect and ending in .qbo. Set the date range so the file starts one day after the date you noted earlier.
Some banks offer only a Quicken file ending in .qfx, or a plain OFX file. The content is the same OFX format under a different label, so renaming the download to end in .qbo often imports cleanly. Sites that export only CSV or Excel leave you two choices: a .qbo converter utility, or manual entry.
Import the file and relink the account
Import from the File menu: Utilities, then Import, then Web Connect Files. Double-clicking the .qbo achieves the same thing. QuickBooks reads the file and asks which account it belongs to. Choose "Use an existing QuickBooks account" and select the right register. Never accept the offer to create a new account, or you will get a parallel register and a broken reconciliation.
If your account is missing from the list, the account type is usually the reason. A credit card statement maps only to a credit card account; a checking statement maps to a bank account. Correct the type under Edit Account and import again.
How do you keep duplicates out?
Date ranges are the first defense. Overlap invites doubles, and the matcher only catches the ones that line up neatly on amount and date. When a range must overlap, review anything the center offers to Add rather than Match. Match means the entry already exists in your books. Add means QuickBooks intends to post a brand new one. A duplicate that slips through is deleted like any other transaction, but catching it at import is cheaper. The monthly reconciliation stays your backstop, and our reconciliation and month-end close routine is worth keeping in place while the feeds run by hand.
If the bank or the import refuses to cooperate
Two refusals come up in practice. The first is a bank your release never learned about, typically a brand launched after the version shipped. The import is rejected because the file's issuer cannot be identified. The CSV conversion route, or an alternate brand on the bank's own download page, usually resolves it.
The second refusal is an OL error at import time, which almost always means an online service is still half active. Recheck Bank Feed Settings on every affected account, then import again. For anything stranger, our QuickBooks bank feed error guides walk through the OL and OLSU families one by one.
The workflow that survives
Sunset removes the automation, not the accounting. The Bank Feeds center, the matching rules, and reconciliation all keep working on a manual schedule. Pick a standing date each month: download, import, match, reconcile. Files run this way for years, and Desktop keeps closing the books it always has.