Every quarter, the same thing happens. The BAS is lodged, the amount is confirmed, and someone in finance logs into the bank portal to make the payment. It’s a manual step in an otherwise structured workflow, and it happens outside every control your business has in place.
The payment itself takes a few minutes. But the context around it, who approved it, which budget it came from, whether it was expected, gets lost the moment it leaves the bank.
For most Australian SMEs, BAS payments are one of the largest recurring outflows. Yet they bypass the approval workflows, budget controls, and audit trails that apply to every other payment.
That’s the gap. And BPAY inside a spend management platform closes it.
How BAS payments typically work today
The ATO accepts BAS payments via BPAY. That part isn’t new. Most businesses already use BPAY to pay their BAS through their bank.
The problem is where the payment happens. When someone logs into the bank portal:
- There’s no approval step before the payment is made
- There’s no link back to the budget it should come from
- There’s no automatic record in the spend management system
- Finance finds out after the fact, if at all
For a payment that can run into tens of thousands of dollars, that’s a significant blind spot.
What changes when you pay BAS via BPAY inside your spend platform
When BPAY is available inside your spend management platform, the BAS payment follows the same path as every other business payment:
- Set up the ATO as a BPAY supplier once. Add the biller code and your reference number. This only needs to happen once.
- Create the payment. Enter the amount from your BAS lodgement.
- Route it through approvals. The payment follows your existing approval workflow, the same one that applies to supplier invoices and other bills.
- Pay with a full audit trail. The payment is recorded against the right budget, with the approver, date, and amount all captured automatically.
No bank login. No separate system. No missing context.
Why this matters for finance teams
BAS payments are predictable. They happen every quarter (or monthly for some businesses). The amount is known after lodgement. There’s no reason they should be treated differently from any other bill.
When BAS payments flow through the same platform as the rest of your spend:
- Visibility improves. Finance can see the payment alongside every other outflow, in real time.
- Budget accuracy improves. The payment is allocated to the correct budget automatically, not reconciled after the fact.
- The audit trail is complete. If anyone asks “who approved this payment and when?”, the answer is already recorded.
- Quarterly admin drops. No more switching between systems to complete a routine payment.
A note on tax obligations
This article covers the payment workflow, not the tax obligations themselves. For guidance on BAS lodgement, GST calculations, PAYG withholding, and other ATO requirements, consult your accountant or registered tax agent. The ATO website also provides detailed guidance on BAS lodgement and payment.
The bigger picture: one payment workflow for everything
BAS is just one of many payments that traditionally happen outside the spend workflow. Utilities, rent, insurance, telecoms, and other BPAY billers all follow the same pattern: someone logs into the bank, makes the payment, and the record lives somewhere else.
When all of these payments flow through a single platform with BPAY, bank transfer, and PayID available side by side, finance teams get a complete picture of where the money is going, before it’s gone.
How to get started
If your business already pays BAS via BPAY through the bank, the switch is straightforward:
- Add the ATO as a BPAY supplier in your spend platform (biller code and reference number from your BAS notice)
- Set up the approval workflow you want for ATO payments
- Next quarter, make the payment from your spend platform instead of the bank
The payment method is the same (BPAY). The destination is the same (ATO). The difference is that now it flows through your controls.
