1. Verify the file's role
Start with a genuine .qbo Web Connect bank statement. Do not use a QuickBooks company file, accountant transfer copy, PDF, or renamed spreadsheet as a substitute.
QBO validation checklist
Validate a QBO file before importing it.
Check the file's structure and the intended import environment separately. A readable QBO statement can still be rejected by QuickBooks, so validation should finish with a backup and a controlled test.
Updated July 25, 2026 · Examples use fictional data.
Use the next step nowInspect supported transaction fields and statement metadata without uploading the QBO source file.
Create a local QBO audit CSV 2. Read the statement locally
Choose the QBO in BankFileKit's local reader. The tool looks for supported bank or credit-card transaction blocks with valid dates and signed amounts. It does not upload the file body, filename, account data, or transaction rows.
3. Review the audit fields, not just the row count
| Audit CSV field | Validation use |
|---|---|
Date and Amount | Compare the date range and amount direction with the expected statement period. |
Description | Spot-check that readable transaction text maps to the expected rows. |
FITID, Memo, CheckNumber | Review supported transaction identifiers and references when the source provided them. |
| Account and statement columns | Check available account type, account ID, bank ID, date range, and FI metadata against the intended test context. |
4. Reconcile the expected period
Compare the source statement's expected transaction count, start/end date, credits, and debits with the local preview and audit CSV. Do not assume a zero-row or partial result is safe to import.
5. Treat duplicate signals as review prompts
BankFileKit warns when a repeated transaction identifier or repeated date/amount/description pattern appears. It never removes a row automatically because recurring charges can be legitimate. Also check whether the same statement period was already imported into the destination company.
6. Keep structure and compatibility separate
A valid-looking QBO structure does not prove that a specific QuickBooks Desktop release, bank connection, account state, or institution field will accept it. BankFileKit's local reader is a structure check, not an Intuit validation service.
7. Test the import safely
- Back up the company file.
- Use a blank company or controlled non-production account first.
- Review the imported transaction count, dates, signed amounts, descriptions, and duplicate behavior.
- Record only generic error information if the test fails.
Do not use a validation checklist as a data-sharing workflow
Validation does not require emailing the QBO to support or uploading it to a third-party converter. If you need help, produce a small fully fictional reproduction instead.
Sources checked July 25, 2026: Intuit: Fix Web Connect import errors; Open Financial Exchange specifications.