QuickBooks Web Connect Import Error QBWC1039: How to Fix It
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.
Short answer: QBWC1039 usually means the Web Connector cannot log in to your company file because access was never authorized, the app and company file are in different locations, or a duplicate registration exists. Fix it by opening QuickBooks as admin in single-user mode, granting the app auto-login under Integrated Applications, and re-adding the Web Connector configuration. If you are importing a bank statement, the cleaner path is a .qbo Web Connect file you drop straight into QuickBooks, no Web Connector app required.
What error QBWC1039 actually means
QBWC1039 is a QuickBooks Web Connector error. The Web Connector is a small Intuit utility that lets third-party apps push and pull data through QuickBooks Desktop. When the connector tries to open a session and QuickBooks refuses the login, it throws QBWC1039. It is a permission and configuration error, not a problem with your bank data. The most common triggers are an app that was never granted access, a company file that has moved since the app was authorized, or the same application registered twice.
People often hit this error while trying to get statement transactions into QuickBooks. It is worth separating two very different things: pulling data through a live app connection (Web Connector) versus importing a static .qbo Web Connect file you downloaded or created from a statement. The file import does not use the Web Connector at all, so it sidesteps QBWC1039 entirely.
How do I fix QuickBooks Web Connector error QBWC1039?
Fix QBWC1039 by authorizing the app inside QuickBooks. Open QuickBooks Desktop as the admin user, switch to single-user mode, then go to Edit, Preferences, Integrated Applications, Company Preferences. Select the third-party app, open its Properties, and check "Allow this application to log in automatically." Save, close, and run the Web Connector again. This grants the login the connector was being denied.
Work through these steps in order:
- Log in as admin, single-user mode. QBWC1039 will keep firing if you are in multi-user mode or logged in as a non-admin. From the File menu choose Switch to Single-user Mode, and confirm you are the Admin user.
- Grant the app auto-login. Edit, Preferences, Integrated Applications, Company Preferences tab. Select the app, click Properties, tick "Allow this application to log in automatically," and answer Yes in the authorization prompt.
- Keep the app file and company file together. The error appears when the Web Connector configuration (.qwc) and your QuickBooks company file (.qbw) live in different folders or on different machines. Move them to the same location, or re-add the .qwc while the correct company file is open.
- Remove duplicate registrations. If the same application shows up twice in the Web Connector, remove both entries and re-add the app once. Duplicates cause the login to collide.
- Update to the latest release. Install the current QuickBooks Desktop release and the latest Web Connector. Older builds have known session-login bugs that surface as QBWC1039.
Why the Web Connector fails when you switch company files
Authorization in QuickBooks is tied to a specific company file. When you authorize an app, that permission is stored inside that one .qbw file. Open a different company file, or restore a backup to a new path, and the connector is now trying to log in to a file that has never granted it access. That mismatch is one of the most common real-world causes of QBWC1039. Re-authorize the app while the exact company file you want to sync is open, and the error clears.
Skip the Web Connector: import a .qbo file instead
If your goal is simply to get bank statement transactions into QuickBooks, you do not need the Web Connector or a live app connection. QuickBooks Desktop reads a .qbo Web Connect file directly through File, Utilities, Import, Web Connect Files. QuickBooks Online reads the same file under Bank transactions, Upload from file. Because there is no app session, there is no QBWC1039.
The catch is that banks give you a PDF or a CSV, not a ready-to-import .qbo. That is exactly what our PDF bank statement to QuickBooks converter produces: drop in the PDF statement, get a clean .qbo (Web Connect) or .iif file, and import it with no connector app in the loop. For firms closing many months at once, the batch converter turns a stack of statements into import files in one pass.
Common Web Connect import errors and their real fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| QBWC1039 on every run | App not authorized in the open company file | Admin, single-user, grant auto-login under Integrated Applications |
| Error after moving or restoring the file | Authorization tied to old file path | Re-authorize the app with the correct company file open |
| App listed twice in Web Connector | Duplicate registration | Remove both, re-add the app once |
| "This file cannot be read" on a .qbo | Wrong format, or a truncated download | Re-download or rebuild the .qbo from the statement, confirm it is a valid Web Connect file |
| .qbo import prompts for an Intuit sign-in | QuickBooks Desktop requires an Intuit account for Web Connect import | Sign in to your Intuit account inside QuickBooks Desktop, then retry the import |
Does QBWC1039 mean my bank data is corrupt?
No. QBWC1039 is a login and permissions error inside QuickBooks, not a data-integrity problem. Your transactions are fine. The connector simply could not open a session with the company file. Once you authorize the app (or switch to a direct .qbo file import), the same data goes in without touching the connector.
Can I avoid the Web Connector entirely?
Yes, for statement imports. The Web Connector matters when a third-party app needs a persistent, two-way sync with QuickBooks. If you only need to load historical transactions from bank or credit card statements, converting the statement to a .qbo or .iif file and importing that file is simpler and more reliable. There is no app to authorize, nothing to re-register, and no QBWC1039. If your books live on a Mac, our browser-based PDF to QBO converter for Mac produces the same import files without any Windows-only tooling.
When the .qbo file still will not import
If the connector is out of the picture and QuickBooks still rejects the file, the problem has moved to the file itself, and the fix is different. Walk through our guide on why a .qbo file will not import into QuickBooks for the format, date-range, and account-matching checks. If numbers look off after a successful import, see how to fix a wrong opening balance after a QBO import.
Prefer to keep your data in a spreadsheet before it ever reaches QuickBooks? You can export the same statement to a clean workbook with a PDF bank statement to Excel converter, review it, then bring it in. And if your books run on CSV exports, a dedicated CSV to QBO converter handles that path.
The bottom line
QBWC1039 is fixable in a few minutes: log in as admin, grant the app auto-login, keep the app and company file together, and clear any duplicate registration. But if all you need is statement data in QuickBooks, the faster and more durable route is a .qbo or .iif file import that never touches the Web Connector. Convert the PDF, import the file, done.