AP approval software does one thing at minimum: it routes invoices to the right person before payment is authorised. Most platforms on the market do this. The distinction that matters for Australian industrial businesses is what happens alongside the routing — whether the software enforces authority limits, validates supplier details, detects duplicates, and produces an audit trail that records the controls applied, not just the outcome.
Over 40% of AP teams identify the approval step as their single biggest processing bottleneck, according to APQC’s Accounts Payable Operations Management Research. The bottleneck is rarely the routing itself. It is the manual work that sits around it — chasing missing information, resolving mismatches, and handling the exceptions that a basic routing tool has no mechanism to flag upstream.
This article covers what to look for in AP approval software beyond routing, the controls that matter most for Australian businesses, and where the gaps in native accounting platform approvals sit.
What “basic routing” actually means
Every accounting platform includes some form of bill approval. Xero allows you to designate approvers who must confirm a bill before it is published to the ledger. MYOB has equivalent functionality. For a small business with one approver and low invoice volumes, this is adequate.
Basic routing means: the invoice arrives, it is assigned to an approver, the approver clicks approve or reject, the decision is logged. That is the full scope.
What it does not mean: the system checked whether the approver had authority to approve that dollar amount. Whether the supplier’s bank account details match the last payment. Whether an identical invoice was submitted and approved three weeks ago. Whether the invoice matches the purchase order raised for this supplier.
Routing is a feature. Financial controls are the outcome. They are not the same thing, and conflating them is how businesses end up with an approval process that generates a paper trail without actually reducing risk.
The threshold enforcement gap
Dollar-value thresholds are one of the most basic governance controls in any accounts payable function. The idea is straightforward: invoices below $5,000 can be approved by a department manager; above $5,000 requires the financial controller; above $20,000 requires the CFO or a director.
The ATO requires that authorised signatories have documented, written authority specifying scope and duration — and for large payments, dual approval is expected. ASIC holds directors personally liable for financial outcomes even when approval authority has been delegated.
The gap in basic routing tools: they route invoices to whoever is configured as the approver. They do not check whether the approver’s delegated authority covers the amount on the invoice. A project manager set up as the default approver will receive and be able to approve a $45,000 subcontractor invoice even if their delegation limit is $10,000. The invoice gets approved. The audit trail shows an approval. The control was not enforced.
AP approval software with threshold enforcement blocks this. It routes each invoice to the approver appropriate for that amount, and it rejects an approval attempt by someone whose authority does not cover the value. The threshold rules are applied automatically — not by the approver’s judgment, and not by whoever configured the invoice that day.
Vendor bank detail validation
Payment redirection fraud cost Australian businesses AU$152.6 million in 2024 — a 66% increase on the prior year, according to the ACCC. The mechanism is specific: an attacker intercepts or spoofs supplier email correspondence and issues a fake invoice (or modifies a legitimate one) with altered bank account details. The invoice looks correct. The approver approves it. The payment goes to the wrong account.
The approval step does not catch this. An approver reviewing an invoice from a familiar supplier, for a familiar amount, will not notice that the BSB has changed. The control that catches it is automated comparison of current bank details against historical payment records — a check that runs before the invoice enters the approval queue, not at the moment of approval.
Basic routing tools do not perform this check. Dedicated AP approval software should.
For construction, wholesale, and distribution businesses — the sectors the ACCC specifically identifies as most frequently targeted due to high transaction values and frequent invoicing — this is not an edge-case risk. It is the most common mechanism through which significant AP losses occur.
Duplicate detection before the queue
The average organisation overpays approximately 0.5% of total AP spend due to duplicate invoices and misdirected payments, according to Ardent Partners and IOFM benchmarks. For a business spending $5 million annually on supplier invoices, that is $25,000 in recoverable overpayments — and recovery depends on supplier goodwill, not legal right.
Duplicate detection in basic routing tools typically runs at the ledger level: the accounting system flags if it sees the same invoice number from the same supplier in the same period. By that point, the invoice has already been through the approval workflow. The approver has already spent time on it.
Effective AP approval software catches duplicates at intake — before the invoice enters the approval queue. The check runs against invoice number, supplier, amount, and date. Flagging happens at the point where it is cheapest to resolve: before a human has reviewed the invoice, not after.
Audit trail depth
ASA 240 (the auditing standard covering fraud responsibilities) and ASA 315 (control environment assessment) both treat documented approval authority and segregation of duties as baseline expectations in an AP function. When an auditor or the ATO requests evidence that a payment was authorised appropriately, “someone clicked approve” is not sufficient. The record needs to show the authority behind the approval, what was checked before it, and how exceptions were resolved.
A useful test: ask any AP approval software vendor to show you what the audit trail looks like for a single invoice. Does it record:
- Who approved, and when
- What dollar amount was authorised
- What the approver’s delegation limit was at that time
- Whether the supplier’s bank details were validated
- Whether a purchase order match was confirmed or an exception was raised
- How that exception was resolved, and by whom
If the audit trail records only the approval event — not the pre-approval verification — it satisfies the appearance of control without the substance.
PO matching and exceptions
Two-way PO matching confirms that the invoice amount, supplier, and line items align with the purchase order raised before the goods or services were ordered. Mismatches — an invoice for $12,000 against a PO for $10,000, or a quantity that differs from what was received — need to be resolved before payment, not after.
Basic approval routing passes this responsibility to the approver: the approver sees the invoice and (manually) checks it against the PO if they remember to. AP approval software with integrated PO matching surfaces the mismatch automatically before the approver sees the invoice, so the approver is making a decision about an exception — not performing the comparison themselves.
For construction businesses managing progress claims against subcontract agreements, and for wholesale distributors matching delivery notes against materials invoices, manual PO matching at the approval stage is the norm and the bottleneck. Automating it upstream means the approval queue contains only invoices that are already verified — not invoices that need verification.
What the best AP approval software actually looks like in practice
A financial controller at a Brisbane wholesale distributor processes 80 invoices per week across 40+ suppliers. Before implementing structured AP approval software, the workflow was: invoices arrived by email, were manually entered into Xero, forwarded to the relevant manager for approval, and paid on the standard run.
Three problems were visible but not measured. First, the warehouse manager was approving invoices above his delegation limit — no system stopped him. Second, a supplier’s bank account changed twice in six months; both were legitimate updates, but neither was flagged — the controller found out after payment, both times. Third, a freight supplier submitted the same invoice twice in the same month; it was caught by the controller during reconciliation, not before payment.
Each of these is a process gap, not a staffing gap. The controller was competent. The approvers were diligent. The process had no mechanism to enforce threshold limits, flag bank detail changes, or detect duplicates before they reached the queue.
The relevant question when evaluating AP approval software is not “does it route invoices?” Every tool does that. It is: which of these gaps does it close, and where in the workflow does it close them?
Checklist: evaluating AP approval software
Before committing to any platform, work through these questions with the vendor:
Threshold enforcement
- Does the system enforce approval limits by dollar amount automatically?
- Does it block approval by someone whose delegation does not cover the invoice amount?
- Can different thresholds be configured by cost centre, entity, or supplier category?
Vendor validation
- Does the system compare supplier bank details against historical records on every invoice?
- Does a changed bank account number generate a hold, or just a note?
- Is the validation step recorded in the audit trail?
Duplicate detection
- Does duplicate detection run before the invoice enters the approval queue?
- What fields does it check — invoice number only, or supplier, amount, and date combined?
PO matching
- Does PO matching occur at the line level or only at the invoice total?
- What happens when a mismatch is detected — does the invoice stop, or is it flagged for the approver to decide?
Audit trail
- Does the trail record what was checked before approval, not just that approval occurred?
- Is it exportable in a format suitable for ATO review or external audit?
Integration
- Does the platform publish directly to Xero or MYOB, or require manual re-entry?
- Does coding and supplier history carry across the integration, or is it lost at the seam?
Where native accounting platform approvals fall short
Xero’s native bill approval requires invoices to be entered into Xero first — which means the supplier data is already in the system before any validation occurs. Approval routing is basic: approve or reject, with no threshold enforcement and no vendor validation layer.
MYOB’s approval functionality has similar scope. Both platforms are designed to record financial data accurately. Neither was designed to manage the control process that sits before the data is recorded.
This is not a criticism of either platform. It reflects their purpose: they are accounting systems, not AP control platforms. For businesses where invoice volume, supplier diversity, and payment values make the gaps material, a dedicated AP automation platform sitting in front of the accounting system closes those gaps without requiring a change to the ledger itself.
The verdict
AP approval software ranges from basic routing tools to full pre-approval control platforms. The right level for your business depends on invoice volume, number of approvers, and the specific risks that manual approval has failed to catch.
At the minimum, look for threshold enforcement and an audit trail that records pre-approval verification. Add vendor bank detail validation if invoice values are significant or if your business operates in construction, wholesale, or distribution — sectors where payment redirection fraud is most prevalent. Add PO matching and duplicate detection before the queue if volume is high enough that manual checking is unreliable.
Basic routing is table stakes. The controls around it are what determine whether your approval process is governance in name or governance in practice.
Also reading: Invoice Approval Software: Native vs Dedicated Tools · How to Implement Purchase Order Matching in AP Workflows · Best AP Automation Software Australia 2026