Import Bank Statements to QuickBooks

Cause:

QuickBooks Online expects QBO format but received IIF or a malformed file.

Fix:

Re-convert your bank statement and select QBO format specifically. Ensure the downloaded file has a .qbo extension. If the error persists, try opening the file in a text editor to verify it starts with "OFXHEADER:100".

Cause:

The statement period overlaps with transactions already in QuickBooks from bank feeds or manual entry.

Fix:

Before importing, check if QuickBooks already has transactions for that date range via Banking > For Review. QuickBooks Online will flag potential duplicates — review each one and select "Exclude" for items already recorded.

Cause:

During import, the wrong bank account was selected as the destination.

Fix:

Delete the imported transactions by going to Banking > select the account > select all imported transactions > Batch actions > Exclude. Then re-import to the correct account.

Cause:

Date format mismatch (MM/DD vs DD/MM) or currency formatting issues in the source PDF.

Fix:

Our converter normalizes dates to ISO 8601 format (YYYY-MM-DD) which QuickBooks handles correctly. If amounts are wrong, check your original PDF for OCR quality — a rescanned copy at 300+ DPI usually resolves accuracy issues.

Cause:

The IIF file references account names that do not match existing accounts in QuickBooks Desktop.

Fix:

QuickBooks Desktop creates new accounts automatically if names do not match. Before importing, ensure your chart of accounts includes the bank account name used in the IIF file. You can edit the IIF file in a text editor to change the account name.

Cause:

This is unrelated to file import — it refers to the direct bank feed connection, not QBO/IIF upload.

Fix:

Manual file imports work independently of bank feeds. If you need both, you can use file import for historical statements and bank feeds for ongoing transactions without conflict.