CommBank statement to Excel. The balance column checked forward, every break given in cents.
Australian statements are day-first and often print Debit, Credit and Balance across a wide table that a page break can slice in half. The register is rebuilt, the balance chain is walked, and any row that does not follow from the one above it is named with its page and the exact difference.
Drop a CommBank 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 wide table is the one a page break damages most
A four or five column register does not tolerate a page edge badly — it tolerates it silently. The rows continue, the headings do not, and anything reading structure rather than content produces a second table instead of a continuation. The count of printed rows against exported rows is the check that catches it, which is why it is on screen rather than in a log.
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.
Continuation across the page edge
A register that resumes after a break is joined when the column structure agrees, and flagged as suspected when it does not.
Debit / Credit / Balance re-added
Each printed balance against the previous one adjusted by the movement. The first failure is named with page and cents.
Day-first dates, written as ISO
The printed order is read from the document; the export writes an unambiguous date.
Rows printed versus rows exported
Stated together, so a lost page is visible before you download.
Where a CommBank statement goes wrong quietly
None of these announce themselves. Each one produces a file that looks correct.
Transaction descriptions that span a line
Only a continuation with no date and no amount joins the row above; anything carrying money stays its own row.
GST and fee summaries
They restate amounts already in the register. Read as transactions they double the period; they are recognised as summaries.
Statements that print the balance only occasionally
Where a balance column is sparse, the chain is checked only on the rows that carry one, and that limitation is stated rather than hidden.
What we will not claim
There is no CommBank layout in this product. If the reader cannot place a line, the line stays visible and flagged — the hole is reported, not patched.
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 CommBank 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 handle a statement that only shows a balance on some rows?+
Yes, and it says so. The chain is then checked only where a balance is printed, and the export states how many rows that covered, so nobody assumes a check that did not happen.
Can I get the file into Xero or QuickBooks?+
There is a Xero-shaped CSV and a QuickBooks .QBO with unique transaction IDs, both written from the same checked ledger as the .XLSX and the plain CSV.
What if the PDF is a scan from a phone?+
It is read the same way. Scans produce more doubtful cells, which is exactly what the yellow flags are for: they order your review by risk instead of by page number.
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 file that has to import cleanly somewhere else.
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.