How to Import a Wells Fargo Statement into QuickBooks (and Xero)

You have a Wells Fargo PDF statement and you need it inside QuickBooks. Maybe bank feeds went stale, the account is closed, you're onboarding a client mid-year, or you tried QuickBooks' built-in PDF upload and got mediocre results. Whatever the reason: you need a way to turn that PDF into a clean import that QuickBooks (or Xero) actually accepts.

This is the workflow. Four steps. Same flow handles Xero - just swap the export format. The hard part is choosing the right format and knowing the Wells Fargo-specific quirks (paired Deposits/Credits and Withdrawals/Debits columns, the Daily Balance Summary section, the discontinued OFX Direct Connect) that confuse generic conversion tools.

Want to use this guide on your blog? Copy this embed code:

---

Why You Can't Just Upload the WF PDF

QuickBooks Online accepts file uploads in .qbo, .ofx, .qfx, and .csv formats. It does not accept PDF for bank imports - the bank-feed PDF upload feature is for occasional gap-filling on connected accounts and silently degrades to OCR with mixed results.

Xero supports .ofx, .csv, .qbo, .qfx, and .qif. Same constraint: no PDF.

So the workflow starts with a format conversion. You can do this manually (paste-and-pray into a spreadsheet, then format and save as CSV) or with a bank statement converter that knows the structure of a Wells Fargo statement. The converter approach is faster and avoids the column-mapping step inside QuickBooks because .qbo files include the column metadata.

For format details, see our QBO vs CSV vs OFX guide - the format decision tree at the top covers every accounting platform in one glance.

---

Step 1: Download the Wells Fargo PDF

1. Sign in at wellsfargo.com
2. Open the account you need
3. Go to Statements & Documents
4. Pick the statement period
5. Click Download PDF

Wells Fargo keeps up to 7 years of statements available this way. Some account types may have shorter retention; check the statement date list before assuming.

A note on Wells Fargo's CSV download: Wells Fargo offers a direct CSV export from the Account Activity view (they label it "Comma Delimited"). It works for recent activity but has limits - see the Wells Fargo to Excel guide for the trade-offs.

---

Step 2: Upload to PDFSub

Open PDFSub's Bank Statement Converter. Drag the Wells Fargo PDF into the drop zone or click to browse.

PDFSub recognizes the Wells Fargo template automatically. For digital PDFs (anything you downloaded directly from wellsfargo.com, not a scanned printout), the extraction runs entirely in your browser through PDFSub's Tier 1 engine - the file never leaves your device. That matters when you're working with client data under an engagement letter.

PDFSub shows you the parsed transactions before you commit to an export, so you can spot-check a few rows against the original PDF.

Wells Fargo-specific handling that PDFSub does automatically:

