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
QuickBooks Online can read a PDF statement itself: Banking, Upload transactions, choose the PDF. Try it first. Use ProperConvert when QuickBooks flags the statement for review, stops before the last page, or the account is not in QuickBooks Online.
For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.
Open the PDF statement, review the extracted transactions, choose QuickBooks Online, and save the converted file on your computer.
Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.
Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.
Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.
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.
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".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.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.
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.
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.
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.
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 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.
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.
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.
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.
Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.
Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.
No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.
Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.
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.
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.
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.
Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.
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.
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 Online imports bank transactions from a file through Banking, Upload transactions. It accepts QBO, QFX and OFX files, which share the OFX structure, and CSV files. Uploaded rows land in the For Review list, where QuickBooks matches them to existing entries and the user adds or excludes them.
Since 2026 the same upload screen also takes a PDF or an image of a statement (JPG, PNG, HEIC). Intuit's AI reads the pages, and a statement it cannot read with confidence is held for a manual review by Intuit staff. If the account is in QuickBooks Online and the statement is a clean PDF, try that first; it costs nothing. A converted file is the better route when the upload flags the statement or stops before the last page, when there are many statements to catch up, when the bookkeeper wants to see and fix every row before it enters the books, or when a client's statement should not be uploaded to a third party.
Settings that matter:
MM/DD/YYYY or DD/MM/YYYY depending on the company settings, digits only, four-digit years.Use OFX, QFX or QBO when the file can be made in that format. It carries the payee, the memo and the check number and gives QuickBooks a transaction ID for duplicate checks. Use CSV when a spreadsheet is the only source and a single description is enough.
The usual causes are a date column QuickBooks cannot read, an amount with a currency symbol or thousands separator, more columns than the three- or four-column layout, or a file over the size limit. Save the file with dates as digits, amounts as plain numbers, and only the needed columns.
The account was chosen during upload. QuickBooks Online does not read the account name from the file. Exclude the rows, delete them from Excluded, and upload again with the right account selected.
In For Review, select the rows, choose Batch actions, Exclude Selected. Open Excluded, select them again, Batch actions, Delete. The rows are gone and the file can be uploaded again.
QuickBooks Online skips rows whose transaction ID it has already seen and, for CSV, rows it reads as duplicates by date, amount and description. Two genuine identical rows on the same day can be dropped from a CSV. Use an OFX-type file with unique IDs for those.
Yes. The 90-day limit applies to a live bank connection, not to a file upload. Any date range can be uploaded from a file.
For one clean statement of an account that is already in QuickBooks Online, the built-in upload is the shortest path, and this page says so. A converter earns its place when the upload flags the statement for review, when a scanned or multi-year statement does not go through, when the account is in QuickBooks Desktop, Quicken, Xero or Sage instead, or when the statement must stay on your computer. The converted file goes through the same Upload transactions screen as a QBO file, with a transaction ID per row, so re-uploading a period does not double it.