CommBank Statement to CSV: The Full Walkthrough

You need Commonwealth Bank transactions in a spreadsheet, and you need them to be right — every Osko transfer, every direct debit, every amount pointing the right way. Usually there is a real deadline attached: a tax return, a home loan application where the broker has asked for six months of statements, a BAS, or a year of records for the accountant.

Sometimes NetBank hands you a CSV and you are done in two minutes. Often you are holding PDFs — because the period is older than the export window, because the account is closed, or because someone emailed them to you. This walkthrough covers both paths, the CommBank layout details that defeat generic converters, and how to prove the CSV matches the statement to the cent.

Quick answer

Two ways to get CommBank transactions into CSV:

1. NetBank's export. CommBank lets you export transaction information for use in other software. You choose the account and date range, pick a format, and export. CommBank's support material describes roughly 15 months of exportable transaction history, alongside up to seven years of viewable online statements.
2. Convert the PDF statement. For anything outside that window, for closed accounts, or for statements supplied by someone else, the data only exists as a PDF. Upload it to BankStatementKit, which reads the transactions and balance-checks the output against the statement's own printed totals.

Rule of thumb: if you can log in to NetBank and your period is inside the export window, take CommBank's export. Everything else goes through the PDF.

Convert a CommBank PDF to a verified CSV

Option 1: CommBank's built-in NetBank export

If you have NetBank access, try this first — the data comes straight from the bank and needs no extraction.

1. Log on to NetBank.
2. Open the account you want and go to its transaction history.
3. Set the date range you need.
4. Choose the export or download option and select your preferred format — CSV rather than PDF if you are heading for a spreadsheet.
5. Open the file in Excel, Numbers or Google Sheets.

Where the built-in export stops

CommBank's export is genuinely useful, and it runs out in predictable ways:

• The export window is shorter than the statement archive. You can view years of statements online but export a much shorter span of transactions. The periods people need for loan files are often on the wrong side of that line.
• You need current access to the account. A closed account, a former joint account, or a statement a client sent you leaves you with no session to export from.
• Statements and transaction exports are not the same document. A statement is the bank's formal record with an opening and closing balance; a transaction export is a list. Lenders and auditors usually want the statement.
• The export needs cleaning. Header rows, date formats and CommBank's own column naming generally need a pass before another tool will accept the file.

Every one of those cases ends in the same place: a PDF.

Option 2: Convert the CommBank PDF statement to CSV

1. Open the statement PDF. If it was emailed to you and asks for a password, have that ready.
2. Upload it, supplying the password if one is needed — the file is unlocked in memory and never written to disk.
3. The transactions are read into seven standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance.
4. Check the verification label, then download the CSV.

Uploads are limited to 20MB or 50 pages, and a scanned or photographed statement falls back to OCR automatically.

Convert a Commonwealth Bank statement

Why CommBank PDFs trip up generic converters

Descriptions wrap, and they wrap because of the payer. This is the main failure mode. Osko and PayID transfers carry a reference typed by whoever sent the money, BPAY entries carry long biller names, and card transactions carry merchant name plus location. Any of those can outrun the column width and continue on the next physical line. A converter that treats every line as a transaction produces phantom rows with empty amounts, which then quietly corrupt every total downstream. Rows have to be assembled around the date and amount columns, with continuation lines folded back in.

Debits and credits are separate columns, not one signed number. Collapse them carelessly and every withdrawal in the file flips sign. This is the error nobody notices until a reconciliation fails weeks later.

Statement furniture looks like data. Statements carry page headers, period summaries, carried-forward balances and interest or fee blocks. Read as flat text, those lines can be mistaken for transactions — and a spurious "balance brought forward" row is enough to break every subsequent check.

Prove the CSV matches the statement

This is the step almost everyone skips, and it is the one that decides whether the file is usable. A CommBank statement gives you two independent checks:

1. The running balance chain. Each row prints a balance. For every row, the previous balance minus the debit plus the credit must equal the printed balance. One dropped or duplicated transaction breaks the chain at exactly the row where it went wrong, which is why this check is worth more than a spot-check of totals.
2. The statement summary. CommBank prints the opening balance, the transactions and charges for the period, and the closing balance. Opening, less total debits, plus total credits, must equal closing — and your extracted rows must produce the same totals.

Done by hand this is fifteen minutes a statement and it is nobody's idea of a good afternoon. BankStatementKit runs both checks on every conversion and labels the result VERIFIED, DISCREPANCY or FAILED, with a discrepancy pointing at the row where the numbers stop reconciling.

More on the layout: CommBank statement converter.

FAQ

The bottom line

If your period sits inside NetBank's export window and you still have access, use CommBank's own export — it is free, native and authoritative. For older periods, closed accounts and statements handed to you by someone else, convert the PDF, and insist on a conversion you can prove. Wrapped Osko references and split debit/credit columns are exactly where silent errors live, and a running balance that reconciles is the cheapest proof you will ever get.