Bank Statement Formats Explained: PDF, CSV, OFX, QFX, and QBO

When you download transaction data from your bank, the file you receive could be in any of several formats: PDF, CSV, OFX, QFX, or QBO. Each format has a specific purpose, distinct strengths, and notable limitations—and picking the wrong one can turn a simple import into a frustrating ordeal.

This guide breaks down every major bank statement format, explains when to use each one, and helps you decide which format best fits your accounting software and workflow. We'll also cover how to convert between formats when your bank doesn't offer the one you need.

Overview of Bank Statement Formats

Banks and financial institutions use several file formats to share transaction data with customers. These formats evolved over decades to serve different purposes—from human-readable documents to machine-readable data files optimized for accounting software.

Here's a quick reference before we dive into the details:

Let's explore each format in depth.

PDF Format

PDF (Portable Document Format) is the most common format for bank statements. When you log into your online banking and download a statement, it's almost always a PDF. It's also the format your bank uses for paper statements that arrive in the mail—just the digital version.

Pros

• Universal availability. Every bank provides PDF statements. It's the one format you can always count on having access to, regardless of your institution.
• Human-readable. PDFs look exactly like a printed statement with clean formatting, logos, headers, and organized tables. They're easy to read and review visually.
• Official records. PDF statements often carry the same legal weight as paper statements. They're suitable for audits, loan applications, visa applications, and legal proceedings.
• Historical access. Banks typically offer PDF statements going back several years through online banking, making them the best source for historical transaction data.
• Security. Many bank PDFs are password-protected, adding a layer of security to sensitive financial data.

Cons

• Not machine-readable. This is the fundamental limitation. PDF is a visual format—it describes where to place text on a page, not what the data means. There are no structured fields, no defined columns, and no consistent schema.
• Difficult to extract data from. Copying and pasting from a PDF usually produces mangled results: columns merge, numbers lose their decimal points, and multi-page tables break apart.
• Can't be imported directly. No major accounting software (QuickBooks, Xero, FreshBooks, Wave) accepts PDF files as a bank import format. You always need to convert first.
• Layout varies wildly. Every bank designs their PDF differently. Chase, Bank of America, TD, and HSBC all use different column orders, date formats, and table structures. This makes automation without AI nearly impossible.

When to Use PDF

Use PDF when you need an official record for documentation purposes, when you're reviewing transactions visually, or when it's the only format available from your bank. For accounting imports, you'll need to convert the PDF to CSV or another structured format first.

CSV Format

CSV (Comma-Separated Values) is the Swiss Army knife of data formats. It's a plain text file where each row represents a transaction and each value is separated by a comma. Any spreadsheet application and virtually every accounting platform can read CSV files.

Pros

• Universal compatibility. CSV is accepted by every major accounting platform: QuickBooks, Xero, FreshBooks, Wave, Sage, MYOB, and others. It's also readable by Excel, Google Sheets, and any text editor.
• Easy to edit. Because it's plain text, you can open a CSV in Excel or Google Sheets, fix errors, add categories, remove duplicates, or restructure columns before importing.
• Flexible structure. CSV doesn't enforce a specific schema. Whether your bank uses "Date, Description, Amount" or "Transaction Date, Payee, Debit, Credit," CSV can represent either layout.
• Lightweight. CSV files are tiny compared to other formats. A year of transactions might be 50 KB—easy to email, store, or upload.
• Works with scripts and tools. Developers, accountants, and data analysts can process CSV files with Python, R, Excel formulas, or command-line tools. It's the most automation-friendly format.

Cons

• No standard schema. Every bank formats their CSV differently. Column names, date formats, sign conventions (negative vs. parentheses for debits), and encoding all vary. You may need to reformat the file for your specific accounting software.
• Not always available. Many banks don't offer CSV downloads at all. You can download a PDF statement, but getting CSV often requires navigating to a separate "activity export" or "transaction download" section—if it exists.
• No metadata. CSV files contain raw transaction data only. There's no account number, bank name, currency indicator, or opening/closing balance embedded in the format itself.
• Encoding issues. Special characters in merchant names (accents, ampersands, non-Latin characters) can break if the CSV isn't saved with proper UTF-8 encoding.

When to Use CSV

CSV is the best general-purpose format for importing transactions into accounting software. If your bank offers a CSV download, use it. If your bank only provides PDFs, convert them to CSV using a tool like StatementKit's bank statement to CSV converter. It's the most widely supported and flexible option available.

OFX — Open Financial Exchange

OFX (Open Financial Exchange) is an XML-based format specifically designed for exchanging financial data between banks, consumers, and financial software. It was created in the late 1990s as a collaboration between Microsoft, Intuit, and CheckFree.

Pros

