QuickBooks Bank Import File Formats: QBO vs CSV vs OFX — Which Should You Use?

QuickBooks supports three file formats for importing bank transactions: QBO, CSV, and OFX. Each has specific strengths, limitations, and ideal situations. Choosing the wrong format causes column-mapping errors, duplicate transactions, or rejected uploads — problems that are entirely avoidable once you know which format fits your situation.

This guide explains each format, provides a decision matrix for picking the right one, compares them side by side, and covers conversion workflows when your bank does not provide the format QuickBooks expects.

Quick Decision: Which Format Should You Use?

Match your situation to the correct QuickBooks import format before spending time converting files:

What Is a QBO File?

A QBO file is the QuickBooks Web Connect format, used exclusively for importing bank transactions into QuickBooks. It is based on the OFX standard but includes additional QuickBooks-specific extensions.

Key characteristics:

• Structured according to OFX (Open Financial Exchange) but customized for QuickBooks
• Contains transaction details: Date, Amount, Description, Transaction ID (FITID), and Account information
• Auto-maps transactions during import to QuickBooks accounts
• Compatible with QuickBooks Online and QuickBooks Desktop

QBO files are preferred for automated bank feeds because they reduce manual column mapping, preserve transaction IDs, and improve reconciliation accuracy. They are especially useful for business accounts that require frequent updates or historical imports when paired with a QBO Web Connect file generated from a PDF statement.

What Is an OFX File?

An OFX file is the Open Financial Exchange format, a standard for exchanging financial data between banks and software. OFX is the base format upon which QBO is built; in fact, QBO is essentially an OFX file with QuickBooks-specific extensions.

Key points:

• OFX is supported by many banks for Web Connect downloads
• It includes transaction data but lacks the QuickBooks-specific auto-mapping enhancements found in QBO
• Compatible with QuickBooks Desktop and Online, though QuickBooks prefers QBO for automated imports
• Some banks, such as Chase and Bank of America, offer OFX for legacy systems or consumer accounts

When OFX files are provided, QuickBooks Online or Desktop can import them directly. However, for PDFs or CSV-only downloads, conversion to QBO is often the most efficient workflow.

CSV Files for QuickBooks Import

CSV (Comma-Separated Values) is a generic, spreadsheet-compatible format that QuickBooks can import, but it requires manual mapping.

Requirements and limitations:

• Required columns: Date, Description, Amount (Payee optional)
• No automatic transaction IDs or auto-matching to QuickBooks accounts
• Date formats must match QuickBooks regional settings
• Amounts must be positive for deposits, negative for withdrawals (or use separate Debit/Credit columns)

CSV is often the only option when:

• The bank does not provide OFX/QFX or QBO downloads
• Statements are converted from PDF to a spreadsheet via Bank Parser

While CSV gives flexibility for editing or cleaning transactions before import, it is prone to formatting errors and requires careful validation. For a complete walkthrough of the CSV import process in QuickBooks, see the QuickBooks CSV upload guide.

QBO vs CSV vs OFX: Comparison Table

What Data Is Preserved or Lost in Each Format?

PDF statements preserve the most data but cannot be imported directly into QuickBooks. CSV and QBO are importable but lose detail in the process. This table shows which fields survive each format.

Legend: ✓ = preserved, ✗ = lost, ~ = partial

This is why PDF-to-QBO conversion (rather than PDF-to-CSV) produces cleaner QuickBooks imports: QBO preserves normalized descriptions, transaction categories, and FITIDs that CSV loses entirely.

Which QuickBooks Import Format Should You Use?

The right format depends on what your bank provides and whether you need to edit transactions before import. Here is when each format is the correct choice.

Use QBO when:

• Your bank offers a QuickBooks Web Connect download (look for ".qbo" or ".qfx" in the export menu)
• You need auto-mapping and reconciliation with minimal manual steps
• Importing more than 90 days of history from a PDF statement (via PDF-to-QBO conversion)
• Accuracy is critical and you want FITID-based duplicate prevention
• You are importing large batches (hundreds of transactions per statement period)

Use CSV when:

• Your bank only exports CSV and QBO conversion is not needed
• You need to edit, filter, or clean transactions in Excel before import
• The import is a one-time small batch (under 100 transactions)
• You are importing to a non-standard account type that QBO does not recognize

Use PDF conversion when:

• Your bank provides PDF statements only — the most common case for older or business accounts
• You need historical transactions beyond 90 days (bank portals usually limit direct exports)
• The bank's online export feature is unavailable or broken
• You are consolidating multiple statement periods into a single QuickBooks import

For PDF statements, convert to QBO using Bank Parser's PDF to QBO converter to preserve transaction IDs and ensure clean reconciliation. Choose CSV output instead if you need to review the transactions in a spreadsheet first.

Banks frequently structure CSV, OFX, and PDF exports differently, which is why some bookkeeping teams use the Bank Parser workflow to normalize transaction formatting before import. The companion bank statement to Excel workflow is also useful for reviewing raw transaction data outside accounting software.

How to Convert Between Formats

Conversion between formats is often required for accurate imports:

PDF to QBO

Use Bank Parser to convert PDFs directly into QuickBooks-ready QBO files. Supports Chase, Wells Fargo, Bank of America, and Capital One.

PDF to CSV

Convert PDFs to spreadsheet-compatible CSV for manual cleaning before import via Bank Parser.

CSV to QBO

Use third-party utilities to wrap a CSV into QBO format if auto-mapping is desired.

OFX to QBO

Usually not necessary, as OFX imports directly, but conversion is possible when QuickBooks requires auto-mapping enhancements.

These conversions ensure that regardless of how the bank provides statements, QuickBooks can import them efficiently.

Common Format Errors When Importing into QuickBooks

Invalid Financial Institution ID (QBO)

Occurs when the FI identifier in the QBO does not match QuickBooks expectations.

Solution: Use a converter like Bank Parser that assigns correct IDs.

Date Format Mismatch (CSV)

QuickBooks may reject CSV if the date format does not match organization settings.

Solution: Standardize all dates to DD/MM/YYYY or MM/DD/YYYY depending on QuickBooks configuration.

Duplicate FITID (QBO)

QBO transaction IDs (FITID) must be unique; duplicates cause import errors.

Solution: Ensure each transaction has a unique FITID. Converters like Bank Parser handle this automatically.

Column Mapping Errors (CSV)

Missing or misnamed columns prevent import.

Solution: Confirm all required columns (Date, Description, Amount) are present and correctly named.

Encoding Issues (CSV)

Non-UTF-8 encoded files can result in garbled characters or rejected uploads.

Solution: Save CSV files in UTF-8 format before importing.

For errors that occur during or after the upload step itself — wrong transaction signs, missing rows, duplicate file warnings, unsupported format rejections — see the QuickBooks bank upload error fixes guide.

Frequently Asked Questions