Bank Statement Kit logo Bank Statement Kit Convert PDF

ANZ Statement to CSV: Why the Scanned PDF Is the Hard Part

You need ANZ transactions in a spreadsheet — for a tax return, for a broker who has asked for six months of statements, for a BAS, or because an accountant has politely asked you to stop sending PDFs. What you want is a clean list of dates, descriptions and amounts that adds up to what the bank says it should.

ANZ makes this awkward in a specific way. Its online transaction exports are short and only cover accounts you can still see, and the statements themselves — the documents lenders actually want — are described by ANZ as scanned copies of the paper statement. That single fact is why so many generic converters produce an empty file for ANZ. This walkthrough covers both routes, the ANZ-specific failure modes, and how to prove the result is right.

Quick answer

Two ways to get ANZ transactions into CSV:

  1. ANZ's own download. ANZ Internet Banking lets you download transaction history for an account and date range, and ANZ's support material describes CSV as one of the available formats. There is also a Transaction Report covering the last 30, 60, 90 or 120 days for most deposit accounts, generatable in the ANZ App. Transaction exports are documented as covering the last two years, for open accounts only.
  2. Convert the PDF statement. For older periods, closed accounts, or a statement someone emailed you, the PDF is all there is. Upload it to BankStatementKit, which extracts the transactions — OCR'ing the page if it is a scan — and balance-checks the output against the statement's own printed totals.

Rule of thumb: if the account is open and the period is inside two years, take ANZ's download. Older than that, or a closed account, and you are converting the PDF.

Convert an ANZ PDF to a verified CSV

Option 1: ANZ's built-in transaction download

If you have Internet Banking access, start here.

  1. Log in to ANZ Internet Banking.
  2. Select the account you want.
  3. To download transactions, choose the download option and set the account and date range, then pick a format — CSV opens in any spreadsheet, and ANZ also lists accounting-package formats.
  4. To retrieve a formal statement instead, use View statements, choose the account from the dropdown list, and download the statement PDF. ANZ documents this working for closed accounts as well as open ones.
  5. In the ANZ App, select the account and tap Statements or Notices, then the share icon to download or print.

Where the built-in download stops

Almost every one of those routes ends at a PDF statement.

Option 2: Convert the ANZ PDF statement to CSV

  1. Open the statement PDF. If it was emailed and asks for a password, have it ready.
  2. Upload it, supplying the password if 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. If the page has no text layer, OCR runs automatically.
  4. Check the verification label, then download the CSV.

Uploads are capped at 20MB or 50 pages per file, so a long multi-year statement may need splitting.

Convert an ANZ statement

Why ANZ PDFs trip up generic converters

The PDF is often a scan. This is the big one and it is specific to ANZ: the bank's own help pages describe online statements as scanned copies of the paper statement. A scanned page contains an image, not text. Ask a text-extraction converter for its contents and it finds nothing, so it returns an empty CSV or an error — and users reasonably conclude the file is corrupt when it is simply an image. Anything that handles ANZ properly has to detect the missing text layer and OCR the page, then rebuild the table from where the characters sit on it.

OCR turns layout problems into number problems. Once you are reading an image, a smudged or tightly kerned digit can become a different digit, and a slightly skewed scan can push an amount into the wrong column. This is why an OCR'd statement must be reconciled rather than trusted — the failure mode is not a missing row you would notice, it is a wrong figure you would not.

Transaction detail wraps. ANZ's detail column carries Osko and PayID references typed by the sender, BPAY biller names and merchant locations, and those spill onto extra lines. Read line by line, one payment becomes three rows, two of them without amounts.

Prove the CSV matches the statement

With an OCR'd source this stops being optional. An ANZ statement offers two independent checks:

  1. The running balance chain. Every row prints a balance. Previous balance, minus the withdrawal, plus the deposit, must equal the printed balance — row after row. This is the check that catches OCR errors, because a misread digit breaks the chain at exactly the row where it happened and cannot hide.
  2. The opening and closing balance summary. The statement prints an opening balance and a closing balance for the period. Opening, less total withdrawals, plus total deposits, must equal closing, and your extracted rows must produce the same totals.

BankStatementKit runs both checks on every conversion and labels the result VERIFIED, DISCREPANCY or FAILED. On a scanned statement that label is the whole point: it is the difference between a spreadsheet you can file and a spreadsheet you are hoping about.

More on the layout: ANZ statement converter.

FAQ

Why does my ANZ statement produce an empty CSV in other converters?

Because ANZ's online statements are described by ANZ as scanned copies of the paper statement, so there is no text layer to extract. Converters that only read embedded text find nothing. Scanned files fall back to OCR here, which reads the page as an image and rebuilds the table.

How far back can I download ANZ transactions?

ANZ documents transaction exports as covering the last two years for open accounts, with Transaction Reports available in 30, 60, 90 or 120 day spans. Statements themselves reach back further and can be retrieved for closed accounts, but they come as PDFs.

Does this work for an ANZ credit card statement?

Yes, it is a PDF and follows the same workflow. A card statement is built around an opening balance, purchases, payments and a closing balance rather than a per-row account balance, so verification uses those printed totals instead of a running balance chain.

Will the CSV import into Xero, MYOB or QuickBooks?

The output is standard CSV with Date, Narration, Reference, Value Date, Debit, Credit and Balance columns, and all three accept a CSV bank transaction import with a column-mapping step. There is no direct OFX or QBO export.

Is uploading a bank statement safe?

The PDF is processed in memory and never stored. Conversion history is kept for 30 days and you can delete it at any time. Your first conversion is free with no account required, and a free account gets three conversions a day. Questions? Contact us.

The bottom line

For an open ANZ account inside the last two years, use ANZ's own download — it is native data and costs nothing. For everything older, for closed accounts, and for the formal statements lenders actually ask for, you are converting a PDF that is very likely a scan. That makes OCR the entry requirement and reconciliation the exit requirement: a converted ANZ statement is only worth having if the running balance still adds up when you are finished.

Turn your scanned ANZ statement into a CSV that reconciles

Every conversion is balance-checked against the statement's own printed totals, and your first one is free with no account required.

Convert an ANZ statement

← All guides