For the file that has to be accepted on the first try

CommBank statement in CSV. Every printed line accounted for before the file exists.

Import screens accept almost anything and complain about nothing. That is why the checks belong before the download: rows printed against rows written, a single consistent sign, ISO dates, and no page furniture in the data. What lands in your accounting software has already survived those four.

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.

Dates on file: DD/MM/YYYY → written out as ISOCurrency: AUD ($)No bank login, ever

The count is the only proof of completeness

A CSV cannot tell you that it is missing four rows. The statement can: count the transaction lines on the page. Putting that number next to the exported row count turns 'complete' from a feeling into something you can look at — and on a wide Australian register, a page break is the usual reason the two would differ.

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.

Printed lines versus written rows

Both counts stated. A shortfall is reported with the page it came from.

One signed amount, rule displayed

Where the statement prints Debit and Credit separately, the fold into one sign is shown so it can be checked against the paper.

ISO dates out

The day-first reading is resolved inside the conversion, not left to whoever opens the file later.

Summary blocks kept out

Totals and fee summaries stay out of the row data and are used as checks on it instead.

Where a CommBank statement goes wrong quietly

None of these announce themselves. Each one produces a file that looks correct.

A repeated heading every page

In a CSV it becomes a row whose description is column headings. It is removed and counted.

Amounts padded with spaces

Right-aligned amounts arrive with leading spaces that make them text. The numeric reading is produced; the printed string is kept beside it.

Accounts with a linked offset

A statement can show two account sections at once. Each is kept as its own ledger rather than appended into one sum.

What we will not claim

We state the column contract; your accounting software decides whether it agrees. We have not tested your version of it, and we will not pretend otherwise.

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

STEP 1

Upload the statement

A native PDF, a scan, or a phone photo of the CommBank statement. No bank connection, no credentials, nothing to authorise.

STEP 2

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.

STEP 3

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

Which CSV shape is right for Xero?+

The Xero-shaped export: Date, Description, Debit, Credit, Balance, with an optional single signed Amount. The plain CSV is the neutral one if the destination is not Xero.

Can I see which rows a person changed?+

Yes. Corrections carry who made them and when, appear in the review report, and keep the printed value alongside the new one.

What if two accounts are on one statement?+

They are read as two ledgers and exported separately, so nothing is summed across accounts by accident.

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.