Accounts payable software automates the routing, review, and sign-off of supplier invoices before payment is made. What most tools miss is the difference between automating a process and controlling it: routing an invoice through an approval chain is not the same as ensuring the right person approves it with the right information in front of them. Before configuring approval workflows in Xero or selecting a dedicated AP platform, evaluate how each option handles exception handling, threshold enforcement, and audit trail integrity, not just how many approvals it can route.
Comparing Your Options Before You Configure Anything
Feature | Xero Native Approvals | Dedicated AP Software (e.g. Pulsify) |
|---|---|---|
Invoice routing | Manual forwarding or basic user permissions | Automated routing based on supplier, amount, and category |
Approval thresholds | Not enforced natively | Configurable thresholds with automatic escalation |
Audit trail | Basic bill history | Full timestamped approval trail with reason capture |
Duplicate detection | None | Automated, pre-approval |
Vendor validation | None | Supplier history comparison, bank detail flagging |
PO matching | Manual | Automated two-way matching before approval |
Exception handling | Manual review required | Flagged automatically before routing |
GST treatment | Manual verification | Auto-applied at line level |
Cost | Included in Xero subscription | Additional subscription, scales with usage |
Setup time | Immediate (limited configuration) | Days to weeks depending on complexity |
This comparison matters because the setup decision is not really about Xero versus something else. It is about whether the controls you need can be enforced within what you already pay for, or whether the gap between Xero’s native capability and what your business requires justifies an additional investment.
What Accounts Payable Software Should Actually Do
Good AP software does not just move invoices from inbox to ledger faster. It enforces the decisions your finance policy requires, consistently, without depending on whoever happens to be processing invoices that week.
That means:
Every invoice is matched to a purchase order before it reaches an approver
Approvals are routed based on configurable rules, not manual decisions
Threshold limits are enforced so invoices above a certain value cannot be approved by someone without the authority to do so
Bank detail changes trigger a verification step, not a direct update
Duplicate invoices are caught before approval, not after payment
Every approval action is timestamped and traceable
When those functions are absent or manual, the approval workflow exists as a process on paper but not as a control in practice.
Evaluation Checklist: What to Look for Before You Commit
Before selecting accounts payable software or committing to Xero’s native approval setup, work through this checklist:
Can approval thresholds be configured per approver, per supplier, or per category?
Are approvals enforced by the system, or can they be bypassed with a manual override?
Is there a full audit trail capturing who approved, when, and with what information visible?
Does the system flag duplicate invoices before they reach an approver?
Are bank detail changes treated as a verification event rather than a routine update?
Is purchase order matching automated, or does the approver have to cross-reference manually?
Can approval rules be applied across multiple entities or cost centres?
Does the system alert when an invoice sits in an approval queue beyond a set timeframe?
Is GST treatment applied automatically, or does it require manual verification at each step?
What happens when the designated approver is unavailable? Is there a delegation mechanism?
Setting Up Approval Workflows in Xero: Step by Step
Xero does not have a dedicated approval workflow module in the traditional sense. What it offers is a user permission structure that, when configured carefully, can enforce a basic approval sequence. Here is how to set it up without creating gaps in your financial controls.
Step 1: Map your approval policy before touching Xero
Before you change anything in Xero, document your approval policy in plain terms. Define:
Which invoices require approval (all of them, or only above a threshold?)
Who can approve at each dollar level
Who covers approvals when a primary approver is unavailable
What documentation must be attached to an invoice before it can be approved
Without this documentation, you are configuring a system around an undefined policy. When something goes wrong, there is no clear standard to compare against.
Step 2: Set user roles to match your approval structure
In Xero, go to Settings, then Users. Assign roles carefully. A user set to “Invoice Only” can create draft bills but cannot approve or pay them. A user set to “Standard” can approve but not pay. A user set to “Adviser” has full access.
For a basic two-step control, assign invoice entry to an “Invoice Only” user and approval to a “Standard” user. The payment function should be restricted to a separate “Adviser” account that the approver does not hold.
This segregation of duties is the most important control Xero’s native structure can enforce. If the person who approves invoices is also the person who processes payments, the control collapses.
Step 3: Build your approval threshold logic
Xero does not enforce dollar-value thresholds natively. A “Standard” user can approve a $5,000 invoice or a $500,000 invoice with the same permissions. This is the most significant gap in Xero’s native approval capability.
There are two practical responses. The first is to define your thresholds in your written approval policy and rely on the approver to flag invoices that exceed their authority. This is a procedural control, not a system control, and it breaks down under time pressure.
The second is to implement an AP automation layer that enforces thresholds before the invoice reaches Xero. A financial controller at a Sydney manufacturing business described the inflection point for her team: once their weekly invoice volume passed 60 bills, the manual threshold check became unreliable. Approvers started approving by memory rather than by checking the policy. The solution was not a new policy. It was a system that prevented approval of above-threshold invoices by anyone below the designated authority level.
Step 4: Configure your approval sequence for the most common invoice types
Group your invoices by category: recurring supplier invoices, one-off purchases, progress claims, and variation invoices. Define who approves each type and what documentation is required at entry.
For recurring suppliers, the pre-approval documentation should be lighter. If a supplier has a clean history and the invoice matches previous patterns, a single approval step is appropriate. For new suppliers, above-threshold invoices, or any invoice where supplier bank details have changed, the approval sequence should require additional verification before the invoice is entered.
Step 5: Set up your audit trail mechanism
Xero logs basic bill history, including when a bill was created and by whom. It does not capture why an approval decision was made, or what information the approver had access to.
For a defensible audit trail, either use Xero’s notes field consistently on every bill (entering the approver’s name, the date of approval, and any relevant reference) or use a dedicated AP layer that captures this automatically. An approval workflow tool that stores timestamped, approver-attributed decisions creates a searchable record that satisfies both internal governance and external audit requirements.
Step 6: Define your exception handling process
What happens when an invoice cannot be approved because something doesn’t match? Define the escalation path in advance. Who receives the exception? What information do they need? How long does the resolution take before the invoice is returned to the supplier?
Exception handling is where most approval workflows break down under pressure. Without a defined path, exceptions sit in queues, approvers override them to clear backlogs, and control failures accumulate quietly until something significant surfaces.
A structured validation and exception review process separates routine invoices from flagged ones before they enter the approval queue. This keeps approval decisions clean and ensures exceptions receive proper attention rather than being cleared by whoever has access.
Step 7: Test your controls before go-live
Before the workflow is live, run three test scenarios: a valid invoice that should approve cleanly, an invoice that should be flagged for threshold reasons, and an invoice with a bank detail change. Confirm that each scenario behaves as your policy requires.
If the threshold test does not trigger an escalation, your control is not working. If the bank detail change is not flagged, your fraud exposure is not addressed. Fix both before the workflow processes real supplier invoices.
Who This Fits and Who It Doesn’t
Scenario | Best fit |
|---|---|
Under 20 invoices per week, single approver, consistent supplier base | Xero native approvals with documented policy |
20-80 invoices per week, multiple approvers, occasional new suppliers | Xero native approvals plus documented threshold policy and manual PO check |
Over 80 invoices per week, multiple entities, frequent new suppliers, or high-value transactions | Dedicated AP software with automated routing, threshold enforcement, and vendor validation |
Construction, wholesale, or healthcare with complex line items | Dedicated AP software with line-item coding and PO matching |
Multiple Xero entities managed by one bookkeeper or accountant | Multi-entity AP software with consistent supplier treatment across entities |
Xero native approvals work well at low volume with a small team that knows each other’s authority limits. As volume increases, the manual elements of the workflow become the point of failure.
Questions to Ask Vendors Before You Commit
Before choosing accounts payable software to layer over or replace Xero’s native approvals, ask:
How does your system enforce dollar-value thresholds? Can a user override an enforcement decision without an audit record?
What happens when an approver is unavailable? Can delegation rules be pre-configured?
How are bank detail changes handled? Does a change trigger a verification step automatically?
What does the audit trail capture? Is it searchable and exportable for external audit purposes?
How is PO matching configured? Does it happen before or after the approval step?
How does your system handle invoices from new suppliers who have no transaction history?
Does your pricing scale with invoice volume, entity count, or user count?
What does onboarding look like? How long before supplier coding history is established?
Avoiding Control Breaks During Transition
The most common mistake when implementing accounts payable software is running the old workflow and the new system in parallel for too long. During the overlap period, invoices can enter the ledger through either path, and the approval controls of one system may not apply to invoices that entered through the other.
Set a firm cutover date and process all invoices through the new workflow from that point. Dual-entry periods create gaps that are difficult to audit retrospectively and can allow invoices to be approved outside the intended control structure.
The goal is not to have a sophisticated approval workflow. It is to have one that actually works when an invoice arrives with a changed bank account number, an amount that exceeds any approver’s authority, or a supplier name that does not match any ABN on record. Pulsify handles these scenarios through automated vendor validation and exception flagging that operates before invoices reach the Xero ledger, preserving the control layer even as volume grows.
Frequently Asked Questions
What is the difference between accounts payable software and Xero’s built-in approval tools?
Xero’s built-in user permissions allow you to restrict who can create, approve, and pay bills, but they do not enforce dollar thresholds, detect duplicate invoices, validate supplier bank details, or match invoices against purchase orders automatically. Dedicated AP software adds these controls as a layer before the invoice reaches Xero, so the ledger receives verified data rather than whatever was entered manually.
Can you set approval thresholds in Xero natively?
Not directly. Xero’s permission levels are role-based, not value-based. A Standard user can approve any invoice regardless of amount. To enforce dollar-value thresholds, you either rely on a documented policy that approvers follow manually, or you implement an AP automation layer that enforces the threshold as a system control. For businesses with defined delegation of authority structures, the latter is more reliable.
Do I need accounts payable software if I already use Xero?
It depends on your invoice volume, supplier complexity, and the financial controls your business requires. If you process fewer than 20 invoices per week with a consistent supplier base and a single approver, Xero’s native tools plus a documented policy may be sufficient. As volume, supplier count, or entity complexity increases, the manual elements of a Xero-only workflow become points of failure.
How long does it take to set up AP software approval workflows?
A basic Xero user permission structure can be configured in under an hour. Dedicated AP software with approval routing, threshold rules, and vendor validation typically takes days to set up and a few weeks to reach full effectiveness as the system learns supplier history. The investment is front-loaded, but it pays back quickly once manual exception handling is reduced.
What should my approval audit trail capture for an Australian finance audit?
At minimum, your audit trail should capture who approved each invoice, when the approval occurred, what the invoice value and supplier details were at the point of approval, and any exceptions that were flagged and resolved. If bank details were changed, the trail should record when, by whom, and whether a verification step was completed. The ATO expects businesses to maintain records that show the business nature of each transaction, which an approval audit trail directly supports.