1. Preserve a recovery point
Back up the company file before importing bank transactions. Do not use the only copy of the books as a converter test environment.
QuickBooks Desktop QBO import
Back up first and test unfamiliar Web Connect files outside your production company. Product menus and sign-in requirements can vary by QuickBooks Desktop release.
Updated July 24, 2026 · Examples use fictional data.
Back up the company file before importing bank transactions. Do not use the only copy of the books as a converter test environment.
Confirm the expected statement period, account type, and transaction count. If needed, use the local QBO to CSV preview before opening QuickBooks.
In supported Desktop versions, the workflow is commonly available under File → Utilities → Import → Web Connect Files. Select the QBO file and follow the account-selection prompt.
Use a blank test company first. If QuickBooks asks whether to use an existing account or create one, verify the account type and avoid connecting an unfamiliar test file to a live account.
Record the QuickBooks release, Windows version, account type, and non-sensitive error category. Never send a real QBO file to BankFileKit support; create a fictional reproduction instead.
Follow Intuit's Web Connect troubleshooting first. A file may be incomplete, use unsupported institution details, conflict with an online-connected account, or require a product sign-in. Changing the extension is not a fix.
The CSV to QBO tool produces a candidate QBO file, but the output has not been verified in a real QuickBooks Desktop environment. It must not be described as guaranteed compatible.