Sample workflow — not a specific client’s data
A real reconciliation summary
The written read-out showing which transactions the feed doubled, dropped, or never delivered while it was down.
Error OL-301 / OL-302
QuickBooks error OL-301: the bank-feed connection fix
Error OL-301 — and its sibling OL-302 — means QuickBooks could not complete an online-banking connection to your bank. The problem lives in the link between the bank and QuickBooks: a connection setting, a change on the bank's side, or the aggregator that carries the data. It is not a problem with your company file. Refreshing or re-linking the connection clears most cases.
- A connection fix, not a file fix
- Refresh, then re-link the feed
- We reconcile what the feed missed
Who this affects
This is about the bank connection, not what is in your books
You will see OL-301 or OL-302 when QuickBooks tries to talk to your bank and the exchange does not complete. The company file is fine — the transactions already posted are still there, and nothing in the data has been damaged. What failed is the online-banking handshake: a login that needs re-authorizing, an agreement waiting on the bank's website, a security change the bank rolled out, or a hiccup in the aggregator service that shuttles the data. Because the cause sits on the bank or aggregator side, the same error can appear even when nothing changed in your QuickBooks.
Start here
OL-301 — a connection fix, or a deeper books problem?
THE FEED WILL NOT CONNECT OR UPDATE
A connection fix
Sign in at the bank, then refresh or re-link the account — this clears most OL-301 and OL-302 messages.
TRANSACTIONS ARE NOW DOUBLED OR MISSING
Now it is reconciliation
A feed that dropped and resumed can leave duplicates or gaps the books must be reconciled to.
See bank-feed issuesRead this as text
- THE FEED WILL NOT CONNECT OR UPDATE: A connection fix — Sign in at the bank, then refresh or re-link the account — this clears most OL-301 and OL-302 messages.
- TRANSACTIONS ARE NOW DOUBLED OR MISSING: Now it is reconciliation — A feed that dropped and resumed can leave duplicates or gaps the books must be reconciled to.
Fix it yourself
The DIY fix for OL-301, step by step
Work from the bank inward. Most OL-301 and OL-302 cases clear once the bank-side blockers are gone and the connection is refreshed or rebuilt.
-
Sign in at your bank first
Log in to your bank's own website and clear anything waiting — a new alert, a security prompt, a terms agreement, or a login change. An unread bank-side notice is one of the most common reasons a feed stops connecting.
-
Refresh or update the account
Back in QuickBooks, refresh the account or run Update on the bank feed. A single re-authorization after the bank-side alert is cleared often brings OL-301 straight back to a working connection.
-
Deactivate and reconnect
If it still fails, turn off online banking for that account, then set it up again from scratch and re-link it to the bank. Rebuilding the connection resolves cases where the old link is stale or broken.
-
Import manually as a fallback
While the feed is down, download a Web Connect (.QBO) file from your bank's website and import it into QuickBooks so posting continues. This keeps you current without waiting on the connection.
-
Reconcile once the feed returns
When the connection is back, reconcile the account against the real bank statement. A feed that lapsed can overlap or skip dates, so confirm every transaction is present once and only once.
When it is more than the feed
When OL-301 leaves a mess in the books
The connection error itself is not a books problem — but the outage it causes can become one. When a feed stops and later resumes, it can pull the same days twice or skip the days it was down, so the register quietly drifts out of step with the bank. If you have had OL-301 or OL-302 for a while, the risk is not the error message; it is the duplicate and missing transactions hiding behind it. That is reconciliation and cleanup work: matching the register back to the bank statement, clearing the doubles, and adding what never came through, so the balance you report is the balance you actually have.
How you can verify us
How we work
We reconcile the account to the real statement before we call it clean. See what cleanup involves.
See QuickBooks cleanupResponse commitment
A real specialist replies within one business day, in writing.
Questions about error OL-301
What does QuickBooks error OL-301 mean?
OL-301, and its close relative OL-302, means QuickBooks could not complete an online-banking connection to your bank. The trouble is in the link between the bank and QuickBooks — a connection setting, a bank-side change, or the aggregator that moves the data — not in your company file. Your books are intact; the feed simply did not come through.
How do I fix OL-301 quickly?
Sign in to your bank's website first to clear any alert or agreement waiting there, then in QuickBooks refresh the account or update the bank feed. If it still fails, deactivate online banking for that account and reconnect it fresh. That refresh-or-relink sequence resolves most OL-301 and OL-302 messages.
Is OL-301 a sign my company file is damaged?
No. OL-301 is a banking-connection error, not a file-integrity error. It does not point to corruption the way file-open errors do. If a bank feed is down, the fix is on the connection or the bank side — not a file repair — though the missed transactions still need to be reconciled once the feed returns.
Why did my bank feed suddenly stop with OL-301?
Banks change how they publish data, update their security or login flow, or require a new agreement, and any of those can break an existing connection until you re-authorize it. Because the cause sits on the bank or aggregator side, the error can appear even though nothing changed in your QuickBooks.
Can I still get my transactions in while OL-301 persists?
Yes. While the feed is down you can download a Web Connect (.QBO) file from your bank's website and import it into QuickBooks manually, so posting continues. Watch for duplicates where the feed later resumes over the same dates — a downtime like this is exactly when a bank feed can hide double or missing entries that reconciliation has to catch.