How to Convert Westpac Bank Statements to Excel or CSV

To convert a Westpac bank statement to Excel, start by choosing the right source file. Use Westpac bank feeds or native transaction exports when the task is live reconciliation and the feed period is complete. Use PDF extraction when the statement record itself matters: audit support, a lender pack, a BAS workpaper, an older period, a feed gap, or a spreadsheet that must preserve statement dates, balances, page references, and the original source.

Westpac supports both paths, and treating them as the same thing is where many bad spreadsheets start. Westpac Online Banking lets desktop users export transaction records in CSV, QBO, QIF, or OFX, with the file type depending on the accounting software used, according to Westpac's own guidance on Westpac transaction export file formats. That export can be the cleanest route for ordinary current-period work because it starts as structured transaction data.

A Westpac statement PDF has a different job. It is the formal statement record, not just a transaction list. It carries the statement period, account details, opening and closing balances, page context, and the layout a reviewer can tie back to the original bank document. If a client sends 18 months of PDFs for a loan application, a BAS review, or an audit request, a desktop transaction export may not cover the exact period or carry the evidence trail the workpaper needs.

Download the right Westpac source file before extracting

Westpac users usually start in one of three places: the Westpac app, Westpac Live or Online Banking, or Westpac Corporate Online. The right download depends on the work you are doing after extraction.

For most SME and retail accounts, save the formal eStatement PDF when the spreadsheet has to support BAS review, audit work, serviceability checks, dispute evidence, month-end sign-off, or backfill evidence. The PDF preserves the statement period, balance movement, account context, and page sequence.

Westpac's eStatement guidance says digital statements can be accessed through the Westpac app or Online Banking, and that Online Banking can download statement PDFs. For missing, older, or closed-account periods, the client may need to retrieve the statements through Westpac support rather than sending screenshots or partial exports.

Desktop Online Banking transaction export is different. It is a transaction file for the selected account and date range, and it can be useful when the job is simply to get recent Westpac transactions into accounting software. It does not automatically replace the statement PDF for evidence work, especially when the reviewer expects opening and closing balances or a retained copy of the source statement.

For historical statement work, ask for the PDF statements covering the exact period before you start building the spreadsheet. For corporate banking exports, treat Westpac Corporate Online files as their own source type with separate columns, transaction-code detail, and reporting conventions. The same source-discipline applies across Australian bank-specific work, so a NAB bank statement to Excel workflow can inform the review process without becoming a template for Westpac.

BankSA, St.George, and Bank of Melbourne are Westpac Group brands, but their statement branding and online banking paths can differ. If those files appear in the same client pack, label them separately and test a sample before assuming the Westpac extraction layout will fit every page.

Build a spreadsheet that preserves Westpac statement evidence

A useful Westpac statement spreadsheet should let a reviewer answer two questions quickly: what happened on the account, and where did this row come from in the source statement? For most bookkeeping and evidence workflows, the core columns are transaction date, description or narrative, debit, credit, balance, BSB and account identifier where shown, statement period, source file, and page number.

Keep debit and credit as separate numeric columns unless the downstream system needs a signed amount column. Separate columns make bank-rec review easier because money out and money in are visible without interpreting signs, and balance checks are easier to follow against the PDF. If the target import requires a single amount column, keep a review copy with the original debit and credit treatment before reshaping the file.

Westpac narratives deserve more than a single unreviewed text dump. A good extraction should preserve merchant names, BPAY biller details, PayID names, Osko references, DE or Direct Entry wording, batch references, card transactions, and internal bank transaction codes where they appear. Those details are what help a bookkeeper code transactions, identify duplicates, support GST treatment, or answer a client's question months later.

For PDF or scanned statements, financial document extraction to Excel is useful when the spreadsheet must retain balances, statement periods, file names, and page references. Invoice Data Extraction can process bank statement PDFs and other financial documents into Excel, CSV, or JSON, including scanned PDFs and image files. For a Westpac PDF, the prompt can define the structure rather than accepting whatever a generic converter guesses.

A practical prompt is: extract one row per transaction with transaction date, narrative, debit, credit, running balance, account identifier, statement period, source file, and page number. Use Australian date formatting and keep debit and credit as separate numeric columns. That prompt shape keeps the spreadsheet useful for BAS reconciliation, audit working papers, lender serviceability packs, and exception checking because every row remains traceable to the original PDF statement.

Prepare Westpac statement data for Xero, MYOB, and QuickBooks Australia

Before importing into Xero, MYOB, or QuickBooks Australia, check date format, description field, debit and credit treatment, account mapping, duplicate risk, and whether a review workbook needs to survive alongside the stripped-down import file. Use the dedicated guides to import bank statements into Xero, import bank statements into MYOB, and import bank statements into QuickBooks for software-specific steps. If the PDF is the evidence source, reconcile the extracted rows back to the Westpac statement before creating the import file.

Treat Corporate Online and complex Westpac files as separate extraction jobs

Westpac Corporate Online files should not be handled as if they were Westpac Live eStatements with a different logo. Corporate users may receive CSV statement files and reconciliation outputs built around previous-day balances, previous-day transactions, transaction-code detail, batch references, and entity-level account structures. Preserve the original file, document the export type, and map the output to the reconciliation process that will actually use it.

Mixed packs need the same discipline. A multi-account PDF, a BusinessChoice card statement, a merchant settlement statement, and a scanned paper bank statement may need different columns and review checks. Combining them into one workbook is fine only if each row identifies the source file, account, statement period, and document type.

Invoice Data Extraction is useful for these mixed packs because it can process PDFs, scanned PDFs, JPGs, PNGs, and large batches through the same prompt-based workflow. The product supports batch processing up to 6,000 files in one job, individual PDFs up to 5,000 pages, and structured outputs in Excel, CSV, or JSON. For complex Westpac packs, the prompt should define separate handling for bank statements, card statements, merchant statements, and irrelevant cover pages, with source file and page references retained for review.

Keep entity, month, account, and source-document fields visible in the workbook. If January's Westpac Corporate Online export, February's PDF statement, and a scanned merchant statement all land in the same workpaper, the spreadsheet should make those differences visible instead of hiding them behind one generic transaction table.

A practical Westpac-to-Excel checklist before you import

Before using the data in Excel, CSV, Xero, MYOB, QuickBooks, a BAS workpaper, or a lender file, run a short control check.

• Confirm the source type: Westpac PDF statement, desktop transaction export, bank-feed data, or Corporate Online export.
• Confirm the date range and account identifier match the workpaper or import period.
• Reconcile opening and closing balances where the PDF statement provides them.
• Check whether debit and credit are separate columns, signed amounts, or a software-specific format.
• Preserve the full transaction narrative before shortening descriptions for import.
• Label the source file, statement period, and page number where the spreadsheet supports evidence or review.
• Check for duplicate rows before importing, especially when a bank feed and extracted statement cover the same period.
• Keep a review workbook separate from any stripped-down import file.

Do not mix Westpac Live exports, PDF extractions, and Corporate Online exports in the same workbook without labelling the source of each row. The import file may only need date, description, and amount. The review file needs enough context to explain the number later.

Australian big-four statement workflows share a pattern, but they are not interchangeable. Use an ANZ bank statement to Excel guide for a comparable bank-specific workflow, then keep the Westpac file handling tied to Westpac's own download paths, statement formats, and transaction narratives.