Convert Wells Fargo PDF bank statement to QuickBooks Desktop

Wells Fargo provides statements for personal and business checking, savings and credit card accounts in US dollars, in English and in Spanish, as single-account and combined statements. The reviewed statements include Business Choice Checking, Initiate Business Checking, College Checking, Business Market Rate Savings, a combined statement of accounts, a Spanish-language business checking statement, an Active Cash Visa Signature card page and one scanned statement.

Countries: United States
Supported statement formats: PDF
Supported destinations: QuickBooks Desktop, QuickBooks Online, Quicken, Xero, CSV/Excel

Wells Fargo PDF statement details

The following details were checked against Wells Fargo statements from 2019 to 2025: Business Choice Checking, Initiate Business Checking, College Checking and Business Market Rate Savings statements, a combined statement of accounts with a checking and a savings account, a Spanish-language Initiate Business Checking statement, one Active Cash Visa Signature card page, and one business checking statement that reached the converter as a scan and was read with OCR. All are US dollar accounts.

Settings for a Wells Fargo PDF statement

• Date: checking and savings rows carry M/D with no zero padding and no year, 10/1 and 10/13. The year comes from the statement date in the page header, October 31, 2021, and the period from "Beginning balance on 10/1" and "Ending balance on 10/31" in the activity summary. A period can end before the statement date, Closing balance on 10/28 on a statement dated October 31, on a closed account. Card rows carry MM/DD transaction and post dates with the year in "Statement Period 10/07/2023 to 11/06/2023".
• Amount: comma for thousands, point for decimals, no sign. Checking amounts sit in two columns whose names change with the account: "Deposits/Credits" and "Withdrawals/Debits" on business accounts, "Deposits/Additions" and "Withdrawals/Subtractions" on personal accounts, "Depósitos/Créditos" and "Retiros/Débitos" on a Spanish statement. Card amounts sit in "Credits" and "Charges" columns.
• Account number: printed in full, 9712246488, after "Account number:" at the top of the account section, and again in the combined statement's account list. Card statements print only "Account ending in" and the last four digits in the first column of every row.
• Account type and currency: the page title and the account section heading name the product, "Wells Fargo Business Choice Checking", "Business Market Rate Savings", "Wells Fargo Active Cash Visa Signature Card". USD throughout.

The balance is printed once per day

The "Ending daily balance" column is filled only on the last transaction of each day. A day with eight transactions has seven rows with no balance. A converter that requires a balance on every row keeps one transaction per day, and one that fills the empty balances by copying the last printed one reports a balance that does not move within the day. The balance has to be checked per day: previous balance plus that day's credits minus that day's debits.

The description wraps, and the second line holds the card and reference

Most descriptions take two lines. The first line is the type and the merchant, Purchase authorized on 10/08 Shell Service Station San Diego CA, and the second line is the authorization code and card, P00381281615635274 Card 7580. ACH rows put the company name on the first line and the trace number and the account holder's name on the second. Zelle rows put Zelle From Ashley Rosario on 07/01 Ref # on the first line and the rest of the reference plus the memo, Jpm99Be88J17 Sweet Professional, on the second, so the reference number is cut in half by the line break. A converter that keeps only the first line loses the card and the memo; one that joins the lines gets the right payee and a reference it can keep or drop.

The first line also carries a date that is not the posting date: Purchase authorized on 10/08, Recurring Payment authorized on 09/30, Zelle From ... on 07/04 posted on 7/7. The DATE column is the posting date. A converter that takes the first date it finds in the text uses the authorization date and moves the transaction a few days earlier than the bank did.

A "<" marks business ACH rows, and it sits in the check number column

Business statements print < in the Check Number column in front of "Business to Business ACH Debit" rows. The mark explains a fee schedule and is not a check number, but it sits exactly where check numbers sit, 9408 and 22811, on the check rows. A converter that reads the column as a number gets a parse error or a check number of zero on every ACH row.

