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 - reasonable questions, none of which happen to capture the specific compliance and fraud risks that Australian finance teams are actually managing.
The result is predictable: businesses buy software that handles invoices well in a generic sense but creates gaps in exactly the areas the ATO cares about. This guide covers eight evaluation criteria that are actually relevant to Australian context, and what to ask vendors before you commit.
Why do standard AP evaluation criteria miss ANZ requirements?
A generic feature checklist will cover document capture accuracy, approval workflow configurability, ERP integration, and price. None of those are wrong - they’re just incomplete.
The gaps show up in four specific areas. Australian GST operates differently from European VAT: line-level treatment, BAS reporting, and mixed-GST invoice handling are not automatically addressed by platforms designed for other markets. ABN validation via the ATO’s ABR is a uniquely Australian requirement with no equivalent in most offshore frameworks. Peppol eInvoicing adoption is further advanced here than in comparable markets, so readiness for structured invoice exchange is increasingly a functional requirement rather than a roadmap item. And BECS and PayTo payment rails require specific handling that many overseas platforms don’t support natively.
None of this appears in a standard feature comparison from a US SaaS review site.
The 8 Evaluation Criteria That Matter
1. GST Line-Level Accuracy
This is the one most commonly glossed over in demos, and it’s where BAS errors actually originate.
A subcontractor invoice in construction might include labour (GST-inclusive), materials (GST-inclusive), and a retention release - potentially treated differently depending on the contract structure. Each line needs the correct tax code. Platforms that extract GST codes from the document using OCR will replicate whatever the supplier printed. That’s fine when the supplier gets it right. When they don’t, the error goes straight to your BAS.
Platforms that apply GST treatment based on supplier history and flag inconsistencies give you a material accuracy improvement. Ask the vendor to show you what happens when a line-level GST treatment differs from what the platform expects based on that supplier’s prior invoices. If they can’t demonstrate that in real time, the feature probably isn’t as developed as the product page suggests.
2. ABN Validation
The ATO’s ABN Lookup allows real-time validation of supplier ABNs. For Australian businesses, paying a supplier with an inactive or cancelled ABN can affect your ability to claim input tax credits - and it can also be a signal you’re dealing with a fraudulent or non-existent entity.
AP automation platforms should validate ABNs automatically at invoice intake, not only during supplier onboarding. Supplier ABN status changes. A supplier who was active when you onboarded them two years ago may have cancelled their ABN, changed entity structure, or had their registration suspended. The check needs to run on every invoice.
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 useful question is what that integration actually covers. A shallow integration pushes a header-level bill into the accounting system - total amount, supplier name, done. A deep integration publishes line-level data with account codes, GST treatments, cost centres, and job codes correctly assigned, ready for review without further manual work.
For MYOB specifically, confirm the integration handles the jobs and categories structure used in MYOB AccountRight. A lot of platforms claim MYOB compatibility but only test against Essentials, which has a different data structure. If your business uses AccountRight for job costing, that distinction matters.
4. Peppol eInvoicing Readiness
The Australian Government’s eInvoicing mandate requires Commonwealth agencies to be capable of receiving Peppol eInvoices. Peppol enablement through the ATO’s access point infrastructure means businesses can now exchange 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 at all - which eliminates the largest category of data extraction errors. For businesses that supply or buy from government agencies, or from large corporate suppliers moving toward Peppol compliance, this is a practical requirement. Not a future one.
5. Vendor Bank Detail Validation and BECS
Payment redirection fraud cost Australian businesses AU$152.6 million in 2024 according to the ACCC’s National Anti-Scam Centre, making fraud vulnerability in accounts payable a critical concern. Once a payment is initiated via BECS, reversal isn’t guaranteed. This is the scenario where “we’ll fix it next time” becomes “we’ve already lost that money.”
AP automation platforms should automatically compare the bank account number on each incoming invoice against the account stored for that supplier. 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, every time. Not just on new suppliers.
6. Multi-Entity Support
Many Australian businesses operate across multiple entities: related companies, trading trusts, joint ventures, operations with separate ABNs. AP automation platforms vary significantly in how well they handle this.
Ask 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 authority matrices for each. A platform that requires separate logins or configurations for each entity creates management overhead that partially offsets the automation benefit. This comes up more than vendors tend to acknowledge during a sales process.
7. Audit Trail Quality
An audit-ready approval matrix requires that the audit trail record every action 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. It should be immutable - a user shouldn’t be able to delete or edit entries.
For businesses subject to ATO audit, this is evidence that correct controls were applied before payment. For businesses with documented delegation-of-authority policies, it’s the mechanism that demonstrates compliance with that policy. Ask the vendor to show you a real audit trail entry for an invoice where an exception was flagged and overridden. The answer to that request tells you a lot about whether the feature is production-ready or exists only to pass a checklist.
8. Pricing Transparency in AUD
Software priced in USD introduces monthly variability into a cost that should be predictable. Vendor pricing pages that show AUD figures but calculate based on a USD conversion rate can change your actual monthly cost without any change to your subscription.
Ask whether firm AUD pricing is available, whether setup fees are included or separate, and whether the pricing model aligns with how your invoice volume actually works. A per-document model can look cheap at low volumes but becomes expensive at scale. A flat monthly model provides cost predictability regardless of volume peaks. Neither is universally better - it depends on your volume pattern.
What to Ask at Vendor Demos
A vendor demo defaults to the platform’s strengths. These questions surface the areas that matter for Australian compliance.
- 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’d 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, what’s the timeline?
- Show me the audit trail for an invoice where a user overrode an exception flag. What’s recorded, and can any part of that record be edited?
- What’s the AUD price for our invoice volume, and does that figure change if we add a second entity?
If a vendor can’t answer those questions in a live demo - not from a slide deck, not “I’ll follow up with that” - that tells you something about how mature those features actually are.
Evaluation Criteria Summary
| 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 Framework
Weight these criteria based on your actual risk profile, not a generic evaluation template.
A business that’s experienced a payment redirection attempt should put bank detail validation at the top of the list. A business with complex subcontractor invoice mixes - particularly in construction - should weight GST line-level accuracy. A business supplying government agencies should prioritise Peppol readiness. Not every criterion applies equally to every business, but all of them apply to someone in the Australian market, and none appear in a generic SaaS evaluation template from an overseas review site.
For a broader look at how AP automation fits into the finance stack, the invoice processing automation overview covers the full workflow from capture through to ledger publication. Businesses evaluating AP controls specifically will find the validation and exception review page useful for understanding what structured exception handling looks like in practice.
Sector-specific considerations are covered separately for construction, distribution and wholesale, and manufacturing - each of which has distinct invoice mix and compliance characteristics that affect how these criteria should be weighted.
Further reading: Best AP Automation Software Australia 2026 · Accounts Payable Software Australia: Buyer’s Guide · The Final Decisive Comparison of Invoice Processing Automation Software