Invoice approval software spans a wide range: from the basic bill approval built into Xero to dedicated third-party workflow platforms that add supplier validation, PO matching, and exception flagging on top. Xero’s native approvals are free and work well for simple routing. Where they fall short is any scenario involving value-based thresholds, supplier verification, or duplicate detection - which is exactly the territory where AP risk is highest. Understanding what each approach actually covers helps you choose the right level of control for your business, rather than discovering the gaps during an incident.
Xero native approvals vs third-party workflow tools: what each covers
Capability | Xero native approvals | Third-party approval tools |
|---|---|---|
Bill routing to nominated approver | Yes | Yes |
Multi-step approvals with conditional routing | No | Yes |
Value-based approval thresholds | No | Yes |
Supplier bank detail verification | No | Yes (in control-layer tools) |
Duplicate invoice detection | No | Yes |
Two-way PO matching at line level | No | Yes (in full AP automation tools) |
GST exception flagging | No | Yes |
Line-item coding by supplier history | No | Yes |
Full audit trail with supplier data at approval | Partial | Yes |
Multi-entity management | No | Yes (in some tools) |
Setup complexity | Low | Low to medium |
Monthly cost | Included in Xero subscription | Additional subscription required |
What Xero native approvals actually do
Xero’s bill approval is built into every subscription tier that supports bills. When a user submits a bill for approval, it moves to ‘Awaiting Approval’ status and the nominated approver receives a notification. The approver can review the bill, approve it, or send it back to draft.
That covers the mechanics of routing. What it does not 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.
Where third-party tools make the difference
A financial controller at a Melbourne wholesale distributor running Xero was processing around 55 invoices a week. Their 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 did not 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. The meaningful differences are:
Conditional routing by value. Most dedicated approval tools allow you to define rules: invoices under $5,000 go to the operations manager, invoices above go to the CFO. Xero does not enforce these rules within the platform - they exist as documented policies that rely on human memory to apply.
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.
Duplicate detection. Third-party tools compare incoming invoices against existing bills in your accounting system 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 the approver’s stated rationale at the moment of approval - creating a record that holds up to scrutiny if a payment is later disputed.
The Dext plus ApprovalMax combination: what it solves and what it costs
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 does not.
The trade-offs are worth understanding:
Two separate subscription costs for functionality that some platforms deliver in one
Context loss between tools: supplier coding decisions made in Dext do not automatically inform the approval logic in ApprovalMax
Dext’s line-item handling is designed for extraction, not for industrial businesses where each invoice line maps to a different account and GST treatment
ApprovalMax does not resolve the supplier bank detail verification gap - it manages the approval workflow, not the validation step before it
For businesses where invoice complexity is low and the primary need is conditional routing, the Dext-plus-ApprovalMax combination is a reasonable fit. 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.
What invoice approval software should actually do at the control layer
Whether you are evaluating Xero native approvals or a dedicated tool, the baseline for genuine AP control includes:
Routing logic that enforces different approval paths based on invoice value, supplier type, or cost centre
Supplier validation that checks bank details against history before the invoice reaches the approver
Duplicate detection that runs before approval, not during payment reconciliation
A full audit trail that captures supplier data at the point of approval
Exception handling that stops anomalous invoices before they reach the ledger
These are the functions that separate a routing tool from a control platform. Xero native approvals deliver routing. Third-party tools vary significantly in how much of the control layer they address.
Governance implications: what the choice affects
The gap between basic routing and a full control layer has three practical implications for Australian finance teams:
Fraud exposure. Payment redirection scams - where a fraudulent invoice arrives with a supplier’s name but changed bank details - cost Australian businesses $152.6 million in 2024, according to the National Anti-Scam Centre. A workflow that does not verify supplier bank details provides no protection against this scenario.
Audit readiness. When a payment is disputed or an audit requires evidence of approval, the record needs to show not just who approved, but what information was presented to the approver at the time. Basic routing tools often cannot provide this.
Segregation of duties. An Adviser-level user in Xero can bypass the approval workflow entirely. If anyone on the team holds Adviser access for reasons unrelated to AP, the approval step is technically optional rather than enforced.
Who each approach fits
Business profile | What fits |
|---|---|
Under 20 invoices per week, single approver, stable suppliers | Xero native approvals with documented manual verification |
20-60 invoices per week, conditional routing needed | Third-party approval workflow tool (ApprovalMax or similar) |
Construction, wholesale, or industrial with PO-based workflows | Full AP automation with integrated validation and PO matching |
Bookkeeper managing multiple Xero organisations | Multi-entity platform that handles approval rules across clients |
Multi-entity groups with complex authority structures | Dedicated platform with multi-entity support |
Questions to ask before choosing
Does the tool enforce value-based approval thresholds inside the platform, or does that rely on documented policy?
What happens when a supplier’s bank details on an incoming invoice differ from the last payment?
Can the approval step be bypassed by any user type in the system?
Does the audit trail capture supplier data at the moment of approval, or only the approval decision?
How does the tool handle duplicate invoices submitted by the same supplier?
Is the tool built for extraction, approval, or both - and what is the integration model between those functions?
Verdict
Xero native approvals are a reasonable starting point for small, stable businesses processing low invoice volumes. They are not adequate as a standalone control for businesses where invoice volumes are growing, supplier lists are expanding, or fraud risk is a genuine operational concern.
Third-party tools vary considerably. Tools focused on conditional routing (like ApprovalMax) address the workflow gaps but not the validation layer. Tools that handle extraction, validation, and approval in a single platform address the full control picture but require a different evaluation conversation.
The question to ask is not ‘does this tool have approvals?’ It is ‘what does this tool do before the invoice reaches the approver?‘
Pulsify’s validation and exception review handles supplier verification, duplicate detection, and exception flagging before bills are published to Xero - which is where the highest-risk moments in AP actually occur.
FAQ
Does Xero have approval workflows built in?
Yes. Xero includes bill approval functionality where invoices can be submitted for approval and approved by nominated users. The native workflow does not include value-based thresholds, supplier bank detail verification, or duplicate detection. These functions require a third-party tool or a dedicated AP automation platform.
Is invoice approval software worth it for a small business?
It depends on invoice volume and supplier risk profile. For businesses processing under 20 invoices a week with a stable, well-known supplier list, Xero native approvals may be sufficient with a documented manual verification process. For businesses above that threshold, or in industries where supplier bank details change frequently, dedicated approval software adds meaningful protection relative to its cost.
What is the difference between ApprovalMax and Xero’s built-in approvals?
ApprovalMax adds conditional routing logic, value-based approval thresholds, and more granular role controls on top of Xero’s native functionality. It addresses the workflow gaps. It does not include supplier bank detail verification or duplicate detection before the approval step - those functions require either a separate tool or a platform that includes the full validation layer.
Can invoice approval software prevent payment fraud?
The most effective fraud prevention happens at the supplier validation stage - before the invoice reaches the approver. Tools that check bank details against historical records and flag changes before routing provide meaningful protection against payment redirection fraud. Tools that only route and approve do not address this risk.
How do you compare invoice approval tools fairly?
Compare at the control layer, not the feature list. The questions that matter: Does it verify supplier bank details before routing? Does it catch duplicates before approval? Does it enforce value thresholds inside the platform? Can any user bypass the approval step? A tool that answers yes to all four is a control platform. A tool that answers no to the first two is a routing tool, regardless of what else is on the feature list.