OL 332 QuickBooks Error, Fix the Bank Login or Import QBO
Convert a PDF bank statement to a QuickBooks file
Drop in a PDF statement and get a QBO (Web Connect) or IIF file you can import into QuickBooks Online or Desktop.
OL-332 in QuickBooks Desktop means your bank's server received the Bank Feeds request and refused it, most often because it did not accept the sign-in details QuickBooks sent. A changed password, a separate Direct Connect PIN, a new security step at the bank, or a notice waiting on the bank's website are the usual triggers. Fix the credentials and reset the connection. While you wait, a .qbo or IIF file made from the statements imports without any connection at all.
The distinction from its neighbor matters. OL-301 is the bank sending back a general error. OL-332 is narrower: the request arrived and the bank said no to who was asking. Accountants who document the code describe it as an invalid customer ID or PIN at the bank's end, and Intuit lists it with the other OL codes in its help article on fixing OL and OLSU Bank Feeds errors in QuickBooks Desktop. So the first place to look is not your company file. It is the login.
What causes QuickBooks error OL-332?
Almost every reported case traces back to one of the causes below. The right column tells you which one you are looking at before you spend an hour on the wrong fix.
| Cause | Where it lives | How you spot it |
|---|---|---|
| Password changed at the bank, old one still saved in QuickBooks | Your QuickBooks file | Error started the day after a password reset or a forced change |
| Direct Connect uses its own PIN or enrollment, separate from the web login | The bank | Web login works fine in a browser but QuickBooks is still refused |
| New terms, an alert or an identity check waiting on the bank's site | The bank | Signing in on the website shows a prompt you have not accepted |
| Third-party or software access switched off at the bank | The bank | The bank's security settings list linked apps and QuickBooks is missing or disabled |
| Bank changed its connection type (Direct Connect to Web Connect or back) | The bank's listing in QuickBooks | Other users of the same bank report the same code in the same week |
| Inactive account with online banking still switched on | Your QuickBooks file | The error names an account you no longer use |
| Version past its support date | QuickBooks itself | Help, About QuickBooks shows a year Intuit no longer services |
How do I fix error OL-332 in QuickBooks Desktop?
Back up the company file first and sign in as Admin in single-user mode. Work through these in order and stop as soon as a download succeeds.
1. Sign in on the bank's website with the exact credentials QuickBooks uses
Not the ones your browser remembers. Type them. If the site asks you to accept new terms, verify your identity or change your password, do it, then try QuickBooks again. This single step clears a large share of OL-332 cases, because the bank blocks outside connections until the prompt is answered.
2. Ask the bank whether Direct Connect has its own PIN
Some banks run Direct Connect as a separate service with its own enrollment, and sometimes its own PIN or a monthly fee on business accounts. If you enrolled years ago, the PIN may have expired or been reset without anyone telling you. The bank's business support line can confirm the enrollment status in a few minutes. If your bank has moved to Web Connect only, stop fighting Direct Connect and download .qbo files instead.
3. Deactivate and set the account up again
Open the Chart of Accounts, right-click the account, choose Edit Account, open Bank Feed Settings and select Deactivate all online services. Save. Then go to Banking, Bank Feeds, Set Up Bank Feed for an Account, and enter the current credentials fresh. Nothing already in the register is removed.
4. Clear online banking from inactive accounts
In the Chart of Accounts, tick Include inactive. Any closed card or old checking account that still has online services switched on can drag the whole bank session into an error. Deactivate online services on each one.
5. Run the test company check
Create a sample company with Express Start, add the same bank, and download. If it fails there too, the refusal is at the bank and you need them, not Intuit. If it works, the problem is inside your company file; run File Doctor from the QuickBooks Tool Hub and repeat step 3.
6. Confirm your version is still supported
Open Help, About QuickBooks. Intuit services each Desktop year for roughly three years, then switches off online banking for it, and some banks set their own shorter window (Wells Fargo, for example, supports Desktop versions that are current or from the prior two years). If you are past the date, no reset helps. The page on discontinued QuickBooks Desktop versions covers what still works, and IIF import is the part that does.
Can I keep importing transactions while OL-332 is unresolved?
Yes. OL-332 blocks the live connection, not file imports. A Web Connect file brought in through File, Utilities, Import, Web Connect Files lands in the same account with the same review screen as a download, and it never asks the bank for permission.
That file can come from three places:
- The bank's own QuickBooks download, when you can sign in on the website and the months you need are inside its window. Windows vary a lot: Wells Fargo keeps card activity for up to 90 days or 300 transactions, Chase offers roughly two years of card activity as .qbo.
- The PDF statements, which reach back years further than any download. Convert the PDF bank statement to a QuickBooks Desktop file, check the total against the statement's ending balance, and import it the same afternoon.
- An IIF file, for a Desktop version where Web Connect has stopped too. IIF is a local import that calls no Intuit service.
Card accounts need one extra check. The file has to declare a credit card account with purchases as charges, or every purchase posts as a deposit and you find out at reconciliation. Our card pages, such as the Wells Fargo credit card to QuickBooks converter, write the account type correctly.
OL-332 compared with the codes around it
| Code | What it points to | First thing to try |
|---|---|---|
| OL-332 | Bank refused the sign-in: customer ID, password or PIN | Sign in at the bank, confirm Direct Connect enrollment |
| OL-301 | Bank returned a general error: account changes, services not active | Sign in at the bank, then test company; see the OL-301 guide |
| OL-222 | A .qbo file QuickBooks cannot read | Replace the file; see the OL-222 guide |
| OLSU-1013 | Setup blocked, often pending approval at the bank | Approve QuickBooks access at the bank; see the OLSU-1013 guide |
| OLSU-1024 | Bank branding files, or an unsupported version | Update and check the version |
What does waiting on OL-332 cost?
When the fix is on your side, OL-332 takes ten minutes. When it is on the bank's side, such as an enrollment the bank has to reissue, it can run for days, and month-end does not move. A business checking account with 100 transactions a month takes about an hour to key and check by hand, and a card account with receipts to match takes longer. Converting the statement and importing it takes a few minutes plus a balance check.
On the Starter plan here, $49 a month covers 50 statements. For a firm with several clients at one bank that has locked everyone out, that is cheaper than one afternoon of data entry, and the books close on time. If you are catching up because a return is due, the closed books feed straight into whatever you use to file the tax return online, so the deadline that matters is the one you actually meet. When several banks fail at once, the bank feed not working page covers closing the whole month from statements.
Frequently asked questions
What does error OL-332 mean in QuickBooks?
OL-332 means the bank's server received the Bank Feeds request from QuickBooks Desktop and refused it, usually because the customer ID, password or Direct Connect PIN did not match what the bank expects. Sign in on the bank's website, clear any prompts, confirm the Direct Connect enrollment, then set up the connection again.
Is OL-332 a QuickBooks Online error?
No. OL-332 is a QuickBooks Desktop Bank Feeds code, including Enterprise. QuickBooks Online shows its own connection messages. The Online version of the workaround is Transactions, Bank transactions, Link account, Upload from file, which accepts a .qbo file.
Why does OL-332 appear when my bank login works on the website?
Because Direct Connect can use a separate enrollment or PIN from your web login, and a browser may be signing you in with saved credentials QuickBooks does not have. Ask the bank to confirm Direct Connect status for the account, then re-enter the credentials in QuickBooks by hand.
Will importing a .qbo file duplicate transactions when the feed returns?
It can. QuickBooks skips a line on its own only when the transaction ID matches one it already has, and a file converted from a statement carries different IDs from the bank's. Start the first download after the last imported date, or match any repeated line in For review instead of adding it.
Can OL-332 be fixed by reinstalling QuickBooks?
Rarely. OL-332 is a refusal at the bank, so reinstalling changes nothing unless your version is past its support date. Fix the credentials first, run the test company check, and update or replace QuickBooks only if the version is the problem.
Skip the manual entry
Upload a PDF bank statement and get a QBO or IIF file ready to import into QuickBooks.
Convert a Statement Free