If you are running MYOB and searching for AP automation, you have probably noticed that most of the market pretends you do not exist.
The comparison guides rank platforms based on Xero integration. The demo videos show Xero dashboards. The case studies reference Xero clients. When MYOB is mentioned at all, it is listed under “other integrations” with no detail about what that integration actually does.
This is not because MYOB is a bad platform. It is because MYOB has a smaller share of the Australian cloud accounting market than Xero, and most AP automation vendors prioritised the bigger market first. Some never came back to finish the job.
For the thousands of Australian construction, wholesale, distribution, and manufacturing businesses that chose MYOB for its inventory module, job costing, or multi-currency capability, the result is a narrower set of AP automation options and a genuine risk of choosing a tool that either does not support MYOB at all or supports it so thinly that the integration creates more problems than it solves.
What MYOB’s native AP workflow does
MYOB handles bill entry, payment scheduling, and supplier management. For businesses with a small, stable supplier list and a single person managing AP, the native workflow is functional. Bills are entered manually or imported, coded to accounts, and scheduled for payment. The ledger stays accurate because the volume is low enough for manual review to catch errors.
MYOB AccountRight in particular offers job costing, inventory integration, and tracking categories that make it a strong fit for industrial businesses tracking costs across projects or departments. These features are part of why many construction and wholesale businesses chose MYOB in the first place and why switching to Xero solely for better AP automation options is rarely a practical decision.
The ATO’s record-keeping requirements apply regardless of which accounting platform you use. Every invoice needs to be recorded with the correct GST treatment, allocated to the right expense category, and retained for five years. MYOB handles the recording and retention. What it does not handle is the governance process that should happen before a bill reaches the ledger.
Where MYOB’s native AP falls short
The gaps are not unique to MYOB - Xero has the same ones. But MYOB users feel them more acutely because the automation tools that close these gaps for Xero users are often not available to them.
No approval routing by value or category. MYOB does not route a AU$60,000 subcontractor invoice to the CFO while letting a AU$200 office supply purchase go through on a single sign-off. Any user with bill entry access can create and approve at any amount. The delegation of authority structure exists in a policy document, not in the software.
No vendor bank detail validation. When a supplier’s bank account changes on an incoming invoice, MYOB does not flag the change. The bill is entered with whatever details are on the document. This is the mechanism behind payment redirection fraud, which cost Australian businesses AU$152.6 million in 2024 according to the ACCC.
No pre-entry duplicate detection. A duplicate invoice is only flagged if the reference number matches an existing entry exactly. A slightly altered reference or the same supplier-amount-date combination with a different invoice number passes through without a warning.
No automated coding from supplier history. Every bill needs to be coded manually. A bookkeeper entering 80 invoices per week from the same 30 suppliers makes the same coding decisions repeatedly, with no system-enforced consistency.
For a deeper comparison of what MYOB handles natively versus what requires an external layer, see MYOB Workflows vs External Automation Layers for Governance Control.
Why most AP automation tools skip MYOB
Three reasons, none of them flattering to the vendors.
Market share. Xero holds the majority of Australia’s cloud accounting market. A venture-funded AP automation startup building its first integration will choose Xero because it reaches the most potential customers. MYOB integration comes second, if it comes at all.
API complexity. MYOB’s API, particularly for AccountRight, has a different data model and authentication pattern than Xero’s. Building a deep, bidirectional integration with MYOB is a separate engineering effort, not a port of the Xero integration. Many vendors underestimate the work and either delay it indefinitely or ship a shallow version.
Two MYOB products, not one. MYOB AccountRight and MYOB Business are different platforms with different APIs and different capabilities. AccountRight offers a richer API with access to jobs, categories, and detailed tax codes. MYOB Business has a more limited API surface. A vendor that supports one does not automatically support the other, and communicating that distinction to customers is something most vendors avoid rather than address directly.
The practical consequence is that MYOB users evaluating AP automation need to ask pointed questions about integration depth, not just whether MYOB appears on the integrations page.
What to look for in MYOB-compatible AP automation
Not all MYOB integrations are equal. The differences that matter for an industrial business are specific.
Bidirectional sync, not one-way push
A one-way integration pushes approved invoices to MYOB. That is useful but limited. A bidirectional integration also pulls the chart of accounts, tracking categories, tax codes, jobs, and supplier list from MYOB into the AP platform. This means invoices can be coded inside the AP tool using the same structure as MYOB, and the coded bill lands in MYOB exactly as the bookkeeper would have entered it. Without the pull, coding happens in a vacuum and the bookkeeper has to verify every posted bill anyway.
Support for both AccountRight and MYOB Business
If your business runs AccountRight, confirm the platform integrates with AccountRight specifically, not just MYOB Business. The two products have different data models. Job costing and tracking categories in AccountRight need to sync into the AP platform for the coding to be accurate.
GST treatment at line level
Australian AP automation for MYOB needs to handle GST at the line-item level, not just apply a single tax code to the whole invoice. A construction subcontractor invoice with labour (GST-inclusive), imported materials (GST-free under Division 38), and equipment hire (GST-inclusive) needs three different treatments on three different lines. The AP tool should apply these from supplier history and flag exceptions rather than extracting whatever is on the PDF and hoping it is correct.
Approval routing that enforces your authority matrix
The AP platform should route invoices to different approvers based on dollar value, cost category, supplier type, or project - the controls that MYOB does not provide natively. This is the delegation of authority enforcement layer. If the platform only offers a single approval step, it is not solving the problem.
Publication to MYOB with full coding
When an invoice is approved, it should publish to MYOB as a complete bill: correct supplier, correct account codes on every line, correct GST treatment, correct tracking category or job allocation. The bookkeeper should not need to open the bill in MYOB and fix the coding after it arrives.
How Pulsify works with MYOB
Pulsify integrates bidirectionally with both Xero and MYOB. The MYOB integration is not a secondary feature. Both platforms receive the same depth of integration.
What Pulsify pulls from MYOB: chart of accounts, tracking categories, jobs (AccountRight), tax codes, and the full supplier list including ABN and bank details. This data is used to code invoices accurately before they reach an approver and to validate supplier details against historical records.
What Pulsify publishes to MYOB: approved bills with line-level account coding, GST treatment per line, tracking category allocation, and supplier assignment. The bill lands in MYOB ready for payment scheduling. No manual re-entry, no coding corrections.
What happens between pull and publish: invoices are captured from email or upload, extracted at line level, coded automatically from supplier history, validated for duplicate invoices and bank detail changes, and routed through a configurable approval workflow based on the business’s delegation of authority matrix. Exception flags are visible to the approver before they make a decision.
The workflow is the same whether the business runs Xero or MYOB. That matters because it means MYOB users are not getting a stripped-down version of a Xero product. They are getting the same controls layer.
Comparison: AP automation options for MYOB users
| Capability | MYOB native | Dext (MYOB) | ApprovalMax | Pulsify (MYOB) |
|---|---|---|---|---|
| MYOB integration | N/A | One-way push | No MYOB support | Bidirectional sync |
| Invoice capture and extraction | Manual entry | OCR extraction | No capture capability | OCR extraction at line level |
| Automated line-item coding | Manual | No | No | From supplier history |
| Approval routing by value | No | No | No (no MYOB integration) | Configurable thresholds |
| Vendor bank detail validation | No | No | No (no MYOB integration) | Automatic on every invoice |
| Duplicate detection at intake | Basic reference match | No | No (no MYOB integration) | Full duplicate check before approval |
| GST treatment at line level | Manual per line | Extracts from document | No (no MYOB integration) | Applied from supplier history |
| Audit trail | MYOB activity log | Extraction log only | No (no MYOB integration) | Full trail: capture through approval |
The table makes the gap visible. For MYOB users, the most commonly recommended AP automation stack - Dext plus ApprovalMax - does not actually work. ApprovalMax does not integrate with MYOB. Dext handles extraction and push, but the validation, coding, and approval layers that make AP automation worth the investment are missing.
The cost of staying manual
MYOB users who cannot find automation tools that support their platform tend to default to manual processes longer than Xero users do. The consequence is predictable: more time spent on data entry, more coding errors that surface at BAS time, more exposure to duplicate invoices and payment redirection fraud, and more month-end pressure on a finance team that is already under-resourced.
A financial controller at a wholesale distributor processing 100 invoices per week in MYOB is doing the same repetitive coding work that a Xero user automated two years ago. The work is not harder because of MYOB. It is harder because the tools that automate it were not built for MYOB.
That gap is closing. But it is closing slowly, and MYOB users need to evaluate what is actually available today rather than what is promised on a roadmap.
What to ask in a demo
If you are evaluating AP automation as a MYOB user, these questions will surface the real integration depth:
- Does your platform integrate with MYOB AccountRight, MYOB Business, or both?
- Is the integration bidirectional? What data does the platform pull from MYOB, and what does it publish back?
- Can I see a live demo with a MYOB connection, not a Xero one?
- How does automated coding work with MYOB’s tracking categories and jobs?
- What happens when a supplier’s bank details change between invoices? Show me the flag.
- How long has the MYOB integration been in production, and how many MYOB customers are currently using it?
If the vendor cannot show you a working MYOB integration in the demo, that tells you where MYOB sits in their priorities.
Sources: ATO - Record-keeping requirements for business · ACCC - Targeting Scams Report 2024 · MYOB - Accounting Software
Further reading: MYOB Workflows vs External Automation Layers for Governance Control · Designing a Delegation of Authority Structure Inside MYOB Step by Step · Best AP Automation Software Australia 2026