Guides library

Understand the file before you import it.

Use these focused guides to choose the right CSV, QBO, OFX, or IIF workflow. They explain what BankFileKit can inspect locally and where QuickBooks compatibility still needs a real test.

Updated July 25, 2026 · All examples use fictional data.

Prepare CSV and Excel files

CSV to QBO file requirementsFields, date confirmation, duplicate warnings, and the local beta boundary.Excel to QBO file requirementsFirst-sheet structure, headings, values, and cautious QBO testing.QuickBooks CSV field mappingMap dates, descriptions, amounts, credits, and debits.QuickBooks Online CSV formatChoose a 3-column or 4-column bank CSV layout.

Understand QBO and OFX files

What is a QBO file?Separate a Web Connect statement from a company or accountant file.QBO file format explainedRead headers, statement blocks, transaction tags, and limits.Open a QBO file in Excel or Google SheetsCreate a local audit CSV for spreadsheet review.OFX vs QBO vs CSVChoose by source structure and intended workflow.CSV vs QBO vs IIF for QuickBooks DesktopUnderstand the role and support boundary for each file type.

Validate, import, and troubleshoot

Validate a QBO file before importCheck rows, metadata, dates, amounts, duplicates, and the real import boundary.Import QBO into QuickBooks DesktopBack up, use a blank company, and compare the result.Fix QBO Web Connect import errorsUse documented checks without changing an extension or guessing bank settings.Avoid duplicate bank transactionsTreat matching rows as warnings and keep period records.Fix CSV to QBO conversion errorsSeparate source-file validation from unverified Desktop import behavior.

Definitions and import troubleshooting are checked against the public source register; BankFileKit does not claim Intuit or bank affiliation.

Use the tool only after you know the target workflow.