• Standardized structure. Unlike CSV, OFX has a defined schema. Every OFX file uses the same tags for dates, amounts, transaction types, and account information. This makes automated processing highly reliable.
• Rich metadata. OFX files include the bank's routing number, account number, account type (checking, savings, credit card), currency, and statement date range. This context helps accounting software set up the import correctly.
• Transaction IDs. Each transaction in an OFX file has a unique identifier (FITID), which enables duplicate detection. If you import the same OFX file twice, good accounting software will recognize and skip the duplicates.
• Broad software support. Most desktop accounting applications support OFX, including Quicken, QuickBooks Desktop, Microsoft Money (discontinued but still used), GnuCash, and Moneydance.
• Transaction type tags. OFX distinguishes between debits, credits, fees, interest payments, ATM withdrawals, and other transaction types—information that CSV can't represent without custom conventions.

Cons

• Limited bank availability. Fewer banks offer OFX downloads compared to PDF or CSV. It's more common at large U.S. and Canadian banks, but many international institutions don't support it.
• Not human-readable. OFX files are XML documents filled with tags like <STMTTRN> and <TRNAMT>. Opening one in a text editor shows raw markup that's difficult to scan visually.
• Hard to edit manually. If you need to fix a date or remove a transaction, editing OFX in a text editor requires understanding its XML structure. One misplaced tag can corrupt the entire file.
• Version fragmentation. OFX has gone through multiple versions (1.x used SGML, 2.x uses XML). Some software only supports specific versions, leading to compatibility headaches.

When to Use OFX

Use OFX when your accounting software supports it and your bank offers it as a download option. The built-in duplicate detection and standardized structure make it an excellent choice for regular, repeatable imports—especially with desktop software like Quicken or GnuCash.

QFX — Quicken Financial Exchange

QFX is Intuit's proprietary variant of OFX, designed specifically for importing transactions into Quicken. If you've ever downloaded transactions from your bank "for Quicken," you received a QFX file.

Pros

• Optimized for Quicken. QFX files open directly in Quicken with a double-click. The import process is seamless—Quicken automatically matches the file to the correct account and runs duplicate detection.
• Includes OFX benefits. Since QFX is based on OFX, it carries the same standardized structure, transaction IDs, and rich metadata.
• Widely offered by U.S. banks. Because Quicken has such a large user base (especially in the U.S.), many banks offer QFX downloads as a dedicated export option alongside CSV and PDF.

Cons

• Proprietary format. QFX is controlled by Intuit. While technically similar to OFX, it includes Intuit-specific headers that make it less interoperable with non-Quicken software.
• Quicken-only (mostly). While some other applications can read QFX files by treating them as OFX, the format is primarily designed for and tested with Quicken. Import into other software may produce inconsistent results.
• Requires Quicken subscription. Quicken has moved to a subscription model, so you need an active subscription to use QFX import. Once your subscription expires, the import feature stops working.
• No manual editing. Like OFX, QFX files are XML-based and difficult to edit by hand. If a transaction needs correction, it's easier to fix it after import in Quicken rather than editing the file.

When to Use QFX

QFX is the right choice if you use Quicken as your primary personal finance tool and your bank offers QFX downloads. For any other software, CSV or OFX is a better option.

QBO — QuickBooks Format

QBO is another Intuit-proprietary format, this time designed for QuickBooks (both Desktop and, historically, Online). Like QFX, it's built on the OFX specification but tailored for the QuickBooks ecosystem.

Pros

• Optimized for QuickBooks. QBO files import smoothly into QuickBooks Desktop with minimal manual configuration. The format maps directly to QuickBooks' internal data model.
• Duplicate detection. Like OFX and QFX, QBO files include transaction IDs that QuickBooks uses to prevent duplicate imports.
• Account matching. QBO files contain account identifiers that help QuickBooks map the import to the correct bank account in your chart of accounts.

Cons

• Declining relevance. QuickBooks Online primarily relies on automatic bank feeds (via Plaid) and CSV import. QBO file import is more relevant for QuickBooks Desktop users.
• Proprietary and restrictive. QBO is controlled by Intuit and not widely supported outside the QuickBooks ecosystem.
• Confusing naming. The .qbo file extension is easily confused with "QBO" as an abbreviation for QuickBooks Online. They're different things: .qbo is a file format; QuickBooks Online is a cloud application.
• Limited bank support. Fewer banks offer dedicated QBO downloads compared to CSV or even OFX. You may need to convert from another format.

When to Use QBO

Use QBO if you're running QuickBooks Desktop and your bank offers QBO downloads. For QuickBooks Online users, CSV import is typically the more practical option, especially when combined with a PDF-to-CSV converter.

Format Comparison Table

Here's a detailed comparison of all five formats across the dimensions that matter most for everyday accounting:

Which Format Should You Use?

The best format depends on two factors: what your bank offers and what your accounting software accepts. Here's a quick decision guide organized by software:

