Macquarie Bank Statements to Excel: Loaded CSV Rows and Source Checks

Load the required personal search rows before CSV export, inspect coverage and import a checked working file in Excel; PDF conversion is conditional. This guide covers the Australia product and the task described below.

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.

Export the displayed rows deliberately, not just the first screen

The personal transaction-download help restricts export to loaded/displayed rows in Online Banking. Search help explicitly names CSV/QIF and describes scrolling to load more. App viewing does not establish app export.

Set the actual account/search conditions, inspect the displayed selection and load the further rows needed before exporting the offered CSV. Preserve the raw file and its filters. In an invented six-month task, exporting only the first loaded portion leaves a coverage gap even if every visible row was captured accurately. Check actual earliest/latest included activity and compare against the intended source interval; do not claim completeness merely from a plausible row count. A subset cannot be reconciled as the full statement. If a suitable PDF original is actually obtained, the manual route below is an alternative; the general statement guide does not establish a universal bank-account PDF type.

Create a CSV from a PDF you have actually obtained

This step starts with a suitable original already in your possession. It does not establish an unverified bank download control. Keep that file unchanged and make a separate working table. A native export that already supplies the required account, dates and detail can bypass PDF conversion.

Manual route: build and check the table

1. Open the original in a trusted local viewer. Record the account alias, currency, printed start/end and any page references in a private source register. Read the complete transaction section, including continuation pages.
2. Decide what the source calls each date. Use the posted date when that is the chosen task; if another relevant date is present, retain it in an additional private worksheet column. Do not use the file's download date as a transaction date.
3. Create a working sheet with date, description, amount. Transcribe each included posted movement once. Join a description continuing onto another line only when it belongs to that same movement. Do not insert section headers, carried balances or summary totals as transactions.
4. For this deposit cash table, use positive inflows and negative outflows. Read the actual source's debit/credit or sign convention before mapping it. Do not assume a borrowing or card balance uses the same convention. Keep different accounts and currencies separate.
5. Compare the worksheet with the original page by page. Mark each source movement checked once; inspect dates, description text, decimal points and signs. If text selection loses columns or joins unrelated lines, transcribe from the visible original instead. If a scanned or unclear page cannot be read reliably, obtain a clearer copy or leave the affected rows unresolved.
6. Save a separate CSV working copy using your editor's CSV format. Inspect the actual delimiter and encoding; changing a file extension does not create a CSV. The small comma-delimited example below shows the chosen fields, not bank-export headers. Preserve any richer private worksheet columns separately if the three-field copy omits information you need.

Optional LocalExtract route: inspect output before importing

Open LocalExtract and select one PDF for the operation. Let the local parser/OCR process it, inspect the resulting transaction table against every relevant page, and export CSV. The current export contains date,description,amount; it does not supply a complete replica of every field in the original. Compare dates, signs, missing or duplicate movements and continued descriptions before relying on it. The original remains the authority for this check. No actual bank PDF or output was tested for this guide, so neither the public help route nor the invented exercise establishes extraction compatibility.

Keep any unresolved row out of a claimed complete reconciliation. A visually plausible table and an equal closing total can still hide offsetting errors. After the checks, import the actual CSV in Excel as described below, inspect the preview and save XLSX from Excel if a workbook is needed. LocalExtract does not export XLSX directly.

Choose dates and amounts, then inspect the Excel import

For a deposit cash account, use positive inflows and negative outflows after reading the original's actual convention. Keep another needed date, currency and source reference in additional private worksheet columns; the three-field CSV does not encode them automatically. One entirely invented comma-delimited example is:

date,description,amount
2026-09-01,Example receipt,250.00
2026-09-02,"Example purchase, supplies",-100.00
2026-09-03,Example fee,-10.00

These are chosen learning fields, not the bank's native headers or a tested statement layout. The comma in a description is protected by quotes, consistent with RFC4180. In Excel use Data → From Text/CSV, inspect delimiter, date types, decimal amounts and signs, then load. Microsoft's import help explains the preview. Save XLSX in Excel after checking.

When the source supplies comparable endpoints for the same complete account/currency/interval, compare opening plus signed movements with closing. A filtered subset, loaded fragment or different interval cannot be reconciled as that complete cycle. Without comparable balances, record that limit and check every row; an equal net total cannot prove each date or description.

Check the method with invented records

We recomputed three deliberately constructed cases on October 11, 2026 using decimal arithmetic: complete rows, an omitted fee and a duplicated movement. The reference total and every number are invented. This checks the reconciliation method only: no bank account, real PDF, OCR result or LocalExtract output was tested. The same learning aid is used across these guides.

Illustrative units, not a real account balance.

Download the blank document checklist or synthetic check data. CSV · JSON.

Frequently Asked Questions

Does export include every matching record automatically?

The personal help limits export to loaded/displayed rows; inspect scrolling and actual coverage.

Is app export established?

No. The cited export scope is personal Online Banking.

Can a partial CSV reconcile a complete statement?

Not as a complete-cycle table. Keep its selected scope explicit.

Was this workflow executed in a bank account?

No. Public help and invented cases were reviewed; no authenticated account or real output was tested.

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.

• Bank guidance 1
• Bank guidance 2
• Bank guidance 3

Updated October 11, 2026: Added task-specific source decisions, date/amount examples and CSV import 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 document collection guide.