Macquarie Bank Statements: Find, Save and Check Account History
Updated · 5 min read
Use the personal account statement route, save the actual offered file and check product-specific history and its real file type. 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.
Use the personal bank-account source and preserve format limits
The personal statement guide documents statement downloads. History varies from two to ten years by account and some records are unavailable online; a closed-account request requires authority/contact and may involve a fee. Its general bank-account prose does not name a universal PDF format. Do not borrow Wrap investment or card PDF details as proof for every bank account.
Direct anonymous retrieval returned 403 in the independent source review while official publicly indexed help text was readable. This is an access limitation, not proof the guide was deleted or that your bank login/download was tested.
Find and keep the actual offered statement
- In personal Online Banking select the account's I want to, then View account statements and reports.
- Select the required statement; the documented action downloads the record through the browser. Inspect its actual file type.
- In the app use account → I want to → View account statements and select/download/view the document. A universal device-level final folder or save control was not established.
- Reopen the retained file and check the actual account, printed interval and complete readable content.
Resolve account-specific history without promising ten years for all
In an invented collection, one product's ten-year history condition cannot establish another product's older record. Check the actual account list and keep unavailable periods marked not located. For a closed record follow the legitimate authorized request route; possible fees and retrieval availability must be checked, not invented. A native transaction selection can serve analysis without being the issued statement.
| Source situation | Collection action | Limit |
|---|---|---|
| Offered bank-account statement | Save actual file and verify type | Universal PDF not proved here |
| Older period not listed | Check product history/support | Two–ten years is product-dependent |
| Closed account | Use authorized official request | No automatic online access guarantee |
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
Are all bank-account statements proven PDF?
No. The inspected general guide establishes downloading, not a universal format.
Does every account have ten years online?
No. The guide describes product-dependent two–ten-year history and unavailable records.
Does an anonymous 403 mean the guide is deleted?
No. Official public indexed help was readable; direct retrieval was limited.
Is closed-account retrieval automatically free?
No. Authority, actual availability and possible fees must be checked.
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