Why does my Wells Fargo CSV have no column names?

Wells Fargo's comma delimited download normally starts straight at the first transaction with no header row. That is legal CSV but many importers assume line one is column names, so they either reject the file or silently swallow your oldest transaction as a header. This converter detects a headerless file and works the columns out from the data itself.

Why are the descriptions blank when I import my Wells Fargo file?

Because the fourth column, the one that would be the payee, is empty on every row. The real description sits in the fifth column, the memo. Any tool that looks for a payee column finds it and imports a statement full of blank descriptions. This converter picks the column that actually contains text rather than the one with the expected name.

What columns does a Wells Fargo CSV have?

Five, in an unusual order: date, amount, a single asterisk, an empty payee column, and the memo that holds the real description. The amount is in column two rather than at the end, which is where most bank exports put it.

How do I know the debits and credits came through the right way round?

Check the first transaction shown in the preview against your statement. Wells Fargo's export has no running balance column, so unlike a Chase file there is no arithmetic check available — the amounts cannot be verified against anything inside the file itself. That is why the converter puts one transaction in front of you and asks you to confirm the direction before you download.

Wells Fargo CSV to QBO Converter

Getting the CSV out of Wells Fargo

Sign in at wellsfargo.com and open the account.
Find the download link on the account activity page — it's usually worded Download Account Activity.
Choose the date range, and pick Comma Delimited as the format. That's Wells Fargo's wording for CSV; there's also a Quicken option, but the comma delimited file is the one to take here.
Drop it above, check the first transaction, download the .qbo.
In QuickBooks Desktop: Banking › Bank Feeds › Import Web Connect File.

What you actually get

Five columns, and not in the order you'd expect:

Position	Holds	Example
1	Date	`01/05/2024`
2	Amount — second, not last	`-45.20`
3	A single asterisk, on every row	`*`
4	Payee — empty on every row	(nothing)
5	Memo — the real description lives here	`GAS STATION 4471 PURCHASE AUTHORIZED`

And usually no header row at all — the file starts straight at the first transaction.

The two things that break other tools

1. There are no column names

Most importers assume line one is a header. Give them a Wells Fargo file and one of two things happens: it's rejected outright, or — worse — your oldest transaction is swallowed as the header row and silently disappears. You don't notice until the opening balance is off by one transaction.

This converter checks whether line one looks like names or like data. If every field on line one parses as a date, an amount and free text, it's a transaction, and the columns get worked out from what they contain instead of what they're called. The results panel tells you which it decided.

2. The payee column is empty — every row

This is the one that produces a technically successful import you'd rather have failed. Column 4 is where a payee would go, and Wells Fargo leaves it blank. The description you actually want is in column 5, the memo.

A tool that maps by column name finds "payee", takes it, and imports a whole statement of transactions with blank descriptions. The dates and amounts are right, so nothing errors — you just have a register full of unidentifiable rows and a re-import ahead of you.

We pick the description column by looking at what's in it: the column carrying real text on most rows wins, whatever it's called. On a Wells Fargo file that's the memo, and the results panel names the column it chose so you can see it made the right call.

One thing we can't check for you here

Wells Fargo's export has no running balance column, and that removes our best safety net. With a Chase file we can add up each balance against the one before it and prove the amounts and their signs are right. With a Wells Fargo file there's nothing inside the file to check against.

So the preview puts one transaction in front of you and asks you to confirm it's pointing the right way. It takes ten seconds and it's the only check available on this format — please don't skip it.

Two smaller quirks

Check numbers are inside the text. A paid check shows up as CHECK # 1042 in the memo rather than in a column of its own. We pull the number out of the text so it becomes a numbered check in QuickBooks instead of an anonymous withdrawal.
Column 3 is always *. It carries no information on any row we've seen. It's ignored — but it's also one more column that a fixed-template importer trips over.

On QuickBooks Online? It's harder than usual with this file

Online reads bank CSVs natively, and normally we'd tell you to try that first. With Wells Fargo there's more to fix than with most banks: you'd add a header row, reorder the columns so the amount comes after the description, move the memo into the description position, and delete the asterisk and payee columns. Doable, but it's a real edit every month. What Online accepts.

On QuickBooks Desktop there's no CSV import at all, so converting is the only route.

Other banks

All six banks compared columns, dates and traps side by side
Chase seven columns, and a Type column worth keeping
Any other bank nothing is hardcoded — the layout is read from the file

Frequently asked questions

Why are all my descriptions blank after importing?

Because whatever you used read the empty payee column instead of the memo. That's the single most common Wells Fargo import problem, and it's why this page exists. Convert the file again here and check the results panel — it names the column it used for descriptions.

Should I pick "Comma Delimited" or the Quicken option?

Take the comma delimited file. The Quicken option gives you a .qfx, and QuickBooks Desktop does not accept .qfx — its bank feed reads Web Connect files, which means .qbo specifically. Downloading the Quicken file for QuickBooks is a dead end.

On QuickBooks Online a .qfx is worth a try — Online does accept it alongside CSV. On Desktop, take the comma delimited file and convert it here.

My file has a header row. Is that a problem?

No. Wells Fargo's own download usually doesn't have one, but files that have been through Excel or a spreadsheet template often do. Either goes through — the check is on what line one contains, not on whether it exists.

Does this work for Wells Fargo savings and credit cards?

Savings uses the same layout — set the account type to Savings after dropping the file. Credit card exports differ by product; the layout is read from the file rather than assumed, so try it. If a column can't be placed, the page says which one instead of failing silently.

Will importing the same statement twice create duplicates?

No. Every transaction in the .qbo carries a unique ID built from its date, amount and description, so an overlapping date range gets matched and skipped by QuickBooks. Keep the account number field the same each month so the IDs stay consistent.

Is my Wells Fargo statement uploaded anywhere?

No. It runs in your browser, and this page ships a Content Security Policy with connect-src 'none' — your browser refuses to let the page make any network request at all. Watch the Network tab in developer tools while you convert; it stays empty.