• The paired Deposits / Credits and Withdrawals / Debits columns are mapped to a single signed amount. Generic tools that expect a "Withdrawals/Deposits" single-column layout misread WF's paired headers.
• The Daily Balance Summary section at the end of the statement is excluded from the transaction list (it's a summary, not transactions). Tools that ignore section boundaries import these as duplicate transactions.
• Check transactions in the Checks Paid section are preserved with check numbers as a reference field.
• Multi-line transaction descriptions (e.g., merchant name on one line, location and reference on the next) are joined into one description field, not split into separate rows.
• Wells Fargo discontinued OFX Direct Connect for personal accounts in 2018 - you can't pull data via QuickBooks' direct connection anymore for many account types. The PDF -> PDFSub -> .QBO workflow is the reliable replacement.

---

Step 3: Choose the Right Export Format

Once the data is extracted, pick the format that matches where the data is going:

Destination	Format	Why
QuickBooks Online	.qbo	Native format, no column mapping, automatic duplicate detection
QuickBooks Desktop	.qbo or .iif	QBO via Web Connect, IIF for batch imports
Xero	.ofx	Preferred over CSV - includes account metadata and duplicate IDs
Sage	.csv or .ofx	OFX preferred when supported
Wave	.csv or .ofx	Either works; OFX gets you duplicate detection
FreshBooks	.csv	Only supported import format
Quicken	.qfx or .qif	QFX for modern Quicken, QIF for older versions

For the rest of this guide, we'll use .qbo and .ofx. Click Download in PDFSub and save the file somewhere you can find it again.

---

Step 4a: Import the .QBO into QuickBooks Online

1. In QuickBooks, go to Banking (or Transactions -> Bank transactions)
2. Click Link account in the top right
3. Choose Upload from file at the bottom of the dialog
4. Drag the .qbo file in (or click to browse)
5. Select the QuickBooks account this statement belongs to
6. Confirm the date range and click Next
7. Review the parsed transactions - they appear in the For Review tab

That's it. Because .qbo is QuickBooks' native format, you skip the column-mapping step that CSV imports force you through. The file includes FITID (Financial Institution Transaction ID) values for every transaction, so if you accidentally re-import the same statement, QuickBooks silently skips the duplicates instead of doubling everything.

File limits to know:

• QuickBooks Online caps uploads at 350 KB per file and 1,000 transactions per import
• Most monthly WF statements fall under this. For business accounts with high transaction volume or year-to-date imports, split by month

---

Step 4b: Import the .OFX into Xero (Same Flow)

If you're working in Xero instead of QuickBooks, the only thing that changes is the file format and the menu path:

1. Go back to PDFSub and export as .ofx instead of .qbo
2. In Xero, navigate to Accounting -> Bank accounts
3. Click on the relevant bank account
4. Click Manage account -> Import a statement
5. Drag in the .ofx file
6. Xero detects the format and parses the transactions
7. Review and confirm

Xero, like QuickBooks, recognizes the OFX duplicate-detection IDs. Re-importing the same file is safe.

---

Common Errors and Fixes

"File could not be processed" in QuickBooks. Usually means the file is over 350 KB or contains more than 1,000 transactions. Split the statement into smaller chunks (one month at a time) and re-import.

Duplicate transactions appearing. If duplicates show up, you probably imported a .csv file (no duplicate detection) instead of .qbo. Re-export from PDFSub as .qbo and use that.

Daily Balance Summary rows imported as transactions. This is a classic generic-tool failure on Wells Fargo statements. PDFSub treats the DAILY BALANCE SUMMARY section as metadata, not transactions. If you're seeing balance-summary rows in your import, you may be using a different tool that doesn't recognize the section header.

Missing column totals. Wells Fargo statements include "Total Deposits/Credits" and "Total Withdrawals/Debits" lines at the bottom of each section. These are summaries, not transactions, and PDFSub excludes them. If your output has fewer rows than expected, count the actual transactions on the PDF (excluding the total lines) before assuming a parse error.

Check numbers missing. WF lists checks paid with the check number. PDFSub preserves these in a reference field. If you don't see them in your import, your destination software may not be displaying the reference column - check the column visibility settings.

Different bank than Wells Fargo? PDFSub recognizes 20,000+ bank templates. The same four-step workflow applies. For format-by-software guidance, see the QBO vs CSV vs OFX decision tree. For a software-agnostic primer on bank statement imports into QuickBooks, see How to Import Bank Statements into QuickBooks Online.

---

When You Already Have WF's Native CSV Export (Limited History)

Wells Fargo offers a direct "Comma Delimited" download inside the Account Activity view for accounts that are still open. It works for quick, recent data but not for historical or audit work:

• Limited history (typically the last 18 months for checking and savings; 90 days for credit cards)
• Transaction feed only - no opening balance, closing balance, fee summary, or daily balance table
• "Comma Delimited" format requires column mapping when imported into QuickBooks; loses the duplicate-detection that QBO/OFX provides

For ongoing month-to-month bookkeeping the native CSV is fine. For audit, tax prep, or historical onboarding, you need the PDF -> PDFSub -> QBO workflow above. If you also need to extract WF data into Excel for analysis (not import), see our Wells Fargo to Excel guide.

---

Summary

1. Download the Wells Fargo PDF from wellsfargo.com (up to 7 years)
2. Upload it to PDFSub's Bank Statement Converter
3. Export as .qbo (QuickBooks) or .ofx (Xero, Sage, Wave)
4. Banking -> Upload from file -> done. No column mapping, automatic duplicate detection

The whole workflow takes about 90 seconds per statement once you've done it once. Paired Deposits/Credits and Withdrawals/Debits columns, Daily Balance Summary, Checks Paid section - all auto-handled.