QBO vs OFX vs QFX vs QIF vs CSV: Bank File Formats Explained

When you download transactions from online banking or convert a PDF statement, you are usually offered a list of formats with cryptic names: CSV, OFX, QFX, QBO, QIF. Picking the wrong one leads to rejected imports, duplicate transactions or a pile of manual clean-up. This guide explains what each format is, what it contains, which software accepts it, and how to choose.

Quick answer: which format for which software

You are importing into	Best format	Alternatives
QuickBooks Desktop	QBO (Web Connect)	None for bank registers in most versions
QuickBooks Online	QBO or QuickBooks-style CSV	OFX, QFX
Xero	OFX or Xero-style CSV	QIF, often QBO/QFX
Quicken (current versions)	QFX (Web Connect)	QIF for some account types and versions; CSV in some versions
Sage	CSV in the Sage template, or OFX	QIF in some products
FreeAgent, Wave, Zoho Books, MYOB and others	CSV or OFX (check the product's help)	QIF in some products
Excel, Google Sheets, analysis	Excel (.xlsx) or CSV
Databases and scripts	CSV or JSON

If you remember one rule: for QuickBooks Desktop use QBO; for everything else, OFX is the safest structured choice when it is accepted, and CSV is the universal fallback.

CSV: comma-separated values

What it is

A CSV file is a plain-text table. Each line is a row and columns are separated by commas (or semicolons in some locales). There is no official bank statement CSV standard; each bank and each accounting product defines its own columns.

What it contains

Whatever columns the creator chose, typically:

Date,Description,Amount
2026-03-02,Payroll - Northwind LLC,4250.00
2026-03-04,Rent - Elm Street Props,-1850.00

Some CSVs use separate Debit and Credit columns, add a running Balance, a Reference or Payee, or a Category.

Strengths

• Universally supported by spreadsheets, accounting software and scripts.
• Human-readable; easy to inspect and edit.
• Flexible: you can include whatever columns you need.

Weaknesses

• No standard layout. Every importer needs the columns mapped, and each program expects different columns.
• Ambiguous dates. 03/04/2026 can be 3 April or 4 March. The file does not say which.
• Sign conventions vary. Some files use negatives for money out, some use separate columns, some use DR/CR text.
• No unique transaction IDs, so software cannot reliably detect duplicates if the same file is imported twice.
• No account metadata such as the account number, currency or closing balance.
• Delimiter and encoding issues: descriptions containing commas need quoting; non-English characters need UTF-8.

When to use it

For analysis in Excel or Google Sheets, for QuickBooks Online or Xero when you want control over mapping, and for any software without OFX support. Our bank statement to CSV converter produces generic, QuickBooks and Xero layouts.

OFX: Open Financial Exchange

What it is

OFX is an open specification for exchanging financial data, created in the late 1990s by a group of companies including Microsoft, Intuit and CheckFree. It is used by banks to deliver downloadable transactions and by financial software to import them. Older versions (1.x) use an SGML-style syntax; later versions (2.x) are XML.

What it contains

An OFX file carries structured information about the account and each transaction:

• Account information: bank identifier, account number, account type, currency.
• Statement range: start and end dates.
• Transactions, each with a type (such as DEBIT, CREDIT, CHECK, ATM, POS, XFER, INT, FEE), the posting date, the amount, a unique transaction ID (FITID), a name or payee, an optional memo and an optional cheque number.
• Ledger balance and its date, and sometimes an available balance.

A simplified transaction looks like this:

<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260304
<TRNAMT>-1850.00
<FITID>20260304-0002
<NAME>Elm Street Props
<MEMO>Rent March
</STMTTRN>

Strengths

• Structured and unambiguous. Dates use a fixed format (YYYYMMDD), amounts are signed, and fields are labelled.
• Unique IDs. The FITID lets software recognise transactions it has already imported. See the FITID glossary entry.
• Account metadata ensures the file is linked to the right account.
• Balances allow the importing software to check the result.

Weaknesses

• Not human-friendly to edit.
• Implementations vary slightly between banks and programs, so a file that one program accepts may need adjustment for another.
• Fewer free tools to create OFX than CSV.

When to use it

Whenever your target software accepts it and you want reliable, duplicate-aware imports: Xero, many personal finance apps, and many accounting products. Our PDF to OFX converter creates OFX from statements. Read more in the OFX glossary entry.

QBO: QuickBooks Web Connect

What it is

QBO is Intuit's format for QuickBooks Web Connect. Technically, a QBO file is an OFX file with Intuit-specific additions, most importantly an institution identifier (the INTU.BID value) that tells QuickBooks which financial institution the data comes from.

Note the potential confusion: "QBO" also commonly abbreviates QuickBooks Online. In the context of file downloads, QBO almost always means the Web Connect file format.

What it contains

Everything an OFX file contains, plus the Intuit identifier. QuickBooks uses the identifier to associate the file with an institution it recognises.

Strengths

• The native way to import bank and card transactions into QuickBooks Desktop, which in most versions does not import CSV into bank registers.
• Accepted by QuickBooks Online as an upload format, with duplicate detection based on FITIDs.
• Lands in the bank feed review screen, where you match and categorise as with a live feed.

Weaknesses

• The institution identifier must be one QuickBooks accepts; otherwise QuickBooks Desktop may reject the file or show an institution error.
• Desktop's Web Connect import depends on the QuickBooks version being supported for online banking services. See what to do when QuickBooks Desktop bank feeds stop working.

When to use it

Always for QuickBooks Desktop; often for QuickBooks Online when you want feed-like behaviour. Our PDF to QBO converter lets you set the identifier, and our free CSV to QBO tool converts a CSV into QBO in your browser. The QBO glossary entry has more detail, and the QuickBooks import guide covers the steps.

QFX: Quicken Web Connect

What it is

QFX is Quicken's equivalent of QBO: an OFX file with Intuit-style institution information, intended for Quicken. Quicken was originally an Intuit product, which explains the shared heritage, although Quicken is now owned and developed separately.

Strengths and weaknesses

Like QBO, it is structured, carries unique IDs and is the preferred import route for current Quicken versions. Quicken may require the institution to be recognised. QuickBooks Desktop does not import QFX files.

When to use it

For Quicken. Our PDF to QFX converter and bank statement to Quicken pages cover the details. See also the QFX glossary entry.

QIF: Quicken Interchange Format

What it is

QIF is an older plain-text format introduced for Quicken. Each transaction is a block of lines, each starting with a single-letter code, and transactions are separated by a caret:

!Type:Bank
D03/04/2026
T-1850.00
PElm Street Props
MRent March
^

Common codes include D (date), T (amount), P (payee), M (memo), N (cheque number) and L (category).

Strengths

• Simple and readable.
• Supported by many personal finance programs and some accounting tools.
• Can carry categories, which OFX does not normally do.

Weaknesses

• No unique transaction IDs, so no reliable duplicate detection.
• Ambiguous dates: QIF dates follow regional formats and some programs use special year notations.
• Limited account metadata.
• Legacy status. Quicken has restricted QIF imports for some account types in some versions in favour of QFX; check what your version allows.

When to use it

When your software accepts QIF but not OFX, or when you need to carry categories into a personal finance program that reads them. Our bank statement to QIF converter produces QIF files, and the QIF glossary entry has more background.

Side-by-side comparison

Feature	CSV	OFX	QBO	QFX	QIF
Structure	Plain table	Tagged (SGML/XML)	OFX + Intuit ID	OFX + Intuit ID	Line codes
Standardised	No	Yes	Intuit-specific	Quicken-specific	De facto
Unique transaction IDs	No	Yes (FITID)	Yes	Yes	No
Account metadata	No	Yes	Yes	Yes	Minimal
Balances	Optional column	Yes	Yes	Yes	No
Unambiguous dates	No	Yes	Yes	Yes	No
Categories	Optional column	Not usually	Not usually	Not usually	Yes
Human-editable	Very easy	Hard	Hard	Hard	Fairly easy
QuickBooks Desktop	No (registers)	No	Yes	No	Not for bank registers
QuickBooks Online	Yes	Yes	Yes	Yes	No
Xero	Yes	Yes	Often	Often	Yes
Quicken	Some versions	Varies	No	Yes	Some account types

Which format does your bank offer?

Most online banking platforms offer a subset of these formats, and the labels vary. You may see "Microsoft Money" (an OFX variant), "Quicken (QFX)", "QuickBooks (QBO)" or "Web Connect", "Spreadsheet (CSV)" or "Comma delimited". Some banks only offer QBO and QFX to business accounts, and some charge for direct connections but not for file downloads.

Two practical points apply almost everywhere. First, downloads usually cover a limited history, so for older periods you will need the PDF statements. Second, the PDF statement is the only source with the bank's official opening and closing balances, which makes it the reference for checking any downloaded or converted file.

How to choose: decision guide

1. Are you importing into QuickBooks Desktop? Use QBO.
2. Does your software accept OFX (or QBO/QFX)? Prefer it for duplicate protection and unambiguous dates.
3. Do you need to edit the data before import, or analyse it? Use CSV or Excel, then convert to the import format afterwards if needed.
4. Is it a personal finance program that only reads QIF? Use QIF.
5. Still unsure? Export CSV in the target software's documented layout. It is the universal fallback.

Converting between formats

Common conversions include:

• PDF to any format: use a statement converter, which extracts the transactions and writes them in the format you choose. Our converter exports Excel, CSV, QBO, OFX, QIF, QuickBooks CSV and Xero CSV from the same verified data.
• CSV to QBO: useful when your bank offers only CSV but you use QuickBooks Desktop. Our free CSV to QBO converter runs in your browser without uploading the file.
• OFX to CSV: for analysis in Excel. Many tools and short scripts can do this because OFX is structured.
• QIF to OFX: for moving older Quicken data into newer software; desktop conversion tools exist for this.

Whatever the conversion, check the result: transaction count, total amount and date range should match the source.

Beyond files: JSON, APIs and open banking

File downloads are no longer the only way bank data moves. Increasingly, transactions travel through APIs.

Open banking and account aggregation. In the UK, the EU and a growing number of other markets, regulations and industry schemes let customers authorise third parties to read account data directly from the bank through secure APIs. Accounting software bank feeds often work this way. The data arrives as structured JSON rather than as a file, with fields similar to OFX: dates, amounts, descriptions, unique IDs and balances.

JSON exports. Developers and data teams often want statement data as JSON, which is easy to process in code and preserves types such as numbers and dates. Our bank statement to JSON converter produces a documented structure with statement metadata, balances and transactions.

Why files still matter. APIs cover current activity at supported banks. Files remain essential for history beyond the API's window, for banks without API access, for closed accounts, for statements supplied by third parties, and for any situation where the only source is a PDF. That is why converting statements into the formats above is still a daily task for many accountants, lenders and analysts.

Keeping a durable archive

If you are building an archive of bank data for the long term, think about formats that will still be readable in ten years:

• Keep the original PDF statements. They are the evidence and the most durable human-readable record.
• Keep a CSV or Excel copy of the transactions. Plain tables are readable by almost any future software.
• Use ISO dates (YYYY-MM-DD) and plain numbers in archived CSVs, which removes ambiguity for anyone reading them later.
• Avoid relying solely on proprietary formats such as QBO or QFX for archiving. They are excellent for importing but depend on specific programs.
• Name files consistently with the account, period and format, and store them together.

Our guide to how long to keep bank statements covers retention periods.

A brief history of bank file formats

The variety of formats makes more sense with a little history. QIF dates from the early days of personal finance software, when programs needed a simple way to exchange data. As online banking spread in the late 1990s, the industry developed OFX as a richer, standardised way for banks and software to exchange data, including over direct connections. Intuit then built its Web Connect formats (QBO for QuickBooks and QFX for Quicken) on top of OFX, adding the institution information its products use. CSV, meanwhile, never went away, because every spreadsheet can read it.

The result is the overlapping set of options you see in online banking today: the old (QIF), the standard (OFX), the program-specific (QBO and QFX) and the universal (CSV).

Common format problems and fixes

Problem	Format	Fix
Dates imported in the wrong month	CSV, QIF	Specify the date order during import, or use ISO dates (YYYY-MM-DD) in CSV
All transactions show as deposits	CSV	Use negative amounts for money out, or separate debit and credit columns
Duplicates after re-importing	CSV, QIF	Don't import overlapping periods; prefer OFX-family formats with FITIDs
QuickBooks Desktop rejects the file	QBO	Check the INTU.BID value and that your QuickBooks version supports Web Connect
Special characters garbled	CSV	Save as UTF-8
Descriptions split into extra columns	CSV	Quote fields that contain commas
Quicken refuses a QIF for a bank account	QIF	Use QFX instead, or check the version's QIF limitations

Frequently asked questions

Is QBO the same as OFX?

A QBO file is built on the OFX structure with additional Intuit information, mainly an institution identifier QuickBooks uses. Many programs that read OFX can read QBO, but QuickBooks Desktop specifically expects the QBO variant.

What is the difference between QFX and QBO?

Both are OFX-based Intuit-style Web Connect formats. QFX is intended for Quicken and QBO for QuickBooks. QuickBooks Desktop does not import QFX files.

Which is better for Xero, CSV or OFX?

OFX is generally more reliable because dates and amounts are unambiguous and each transaction has a unique ID. CSV is useful when your bank only offers CSV or when you need to edit data first. See our Xero import guide.

Can I open an OFX or QBO file in Excel?

Not directly in a useful way, because they are tagged text, not tables. Convert them to CSV first, or export CSV alongside the OFX when converting statements.

Is QIF still supported?

Many programs still read QIF, but it is considered a legacy format. Quicken has limited QIF imports for some account types in some versions. Prefer QFX or OFX when available.

What does FITID mean?

FITID is the financial institution transaction ID: a unique identifier for each transaction in OFX-family files. Importing software uses it to avoid duplicates.

Summary

CSV is universal but ambiguous; OFX is structured and duplicate-aware; QBO and QFX are OFX variants for QuickBooks and Quicken; QIF is a simple legacy option. Match the format to the software you are importing into, prefer OFX-family formats when accepted, and keep CSV or Excel for analysis. If your source is a PDF, convert once and export to any of them from the same verified data.