Bankcard deposits carry a date glued to the description

Merchant card deposits print as 10/06Bankcard Deposit -0226447858 with the date attached to the first word and no space. The row date, 10/6, is in the Date column as usual. A converter that tokenizes the description on spaces gets a payee of 10/06Bankcard, which then does not match the rule set up for Bankcard Deposit. The related Bankcard Fee, Bankcard Discount Fee and Bankcard Interchange Fee rows post once a month on one day as three separate debits.

Checks are listed twice

Every check appears in the Transaction history with Check as the description and the number in the Check Number column, and again in "Summary of checks written", three checks per row across the page. The summary's own note says the checks are also in the preceding Transaction history. A converter that reads both sections doubles every check. A * after a number in the summary marks a gap in the check sequence and is not part of the number. Returned checks appear a third time under "Items returned unpaid" with a Check Reference # and no check number.

A combined statement is several statements in one file

A "Combined Statement of Accounts" starts with a list of accounts, their numbers and their opening and closing balances, then prints each account as its own section with its own "Account number:", activity summary, Transaction history, Totals and, for checking, "Summary of checks written". A savings section adds an "Interest summary". A converter that reads the file as one account gives the savings transactions to the checking account and reconciles to the wrong total. The account changes at each "Account number:" heading.

Spanish-language statements

Wells Fargo prints statements in Spanish for customers who ask. The layout is the same, but every heading, column name and summary label is translated: "Resumen de la actividad del período de estado de cuenta", "Saldo inicial al 1/1", "Historial de transacciones", "Totales", and the date column is labeled (mes/dia). The transaction descriptions stay in English, and the page includes a translation table, "Traducciones de términos de transacciones", that lists English descriptions with their Spanish equivalents. A converter that finds the transaction table by the English heading finds nothing on this file, and one that reads the translation table as transactions produces rows with no amounts. The column positions and the row shape are unchanged, so a converter that locates the table by the date column and the amount columns works on both.

Scanned Wells Fargo statements

One reviewed statement was a scan, and its OCR text shows the usual damage in a layout that is already dense: Zelle read as zelle, Inc as lnc, Style as style, and reference codes with l and 1 swapped, Jpm99Be88Jl 7. The two-line descriptions survive, but the pieces of the first line come through as separate elements, Zelle From Ashley Rosario on, 07/01, Ref#, that have to be rejoined by position. The amounts and the running balances read cleanly because they sit alone in their columns, so the per-day balance check still works and catches a row that OCR moved to the wrong column.

Credit card statements list the state as a separate column

The card statement has seven columns: card ending, transaction date, post date, a 17-character reference number, description, Credits and Charges. The merchant's state prints as a separate element to the right of the description, ARCO #42687 AMPM LA MIRADA then CA, and some rows put a phone number between them, Nike.com 800-8066453 CA. Rows are grouped under "Other Credits" and "Purchases, Balance Transfers & Other Charges", each closed by a total line. Credits and charges are both positive in their own columns. A converter that joins everything after the reference number into one payee gets a state code on the end of every merchant, and one that reads the section totals as rows doubles the section.

PDF input challenges

A bank PDF can contain searchable text, scanned page images, or a mixture of both. Searchable text still needs layout analysis because transaction descriptions wrap, columns move, and headers or balances repeat at page breaks. A scanned statement adds OCR uncertainty.

Page breaks

A transaction may begin at the bottom of one page and continue on the next. Continuation pages can omit column headings, repeat an opening balance, or insert footer text and legal pages between transaction pages. A conversion should join split rows and exclude repeated page furniture before it writes the output.

OCR

On scanned pages, OCR can turn 0 into O, 1 into l, or 5 into S. It can also lose a minus sign or decimal mark, read two columns in the wrong order, or struggle with skewed and faint pages. The running balance is the best check: a damaged amount or missing row breaks the balance sequence.

PDF questions

Can I convert a scanned bank statement?

Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.

Why does copying and pasting a PDF into Excel fail?

