QuickBooks Desktop OL-200 Series Errors and the Stuck Bank Feeds Payment

QuickBooks Desktop users who send checks and bill payments through Bank Feeds are reporting a stubborn family of online banking errors: OL-200, OL-202, OL-206, and OL-226. The message that rides along says the last online connection did not complete and that the software cannot recover on its own. The good news is that the accepted fix is well documented, and it does not require file repair.

What do these four error codes mean?

They are siblings. Each one surfaces while you download transactions or send payments from the Bank Feeds Center, and each points to the same root cause.

At some point in a previous session, one or more online payments failed to send. The session broke before the software could close it out. That payment now sits in the outgoing queue. Every new connection tries to finish the old session, fails, and stops cold. Downloads stall along with sends, because the session aborts before either can complete.

The symptoms are consistent: an error banner during send and receive, payments piling up in the items-to-send list, and the same failure repeating on every sync. All four codes are handled as one problem in the accepted answer, with a single resolution path.

Why does the repair start with a phone call?

Because the connection broke mid-flight, the software cannot tell you whether the bank actually received the payment. If the bank received it and you delete it from the queue, your books and the bank statement diverge. The check clears in the real world while your file shows nothing.

So the accepted answer puts two prerequisites first. Call the bank and ask which sent items arrived and which are still queued. Then back up your company file before you touch anything else.

Neither step is optional in the fix as written. Both protect you from the one outcome worse than a stuck queue: a payment that lives at the bank but not in your books.

How do you isolate the stuck payment?

Open the Banking menu, choose Bank Feeds, then Bank Feeds Center. From the account list, select the account with the blocked items.

In the panel that lists items waiting to go to your bank, clear the checkbox on every online check and bill payment. Then send one item at a time. Select the first payment, send it, and wait for the result. If it goes through, move to the next. The payment that brings the error back is your stuck item.

It is tedious, and it works. Sending singly turns a vague failure into one identifiable transaction.

Clearing the stuck payment with Ctrl held

This part looks odd, but follow it exactly. You hold the Ctrl key through nearly the whole repair.

With Ctrl held, choose Send/Receive or Sync Accounts. Keep holding, releasing only to type your user ID, password, or PIN. A notice about the unfinished connection appears; acknowledge it while still holding Ctrl. A second prompt asks whether to resend the request to your bank. Answer it with Ctrl held, and only after the bank has confirmed what it received.

Next, open the stuck payment in your register. Hold Ctrl and clear the checkbox that marks it as an online payment. Dismiss any notice that appears.

With the payment still selected, hold Ctrl and delete it. The software refuses at first and says the payment cannot be deleted. Acknowledge that refusal, and a follow-up prompt offers to lift the restriction. Choose Yes, then delete again, and the payment leaves the queue.

The Ctrl key is a deliberate override. Payments inside an unfinished online session are locked against edits, and an ordinary delete is blocked by design. Holding the key tells the software you intend to force the change anyway. That power cuts both ways, which is why the backup and the bank call come first.

After the queue clears

Once the stuck item is gone, the next connection should complete normally, and the error family stops repeating.

If the bank never received the payment, recreate it and send it again. If the bank did receive it, record it in your books so the two sides match.

The OL-200 family is not file corruption, and it rarely needs repair tools. It is a queue that cannot drain until the stuck item is cleared by hand. Users who skip the bank call and delete blindly sometimes spend the following week chasing duplicates.