US Bank statement to Excel. One row per transaction, each one still pointing at its page.
Turning the statement into a sheet is the easy half. The half that decides whether the sheet is usable is whether its totals survive contact with the paper. Here the register is rebuilt first, the running balance re-added second, and the workbook written third — with the doubt left visible instead of smoothed out.
Drop a U.S. Bank 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.
A workbook that looks right and totals wrong
Nothing about a bad conversion announces itself. The columns line up, the dates look like dates, and the sum at the bottom is simply not the sum on the statement. The only defence is to check the bottom against the page and to name the row where the two diverge. That is what this produces: not a promise that the sheet is right, but a list of the places where the paper says something different.
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.
The closing figure on the page
It is read from the statement and compared with the register's own last balance. The two are shown together; neither silently replaces the other.
Every row adds forward
Previous balance ± amount = printed balance. The first failure is named, with page and the size of the difference.
Amounts that are text in the source
A numeric reading is produced alongside the printed string, and a cell that cannot be read as a number keeps its printed form and is flagged.
One row per transaction
No merged cells across rows, no subtotal rows posing as transactions, no repeated headings in the middle of the register.
Where a U.S. Bank statement goes wrong quietly
None of these announce themselves. Each one produces a file that looks correct.
Descriptions that contain a date
'ACH 03/14 PAYROLL' has a date inside the description. The transaction date is the column, not the first date-like string on the line.
Negative amounts in parentheses
Accounting-style negatives are common. The numeric field is derived from the brackets; the printed cell is preserved unchanged.
A table split by a page break
When the column structure agrees across the break it is joined; when it does not, it is flagged as suspected rather than merged on faith.
What we will not claim
There is no per-bank template here, and this page is not going to claim one. A layout we cannot read is reported as a layout we cannot read, on the page where it happened.
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 U.S. Bank 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 Excel 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
Does it work on a scanned statement?+
Yes, and a scan is where the flags earn their keep: the cells the reader is least sure about are listed first, so the review starts where the risk is rather than at row one.
Can I export to QuickBooks rather than Excel?+
Yes. The .QBO export carries a unique transaction ID and the opening and closing balances, which is what makes re-importing the same file safe.
How do I show someone where a number came from?+
Click the cell and the original page opens at that region. The review report records the same link, so a third party can follow it without you in the room.
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.