A 300-invoice-a-month Australian business running Xero can get supplier invoices captured, coded, approved and into a payment file for somewhere between A$200 and A$500 a month in software. That is the whole answer to the pricing question, and it is worth stating up front because most Australian SMBs land in exactly that band once they combine a capture tool with an approvals tool. What that spend buys is roughly this: the person who currently opens the AP inbox, types bills into Xero, chases a manager for sign-off and then re-keys the payment into the bank stops doing three of those four things.
The fourth is where the money actually leaks, and it is the part most articles skip. Below is the process end to end, with what each step costs, what stays with a human, and the four specific ways it goes wrong.
The stack, priced in AUD
| Layer | Tool | Current AUD pricing |
|---|---|---|
| Capture and coding | EzzyBills | Annual document quota: Light A$132/yr, Standard A$297/yr, Premium A$605/yr, E10 A$1,210/yr, GST inclusive |
| Capture and coding | Lightyear | Credit-based monthly: Essentials 125 credits A$155/mo, Standard 250 credits A$255/mo, Professional 500+ credits custom |
| Approvals and matching | ApprovalMax | Moved to usage-based tiers from August 2026, sized by number of approvers and documents per month |
| Payment execution | Bank ABA file, BPAY, PayID | No licence cost, but transaction and FX costs apply |
Three things about that table matter more than the numbers themselves.
First, the pricing models are not comparable. EzzyBills sells you an annual document quota; at 300 invoices a month you are buying roughly 3,600 documents a year, which puts you in its upper tiers rather than the entry plan. Lightyear sells monthly credits where one exported invoice equals one credit, so 300 invoices sits just above its 250-credit Standard plan and pushes you into custom Professional pricing. Neither is expensive. But a quote built on the entry tier will be wrong by a factor of three by the time you go live.
Second, ApprovalMax pricing published anywhere other than ApprovalMax is now unreliable. Third-party directories still list flat starting rates around A$65 a month, and an Australian reseller tear sheet from early 2025 lists Standard at $59/month inc GST, Advanced at $95 and Premium at $133. Those describe the old per-organisation model. New customers in Australia, New Zealand and the UK now start on the tiered usage-based model immediately, and ApprovalMax Capture, which used to be a paid add-on, is included across all plans at no extra charge. That last change quietly makes the "capture tool plus approvals tool" stack redundant for some businesses.
Third, the payment layer has no licence line and is where the real cost sits.
Walking the process
Invoice arrives. Supplier emails a PDF to a dedicated AP address. The capture tool ingests it directly. No human touches it.
Extraction and coding. Current Australian tooling pulls supplier, ABN, invoice number, amounts, GST and line items, then creates a draft bill in Xero with the correct GST codes, tracking categories and PO references. This is genuinely solved for standard supplier invoices. It is not solved for handwritten dockets, multi-page statements, or the subcontractor who sends a photo of a photo.
Approval routing. The draft bill routes by rule: amount threshold, cost centre, tracking code, project. The approver gets a notification, sees the invoice image next to the coding, and approves or rejects on a phone. This is the step that most often removes the largest amount of elapsed time — not staff hours, elapsed days.
Matching. Purchase order to invoice to receipt. This is where automation earns its keep in construction, trades and anything with materials. It is also where it is hardest to configure, because three-way matching only works if purchase orders are actually raised in the first place.
Payment. The approved bill sits in Xero awaiting payment. Someone exports an ABA file, uploads it to the bank portal, authorises it, and marks the bills paid. Or pays each one by BPAY.
Reconciliation. Bank feed matches the payment back against the bill.
Steps one through four are automated and cheap. Step five is where the process usually breaks back into manual work.
Capture is now the commodity; approvals and payment are the value
The 2019-era pitch for AP automation was "stop typing invoices into Xero". That problem is now solved by tools costing A$132 a year at the low end. If your business case rests entirely on saving keystrokes, the numbers will be underwhelming at 300 invoices a month.
The defensible business case is elapsed time and control. An invoice that takes eleven days to get approved because it is sitting in a manager's inbox costs you early-payment discounts, supplier goodwill and month-end accuracy. A payment run assembled by hand from a Xero report costs you duplicate payments and the occasional wrong BSB. Australian guides recommend that SMEs calculate their current cost per invoice and document how long each step takes from receipt to payment before selecting anything, and the cycle-time number is almost always the one that moves.
The four ways this fails
Dirty supplier master
One Australian AP guide puts it bluntly: every AP automation project fails the same way if the supplier master is dirty — duplicate suppliers, missing ABNs, inconsistent naming. Automated coding relies on matching an incoming invoice to a known supplier record. If you have "ABC Plumbing", "ABC Plumbing Pty Ltd" and "ABC Plumbing (new)" in Xero, the tool will confidently code to the wrong one and your GL will drift. This is the highest-leverage work in the whole project and it happens before any software is switched on.
A second inbox
Invoices arriving through scattered personal inboxes are the second failure mode. If half your suppliers still email the site manager directly, the AP tool becomes a second inbox rather than a control layer and you now run two processes instead of one. Fixing this is a supplier communication exercise and an internal policy decision, not a configuration setting.
Weak extraction
Australian AP consultancies list poor extraction software and missing key field capture as a primary pitfall: if the tool does not reliably capture amounts, tax and required references, you have added a review step rather than removed a typing step. Test extraction on your ugliest twenty suppliers during the trial, not your cleanest five. Lightyear publishes a 30-day trial; with EzzyBills, ask for the trial terms in writing before you commit to an annual document quota, because the quota is the thing you are locking in.
The pay-out gap
This is the one that survives an otherwise successful rollout. Invoice intake is automated, approvals are clean, and then payment execution still happens by hand in a bank portal — the pay-out gap, which reintroduces duplicate manual work and, on international supplier payments, bleeds 2 to 3 per cent per transaction in hidden FX costs. For a business paying A$40,000 a month to overseas suppliers, that is around A$1,000 monthly, several times the entire software spend.
Closing it means either moving to a platform that pays through BPAY, PayID or bank transfer and syncs back to the accounting system, or building the payment file generation, authorisation checkpoint and reconciliation write-back yourself. That second path is where n8n workflows that sit between Xero, the approvals tool and the bank do real work: batching approved bills into an ABA file on a schedule, checking supplier bank details against the last payment made to that supplier, and flagging anything that changed.
What stays with a person, permanently
Exception handling. Supplier onboarding and bank detail verification. Final payment authorisation. Anything involving a dispute. Do not scope these out — the businesses that get burned are the ones that automated the release of funds along with everything else.
Before you buy anything
Export twelve months of bills from Xero, sort by supplier name, and count how many distinct records refer to the same legal entity. Then count how many of last month's invoices arrived somewhere other than the AP inbox. Those two numbers tell you more about whether an automation project will succeed than any vendor demo. Cost, expertise, data security and integration risk are the four barriers Australian businesses cite most, and the first two are addressed by knowing your own data before you shop. On data residency, it is worth confirming where the vendor stores AP records and whether backups stay onshore, given Notifiable Data Breach obligations and cross-border transfer expectations.
If you would rather have the answer than the exercise, IOTAI will map your current invoice-to-payment flow, price the stack against your actual monthly volume and supplier mix, and tell you what the pay-out gap is costing you in FX and rework — including a straight answer if the honest conclusion is that off-the-shelf capture plus approvals is all you need and there is nothing for us to build. Start with the payback numbers for your invoice volume, and we will scope the build from there.