CommBank Statement PDFs: New and Existing NetBank Routes
Updated · 5 min read
Match the actual NetBank version, select the issued period and download its PDF; verify the local copy. This guide covers the Australia product and the task described below.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Choose the NetBank instructions matching your interface
The new NetBank page describes rollout from late August 2026. The other NetBank support page explicitly asks users to compare their interface with its illustration. Do not combine labels from both versions into one supposed universal menu. The support page distinguishes up to seven years of statements, two years of transaction details and custom summaries.
The feature changes page confirms native transaction CSV remains in new NetBank while OFX/QIF are removed there. It does not establish exact current CSV-export controls, range or headers. A bank's ability to download multiple documents is not evidence that LocalExtract processes a batch.
Download the issued PDF in the applicable version
For new NetBank:
- From Home choose the account, then Account details.
- Choose Download latest statement, or View all statements for another period.
- For the full list choose financial year, select the wanted statement and use Download(PDF).
For the other interface, the support guide uses View accounts → Statements, then account and Download. Follow the route matching your screen and save the actual file. Reopen it outside NetBank and confirm its printed account/cycle and complete readable pages.
Choose the period document rather than an activity substitute
An invented three-year statement request can fall within the published statement window while the transaction-detail view has a different range. Absence from that detail view is not proof the issued PDF is gone. Search the applicable statement list and keep any unlocated period unresolved. A custom summary may answer another date-based question; it is not automatically the same issued period document.
| Source | Useful task | Required check |
|---|---|---|
| Issued statement PDF | Original period collection | Actual account and printed cycle |
| Transaction CSV | Working movement analysis | Exported filters/dates/headers |
| Custom summary | Its documented selection | Do not relabel as issued original |
Finish collection before making a worksheet
Reopen the actual saved file outside the banking viewer. Compare the document title, account alias, printed start/end and readable complete pages with the request. Preserve the original unchanged; record the date collected separately from its printed period. Keep a request pending or a file not located until the record is actually received and checked. Two copies of one cycle do not collect a second period, and the filename alone does not prove coverage.
Use the blank private checklist below to record expected account-period identities, received files and unresolved questions. Do not put full account numbers into shared filenames. A working table is a separate analysis; a third party requesting the issued statement can require information the table omits.
Test the collection checklist with four invented periods
We checked set membership for three deliberately constructed document lists on October 11, 2026. The desired periods are P1, P2, P3 and P4; these aliases do not represent a bank’s actual monthly cadence or archive. A complete list has four files and four unique periods. Omitting P3 leaves three files and a gap. Downloading P2 twice gives five files but still only four unique periods. More files do not necessarily mean more coverage. No bank account, PDF, OCR output or LocalExtract result was tested.
| Invented case | File count | Unique periods | Missing period |
|---|---|---|---|
| Complete | 4 | 4 | None |
| P3 absent | 3 | 3 | P3 |
| P2 saved twice | 5 | 4 | None |
Blank document-collection checklist · constructed CSV results · inputs and method in JSON. Use aliases rather than full account numbers; adapt the actual period list to the documents your account issues.
Frequently Asked Questions
Is one NetBank menu universal?
No. Official pages distinguish new and other interfaces during rollout.
Are activity and statement windows identical?
No. The cited support page describes different coverage.
Does NetBank multi-download prove App batch processing?
No. LocalExtract currently processes one PDF per operation.
Is a custom summary necessarily the original statement?
No. Inspect its actual purpose, interval and document identity.
If PDF is the relevant source
LocalExtract processes one PDF at a time on the device and exports CSV with date,description,amount. Parsing and OCR do not require uploading the statement. This is a working table that needs comparison with the original; no bank compatibility was validated here. There is no direct XLSX, QBO or OFX export, bulk queue or automatic accounting sync. To obtain XLSX, import the checked CSV and save from Excel.
The free evaluation covers ten pages in total. Pro is USD 10/month or USD 60/year. Account, subscription, update and periodic Pro checks need network access. See downloads and product scope.
Sources and verification scope
Public official guidance checked October 11, 2026. Account controls, document availability and bank layouts were not authenticated-tested. The method exercises use invented records, not actual bank samples or measured extraction results.
Updated October 11, 2026: Clarified the document route, product limits and file-coverage checks. No bank format or app output was validated.
Keep the source task and product conditions explicit, preserve the original and leave missing records or rows unresolved. Check the actual file before using it.
For the next task, see the same bank’s working-table guide.
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy