The three common choices
CSV is universal, OFX is a structured financial format, and QBO is QuickBooks' Web Connect variant. The best choice depends on whether you need manual review or a supported structured import.
- CSV is easiest to inspect, edit, deduplicate, and map before import.
- OFX carries structured financial fields but still requires account and sign review.
- QBO is an OFX-based QuickBooks Web Connect file and should match the destination account and date range.
Decision rule
Use Excel or CSV when the client data needs review, cleanup, or mapping. Use QBO/OFX when the transaction structure is already clean and the goal is a faster QuickBooks import.
Keep the source statement as the control
The PDF statement remains the source record. Before import, compare the converted period, opening balance, closing balance, transaction count, and obvious statement totals with the source.
A successful file import does not prove that every transaction is correct. Reconcile the imported activity to the statement before treating the accounting period as complete.
Review a small sample before importing the full period
Inspect representative rows rather than only the first transaction. Include a deposit, a withdrawal, a fee, a long wrapped description, and a transaction near a page break when those patterns exist.
For each sample row, compare the date, description, amount, debit or credit direction, and running balance with the PDF. Remove statement headers and summary totals if they were incorrectly represented as transactions.
Use a controlled import order
Import into a test or review workflow first when the file covers a new bank layout or account type. Confirm the destination account, date range, opening state, duplicate handling, and currency before importing additional months.
Keep a record of the source PDF, converted file, review date, reviewer, and any corrections. That record makes repeat processing easier and supports a consistent bookkeeping control process.
Checklist
- Destination QuickBooks account confirmed
- Statement period and currency confirmed
- Opening and closing balances checked against the PDF
- Representative deposit, withdrawal, fee, and wrapped-description rows reviewed
- Debit and credit signs confirmed
- Repeated headers and summary rows excluded
- Duplicate transaction risk checked before import
- Converted file saved with the source statement and review record
- Imported activity reconciled to the statement
Reference table
| Format | Best for | Tradeoff |
|---|---|---|
| CSV | Flexible imports and cleanup | Requires column mapping |
| OFX | Structured financial data | Destination support varies |
| QBO | QuickBooks Web Connect workflows | Needs careful account matching |
FAQ
Can QuickBooks import PDF statements directly?
Some current QuickBooks Online regions can accept eligible PDF or image statements, while other regional guidance and QuickBooks Desktop use converted transaction files. Check current Intuit support, then choose QBO/OFX or CSV when you need reusable, explicitly reviewed output.
Which format should a bookkeeper choose?
Choose QBO/OFX for cleaner QuickBooks imports and CSV when you need spreadsheet review or custom mapping before import.
Does a successful QBO import prove the data is correct?
No. A file can import successfully while still containing a missing row, duplicate, incorrect sign, or wrong account mapping. Reconcile the imported activity to the source statement.
How should I test a new bank statement layout?
Review a representative sample of transaction types and import one statement period into a controlled workflow before processing additional months.