Chase bank statement to Excel. Every running balance re-added, and the row where it breaks named.
The statement is not yours, so you cannot log in and download it — a client sent you a PDF, or a folder of them, and the transactions have to come out with the balances still meaning something. We rebuild the ledger line by line, re-add the running balance, and where it stops adding up we tell you the row and the exact difference. We never touch the figure.
Drop a Chase 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.
Why a Chase statement is the easy one to get wrong quietly
Look at the first line of the register: if the most recent transaction sits at the top — the way a lot of business checking exports print — then reading down the page walks the running balance backwards, and a quick eyeball says the column is broken when it is not. A converter that writes rows in page order hands you a ledger where every subtotal is nonsense. So the direction is settled before anything is called reconciled: the workspace works out which way this statement runs, says which way it found, and only then re-adds the balances.
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.
Which end is the first transaction
The statement direction is detected and shown. A descending statement is re-sequenced for the balance check, while the rows you export keep the order they were printed in unless you ask otherwise.
Opening + deposits − withdrawals = closing
One sum against the summary box on page 1. If it does not match, the difference is stated in cents, not rounded away, and the statement is not called balanced.
Row-to-row running balance
Each printed balance is compared with the previous balance plus or minus that row's amount. The first row that fails is named with its page and the size of the gap.
Month N closing vs month N+1 opening
When you upload several months at once, the seam between them is checked. A missing month shows up as a gap rather than as a quietly shorter ledger.
Where a Chase statement goes wrong quietly
None of these announce themselves. Each one produces a file that looks correct.
Page furniture becomes transactions
Repeated account headers, page numbers and the 'continued' line are not money. If they land in the data they inflate the row count and every total downstream.
Check images in the middle of the register
Scanned check images can be read as a row of numbers. Anything we cannot place in a dated, amount-bearing line is flagged rather than guessed at.
Two-digit years and US date order
01/02/2026 is 1 February in London and 2 January in New York. On a US statement the order is month-first; the workspace states which reading it used, and an ambiguous cell is flagged instead of being silently resolved.
What we will not claim
We do not have a Chase template, and we are not going to build one. If a layout defeats the reader, the page says so and marks the cells it could not place — it does not fill the gap with a plausible number.
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 Chase 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
Is this the same as downloading activity from Chase?+
No. Chase lets the account holder export their own activity. This is for the other case — the statement arrived as a PDF from someone else, often for a period that is already closed, and you need it as a ledger with the balance proven.
What comes out — a sheet, or something my accounting software can take?+
Both. The .XLSX workbook has one row per transaction with dated, numeric columns; there is also a plain CSV, a QuickBooks .QBO file with unique transaction IDs, and a Xero-shaped CSV. The workbook carries a Review sheet listing every cell a person confirmed or corrected.
What happens when the balance does not add up?+
The row is flagged in yellow with the arithmetic that failed and the exact difference, and the statement is not reported as balanced. Yellow means look at this — not that we have decided it is an error, and not that we have corrected it.
How much 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 file that has to import cleanly somewhere else.
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.