Why your ATO payments should go through your spend management platform, not your bank

Here’s something that doesn’t get talked about enough: the largest recurring payments most Australian SMEs make have the least oversight.

ATO obligations (BAS, PAYG, GST, income tax) can easily total $100,000 or more per year for a mid-sized business. Yet in most companies, these payments happen in the bank portal, made by whoever has the login, with no approval step, no budget allocation, and no audit trail beyond a line on the bank statement.

Every other payment in the business goes through controls. Supplier invoices get approved. Card spend has budget limits. Bill payments follow workflows. But ATO payments? They just happen.

That’s not a compliance problem. It’s a visibility problem.

The current state: ATO payments live outside your controls

In a typical Australian SME, ATO payments follow this path:

The accountant or bookkeeper lodges the BAS (or other return)
They tell finance “pay $X to the ATO by [date]”
Someone logs into the bank and makes the BPAY payment
The payment appears on the bank statement a day or two later
Finance reconciles it at month-end

At no point in this process does the payment flow through the same approval workflow that applies to a $500 supplier invoice. There’s no pre-payment approval. There’s no budget check. There’s no record of who authorised it or why.

For a $30,000 quarterly BAS payment, that’s a significant gap.

What changes when ATO payments flow through your spend platform

When you route ATO payments through a spend management platform (via BPAY), the payment follows the same path as every other business payment:

Pre-payment approval. The payment is created, and the designated approver reviews and authorises it before the money moves.
Budget allocation. The payment is allocated to the correct budget or cost centre automatically, not reconciled after the fact.
Audit trail. The system records who created the payment, who approved it, when it was paid, and which budget it came from.
Real-time visibility. Finance sees the payment the moment it’s made, not when the bank feed arrives two days later.

The payment method is still BPAY. The destination is still the ATO. The difference is everything that happens around the payment.

3 reasons this matters more than you think

1. ATO payments are large and predictable, which makes them easy to overlook

Because ATO payments are expected, they often get treated as routine. “Just pay the BAS” becomes a standing instruction. But routine doesn’t mean low-risk.

A quarterly BAS of $40,000 is the same size as a major supplier contract. If a supplier invoice for $40,000 arrived without an approval workflow, finance would flag it immediately. ATO payments deserve the same scrutiny, not because the ATO is untrustworthy, but because the business should know who authorised a $40,000 outflow and why.

2. Visibility gaps compound over time

When ATO payments happen in the bank, they create a blind spot in your cash flow picture. Finance can’t see the payment in real time. Budget owners don’t know the money has left. The CFO’s dashboard shows the payment only after reconciliation.

Over a year, a business might make 8 to 12 ATO payments (quarterly BAS, PAYG instalments, income tax, FBT). If each one is invisible for 2 to 3 days, that’s 20 to 36 days of incomplete cash flow data across the year. With all payments flowing through one platform, that blind spot disappears. For businesses managing tight cash positions, that matters.

3. Audit readiness improves without extra work

When an auditor asks “who approved this ATO payment?”, the answer should be immediate. If the payment was made through the bank portal, the answer is “whoever had the bank login that day.” If the payment was made through a spend platform with approvals, the answer is a name, a date, and a record.

This isn’t about adding bureaucracy. It’s about capturing information that’s already part of the process but currently gets lost.

What this looks like in practice

Here’s a practical example for a business that pays BAS quarterly and PAYG instalments quarterly:

Before (bank portal):

Q1 BAS: $35,000 paid via bank BPAY. No approval record. Reconciled at month-end.
Q1 PAYG instalment: $8,000 paid via bank BPAY. No approval record. Reconciled at month-end.
Total: $43,000 in ATO payments with no pre-payment controls.

After (spend platform with BPAY):

Q1 BAS: $35,000 created as a BPAY payment. Approved by the Finance Director. Allocated to “Tax — BAS” budget. Paid and recorded in real time.
Q1 PAYG instalment: $8,000 created as a BPAY payment. Approved by the Finance Director. Allocated to “Tax — PAYG” budget. Paid and recorded in real time.
Total: $43,000 in ATO payments with full approval trail, budget allocation, and real-time visibility.

Same payments. Same amounts. Same BPAY method. Completely different level of control.

The objection: “It’s just the ATO, we don’t need approvals for that”

This is the most common pushback, and it’s understandable. ATO payments feel different from supplier payments because the amount is determined by the tax return, not by a purchase decision.

But the approval isn’t about questioning the amount. It’s about:

Confirming the payment is expected. Did the BAS actually get lodged? Is this the right amount?
Recording who authorised it. For audit purposes, governance, and internal accountability.
Allocating it to the right budget. So cash flow forecasts and budget reports are accurate in real time, not after reconciliation.

The approval step takes 30 seconds. The visibility it creates lasts all year.

A note on tax obligations

This article discusses the payment workflow for ATO obligations, not the tax calculations, lodgement requirements, or compliance obligations themselves. For guidance on BAS, GST, PAYG, income tax, or FBT, consult your accountant or registered tax agent.

Getting started

If your business currently pays the ATO through the bank portal, the transition is simple:

Set up each ATO obligation as a BPAY supplier in your spend platform (biller code and reference number from the ATO notice)
Define the approval workflow (e.g., Finance Director approves all ATO payments above $5,000)
Create a budget category for tax payments so they’re tracked separately from operating expenses
Next quarter, make the payment from your spend platform instead of the bank

The payment still goes via BPAY. The ATO still receives it the same way. The only difference is that your business now has a complete record of every ATO payment, with approvals, budget allocations, and real-time visibility.

Frequently asked questions

Won't this slow down ATO payments?

No. The approval step takes seconds for a payment that’s already expected. And because the BPAY supplier is set up once, creating the payment is faster than logging into the bank each time.

What if our accountant makes the ATO payments on our behalf?

Many accountants lodge the return and instruct the business to pay. With this approach, the accountant confirms the amount, and the business makes the payment through the normal approval workflow. The process is the same, just with better controls.

Does this replace our accounting software for tax tracking?

No. Your accounting software (Xero, MYOB, etc.) still handles the tax calculations, BAS preparation, and lodgement. The spend platform handles the payment workflow: approvals, budget allocation, and audit trail. They complement each other.

Is this relevant for sole traders or micro businesses?

This approach is most valuable for businesses with multiple people involved in finance (approvers, budget owners, bookkeepers). For sole traders who handle everything themselves, the audit trail benefit still applies, but the approval workflow is less relevant.