There is no longer one universal answer for PDF bank statements. Current US QuickBooks Online guidance allows eligible users to upload an English-language PDF or image for extraction and side-by-side review. Current UK guidance still directs PDF users to convert the statement before import, and QuickBooks Desktop documents .qbo for Web Connect bank transactions.
Download a bank-provided transaction file when it covers the required period and account. For PDF-only history, client-supplied statements, scanned documents, or workflows that need a reusable review file, convert the PDF into reviewed rows before choosing QBO/OFX or CSV.
This guide separates product support from accounting control: how to convert a PDF for QuickBooks, which format to choose, and what to verify before reconciliation. If you work in Xero instead, see the companion guide on importing bank statements into Xero.
Choose the current import path for your QuickBooks product
Product support changes over time and differs by country. Confirm the current Intuit instructions for the destination company file and account instead of assuming that every QuickBooks product accepts the same files.
Current documented routes include:
- PDF or image — available in current US QuickBooks Online guidance for eligible English-language statements, with extracted fields shown for review.
- QBO, QFX, or OFX — structured transaction files supported in documented QuickBooks Online upload routes; QuickBooks Desktop Web Connect specifically documents .qbo.
- CSV — a mapped transaction list with Date, Description, and Amount, or separate Credit and Debit columns.
- Excel — useful as a human review and cleanup layer before saving or mapping bank transactions to a supported destination format.
File acceptance does not prove accounting accuracy. The route should preserve enough structure to verify the period, account, signs, balances, and duplicate risk against the PDF.
Method 1: QBO/OFX import — structured transaction files
QBO/OFX is useful when the destination supports a structured financial file and the reviewed account fields match the destination account.
Step 1: Convert and review the PDF. BankScanPro prepares QBO/OFX output from reviewed transaction rows. Compare dates, descriptions, amounts, signs, and available balances with the source before generating the file.
Step 2 (QuickBooks Online): Use the current manual upload flow. Select the destination bank or credit-card account, upload a supported file, and review the mapped transactions before accepting them. Menu labels may differ by product and country.
Step 2 (QuickBooks Desktop): Use Web Connect with .qbo. Current Intuit Desktop guidance identifies .qbo as the bank transaction format and requires an Intuit Account sign-in. Back up the company file before importing because imports cannot simply be undone.
Step 3: Review and reconcile. Match or categorize imported activity according to the product workflow, then reconcile the imported period to the source statement. Keep the PDF and converted file with the review record.
Method 2: CSV import — when to use it and the exact column format QuickBooks needs
CSV is more widely available than OFX but requires more setup. If your converter only outputs CSV, or if you need to edit the transaction data before importing, CSV is the practical choice.
QuickBooks Online CSV requirements: Current US guidance accepts a three-column layout — Date, Description, and Amount — or a four-column layout with separate Credit and Debit fields. Keep every date in one consistent recognized format and leave zero-only amount cells blank where the current instructions require it.
Current US guidance also lists a 350 KB transaction-list limit and up to 1,000 lines per upload. Recheck those limits before a large import, then shorten the date range when needed.
QuickBooks Desktop: Do not assume that the Online CSV bank transaction flow applies to Desktop. Current Desktop documentation identifies .qbo for Web Connect bank data. Other spreadsheet import capabilities vary by data type and version.
The main risk with CSV imports is column mismatch — importing with the wrong date format, or a debit/credit column in the wrong sign convention, can produce transactions with incorrect amounts. Always verify a few transactions against the original statement after the import completes.
Method 3: Excel review — prepare data before the supported import route
Excel is the strongest review format when transaction rows need filtering, annotations, formulas, sign correction, or duplicate checks before import. It should not be treated as a universal bank transaction upload format across QuickBooks products.
Use the reviewed workbook to produce a destination-compatible CSV or structured file. Preserve an unchanged copy so corrections remain traceable to the source PDF.
For one-off imports that need cleanup, Excel reduces mapping risk. For repeatable, already-reviewed workflows, QBO/OFX or CSV is easier to standardize.
QuickBooks Online vs. QuickBooks Desktop: import differences
The two versions of QuickBooks have different import interfaces and slightly different file support. The key differences:
- QuickBooks Online: Current documented file support and direct statement extraction vary by country and product version.
- QuickBooks Desktop: Current bank-data guidance identifies .qbo as the Web Connect file and requires an Intuit Account sign-in.
- Mapping: CSV requires field mapping; structured files carry more transaction metadata but still need account and period checks.
- Recovery: Back up Desktop company data and preserve source files before import. Do not rely on duplicate detection as an undo mechanism.
Common import errors and how to fix them
"File format not recognised" — confirm that the file type is supported by the exact product and region. Desktop Web Connect expects .qbo; Online support can differ. Re-export only after confirming the destination requirement.
"No new transactions found" — QuickBooks has either already imported these transactions (duplicate detection triggered) or the date range in the file overlaps entirely with an existing import. Check the register for the account and compare the date range in your import file.
Transactions imported with wrong amounts — usually a CSV sign convention issue. If debits appear as credits or vice versa, check whether your CSV uses a single amount column (debits as negative) or separate debit/credit columns, and re-map accordingly.
Date format errors in CSV — use one recognized date format throughout the file and compare several imported dates with the statement before accepting the batch.
Connected-feed overlap — compare the manual import period with transactions already downloaded by the bank feed. Resolve overlap in a controlled copy or with an accountant instead of disconnecting a production feed without a recovery plan.
How to verify your import is accurate before reconciling
An import that completes without errors is not the same as an import that is accurate. Even when QuickBooks Online provides side-by-side PDF extraction review, the user remains responsible for checking the period and rows before reconciliation begins.
Check the transaction count. Count the transactions in the original PDF statement and compare to the count imported. A mismatch means at least one transaction was dropped or duplicated.
Check the period totals. Sum all imported debits and credits for the period. Compare to the total debits and credits shown on the bank statement. Any discrepancy points to an amount error in a specific transaction.
Check the closing balance. Opening balance + total credits − total debits should equal closing balance for a standard bank account. BankScanPro provides balance and transaction review signals, but the user should still compare the output with the statement before downstream use.
Catching a data error before reconciliation is straightforward. Discovering it mid-reconciliation — when the difference has been distributed across dozens of matched transactions — takes considerably longer to unwind.
Current Intuit sources
- QuickBooks Online manual upload guidance — current US statement and transaction-list support.
- QuickBooks Desktop import guidance — current .qbo Web Connect requirement.
- QuickBooks UK PDF conversion guidance — evidence that availability differs by region.
Frequently asked questions
Can I import a PDF bank statement directly into QuickBooks?
It depends on the QuickBooks product and region. Current US QuickBooks Online guidance allows eligible English-language PDF or image statement uploads, while current UK guidance still directs users to convert PDFs before import. QuickBooks Desktop Web Connect uses .qbo files. Check the current Intuit instructions for the destination account before importing.
When should I choose QBO/OFX instead of CSV?
Choose QBO/OFX when the destination supports a structured financial file and the account details are confirmed. Choose CSV when you need to inspect, edit, or map a three- or four-column transaction list before upload. Neither route removes the need to check the imported rows against the statement.
Does this work with QuickBooks Online and QuickBooks Desktop?
Yes, but the routes differ. Current QuickBooks Online file support depends on country and product version. QuickBooks Desktop documents .qbo as its Web Connect bank transaction format. BankScanPro provides QBO/OFX, CSV, and Excel outputs so you can select and review the route supported by the destination.
How many months of statements can I import at once?
Import limits vary. Current US QuickBooks Online guidance lists a 350 KB transaction-list file limit and up to 1,000 lines per upload. Recheck the current guidance, then use shorter date ranges when needed. Period-by-period imports also make duplicate and reconciliation checks easier.
Will QuickBooks create duplicates if I import a statement I've already reconciled?
Duplicate handling is not a substitute for review. Check the destination register, connected bank-feed coverage, prior manual imports, and statement date range before upload. After import, compare transaction count and period totals with the source statement before reconciling.
What if my bank isn't supported?
Browse BankScanPro's bank directory for named guides across the US, UK, Canada, Australia, and Europe. If your bank is not listed, you can test the statement layout with the free allowance. Review extracted dates, descriptions, amounts, and balances against the source before importing the resulting file.