COMMBANK SMART ACCESS · PAYID AND BPAY
commonwealth bank statement example
A Commonwealth Bank statement reports in Australian dollars against a BSB and account number, with fast PayID transfers and BPAY bill payments sitting alongside everyday card activity. This guide covers reading those and keeping identifiers intact. This commonwealth bank statement example is an invented Smart Access month in Australian dollars, where a PayID transfer names an email address and a BPAY row carries a biller code and customer reference.
Download an authentic Commonwealth statement
In the CommBank app, open the account, Manage, then View statement. In NetBank, choose View accounts, then Statements.
Commonwealth official statement instructions ↗
Identify the account before the activity
The BSB and account number at the top of the statement identify which account produced it. Where you hold an everyday account, a savings account and a credit card, three documents arrive for the same month and the only reliable way to keep them apart afterwards is the identifier plus the period.
Record both in your extraction. The BSB is text, not a number: leading zeros are common and a numeric import destroys them without warning.
Fast transfers identify people, not accounts
A payment addressed to a PayID resolves to a phone number, email address or business identifier rather than a BSB and account number. The counterparty on the statement therefore appears in a different form from a traditional transfer, and a short message from the sender may be attached.
That message is frequently the only description of the payment's purpose, so capture the description field in full rather than truncating it to a recognisable name.
Bill payments and recurring arrangements
BPAY payments carry a biller code and a customer reference; direct debits recur under authorities you granted, with amounts that may vary between collections. Both are numeric-looking fields that spreadsheets mishandle, and both are worth preserving as text.
Listing the recurring arrangements once gives you a checklist for every later statement, which is the quickest way to notice a cancelled or duplicated authority.
Card purchases and the period boundary
Card purchases post after authorisation, which means a purchase made in the final days of the statement period can appear in the next one. This is the most frequent reason a customer believes a transaction is missing, and the fix is simply to check the following statement before investigating further.
Reconcile on the posting dates printed on the statement; add the purchase date in a separate column if your reporting needs it.
Running balance as a continuous audit
Where a balance is printed after each transaction, recompute it from the opening figure as you read. The first row where your figure and the printed one diverge is where the extraction went wrong, which turns an unexplained total into a single row to inspect.
Without that column, a failed reconciliation tells you only that something is wrong somewhere in the period.
Downloading CommBank statements from NetBank
Three CommBank products mean three separate requests for the same month. A statement is a closed document with opening and closing balances; a transaction list on screen keeps changing and cannot be reconciled.
Keep the PDF with any spreadsheet derived from it.
Fast payments in this commonwealth bank statement example
The identifier rows come first because three CommBank products in one month are easy to confuse later.
| Field | Why it matters here |
|---|---|
| BSB and account number | Account identification; both stored as text |
| Statement period | 02 Mar to 01 Apr on the specimen |
| Opening balance | A$3,015.62 on the specimen |
| PayID transfers | Counterparty identified by phone, email or business ID |
| BPAY biller code and reference | Numeric fields that must stay text |
| Direct debits | Collected by the payee under your authority; the amount may differ each time |
| Running balance | Row-by-row check on the extraction |
Once BSB and BPAY fields are stored as text, check:
- No identifier lost a character between the PDF and the sheet
- Transfer messages were captured in full, not truncated to a name
- A seemingly missing purchase was checked against the next statement first
National Australian conventions versus CommBank's own
Comparing another Australian bank shows which conventions are national and which are the bank's own. The Australian payment schemes above are documented by AusPayNet, the Australian payments industry body.
With the document saved locally, the Excel converter and CSV converter handle conversion and the extraction guide the checks.
Commonwealth Bank statement example: PayID and BPAY numbers
What are the two numbers on a CommBank BPAY row?
The first is the biller code, which identifies the organisation; the second is your customer reference with that organisation. Store both as text so leading zeros survive.
How do I work out the purpose of a transfer?
Read the description: a sender can attach a short message, and that is frequently the only record of why the payment was made.
Why would a purchase be missing from this statement?
It most likely posted after the period closed. Check the next statement before investigating.
What should I do with the BPAY reference?
Keep it as text. It identifies which of your accounts with a biller the payment was applied to.
Why does a CommBank transfer show an email address instead of a name?
It was sent to a PayID registered to that email. The receiving bank resolves the PayID to an account, but the statement keeps the identifier you used.