Suncorp Internet Banking exports transactions as CSV, OFX, QIF or ASCII. Each export file can cover no more than 364 days, and Internet Banking holds up to about two years of transactions, depending on the account type. The PDF eStatements reach much further back, to 1 July 2013.
That gap decides the method. For a period inside the last two years, Suncorp's own CSV export is the quickest way to get a Suncorp bank statement to Excel. For anything older, or when you need each statement's period and its printed opening and closing balances, the PDF statements are the record, and the job is to convert them into one spreadsheet with a row per transaction.
This year there is a second reason to collect the history. Suncorp Bank's customers are moving to ANZ during 2027, and nothing published so far says what happens to past statements, the eStatement archive or transaction exports after the move. The simplest position is to have what you need on file now, from Suncorp Internet Banking.
What Suncorp Internet Banking Exports, and Where It Stops
Suncorp's business banking FAQ on downloading statements into a file type other than PDF lists four export formats, each with the software Suncorp says it suits:
| Format | Suncorp's description |
|---|---|
| CSV | Microsoft Excel format |
| OFX | Used by Xero |
| QIF | Used by MYOB and Quicken |
| ASCII | Used by customised accounting software |
The limits sit beside the formats. The period for each file must be "no greater than 364 days", so a two-year pull is at least two exports. Suncorp's Internet Banking Help for Businesses puts the reach of the history plainly: "Depending on your account type, you can retrieve up to 2 years of transactions." The transaction list opens on the last 30 days, so widen the date range before exporting, and the export lets you choose the date format. These details come from Suncorp's business banking pages; a personal account holder should check the window their own Internet Banking offers before relying on it.
When you download Suncorp transaction history for bookkeeping, set each export's range to a BAS quarter or a half-year (1 July to 31 December, 1 January to 30 June) rather than a rolling 364 days. A full financial year runs 365 or 366 days, more than the cap allows. Each file then lines up with a period you will report on, and nothing falls into a gap or overlaps between two files. Pick one date format and use it for every export, or the files will not sort together once they are combined.
The statements themselves are a separate archive. Suncorp's eStatements FAQ says eStatements "issued since 1 July 2013" are available in Internet Banking and the app, and that statements from before then are sent free of charge on request by secure message. Bendigo Bank splits the two archives differently, with 18 months of transactions to export and seven years of PDFs, so converting Bendigo, Adelaide Bank and RACQ Bank statements to Excel relies on the PDFs for anything past that window.
An export and a statement are not the same document. The CSV is a list of transactions for the dates you chose. It does not carry the statement period, and it does not carry the opening and closing balances the bank printed, which are the figures a reconciliation ties to. Every Australian bank draws the line between export and PDF in its own place, as the guide to Commonwealth Bank statements to Excel shows for CommBank. St.George, Bank of Melbourne and BankSA show only about three months of transactions online, so turning St.George group statement PDFs into Excel becomes the main route much sooner there.
When the PDF Statements Are the Record, and How to Convert Them
Everything older than the export window exists only as PDF statements, and that covers more work than it sounds:
- Periods older than the export window. A catch-up on a business that has not been reconciled for three years, an amended prior-year return, a loan application that wants several years of history, or a tax file that needs Suncorp eStatements older than two years.
- A client who sends PDFs, not a login. Most bookkeepers receive statements, not Internet Banking access, and the PDFs are what they have to work from.
- Years of quarterly statements. A business on quarterly statements can have twenty or more of them for a five-year run, each one a separate PDF.
- What the export leaves out. Each statement's period and its printed opening and closing balances, which are the anchor for a reconciliation and what a reviewer expects to see.
The spreadsheet to aim for
One row per transaction, with the date, description, debit, credit and running balance, and the statement period on every row. With the period on each row, any transaction traces back to the statement it came from, and a year's worth of statements can be filtered back down to one when a query comes in.
Then check the result the way the statements check themselves. For each statement, the opening balance plus credits minus debits should equal the printed closing balance. Across statements, each closing balance should equal the next statement's opening balance. A missing page or a missing statement shows up as a break in that chain, which is far easier to find in a spreadsheet than by flicking through PDFs.
Layouts that change across a long run
Statements collected over several years do not always share one layout. Some show debits and credits in separate columns, others a single signed amount; dates can be written out on one and in numbers on another. The output has to flatten all of that into one column set and one date format across the whole batch. Otherwise SUMIFS formulas miss rows, dates stored as text sort alphabetically rather than by date, and an accounting import rejects the file. Copying and pasting from the PDF does not get there: multi-line descriptions split across cells, and each page break restarts the cleanup.
Converting a batch
Our extraction assistant is built for this job. Upload the Suncorp PDFs as you have them, digital or scanned, several years of statements as one task (up to 6,000 files), and say in plain words what the spreadsheet should look like: one row per transaction, the columns you want, and the statement period and printed balance on each row. An empty prompt box also offers ready-made prompts for bank statements that set up one row per transaction, which you can adjust and save to your Prompt Library for the next client with Suncorp statements. The results download as Excel, CSV or JSON, with the same columns and formats for every statement in the batch.
Each row carries a Source File column naming the file and page it came from. A value or a row the panel of AI agents cannot agree on is flagged as Review Needed, with what to check, so you look at those rows first instead of rereading every statement, and a page that cannot be processed is reported rather than skipped in silence. If you are weighing tools to convert bank statement PDFs to Excel, that combination is what keeps a balance check across forty statements manageable: the balance chain tells you whether anything is missing, and the source column tells you where to look when a figure needs checking.
Suncorp Bank's Move to ANZ: What Is Published About Your Statement History
ANZ completed its purchase of Suncorp Bank in 2024, and the customer move is now scheduled. Suncorp Bank's announcement of the move to ANZ, dated 7 September 2026, says its 1.2 million customers, brokers and aggregators will move to ANZ's banking products, services and digital platforms by June 2027.
The rest of what is published comes from two pages. Suncorp's Move Hub sets out the phases: understanding the move from September 2026, getting ready with detailed move information at the end of 2026 and early 2027, and the move itself during 2027. ANZ's Suncorp Bank move page adds that Suncorp Bank customers "can't delay or opt out of the move to ANZ".
What none of these pages says, as of November 2026, is anything about past statements, the eStatement archive, transaction-history exports or bank feeds after the move. The Move Hub says more information will be shared in the coming months.
Suncorp's eStatements FAQ says the holder of a closed account can still find eStatements in Internet Banking, as long as their online banking has not been deactivated.
The practical step is the one a careful bookkeeper takes before any change of bank. While Suncorp Internet Banking is in front of you:
- Download the eStatements for every period the business may need. The ATO generally expects business records to be kept for five years, and a catch-up, an amendment or a lender can reach back that far.
- Run the CSV or OFX exports the two-year window allows, one file per quarter or half-year, each 364 days or less.
- Convert the PDFs for the older periods into the spreadsheet described above, and keep the PDFs beside it as the source documents.
Done that way, the Suncorp Bank statements from before the move to ANZ sit in your own files, whatever ANZ later publishes about its archive.
Example: The 2026-27 Financial Year on Two Banks' Statements
The Australian financial year from 1 July 2026 to 30 June 2027 contains the whole move period. Any business whose accounts move to ANZ in 2027 will have that year's transactions on two banks' statements: Suncorp's up to its move date, ANZ's after it.
Take a quarterly GST payer. The September and December 2026 quarters sit entirely on Suncorp statements. Whenever the accounts move in 2027, the March or the June quarter will usually straddle the move, so one BAS period needs transactions from both banks, and the year-end reconciliation needs the full twelve months in one place.
Build the year as one spreadsheet with one column set for both banks:
| Column | What it holds |
|---|---|
| Bank | Suncorp or ANZ |
| Statement period | As printed on the statement the row came from |
| Date | One format for every row |
| Description | The transaction narrative |
| Debit / Credit | Separate columns, or one signed amount, but the same choice throughout |
| Balance | The running balance as printed |
The join is where the check matters most. Check that the closing balance on the last Suncorp statement is accounted for on the first ANZ statement for the same account, whether it appears as the opening balance or as a transfer in. If it is, the year is continuous. If there is a difference, explain it before lodging: a transaction processed across the move date, or a statement missing on either side of the join, is the usual cause.
For the ANZ side, the guide to converting ANZ bank statements to Excel covers ANZ's own exports and statements. In our extraction assistant, the Suncorp and ANZ PDFs can go into the same task, with the prompt asking for the bank and the statement period on each row, and both come back in the same columns and formats. Once the year's transactions are in one file and reconciled, the BAS work follows the usual route, set out in the guide to preparing BAS from Xero.
Getting Suncorp Transactions into Xero or MYOB
Inside the export window, Suncorp has already matched the formats to the software: OFX for Xero, QIF for MYOB. Those exports, or a bank feed where the account has one, are the direct route for recent periods.
The converted spreadsheet is for what they do not reach: history older than two years, or a period before a bank feed was connected. Treat it as a staging file, and import it a period at a time so each import can be checked against the statement's closing balance. The two packages take it differently. Xero's manual statement import accepts a CSV, so the spreadsheet saved as CSV in Xero's column layout, with one date format throughout, goes straight in. MYOB's bank statement import does not take CSV or Excel, so the spreadsheet is the step before a QIF or OFX file for MYOB. In both cases the spreadsheet feeds the import; nothing posts into the ledger for you.
The step-by-step for each package is in the guides to importing bank statements into Xero and importing bank statements into MYOB, including the formats each one accepts and how to avoid importing a period twice when a bank feed already covers part of it.