Xero’s native approval queue works well for what it’s designed to do: flag bills for a nominated approver’s review before they’re posted. The gaps appear when businesses need more than basic flagging - when different amounts should go to different approvers, when supplier details need to be verified before approval, or when a duplicate submission needs to be caught before it reaches the approval queue at all.
Understanding what each approach actually covers is the starting point for choosing the right level of control.
What do Xero native approvals do?
When a user submits a bill for approval, it moves to Awaiting Approval status and the nominated approver receives a notification. The approver reviews the bill, approves it, or sends it back to draft. That covers the mechanics of routing.
What it doesn’t cover: automatically routing bills to different approvers based on value or supplier category; preventing an Adviser-level user from bypassing the approval step entirely; verifying that the supplier’s bank details match the last verified record; catching a duplicate invoice submitted by the same supplier two weeks apart; matching the invoice amount against an open purchase order.
For a business processing ten invoices a week from a stable group of known suppliers, these gaps may be manageable through manual verification. For a growing business with rotating staff and frequent new suppliers, the same gaps represent genuine financial exposure. Understanding the real cost of manual AP makes the case for addressing them early.
The Melbourne wholesale distributor scenario
A financial controller at a Melbourne wholesale distributor was processing around 55 invoices a week. Their Xero approval workflow - submit, notify, approve, publish - worked well for routine bills. The problem emerged when a subcontractor submitted a revised invoice three months after the original, with different line totals and the same invoice number. Xero didn’t flag it. The controller caught it manually only because she happened to be reviewing the original bill the same week.
This is the scenario third-party workflow tools are built for. Xero recorded both invoices correctly. It didn’t compare them. A dedicated AP platform with duplicate detection would have flagged the match at intake and held the second invoice for review before it reached the approval queue.
Where do third-party tools make the difference?
Conditional routing by value. Most dedicated approval tools allow you to define rules: invoices under AU$5,000 go to the operations manager, invoices above go to the CFO. Xero doesn’t enforce these rules within the platform - they exist as documented policies that rely on the AP officer to apply them correctly. Under volume, this relies on memory.
Supplier validation. Tools that include a control layer check incoming invoices against supplier records - flagging when a bank account differs from the last payment, when an ABN doesn’t match the registered supplier name, or when the invoice address is new. Xero performs none of these checks natively. Vendor impersonation and BEC fraud, which cost Australian businesses AU$152.6 million in 2024 according to the ACCC, works specifically by changing the bank details on a legitimate-looking invoice. A workflow that doesn’t compare those details against history provides no protection.
Duplicate detection. Third-party tools compare incoming invoices against existing bills and flag potential duplicates before they reach the approver’s queue. Xero will allow a duplicate bill through if the user doesn’t notice it manually.
Audit trail depth. Xero records who approved a bill and when. More sophisticated tools capture the supplier’s bank details, the invoice data, and whether any exceptions were noted at the moment of approval - creating a record that holds up to scrutiny if a payment is later disputed.
The Dext plus ApprovalMax combination
Many Australian businesses that have outgrown Xero native approvals end up running Dext for invoice capture and ApprovalMax for approval workflows. This combination addresses real gaps - Dext handles OCR extraction well, and ApprovalMax provides conditional routing and approval thresholds that Xero doesn’t.
The trade-offs: two separate subscription costs, context loss between tools (supplier coding decisions made in Dext don’t automatically inform approval logic in ApprovalMax), and ApprovalMax doesn’t resolve the supplier bank detail verification gap. It manages the approval workflow, not the validation step before it. For construction, wholesale, and industrial businesses where line-item accuracy and supplier validation matter, a platform that handles extraction, validation, and approval in a single workflow is worth evaluating against the two-tool stack. Our AP automation software comparison covers the options.
What the choice depends on
For businesses processing under 20 invoices a week with a single approver and a stable, familiar supplier list, Xero native approvals with a documented manual verification process are often sufficient. The controls are procedural rather than system-enforced, but the volume makes that manageable.
For businesses processing 20 or more invoices per week, with multiple people approving, or in industries where supplier bank detail changes are a realistic fraud vector - construction, wholesale, trades - the gaps in Xero’s native approvals are genuine risks, not theoretical ones. A dedicated approval tool or a full AP automation platform that includes the validation layer is the appropriate response.
The question to ask when evaluating isn’t “does this tool have approvals?” It’s “what does this tool do before the invoice reaches the approver?”
Sources: ACCC National Anti-Scam Centre - Targeting Scams Report 2024 · ATO - Record-keeping requirements for business
Further reading: AP Software: What Finance Teams Need That Xero Does Not Provide · Automated Line-Item Coding for Mixed GST Split Invoices · Best AP Automation Software Australia 2026