Many finance teams in Australia and New Zealand shortlist accounts payable software on invoice capture accuracy, then discover the real differences lie elsewhere: whether approvers need an ERP licence, whether supplier bank details are verified against source registers, and how deeply the platform writes back to the finance system. This guide sets out the questions worth asking, and where vendors genuinely differ.
If you are comparing AP automation platforms for an organisation in Australia or New Zealand, most vendor websites will tell you roughly the same thing. They all capture invoices, they all route approvals, and they all claim high accuracy. The differences that decide whether an implementation succeeds are rarely the ones on the feature list.
This guide is written for finance teams that have outgrown manual accounts payable, or an earlier automation tool that no longer delivers the efficiency they expected, but do not need an enterprise spend suite, including local government and not-for-profits. The decision is rarely finance’s alone, so it also covers what IT, procurement and risk will want to know. It does not rank vendors. It sets out what to compare, explains why each question matters, and shows where the market genuinely divides.
We build RapidP2P, an Australian AP and procure-to-pay platform, so you should know that upfront. We have tried to write the guide we would want if we were on your side of the table, and we say where we fit at the end.
What to compare
The questions below are the ones that separate vendors in practice. They are deliberately phrased the way a buyer would ask them rather than the way a requirements document would.
| Question | Why it matters |
|---|---|
| How will invoices get into the system, and what happens when capture is not confident? | Exceptions, not data entry, are where AP teams spend their time. |
| Does matching work line by line, and who can override a mismatch? | Matching on invoice totals alone can hide line-level errors. |
| Can approval rules follow your delegation of authority without custom development, and how granular can they get? | Rules that need professional services become expensive to change. |
| Do approvers need an ERP licence? | Occasional approvers can add significantly to the total cost. |
| How are suppliers and bank details verified before payment? | Changed bank details are how payment redirection fraud works. |
| Will it fit your finance system, and how much writes back automatically? | Integration decides more shortlists than features do. |
| What does the audit trail record, and where is your data stored and processed? | Auditors and IT will ask, whatever finance prefers. |
| What does the AI decide, and what does a person decide? | You need to be able to explain the boundary to an auditor. |
| What will it really cost over three years? | The licence fee is rarely the whole cost. |
How will invoices get into the system?
How do invoices arrive, and in what formats? Ask what happens when capture is not confident, because that is where AP teams actually spend their time. A platform claiming very high accuracy with poor exception handling will cost you more than one that is honest about both.
Ask specifically about Peppol e-invoicing. Peppol is an international network, used across Europe and parts of Asia as well as in Australia and New Zealand, so native support matters wherever your suppliers or customers use it. Some platforms receive Peppol documents natively; others convert them to PDF and read them back, which reintroduces the error the standard exists to remove.
How does matching work?
Two-way and three-way matching are near-universal claims. The useful questions are whether matching works line by line or only on invoice totals, how tolerances are configured, who can override a mismatch, and whether partial deliveries are handled without manual workarounds.
How flexible is approval routing?
Can your delegation of authority be configured without custom development? Check how granular it can be: by dollar threshold, cost centre, project, entity and invoice type. Approval structures are rarely simple, and a platform that needs professional services for every change becomes expensive quickly.
How are approvers licensed?
Licensing models differ, and none is automatically cheaper. Some platforms run inside your ERP and use its user licences; some ERP vendors offer lighter approver or self-service licences for occasional users; and some platforms sit outside the ERP altogether. In an organisation with dozens of budget holders, the difference can be material, so ask each vendor, and your ERP vendor, to price your actual number of occasional approvers.
How are suppliers and payments protected?
Ask how a new supplier is created, and what is checked before they can be paid. Many platforms validate that an ABN (Australian Business Number) or NZBN (New Zealand Business Number) is correctly formatted. Fewer check it against the Australian Business Register or the NZBN Register. Fewer still verify bank account details against the account holder’s name before payment is released.
Payment redirection scams, where a fraudster gets a legitimate supplier’s bank details changed, cost Australians A$166.8 million in reported losses in 2025, according to the ACCC. Supplier bank details deserve more scrutiny than they usually get.
Check where payment actually happens. In Australia and New Zealand most AP platforms hand an approved, coded invoice back to your finance system or bank to be paid, rather than paying suppliers themselves; a few, usually those built for cross-border payments, execute payment directly. Neither is better, but it changes who holds supplier bank details and where the final control sits.
Will it fit your finance system?
Integration is where most shortlists are decided, and where vendor language is least precise. Establish three things: which systems are genuinely supported rather than technically possible; whether data moves in real time or in batches; and how much writes back automatically.
If you run TechnologyOne, Civica Authority, Jobpac or SAP Business One, the field narrows considerably — many platforms marketed in Australia are built primarily around Xero, MYOB, NetSuite or Dynamics.
What will auditors and IT want to see?
Ask what the audit trail actually records. Not whether there is one — there always is — but whether it captures what changed, who changed it, what the value was before, and whether that record can be altered. Ask how segregation of duties is enforced, particularly around supplier creation and payment approval.
Ask where your data is stored at rest and, separately, where it is processed or routed, and what security certifications the vendor holds. The two are not always the same, and some platforms use services outside the country for document processing or AI. For government, local government and many public-sector-adjacent organisations, data residency in a specified country or region is close to a hard requirement, and ISO 27001 or equivalent is usually expected.
What does the AI decide, and what do you decide?
Most vendors in this category are now marketing AI. The useful question is not how advanced it is, but where the boundary sits: which decisions does the system make on its own, and which still require a person?
Both answers can be right for different organisations. What matters is that you can explain the boundary to an auditor. If a platform codes and approves an invoice autonomously, you should be able to see why it did, and be able to show that reasoning six months later. Ask to see that view during the demonstration rather than taking the claim on trust.
Ask separately how your data is used. Some vendors train their models on customer invoice data, some do so only with consent, and some not at all. Whatever the answer, get it in writing rather than in a sales conversation.
What will it really cost?
Compare pricing models, not headline numbers. Per-user pricing rewards small teams and penalises wide approval networks. Per-document pricing scales with growth, which may or may not suit you. Ask what happens to your cost if invoice volume doubles, and get the answer in writing.
The licence fee is rarely the whole cost. The items buyers most often miss are:
- implementation and configuration
- integration work on the ERP side, which may fall to your team or your ERP partner
- ERP licences for approvers, if the platform runs inside your finance system
- non-production environments for testing and training
- data migration and user training
- changes later, when your approval structure or entity list shifts
Ask for these as line items rather than a total, and ask which are one-off and which recur.
Ask who performs the implementation, where they are located, and how many comparable implementations in your market they have completed.
Where the market actually divides
Three fault lines matter more than the rest.
Invoice-only versus full procure-to-pay. Many platforms sold as AP automation begin at the invoice. That processes spend efficiently but does nothing to control it. Platforms covering requisitions and purchase orders can check budget before a commitment is made. If your problem is that spend is already committed by the time finance sees it, invoice automation will not solve it.
Inside the ERP versus alongside it. Products embedded in the ERP inherit its data model and its licensing. Independent platforms avoid the licensing question and work across multiple finance systems, but require a well-built integration. Neither is better in the abstract.
Capture-led versus process-led. Some vendors come from document capture and added workflow. Others come from finance process and added capture. It usually shows in how they handle exceptions, approvals and controls.
Choosing for your situation
If your ERP is uncommon in this market
Start with integration and let it filter the list. A platform with a proven connector to your finance system is worth more than a stronger feature set you will spend a year integrating.
If your sector has its own AP requirements
Most platforms in this category are horizontal, built to handle invoices in general rather than the particular shapes a sector produces. Construction and other project-based sectors have payment structures that standard AP tools often do not model. Manufacturing needs matching against goods receipt, with partial deliveries the norm. Retail runs high volumes of low-value invoices across many sites. Local government has statutory reporting and procurement rules that sit outside standard AP.
Ask any vendor to demonstrate your sector’s cases rather than a clean invoice, and ask how much of the fit comes from configuration rather than custom development.
If your problem is approval delay
Focus on approval configuration and mobile use, not capture accuracy. Late payment is usually caused by invoices sitting with approvers, not by slow data entry.
If your problem is payment risk
Prioritise supplier onboarding, register verification and bank detail validation. Treat capture as secondary.
If you are trying to control spend rather than process it
You need procurement, not AP automation. Be clear about this early, because the two are sold using similar language.
If you operate across several countries
Ask how the platform handles separate entities, foreign currency and local tax rules in each country you operate in. Test it with your own entity structure and tax codes, not a sample company.
Common mistakes
- Weighting capture accuracy heavily and integration lightly, when integration is what fails
- Comparing a headline licence cost without the ERP licences approvers will need
- Accepting a demonstration using the vendor’s sample invoices rather than your own
- Not asking who performs the implementation, or where
- Treating AP automation as a solution to a procurement problem
Where RapidP2P fits
RapidP2P is built for organisations in Australia and New Zealand whose approval structures, finance system or sector make generic AP tools a poor fit.
Customer results include:
- Twin Towns cut invoice processing time and costs by 80%.
- Sonic Healthcare cut manual keystrokes by up to 90% across 14 entities.
- Royal Flying Doctor Service cut invoice approvals from up to two weeks to one day.
- Moorabool Shire Council went live in six weeks, within budget.
It is not the right choice for everyone. If you are a small business that mainly needs approvals, a lighter tool will cost less. If sourcing and contract management are central to what you need today, look at an enterprise spend suite.
How we put this together
Vendor information is drawn from publicly available material, including vendor documentation and independent review sites. The vendor references in this guide reflect how each vendor positions itself and are a guide to the shape of the market, not a judgement on any product. We have not tested every platform ourselves, and capability varies by edition and configuration, so treat this as a starting point for your own evaluation rather than a substitute for it.
Disclosure: Efficiency Leaders builds RapidP2P, an Australian AP and procure-to-pay platform. We are named in this guide alongside other vendors.
Common questions
What does AP automation actually cost in Australia and New Zealand?
Most vendors price on a combination of platform fee and volume, quoted after scoping, so published figures are rare and rarely comparable. The more useful question is how the model behaves as you grow. The main cost drivers are invoice volume, the number of entities and finance systems, and how much of procure-to-pay is in scope. To compare like for like, ask each vendor to price the same volume and scope over three years.
What is the difference between AP automation and procure-to-pay?
AP automation starts when an invoice arrives. Procure-to-pay starts before the spend is committed, with a requisition and an approved purchase order. If the outcome you want is fewer surprises rather than faster processing, you are looking for the second.
Do I need Peppol e-invoicing support?
If you supply government in either country, increasingly yes. Australian Government agencies pay eligible e-invoices within five days, compared with 20 days for other invoices. In New Zealand, in-scope government agencies must send and receive e-invoices from 2026, and request them from large suppliers from 2027. More broadly it removes a scanning step for the suppliers that use it. Ask whether documents are received natively or converted.
What should New Zealand organisations check?
The same questions apply, plus three local ones: whether the platform validates suppliers’ NZBN and GST numbers, whether it receives Peppol invoices in the PINT A-NZ format shared by both countries, and whether it integrates with the finance systems you run in New Zealand.
How long does implementation take?
It depends far more on your approval complexity and ERP than on the platform. Ask any vendor for a comparable reference in your market rather than an average.
Can AP automation work with TechnologyOne or Civica Authority?
Yes, but the field is smaller than it looks. Both are common in Australian local government and the public sector, while many platforms marketed here are built primarily around Xero, MYOB, NetSuite or Dynamics. RapidP2P integrates with TechnologyOne, as do EzeScan and Xcellerate IT; Civica Authority is supported by fewer platforms again. Ask any vendor for a named reference running your ERP and version, because “supported” can mean anything from a maintained connector to a file export.
Will AI approve invoices without a person?
Some platforms now offer this. Whether it suits you depends on your control environment and your auditor. The question to ask is whether you can see and reconstruct the reasoning behind any automated decision.
Is a global platform better than a local one?
Not inherently. Global platforms generally offer broader multi-entity and multi-currency capability. Local platforms generally offer closer fit with local finance systems, local compliance and same-timezone support. The right answer depends on which of those you need.
What should I ask for in a demonstration?
Your own invoices, including the messy ones. Your own approval structure. A live look at the audit trail. And the exception queue, not just the happy path.
Where to start
If you take three things from this guide: confirm ERP fit first, because it disqualifies more platforms than any other criterion; ask to see a vendor’s exception queue rather than its accuracy claim; and price the whole thing, not the licence.
We publish this because we think the category is poorly served by feature lists. If you want a second opinion on a shortlist you have already drawn up — including one we are not on — we are happy to give it.
