Wells Fargo statement to CSV. Headers stripped, signs consistent, one row per line printed.
A CSV built from a statement is only as good as the rows under it. If two rows went missing at a page break, the file is shorter than the paper and nothing in it looks wrong. The count is printed beside the download, so 'shorter than the paper' is something you can see rather than something you find out in three weeks.
Drop a Wells Fargo statement here
Or click to pick the file. It opens in the same page you would have used anyway — the balance chain starts re-adding on the next screen.
Three files free, 60 pages in total, no card needed. Paid plans are priced by the page — one page of the original is one page, up to 500 pages in a single file.
What the receiving system will do with a bad file
It will take it. Import screens validate shape, not arithmetic. Two hundred rows of a four-hundred-row statement import perfectly and produce a balance that is off by an amount nobody can explain later. That is why the row count and the balance check belong on the outside of the file, before it exists.
What gets checked before you download
Every line below is arithmetic on the paper you sent — not a supplier's claim about how good its reading is. Where the arithmetic fails, you get the row and the exact difference, and the statement is not called balanced.
Every printed line accounted for
Lines on the page minus lines in the file equals zero, or the difference is stated and the affected page is named.
A single signed amount column
Or separate debit and credit columns — your choice. The sign is taken from the statement's own structure, and the choice is recorded so the file can be regenerated the same way.
ISO dates
A US statement is month-first; the CSV writes 2026-03-04 so no downstream locale can read it as 3 April.
Where a Wells Fargo statement goes wrong quietly
None of these announce themselves. Each one produces a file that looks correct.
The 'continued from previous page' line
It is not a transaction, and its presence in a CSV is usually why an import has one mysterious row at the top of each page's worth of data.
Currency symbols in amounts
A dollar sign makes the column text. It is stripped from the numeric value while the printed original is kept beside it.
End-of-period totals
Totals are claims about the rows, not rows. They stay out of the file and are used to check it.
What we will not claim
We document the column contract; we do not guarantee your software honours it. If your import has an opinion about date order or sign convention, tell it ours and compare.
The same goes for the arithmetic: a clean run means the checks we ran found nothing to flag. It does not mean the document is correct — it means nothing in it failed the checks listed above.
How it runs
Upload the statement
A native PDF, a scan, or a phone photo of the Wells Fargo statement. No bank connection, no credentials, nothing to authorise.
The ledger is rebuilt and walked
Rows are put back in the order the statement prints them, page furniture is removed, and the balance chain is re-added line by line.
Check the flags, then export
Anything that did not add up is listed first, with its page and exact difference. Then take the CSV file, the other export shapes, and the review sheet.
What lands on your disk
- The .XLSX register — one row per transaction, no merged cells, amounts as numbers
- A Review sheet: who confirmed or corrected which cell, and what it said before
- Plain CSV, Xero-shaped CSV, and QuickBooks .QBO with unique transaction IDs
- A check report stating the rows printed, the rows exported, and every difference found
- Every cell still clickable back to the page and region it was read from
- Files are read, then destroyed — a second upload is a second read
Questions
Can I get both CSV and Xero format?+
Yes, from one upload. Both are written from the same checked ledger, so they cannot disagree.
How do I know no row was invented?+
Every exported row still points at the page and region it came from, in the workspace and in the review report. A row with no source does not get exported.
Can two people work on the same statement?+
Each confirmation is recorded with who made it and when, so a two-person review leaves two names in the trail rather than one.
What does it cost?+
Three files are free, 60 pages in total, with no card and no account needed to try. Paid plans are sold by the page — $19 a month buys 1,000 pages — and a page is one page of the original document.
For the working paper you have to be able to defend.
For the import where QuickBooks decides whether a row is already there.
The same checks, without naming a bank — including the ones whose layouts we do not recognise.
A .QBO with the institution, the account and a transaction ID per row, so a re-import is refused.