An Australian business running MYOB and processing 100 supplier invoices a month is spending roughly $2,767 a month on the handling alone, if you take the A$27.67 per invoice figure that Australian AP guides are now quoting for manual processing. That number covers keying, chasing approvals, filing and reconciling. It does not include the cost of paying the same invoice twice, or paying a supplier whose bank details were changed by someone other than the supplier.
Against that, a full AP automation stack at the same volume typically lands between A$400 and A$800 per month. The arithmetic is not subtle. What is subtle is the build, because MYOB users cannot simply copy the Xero playbook. This is a walkthrough of the whole cycle — what each step looks like manually, what it looks like automated, where MYOB specifically gets in the way, and what a person still has to do at the end of it.
The seven steps, and where the time actually goes
End-to-end AP is not one task. Current Australian guidance breaks the full cycle into document capture, supplier validation including ABN verification, GL coding, two-way and three-way matching, approval routing, payment scheduling and sync back to the ledger. Older content treated AP automation as scan-and-approve. It is not, and if you buy on that basis you will automate the cheapest step and leave the expensive ones alone.
Capture. Today: invoices arrive in a shared inbox, as PDFs, as photos of dockets from site, occasionally as a printout in a ute. Someone opens each one and reads it. Automated: a dedicated AP inbox, plus a mobile capture path for field staff, feeds an extraction engine that pulls supplier, ABN, invoice number, date, totals, GST and — this is the part that matters — line items.
Supplier validation. Today: usually nothing, or a glance at whether the name looks familiar. Automated: the extracted ABN is checked, the supplier is matched against your MYOB card file, and any change to bank details on the invoice is flagged as an exception rather than accepted. Bank detail changes are the single control most worth building, because undetected changes are the mechanism behind most supplier payment fraud.
Coding. Today: the bookkeeper knows that anything from a given supplier goes to a given account, and codes it from memory. Automated: coding is proposed from supplier history and line-item text, with GST treatment applied per line. Line-level AI coding is now standard in the better tools, where 2020-era content assumed line coding was manual.
Matching. Today: if you raise purchase orders at all, someone opens the PO and eyeballs it against the invoice. Automated: two-way matching against the PO, three-way where you also capture a delivery docket or a site sign-off. Ocerra, one of the MYOB-listed apps, is described on MYOB's own app directory as providing document comparison and approval through two-way and three-way matching with tight MYOB integration.
Approval. Today: an email to whoever is meant to approve it, then a follow-up email, then a text. Automated: routed by an approval matrix — cost centre, amount threshold, delegated authority — with a record of who approved what and when.
Payment. Today: an ABA file built by hand, or individual payments in internet banking. Automated: a batch built from approved invoices only, with payment terms respected rather than everything paid on the day someone remembers.
Sync. Today: re-keying into MYOB, or an import that half works. Automated: the bill lands in MYOB coded, attached to its source document, with the approval trail intact.
The MYOB-specific gap, stated plainly
If you are on Xero, the well-trodden path is Dext for capture plus ApprovalMax for approvals, and it covers most requirements with gaps between the tools but functional coverage. MYOB users cannot follow it, for two specific reasons.
First, ApprovalMax does not support MYOB. It is priced at A$83 per month per organisation and is a Xero-oriented product. If you have read a comparison article recommending it and you run MYOB, that recommendation does not apply to you. Approval has to sit somewhere else.
Second, Dext pushes to MYOB one way. Current MYOB-focused analysis describes Dext supporting MYOB with a one-way push of extracted invoices — capture works, but feedback from MYOB back into the tool is limited. Dext starts from around A$21 per month and does the extraction job well. It is not an approval system and it does not close the loop.
That leaves MYOB users with three practical shapes. Buy a MYOB-native platform such as Ocerra or Pulsify, which offer bidirectional sync and line-level extraction. Buy Lightyear, listed in Australian comparisons at A$199 per month with a plan structure elsewhere shown as A$155 per month for 125 credits, with integration fees possible. Or use a capture tool for what it is good at and build the approval, validation and exception layer yourself around the MYOB API.
The third option is the one most people do not cost properly. It is genuinely viable — a workflow engine sitting between the capture tool, the MYOB API, your ABN lookups and your approvers gives you an approval matrix that matches your actual delegations rather than the vendor's model of them. This is exactly the shape of work we do when we build AP and approval workflows on n8n for businesses whose ledger is MYOB and whose approval rules do not fit an off-the-shelf product. It is not a weekend project, and anyone telling you it is has not built one.
What it costs, by volume
| Volume | Sensible shape | Indicative monthly |
|---|---|---|
| Under 20 invoices | MYOB native, manual entry and approvals | Nil beyond your MYOB subscription |
| 20–100 invoices | Capture plus a real approval and validation layer | A$200–A$500 |
| 100–500 invoices | Full platform with matching and exception handling | A$400–A$800 |
Other reference points from current Australian pricing tables: AutoEntry sits around A$33 per month at the base tier as a Dext alternative, priced per credit, with higher effective costs once line-item extraction is switched on; Airwallex's bill payment and AP functionality is listed in comparisons from roughly A$75 to A$99 per month depending on plan; and Tipalti starts at US$99 per month plus invoice, payment and usage fees — a US price, so budget the conversion and the variable fees on top. The pattern across all three is that the headline number is the floor, not the bill.
Add implementation to whichever line applies. Tier 2 and 3 stacks are measured in weeks, not the instant setup vendors imply.
What a person still does
Automation handles the happy path. Your AP person moves from data entry to three jobs.
They own the exception queue: invoices where extraction confidence is low, where the PO does not match, where the supplier is new, where bank details changed. That queue is the whole point. If it is empty every day, your thresholds are too loose.
They maintain supplier master data. Duplicate vendor cards, missing ABNs and stale bank details are the reason anomaly detection produces noise instead of signal, and cleaning them is routinely underestimated as a prerequisite rather than a nice-to-have.
They maintain the approval matrix. Who approves what, at which threshold, and who acts when that person is on leave. This changes as the business changes and nobody else will notice when it goes stale.
Failure modes worth designing against
Partial automation is the common failure. Capture without approvals gets invoices into MYOB faster and gets bad invoices into MYOB faster too. Approvals without validation means someone signs off a payment to a changed bank account with full confidence, because it looked normal. Both patterns show up when SMEs assemble the cheapest stack that technically works.
The specific things that go wrong at 20–100 invoices a month are informal approval chains, duplicate payments and undetected bank detail changes. Above 100, manual line coding stops being sustainable and PO matching becomes the bottleneck. Poor GST coding and unverified ABNs create an audit problem that surfaces months later, which is why GST coding and ABN verification are now advertised as differentiators rather than assumed.
One more: treat AI claims sceptically. At least one 2026 Australian guide rates tools on AI honesty and marks some as veneer where the claim does not map to real automation. Ask any vendor to process ten of your actual invoices, including the ugly ones, before you sign.
The first move
Pull last month's supplier invoices and count them. Then sort them into three piles: ones that arrived as clean PDFs from a regular supplier, ones that needed a phone call before anyone could code them, and ones that referenced a purchase order. Those three counts tell you your volume tier, your realistic exception rate, and whether matching is worth building at all. It is a genuinely useful hour, and it changes what you should buy.
From there, we will map your current AP cycle against the MYOB integration constraints, tell you whether a platform or a custom workflow layer is the better answer for your volume and approval structure, and give you a fixed scope with a build cost and a monthly run cost — including a straight answer if the honest recommendation is to stay manual for now. That is what an AP automation assessment delivers, and most builds of this shape run two to four weeks.