Most AP automation software evaluations in Australia are built on criteria that originated in the US or UK market. They assess OCR accuracy, processing speed, and ERP integration without accounting for the specific compliance, payment, and tax infrastructure that Australian businesses operate within. The result is that finance teams buy software that handles invoices well in a generic sense but leaves material gaps in the areas that create actual risk in an Australian context.
This guide sets out eight evaluation criteria tailored to ANZ requirements. Each criterion maps to a specific compliance, fraud, or operational risk that Australian finance teams face.
Why Standard AP Evaluation Criteria Miss ANZ Requirements
A finance team evaluating AP software using a generic feature checklist will typically assess document capture accuracy, approval workflow configurability, ERP integration, and price. These are legitimate criteria. They are also insufficient for the Australian market.
The gaps emerge in four areas. First, Australian GST operates differently from VAT in the UK and Europe - the line-level treatment requirements, BAS reporting obligations, and the specific handling of mixed-GST invoices are not automatically addressed by platforms designed for other markets. Second, ABN validation via the ATO’s ABR is an Australian-specific requirement with no direct equivalent in most offshore evaluation frameworks. Third, Peppol eInvoicing adoption is further advanced in Australia than in most comparable markets, meaning readiness for structured invoice exchange is increasingly a functional requirement rather than a future consideration. Fourth, the BECS and PayTo payment rails that underpin Australian bank-to-bank payments require specific handling that overseas platforms may not support natively.
None of these appear in a standard feature comparison table sourced from a US SaaS review site.
The 8 Evaluation Criteria That Matter for Australian Businesses
1. GST Line-Level Accuracy
GST accuracy at the line level determines whether your BAS is reliable or requires regular amendment. An invoice from a construction subcontractor may include labour (GST-inclusive), materials (GST-inclusive), and a retention release (potentially treated differently depending on the contract structure). Each line requires the correct tax code.
Platforms that extract GST codes from the document using OCR will replicate whatever the supplier printed. Platforms that apply GST treatment based on supplier history and flag inconsistencies provide a material accuracy improvement. Ask the vendor to demonstrate what happens when a line-level GST treatment differs from what the platform expects based on prior invoices from the same supplier.
2. ABN Validation
The ATO’s ABN Lookup service allows real-time validation of supplier ABNs. For Australian businesses, paying a supplier without a valid ABN can affect your ability to claim input tax credits on the associated GST. It can also be a signal of a fraudulent or non-existent supplier entity.
AP automation platforms should validate ABNs automatically at invoice intake and flag any invoice from a supplier with an inactive, cancelled, or unregistered ABN. This check should run on every invoice, not only during supplier onboarding. Supplier ABN status can change after onboarding.
3. MYOB and Xero Integration Depth
Integration depth is not the same as integration existence. Most AP platforms claim to integrate with Xero and MYOB. The substantive question is what the integration actually covers.
A shallow integration pushes a header-level bill into the accounting system with a total amount and a supplier name. A deep integration publishes line-level data with account codes, GST treatments, cost centres, job codes, and tracking categories correctly assigned - ready for review without further manual work. For MYOB specifically, confirm that the integration handles the jobs and categories structure used in MYOB AccountRight, not just a flat bill import.
4. Peppol eInvoicing Readiness
The Australian Government’s eInvoicing mandate requires Commonwealth agencies to be capable of receiving Peppol eInvoices. The broader Peppol network in Australia, operated through the ATO’s access point infrastructure, enables businesses to send and receive structured invoice data directly between compliant systems.
For AP automation software, Peppol readiness means the platform can receive structured invoice data from Peppol-enabled suppliers without OCR extraction. This eliminates the largest source of data extraction errors. For businesses with government customers or large corporate suppliers moving toward Peppol compliance, an AP platform that cannot receive Peppol invoices will require a parallel manual intake process.
5. Vendor Bank Detail Validation and BECS
Payment redirection fraud - where attackers alter the bank details on an otherwise legitimate invoice - cost Australian businesses AU$152.6 million in 2024 according to the ACCC’s National Anti-Scam Centre. The Australian financial system processes bank-to-bank payments via the Bulk Electronic Clearing System (BECS), and increasingly via PayTo for real-time payments. Once a payment is initiated via BECS, reversal is not guaranteed.
AP automation platforms should automatically compare the bank account number on each incoming invoice against the account stored for that supplier in the system. If the account has changed, the invoice should be held and flagged before it reaches the approval queue - not after. This check needs to run on every invoice, not only on first-time suppliers.
6. Multi-Entity Support
Many Australian businesses operate across multiple entities - related companies, trading trusts, joint ventures, or interstate operations with separate ABNs. AP automation platforms vary significantly in how they handle multi-entity workflows.
Evaluate whether the platform supports a single dashboard across all entities, whether supplier coding rules and bank detail records are shared or siloed per entity, and whether approval workflows can be configured at the entity level with different DoA matrices for each. A platform that requires separate logins or separate configurations for each entity creates management overhead that partially offsets the automation benefit.
7. Audit Trail Quality
An audit trail in AP automation should record every action taken on every invoice: when it was received, what exceptions were flagged, who reviewed each flag, who approved, whether any override was applied, and when the approved invoice was published to the ledger. The record should be immutable - it should not be possible for a user to delete or edit entries.
For Australian businesses subject to ATO audit, the audit trail is evidence that the correct controls were applied before payment. For businesses with documented delegation-of-authority policies, the audit trail is the mechanism that demonstrates compliance with that policy. Ask the vendor to show a real audit trail entry for an invoice where an exception was flagged and overridden.
8. Pricing Transparency in AUD
Software pricing published in USD is not unusual, but it creates budget ambiguity for Australian finance teams. Exchange rate fluctuations affect the actual AUD cost of a USD-priced subscription. Vendor pricing pages that show AUD figures but calculate based on USD conversion introduce monthly variability into a cost that should be predictable.
Evaluate whether the vendor publishes firm AUD pricing, whether setup fees are included or separate, and whether the pricing model (per document, per month, per user) aligns with your invoice volume pattern. A per-document model may be cost-effective at low volumes but expensive as invoice volume grows. A flat monthly model provides cost predictability regardless of volume peaks.
What to Ask at Vendor Demos
A vendor demo defaults to showing the platform’s strengths. The following questions surface the areas that matter most for Australian compliance requirements.
- Show me what happens when a supplier’s bank account changes on an incoming invoice. What does the platform do automatically, and what does it require from a user?
- How does the platform handle a line on a subcontractor invoice where the GST treatment differs from what you would expect based on that supplier’s history?
- Can you validate an ABN in real time against the ATO’s ABR during the demo? What happens when the ABN is inactive?
- Does the platform currently support receiving Peppol eInvoices? If not, is it on the roadmap and when?
- Show me the audit trail for an invoice where a user overrode an exception flag. What is recorded, and can any part of that record be edited?
- What is the AUD price for our invoice volume, and does that figure change if we add a second entity?
Evaluation Criteria Comparison
| Criterion | What to look for | Red flag |
|---|---|---|
| GST line-level accuracy | Supplier-history-based treatment with exception flagging | OCR extraction only, no verification logic |
| ABN validation | Automatic check against ATO ABR on every invoice | Onboarding-only check, no ongoing validation |
| MYOB integration depth | Line-level coding, jobs, tracking categories, two-way sync | Header-level bill import only |
| Xero integration depth | Line-level coding, tracking categories, two-way sync | Single-direction push, no coding logic |
| Peppol readiness | Can receive structured Peppol invoices natively | No Peppol support, no roadmap |
| Bank detail validation | Automatic comparison on every invoice, holds invoice if changed | Manual check only, or no check |
| Multi-entity support | Single dashboard, shared supplier rules, per-entity DoA | Separate logins or configurations per entity |
| Audit trail | Immutable, records every flag, override, and approval | Approval-only log, no exception history |
| AUD pricing | Published firm AUD pricing, no setup fee surprises | USD pricing only, variable AUD conversion |
Applying the Criteria
A finance team using this framework should weight criteria based on their specific risk profile. A business that has experienced a payment redirection attempt should weight bank detail validation heavily. A business with complex subcontractor invoice mixes should weight GST line-level accuracy. A business supplying government agencies should weight Peppol readiness.
The criteria are not equally relevant to every business. They are all relevant to some Australian businesses, and none of them appear in a generic SaaS evaluation template sourced from an overseas review site.
For a broader look at how AP automation fits into the finance stack for Australian businesses, the invoice processing automation overview covers the full workflow from capture through to ledger publication. For businesses evaluating AP controls specifically, the validation and exception review page covers what structured exception handling looks like in practice.
Businesses with specific industry requirements can also review the sector-specific considerations for construction, distribution and wholesale, and manufacturing - each of which has distinct invoice mix and compliance characteristics that affect how these eight criteria should be weighted.