QuickBooks Online

QuickBooks Online supports CSV, OFX, and QFX imports. CSV is the most practical choice because it's the easiest to review and edit before importing. If you're getting bank data from PDF statements, convert them to CSV using StatementKit and import directly.

QuickBooks Desktop

QuickBooks Desktop works best with QBO files (its native format) or OFX. If your bank doesn't provide either, CSV import is available through the "Web Connect" feature or third-party add-ons.

Quicken

Quicken is optimized for QFX files. If your bank offers QFX downloads, use them for the smoothest experience. OFX files also work well. CSV import in Quicken is functional but requires more manual column mapping.

Xero

Xero accepts CSV and OFX. CSV is recommended because Xero has a flexible column mapper that handles various CSV layouts. OFX works well too, but CSV gives you more control over the data before import.

FreshBooks

FreshBooks supports CSV, OFX, and QFX for bank transaction import. CSV is the most commonly used because it's the format most users have access to. See our detailed guide on importing bank statements into FreshBooks.

Wave

Wave supports CSV and OFX. Since Wave is free accounting software popular with freelancers, CSV import is the most accessible option.

Sage / MYOB

Both platforms accept CSV and OFX. CSV is the safer choice due to wider format tolerance in their import tools.

Excel / Google Sheets

For spreadsheet-based bookkeeping or financial analysis, CSV is the obvious choice. You can also use StatementKit's bank statement to Excel converter to get an XLSX file that opens directly in Excel with proper column formatting.

How to Convert Between Formats

In an ideal world, your bank provides the exact format your software needs. In reality, you'll often need to convert. Here are the most common conversion scenarios:

PDF to CSV

This is by far the most common conversion. Banks always provide PDFs, but accounting software needs structured data. StatementKit converts any bank statement PDF to CSV in seconds using AI-powered extraction. The tool handles different bank layouts, multi-page statements, and various date and currency formats automatically.

PDF to Excel

If you want to review and manipulate transaction data in a spreadsheet before importing into accounting software, convert to Excel first. StatementKit also offers PDF to Excel conversion that preserves column structure and data types.

CSV to OFX/QFX/QBO

Some users need to go from CSV to a financial-specific format. Third-party tools and online converters can wrap CSV data in OFX, QFX, or QBO structure. This adds transaction IDs and account metadata that the original CSV lacked. However, for most users, importing CSV directly is simpler.

OFX to CSV

If you have an OFX file but your software only takes CSV (or you want to view the data in Excel), you can convert OFX to CSV using free online tools or scripting libraries. The conversion strips out XML tags and presents the transaction data in a flat table format.

The Practical Reality

For most small businesses and freelancers, the workflow is simple: your bank gives you a PDF, you convert it to CSV, and you import the CSV into your accounting software. The PDF-to-CSV conversion is the critical step, and using an AI-powered tool makes it reliable and fast.

Try StatementKit free to convert your first bank statement in under a minute.

Frequently Asked Questions

What is the difference between OFX and QFX?

OFX (Open Financial Exchange) is an open standard for exchanging financial data. QFX (Quicken Financial Exchange) is Intuit's proprietary version of OFX with additional headers specifically for Quicken. They share the same underlying structure, but QFX files include Intuit-specific metadata that makes them work seamlessly with Quicken while potentially causing issues in other software.

Can I open a QBO file without QuickBooks?

Technically, yes. QBO files are text-based XML files, so you can open them in any text editor. However, the data won't be easy to read in raw form. Some free accounting tools like GnuCash can import QBO files by treating them as OFX. For a human-readable view, you're better off converting to CSV first.

Why doesn't my bank offer CSV downloads?

Some banks only provide PDF statements through their online banking portal. They may offer CSV or OFX downloads through a separate "transaction export" or "download activity" feature, often found in account settings or transaction history pages rather than the statements section. If your bank truly doesn't offer any structured format, converting the PDF to CSV with StatementKit is the fastest solution.

Which format has the best data quality?

OFX and its derivatives (QFX, QBO) have the best structured data quality because they follow a standardized schema with typed fields for dates, amounts, and transaction types. CSV quality depends entirely on the bank's export implementation. PDF has the richest visual information but the poorest data extractability.

Is there a universal format that works everywhere?

CSV is the closest thing to a universal format. While it lacks the standardized schema of OFX, its simplicity and near-universal software support make it the safest default choice. Every major accounting platform accepts CSV, and the format is easy to inspect and fix if issues arise.

Do all formats preserve the same transaction details?

No. PDF statements often contain the most detail: full merchant names, reference numbers, running balances, and sometimes even merchant categories. OFX/QFX/QBO preserve structured fields like transaction IDs and types. CSV contains whatever the bank chooses to include. When converting from PDF to CSV, an AI tool like StatementKit extracts as much detail as the PDF contains.