Wells Fargo CSV to QBO Converter

The Wells Fargo export is the most minimal of the big-bank CSVs, and its defining quirk is that it has no header row at all. The file starts with a transaction on line one. Every line is five quoted fields in a fixed order — date, amount, a literal asterisk, an empty field, and the description — so a row looks like "03/14/2026","-42.19","*","","AMAZON MKTPLACE PMTS". The third and fourth fields never carry information; they are placeholders in a layout that has stayed unchanged long enough for people to build around it.

A missing header row is where most tools quietly cost you a transaction: line one gets read as column names, so the oldest or newest row in the file never gets converted. Everything else imports perfectly, which is what makes it easy to miss — you notice a month later while reconciling, and by then working out which row vanished is genuinely hard. This converter checks whether line one parses as a date and an amount, and when it does it keeps that line as data and numbers the columns instead. The mapping step says so plainly, and a checkbox is there to overrule it either way.

Beyond that one issue Wells Fargo is well behaved. Dates use MM/DD/YYYY with four-digit years, which leaves no room for the day-first misreading that scrambles imports from other sources. Amounts are already signed the way OFX and QuickBooks expect, negative for money out and positive for money in, so nothing needs inverting. And because the fields are quoted, a description containing a comma stays in one field instead of splitting the row. With the header question handled for you, the conversion is three column choices and a download.

The column list shows a date and a dollar amount where names should be. The first transaction is being read as the header row. Tick My file has no header row on the mapping step and the columns switch to Column 1 through Column 5, with the transaction restored to the data. This should already be automatic for a Wells Fargo export — the checkbox is the manual override for the cases detection misses, such as a file you have already edited in Excel.

The QBO file has one fewer transaction than the CSV. Same cause, seen from the other end — the consumed header row is the missing transaction. Compare the row count reported on the mapping step against the line count of the original file before you import anything; the discrepancy is much cheaper to catch here than during reconciliation.

Descriptions are cryptic strings of codes. Wells Fargo passes through the raw payment-network description, so ACH transfers and card purchases often arrive with reference numbers and trace codes attached to the merchant name. The converter carries the text across unchanged. QuickBooks bank rules matching on a substring of the merchant name handle these well once they are in For Review.

Importing a second overlapping range created duplicates. A CSV carries no transaction identifiers, so the converter generates one per row at the moment of conversion. Two files covering overlapping dates therefore produce two unrelated sets of IDs and QuickBooks cannot match them. Download consecutive, non-overlapping ranges, and convert each file exactly once.