PDF text stores page positions rather than a spreadsheet table. Wrapped descriptions, repeated headers, and visually aligned columns can paste in the wrong order or into the wrong cells.

How do I know whether the PDF contains searchable text?

Try selecting a transaction description in a PDF reader. If individual words can be selected, the page probably contains text. If the whole page behaves like one picture, it requires OCR.

QuickBooks Desktop import settings

QuickBooks Desktop imports bank transactions in two formats: QBO (Web Connect) and IIF. They go into QuickBooks through different doors, and the right one depends on the QuickBooks version and on how much detail the file must carry.

• QBO (Web Connect) imports under Bank Feeds, the same way an online banking download arrives. Transactions land in the Bank Feeds Center for review, where QuickBooks matches them to existing entries and lets the user add, match or ignore each one. It is the simpler path, but it only works while the QuickBooks version is supported: Intuit discontinues each version after about three years, and a discontinued QuickBooks stops importing QBO files.
• IIF is the older format and still reliable. It imports directly into the register, with no review step and no duplicate check. In return it needs more specific data: the bank account name exactly as it is in QuickBooks, a vendor or payee name for each row, and an expense or income account name for each row.

Settings that matter for a QBO file:

• Account ID and bank ID: QuickBooks links the file to an account by the account ID inside it. Use the same ID every time for the same account, or QuickBooks asks to create a new one. The bank ID must be one that QuickBooks recognizes, or the file is refused with a message that the bank does not support Web Connect.
• Account type: checking, savings or credit card. A credit card file imported into a checking account reverses every sign.
• Dates: four-digit years. Cross-year statements must carry the correct year on every row.
• Amounts: signed. Money out is negative. No currency symbols.
• Transaction IDs: each row needs a unique ID. QuickBooks uses the ID to skip rows it has already imported, so a file with repeated IDs loses transactions, and a file with new IDs for old transactions creates duplicates.
• Payee and memo: the payee field is short and QuickBooks truncates it. Put the rest of the description in the memo.

Settings that matter for an IIF file:

• Bank account name, not an ID, matching the chart of accounts. Sub-accounts use the full path, Parent:Sub.
• Vendor names that match existing vendors, or QuickBooks creates new ones during import.
• Expense or income account for every row, or a default account that the converter fills in.
• Back up the company file before importing an IIF file. There is no undo.

QuickBooks Desktop questions

Which format should I use, QBO or IIF?

Use QBO when QuickBooks is less than three years old and the transactions should go through Bank Feeds for review and matching. Use IIF when QuickBooks is discontinued, when the transactions should land directly in the register, or when each row must carry a vendor and an expense account.

My QuickBooks is older than three years. Can I still import?

Not with QBO. A discontinued QuickBooks version refuses QBO files and no longer connects to online banking. IIF still imports, because it does not depend on Intuit's servers.

Why does QuickBooks say my bank does not support Web Connect?

The bank ID in the QBO file is not one QuickBooks recognizes. A converter sets the bank ID from its own list. Choose a listed bank, or use an ID that QuickBooks accepted before.

Why did QuickBooks create a new account instead of using mine?

The account ID in the file does not match the ID QuickBooks stored for the existing account. Use the same account ID as the last successful import, or connect the file to the existing account when QuickBooks asks.

Why are transactions missing or doubled after import?

QuickBooks skips rows whose transaction ID it has seen before. Missing rows usually mean repeated IDs in the file. Doubled rows usually mean a statement that was already imported with different IDs. Both are fixed by importing each period once, with IDs that stay the same for the same transaction.

Can I import into a sub-account?

Yes, in both formats. For QBO, match the file to the sub-account in Bank Feeds. For IIF, write the full path Parent:Sub as the account name.

Where do IIF import errors go?

QuickBooks writes a new IIF file next to the original with a timestamp in its name, containing only the failed rows and an error message per row. Fix the cause in QuickBooks, usually a missing account or vendor, and import the timestamped file.