Most AP software buying decisions start in the wrong place. A finance manager googles “best accounts payable software Australia,” finds a comparison table ranked by price or star rating, and tries to match features to a vague sense of what the business needs. The result is either overspending on enterprise tools for a 30-invoice-a-month operation, or underspending and staying stuck with a process that is breaking in three separate places.
The right starting point is invoice volume. How many supplier invoices does your business process per month? That single number determines which category of solution fits, and which features actually matter versus which ones are noise.
This guide is structured around three volume tiers: under 20 invoices a month, 20–100, and 100–500. Each tier has a different problem profile and a different appropriate solution.
Why Invoice Volume Is the Right Frame
Invoice volume is a proxy for process complexity. At low volume, a single person can manage the whole workflow — receive, code, approve, pay — without anything breaking. At higher volumes, the same manual process develops predictable failure points: missed approvals, duplicates, coding inconsistency, and supplier payment details that change without anyone catching them.
The failure points are not random. They are structural. They appear at roughly the same thresholds regardless of industry. Understanding which tier you are in means you can identify exactly which problems you have, rather than buying software against a vague concern that “our AP process isn’t great.”
Tier 1: Under 20 Invoices a Month
What Xero and MYOB Handle Natively
At this volume, both Xero and MYOB provide adequate tools without any additional software. Xero’s Awaiting Approval queue allows invoices to be held before payment. MYOB AccountRight supports basic bill entry and payment scheduling. A bookkeeper or office manager processing 15–20 supplier invoices a month can manage the full workflow inside either platform without meaningful gaps.
The specific capabilities that are sufficient at this tier:
- Bill entry and coding: Manual entry is fast at this volume. A bookkeeper can code 15 invoices a week accurately without automation.
- Single-step approval: Xero’s approval queue is binary — approved or not. For a business with one approver, this is fine.
- Bank reconciliation: Both platforms reconcile supplier payments against bank feeds reliably.
- BAS preparation: GST is manageable manually at this volume. A single incorrect GST code is easy to catch and fix before the BAS is lodged.
When to Stay Where You Are
If your business receives fewer than 20 invoices a month, processes them through a single approver, and has no history of duplicate payments or supplier fraud incidents, the native tools in Xero or MYOB are the correct answer. There is no business case for additional software at this volume. The AU$27.67-per-invoice processing cost benchmark represents a real cost, but at 15 invoices a month it is a AU$5,000 annual figure — well within the cost of most dedicated AP platforms.
The exception is risk profile. A business in a sector with high BEC (business email compromise) exposure, or one that has already experienced a payment redirection incident, may benefit from bank detail validation even at low volume. But for most Tier 1 businesses, the right answer is to stay native.
Tier 2: 20–100 Invoices a Month
Where Native Tools Break Down
At 20 invoices a month, the manual process starts to show friction. At 50, something predictable has usually broken. At 100, it has definitely broken — the question is just how visibly.
The specific failure points at Tier 2 are consistent across construction, wholesale, and distribution businesses:
Informal approval chains. When invoices need more than one person to approve them, the process defaults to email. One person forwards the invoice, the other replies with approval, and neither Xero nor MYOB records that exchange in a structured way. The audit trail is a forwarded email chain. If the approver is on leave, the invoice sits until someone chases it. Month-end close becomes a search for emails that prove who approved what.
Duplicate invoices. Suppliers resend invoices when they do not receive confirmation of receipt or payment. At Tier 2, a business might receive 3–5 duplicate invoices per month across a supplier base of 20–40 vendors. Without automated detection, duplicates reach the payment queue and get paid. Recovering a duplicate payment requires a credit note process that typically takes two to four weeks.
Manual coding without history. Every invoice coded manually is a decision point. At 50 invoices a month, the same supplier might be coded differently by two different people in the same fortnight — one using a direct cost code, one using an overhead code. The inconsistency compounds across months and creates reconciliation problems at year end.
Bank detail changes that nobody catches. Payment redirection scams work by altering the bank account number on an otherwise legitimate-looking invoice. The ACCC’s National Anti-Scam Centre reported that payment redirection scams cost Australian businesses AU$152.6 million in 2024 — a 66% increase on the prior year. At Tier 2, the manual bank detail check is a glance. It is not a structured verification. That is how a Victorian construction business lost AU$900,000 on a single invoice that arrived from what appeared to be a supplier’s genuine email address.
What an Approval and Validation Layer Adds
The solution at Tier 2 is not full AP automation. It is an approval and validation layer that sits between invoice arrival and the accounting system. This layer needs to do three things:
- Route invoices to the correct approver automatically, based on dollar value, cost centre, or supplier type, without relying on a human to forward an email.
- Detect duplicates at intake, before the invoice reaches the approval queue.
- Flag changed supplier bank details, against the payment history stored for that supplier, before anyone approves the payment.
Tools that cover this profile include configurable approval workflows with threshold-based routing and supplier validation built into the intake step. ApprovalMax handles the approval routing problem well for businesses where DoA (delegation of authority) complexity is the primary concern. Purpose-built platforms like Pulsify cover the full Tier 2 scope: intake validation, duplicate detection, bank detail flagging, and approval routing in a single workflow that integrates directly with Xero and MYOB.
What to Evaluate at Tier 2
| Control | Why it matters at this volume |
|---|---|
| Multi-step approval routing | Single-step Xero approval is insufficient once two or more people sign off on payments |
| Duplicate detection at intake | Suppliers resend; the detection needs to happen before approval, not at reconciliation |
| Vendor bank detail validation | Payment redirection risk is real at this volume; manual checks are unreliable |
| Xero/MYOB integration depth | The platform should publish clean, coded bills to the ledger without a manual step |
| ABN validation | Invalid or inactive ABNs should be flagged before an invoice is approved |
| GST coding consistency | Inconsistent GST treatment at this volume creates BAS amendment risk |
Tier 3: 100–500 Invoices a Month
Why Full AP Automation Is Needed
At 100 invoices a month, the problems that appeared at Tier 2 become structural. They are no longer occasional gaps — they are daily occurrences that consume material finance team time and carry escalating risk. An approval and validation layer is necessary but no longer sufficient on its own.
The additional requirements at Tier 3 are:
Line-level coding. A construction business processing 200 invoices a month receives bills that combine labour, materials, plant hire, and subcontractor fees on a single document. Each line requires a different account code and potentially a different GST treatment. Manual line-level coding at this volume is not sustainable. A platform that applies historical coding patterns at the line level — based on supplier history and line description — removes the per-invoice judgment call and delivers consistent coding to the ledger. See automated line-item coding for how this works in practice.
PO matching at scale. Wholesale and distribution businesses in particular operate with purchase orders for most supplier transactions. At 100-plus invoices a month, manually matching invoice lines to PO lines is a half-day task per week. Two-way PO matching that compares invoice quantities and values against the original purchase order — at the line level, not just the header — surfaces discrepancies before approval rather than after payment.
Multi-entity management. Growth-stage businesses in construction and wholesale often operate across multiple entities — separate ABNs, separate Xero or MYOB files, often with shared suppliers. AP automation at Tier 3 needs to handle a consistent supplier record across entities, so a bank detail change flagged in one entity is visible in another.
Exception handling as a system, not a person. At 300 invoices a month, a finance team cannot triage every invoice individually. The platform needs to concentrate human attention on exceptions — changed supplier details, PO mismatches, amount anomalies, new payees — while routine invoices move through without unnecessary handling. Exception handling built into the workflow is a prerequisite, not a feature.
What Full AP Automation Covers
The capability profile for Tier 3 looks like this:
| Capability | What it replaces |
|---|---|
| Automated line-item coding from supplier history | Manual per-line coding on every invoice |
| Two-way PO matching at line level | Manual cross-referencing of invoices against purchase orders |
| Automated exception flagging and triage | Human review of every invoice before approval |
| Multi-entity AP from a single dashboard | Separate manual processes per entity |
| Configurable DoA enforcement with category-based routing | Email-based approval chains |
| Audit trail with full override history | Email threads and spreadsheets |
At Tier 3, the business case for full AP automation is straightforward. The AU$27.67-per-invoice benchmark applied to 200 invoices a month is AU$66,000 per year in processing cost. A full AP automation platform at this volume typically costs AU$400–$800 per month. The payback period, measured on processing time alone, is typically under three months. That does not include the avoided cost of a single duplicate payment or fraud incident.
What to Look For Regardless of Tier
Three evaluation criteria apply across all volume tiers for Australian businesses:
Xero or MYOB integration depth. Integration with Xero or MYOB is table stakes — every credible platform does it. What matters is integration quality: does the platform publish clean, correctly coded bills to the ledger without a manual step at the join? Does it maintain the supplier record consistently across both systems? Does it support both platforms if the business operates across entities on different software?
GST handling. Australia’s GST framework creates specific problems for AP: mixed GST treatments on a single invoice, GST-free line items alongside taxable ones, and the import GST treatment for overseas supplier invoices. A platform that extracts whatever GST code appears on the document without applying any logic passes errors through to the BAS. A platform that verifies GST treatment against supplier history and flags inconsistencies catches those errors before they compound across a reporting period.
ABN validation. The ATO requires businesses to withhold 47% of payment to suppliers who do not provide a valid ABN. An AP platform that validates supplier ABNs against ATO records at intake surfaces the problem before payment rather than after a BAS lodgement creates the liability.
Audit trail quality. Every exception flag, approval decision, override, and coding change should be recorded with a timestamp and user identity. For ATO and internal audit purposes, the audit trail is the proof that the process was followed. A platform that records only the final approval — without the exception history, override decisions, and approval chain — is not producing a complete audit trail.
Where Pulsify Fits
Pulsify covers Tier 2 and Tier 3: businesses processing 20–500 invoices a month that need approval routing, supplier validation, duplicate detection, and line-level coding in a single integrated workflow. It integrates directly with Xero and MYOB, validates ABNs, flags bank detail changes automatically, and enforces DoA rules at the invoice level. For businesses in construction, wholesale, and distribution where invoice complexity is high, the platform handles the specific line-level and GST problems those sectors produce without requiring a separate extraction tool.
For Tier 1 businesses, native Xero or MYOB is the right answer. For Tier 2 and above, adding a dedicated AP layer is the decision that matters.
Sources
- ACCC National Anti-Scam Centre: Targeting Scams Report 2024
- ATO: eInvoicing for business
- ATO: Withholding if ABN not quoted
- Deloitte Access Economics / ATO: Cost of processing emailed PDF invoices in Australia (AU$27.67 per invoice benchmark)